Erro : (COMM_FAILURE) Help

2 respostas
T

Olá colegas,

Estou com o problema (report abaixo) já faz algum tempo e até agora não consegui encontrar o motivo, esse erro não acontece com frequencia, para resolver o problema basta eu fechar e abrir novamente o client e fica tudo ok. Alguem pode me ajudar ? muito obrigado.

Jul 24, 2009 1:53:52 AM com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl waitForResponse

WARNING: "IOP00410219: (COMM_FAILURE) Communications timeout waiting for response.  Exceeded 1,800,000 milliseconds"

org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3180)

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3195)

at com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl.waitForResponse(CorbaResponseWaitingRoomImpl.java:198)

at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.waitForResponse(SocketOrChannelConnectionImpl.java:1196)

at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.waitForResponse(CorbaMessageMediatorImpl.java:291)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:389)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:357)

at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:219)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:192)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)

at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)

at com.sun.enterprise.naming._SerialContextProvider_DynamicStub.lookup(com/sun/enterprise/naming/_SerialContextProvider_DynamicStub.java)

at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at br.com.rtkomp.util.FactoryConn.getObjeto(FactoryConn.java:33)

at br.com.rtkomp.business.Autorization.getResponseConsultaQuitacao(Autorization.java:120)

at br.com.rtkomp.server.ServerListener.process(ServerListener.java:54)

at org.jpos.iso.ISOServer$Session.run(ISOServer.java:126)

at org.jpos.util.ThreadPool$PooledThread.run(ThreadPool.java:100)

Jul 24, 2009 1:53:52 AM com.sun.enterprise.naming.SerialContext lookup

SEVERE: NAM0004: Exception during name lookup : {0}

java.rmi.MarshalException: CORBA COMM_FAILURE [telefone removido] Maybe; nested exception is:

org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:271)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)

at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)

at com.sun.enterprise.naming._SerialContextProvider_DynamicStub.lookup(com/sun/enterprise/naming/_SerialContextProvider_DynamicStub.java)

at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at br.com.rtkomp.util.FactoryConn.getObjeto(FactoryConn.java:33)

at br.com.rtkomp.business.Autorization.getResponseConsultaQuitacao(Autorization.java:120)

at br.com.rtkomp.server.ServerListener.process(ServerListener.java:54)

at org.jpos.iso.ISOServer$Session.run(ISOServer.java:126)

at org.jpos.util.ThreadPool$PooledThread.run(ThreadPool.java:100)

Caused by: org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3180)

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3195)

at com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl.waitForResponse(CorbaResponseWaitingRoomImpl.java:198)

at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.waitForResponse(SocketOrChannelConnectionImpl.java:1196)

at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.waitForResponse(CorbaMessageMediatorImpl.java:291)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:389)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:357)

at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:219)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:192)

 10 more

Jul 24, 2009 1:54:11 AM com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl waitForResponse

WARNING: "IOP00410219: (COMM_FAILURE) Communications timeout waiting for response.  Exceeded 1,800,000 milliseconds"

org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3180)

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3195)

at com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl.waitForResponse(CorbaResponseWaitingRoomImpl.java:198)

at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.waitForResponse(SocketOrChannelConnectionImpl.java:1196)

at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.waitForResponse(CorbaMessageMediatorImpl.java:291)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:389)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:357)

at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:219)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:192)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)

at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)

at com.sun.enterprise.naming._SerialContextProvider_DynamicStub.lookup(com/sun/enterprise/naming/_SerialContextProvider_DynamicStub.java)

at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at br.com.rtkomp.util.FactoryConn.getObjeto(FactoryConn.java:33)

at br.com.rtkomp.business.Autorization.getResponseConsultaAdiantamento(Autorization.java:51)

at br.com.rtkomp.server.ServerListener.process(ServerListener.java:50)

at org.jpos.iso.ISOServer$Session.run(ISOServer.java:126)

at org.jpos.util.ThreadPool$PooledThread.run(ThreadPool.java:100)

Jul 24, 2009 1:54:11 AM com.sun.enterprise.naming.SerialContext lookup

SEVERE: NAM0004: Exception during name lookup : {0}

java.rmi.MarshalException: CORBA COMM_FAILURE [telefone removido] Maybe; nested exception is:

org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.javax.rmi.CORBA.Util.mapSystemException(Util.java:271)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:205)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.invoke(StubInvocationHandlerImpl.java:152)

at com.sun.corba.ee.impl.presentation.rmi.bcel.BCELStubBase.invoke(BCELStubBase.java:225)

at com.sun.enterprise.naming._SerialContextProvider_DynamicStub.lookup(com/sun/enterprise/naming/_SerialContextProvider_DynamicStub.java)

at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:398)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at br.com.rtkomp.util.FactoryConn.getObjeto(FactoryConn.java:33)

at br.com.rtkomp.business.Autorization.getResponseConsultaAdiantamento(Autorization.java:51)

at br.com.rtkomp.server.ServerListener.process(ServerListener.java:50)

at org.jpos.iso.ISOServer$Session.run(ISOServer.java:126)

at org.jpos.util.ThreadPool$PooledThread.run(ThreadPool.java:100)

Caused by: org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 219 completed: Maybe

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3180)

at com.sun.corba.ee.impl.logging.ORBUtilSystemException.communicationsTimeoutWaitingForResponse(ORBUtilSystemException.java:3195)

at com.sun.corba.ee.impl.transport.CorbaResponseWaitingRoomImpl.waitForResponse(CorbaResponseWaitingRoomImpl.java:198)

at com.sun.corba.ee.impl.transport.SocketOrChannelConnectionImpl.waitForResponse(SocketOrChannelConnectionImpl.java:1196)

at com.sun.corba.ee.impl.protocol.CorbaMessageMediatorImpl.waitForResponse(CorbaMessageMediatorImpl.java:291)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete1(CorbaClientRequestDispatcherImpl.java:389)

at com.sun.corba.ee.impl.protocol.CorbaClientRequestDispatcherImpl.marshalingComplete(CorbaClientRequestDispatcherImpl.java:357)

at com.sun.corba.ee.impl.protocol.CorbaClientDelegateImpl.invoke(CorbaClientDelegateImpl.java:219)

at com.sun.corba.ee.impl.presentation.rmi.StubInvocationHandlerImpl.privateInvoke(StubInvocationHandlerImpl.java:192)

 10 more

2 Respostas

Tchello

Pelo que eu entendi ta dando TimeOut na comunicação dos dispositivos (sockets, etc).
Isso pode acontecer quando esse canal(conexão, etc) fica muito tempo “sem ser utilizado”, dai ele fecha.
Posso estar errado, mas começaria pesquisando por isso.
Abraços!

T

Bom, pode até ser, mas assim, pelo que vi nos logs o ejb não ficou nem 15min sem utilização…Existem 2 EARs distintos lá e em outro servidor 2 appClient distintos também, e só 1 appClient perdeu a conexão e eu tive que reinicia-lopara voltar.

Entre os EARs eu notei uma diferença, o EAR que ficou “fora do ar” estava sem o @TransactionMAnager(CONTAINER) nos SessionsBeans e o que ficou no ar estava com o @TransactionMAnager(CONTAINER)…E todas as vezes que aconteceu esse problema foi somente no que está sem o @TransactionMAnager(CONTAINER). Será que isso tem ligação?

obrigado.

Criado 24 de julho de 2009
Ultima resposta 24 de jul. de 2009
Respostas 2
Participantes 2