2014-10-30 1 views
-2

javax.naming.NamingException : 지정된 호스트에 연결할 수 없습니다 : Connection refused : connect [루트 예외 org.omg.CORBA.COMM_FAILURE : 연결이 거부되었습니다 : vmcid 연결 : 0x0 부 번호 : 0 완료 : 아니요] weblogic.corba.j2ee.naming.Utils.wrapNamingException (Utils.java:83) at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry (ORBHelper.java:656) at weblogic.corba.j2ee.naming.ORBHelper 로직에서 weblogic.factories.iiop.iiopEnvironmentFactory.getInitialContext (iiopEnvironmentFactory.java:33) 에서 weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext (InitialContextFactoryImpl.java:85) 에서 .getORBReference (ORBHelper.java:594) .factories.iiop.iiopEnvironmentFactory.get InitialContext (iiopEnvironmentFactory.java:71) at weblogic.jndi.Environment.getContext (Environment.java:315) at weblogic.jndi.Environment.getContext (Environment.java:285) at weblogic.jndi.WLInitialContextFactory.getInitialContext getInitialContext (NamingManager.java:667) 에서, javax.naming.InitialContext.getDefaultInitCtx (InitialContext.java:288)에서 at javax.naming.InitialContext.init (javax.naming.InitialContext에서 InitialContext.java:223) . (InitialContext.java:197) Utils.RequestProcessor.AuthorisationRequestProcessor.LookUp (AuthorisationRequestProcessor.java:75에서 ) Utils.RequestProcessor.AuthorisationRequestProcessor.chec에서 kUser (AuthorisationRequestProcessor.java:155) Utils.RequestProcessor.AuthorisationRequestProcessor.processPreprocess (AuthorisationRequestProcessor.java:243)에서 org.apache.struts.action.RequestProcessor.process (RequestProcessor.java:173)에서 org.apache에서 . struts.action.ActionServlet.process (ActionServlet.java:1913) at org.apache.struts.action.ActionServlet.doPost (ActionServlet.java:462) at javax.servlet.http.HttpServlet.service (HttpServlet.java : weblogic.servlet.internal.StubSecurityHelper $ ServletServiceAction.run (StubSecurityHelper.java:227) weblogic.servlet.internal.StubSecurityHelper에서 에서 javax.servlet.http.HttpServlet.service (HttpServlet.java:820) 에서 727) . invokeServlet (StubSecurityHelper.java:125) 에서 weblogic.servlet.internal.ServletStubImpl.execute (ServletStubImpl.java:301) weblogic.servlet.internal.TailFilter.doFilter (TailFilter.java:26) 에서 weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl. 자바 : weblogic.servlet.internal.FilterChainImpl.doFilter (FilterChainImpl.java:56) 에서 org.ajaxanywhere.AAFilter.doFilter (AAFilter.java:46) 56) weblogic.servlet.internal.WebAppServletContext $ ServletInvocationAction에서. wrapRun (WebAppServletContext.java:3730) weblogic.servlet.internal.WebAppServletContext $ ServletInvocationAction.run (WebAppServletContext.java:3696) weblogic.security.acl.internal.AuthenticatedSubject.doAs (AuthenticatedSubject.java:321)에서 에서 에서 weblogic.security.service.Securit yManager.runAs (SecurityManager.java:120) weblogic.servlet.internal.WebAppServletContext.securedExecute (WebAppServletContext.java:2273)에서 weblogic.servlet.internal.WebAppServletContext.execute (WebAppServletContext.java:2179)에서 로직에 . weblogic.work.ExecuteThread.run (ExecuteThread.java:221) 에서 servlet.internal.ServletRequestImpl.run weblogic.work.ExecuteThread.execute (ExecuteThread.java:256)에서 (ServletRequestImpl.java:1490) 의해 발생 : org.omg.CORBA.COMM_FAILURE : 연결 거부 : vmcid 연결 : 0x0 부 번호 : 0 완료 : 아니요 weblogic.iiop.Utils.mapToCORBAException (Utils.java : 886) at weblogic.iiop.IORManager.locateNameService (IORManager.java:213) at weblogic.iiop.IORManager.createInitialReference (IORManager.java:123) at weblogic.corba.orb.ORB.string_to_object (ORB. 자바 : weblogic.corba.orb.ORB.resolve_initial_references (ORB.java:235 341) ) weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry에서 (ORBHelper.java:631)이org.omg.CORBA.COMM_FAILURE가하는 일 : Connection refused : connect vmcid : 0x0 minor code : 0 completed : 의미가 없습니까?

+1

Google에 게시 했습니까? 이 질문은 몇 번 질문되었습니다 : http://stackoverflow.com/questions/13017782/issues-with-corba-communication http://stackoverflow.com/questions/2633790/error-when-trying-to-connect- to-jacorb-naming-service –

답변

0

뜻 그 클라이언트가 서버에 연결할 수 없습니다. 귀하의 경우, 네이밍 서비스가 실행되고 있지 않은 것 같습니다.

관련 문제