This content has been marked as final.
Show 4 replies
-
1. Re: Where did my messages (sent by a SessionBean) go?
clebert.suconic Apr 5, 2007 11:25 AM (in response to tonylmai)You could enable tracing on org.jboss.jms and org.jboss.messaging at log4j and look at what happens after your method invocation.
-
2. Re: Where did my messages (sent by a SessionBean) go?
tonylmai Apr 5, 2007 6:01 PM (in response to tonylmai)Here is the trace. I don't see confirmation that a message had been sent.
2007-04-05 14:52:34,375 DEBUG [org.jboss.jms.message.MessageIdGeneratorFactory] checked out MessageIdGenerator for 0, reference count is 5
2007-04-05 14:52:34,375 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] ConnectionEndpoint[45] creating non transacted session, AUTO_ACKNOWLEDGE, non XA
2007-04-05 14:52:34,375 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] created and registered SessionEndpoint[46]
2007-04-05 14:52:34,375 DEBUG [org.jboss.jms.server.endpoint.ServerConnectionEndpoint] created SessionDelegate[16030232, ID=46]
2007-04-05 14:52:34,484 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@1fecaeb, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@f631d8{ url=null ,addedOrder=0}
2007-04-05 14:53:28,859 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for td-private, using default security config
2007-04-05 14:53:28,859 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] accepted: Socket[addr=/192.168.1.101,port=3875,localport=2705]
2007-04-05 14:53:28,875 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SecondaryServerSocketThread: transferred socket: 5c4o12t-xx5l00-f05qv1bb-1-f05qv1z6-7
2007-04-05 14:53:28,875 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] found socket: Socket[addr=/192.168.1.101,port=3875,localport=2705]
2007-04-05 14:53:29,046 DEBUG [org.jboss.mx.loading.RepositoryClassLoader] setRepository, repository=org.jboss.mx.loading.HeirarchicalLoaderRepository3@1fecaeb, cl=org.jboss.mx.loading.HeirarchicalLoaderRepository3$CacheClassLoader@1d82219{ url=null ,addedOrder=0}
That was the end of the log. Hope it makes sense to you. Thanks for your help. -
3. Re: Where did my messages (sent by a SessionBean) go?
tonylmai Apr 5, 2007 6:06 PM (in response to tonylmai)Here is a log for a successful sent and received.
2007-04-05 15:02:27,734 DEBUG [org.jboss.jms.server.security.SecurityMetadataStore] No SecurityMetadadata was available for td-private, using default security config
2007-04-05 15:02:27,734 DEBUG [org.jboss.remoting.transport.socket.SocketWrapper] ClientSocketWrapper[Socket[addr=/192.168.1.101,port=3875,localport=2705].178de07] closing
2007-04-05 15:02:27,734 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] accepted: Socket[addr=/192.168.1.101,port=3903,localport=2705]
2007-04-05 15:02:27,734 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] SecondaryServerSocketThread: transferred socket: 5c4o12t-xx5l00-f05qv1bb-1-f05qv1z6-7
2007-04-05 15:02:27,734 DEBUG [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] found socket: Socket[addr=/192.168.1.101,port=3903,localport=2705]
As you can see, there was confirmation that the client indeed had received the message.
This message was sent by the remote test app. The previous log was for the SessionBean resided within the server sending the message to an external client.
Thanks -
4. Re: Where did my messages (sent by a SessionBean) go?
tonylmai Apr 5, 2007 8:39 PM (in response to tonylmai)There was a transient field in my message class that was changed for testing and we forgot to put it back to transient status. Hence the message object was not serializable.
It would have been nice if JBoss Messaging would display an message or throw an exception instead of silently swallowed the error and not route the message to its destination.