[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Howard, Here's another error for you. This ones a little different to the others but happens occasionally. | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.ServerInvoker] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) ServerInvoker (SocketServerInvoker[172.16.113.22:1241677967]) added client callback handler CallbackManager[15d09a2] with session id of 4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow and callback handle object of null. | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.InvokerRegistry] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) removed org.jboss.remoting.transport.local.localclientinvo...@bccf2c from registry | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) Session id for callback handler is 4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] using callbackTimeout value 1 | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[jbdevapp2:4457] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) DefaultCallbackErrorHandler[SocketServerInvoker[jbdevapp2:4457]] setting callback handler to ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) adding callback handler ServerInvokerCallbackHandler[4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot+4sg35m-rs9red-fxcbs2e1-1-fxcvn6b3-20ow] | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) found calllback handler for remoting session ...-fxcvn6ar-20ot UID=4sg35m-rs9red-fxcbs2e1-1-fxcvn6ar-20ot | 2009-07-20 08:30:22,001 DEBUG [org.jboss.jms.server.connectionmanager.SimpleConnectionManager] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) registered connection ConnectionEndpoint[zo02-5b6nvcxf-1-1e2sbcxf-der9sr-m53gs4] as ...-fxcvn6ar-20ot | 2009-07-20 08:30:22,002 DEBUG [org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) No SecurityMetadadata was available for phaseQueueToHandler, using default security config | 2009-07-20 08:30:22,013 DEBUG [org.jboss.remoting.Client] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) starting callback Connector: InvokerLocator [bisocket://172.16.113.22:640465832/callback?callbackServerHost=172.16.113.22&callbackServerPort=640465832&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=4sg35m-rs9red-fxcbs2e1-1-fxcvn6bh-20p3&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] | 2009-07-20 08:30:22,017 DEBUG [org.jboss.remoting.ServerInvoker] (Thread-301) ServerInvoker (SocketServerInvoker[172.16.113.22:1340483958]) removing client callback handler with session id of 4sg35m-rs9red-fxcbs2e1-1-fxcvklqp-20gk+4sg35m-rs9red-fxcbs2e1-1-fxcvkq01-20gn. | 2009-07-20 08:30:22,020 DEBUG [org.jboss.remoting.ServerInvoker] (EJB-Timer-1248041699774[target=jboss.j2ee:ear=phase-engine.ear,jar=phase-engine.jar,name=DestBridgeCheckTimerBean,service=EJB3]) SocketServerInvoker[172.16.113.22:640465832] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory. | 2009-0
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Sorry I haven't got time to go further with your log, I'll hopeuflly come back soon. On a glimpse at the info I think it showed some network problem. Thanks! Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244634#4244634 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4244634 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hi, Thanks for the good info, I'll investigate. Howard View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241136#4241136 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241136 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hey Howard, Got a little further on figuring this out. What I did is write a keep alive generator for the bridges so I could monitor them. Each bridge has a timer bean which send a message across the bridge at 10 second interval. Unfortunately this did not stop the bridges from failing but did let me highlight the point where the bridge went down. | 2009-06-30 06:40:15,015 ERROR [org.jboss.remoting.transport.socket.ServerThread](WorkerThread#2[172.16.113.11:65011]) WorkerThread#2[172.16.113.11:65011] exception occurred during first invocation | | 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) Exception in thread "Timer-3" | 2009-06-30 06:42:48,530 ERROR [STDERR] (Timer-3) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 06:42:48,531 ERROR [STDERR] (Timer-3)at java.util.TimerThread.run(Unknown Source) | 2009-06-30 06:44:43,967 ERROR [STDERR] (Timer-12) Exception in thread "Timer-12" | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 06:44:43,968 ERROR [STDERR] (Timer-12) at java.util.TimerThread.run(Unknown Source) | 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) Exception in thread "Timer-15" | 2009-06-30 07:03:06,112 ERROR [STDERR] (Timer-15) java.lang.IllegalStateException: org.jboss.remoting.ConnectionValidator.run() should not be called directly; use org.jboss.remoting.ConnectionValidator.addConnectionListener() instead. | | 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:289) | | 2009-06-30 07:03:06,226 ERROR [STDERR] (Timer-15) at java.util.TimerThread.mainLoop(Unknown Source) | 2009-06-30 07:03:06,227 ERROR [STDERR] (Timer-15) at java.util.TimerThread.run(Unknown Source) | 2009-06-30 07:04:33,427 ERROR [org.jboss.jms.server.bridge.Bridge] (Thread-281) Failed to start source connection | Hopefully this will give you enough info to help pinpoint where the error occurs. If you have any ideas for further tests let me know. Cheers, R. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241122#4241122 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4241122 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Sorry about the delay in getting back to you. Here's the log from the box1, after the idle time. It seems that the remoting session etc. is found. Spot anything interesting? The second log extract is from box2 when I try to redeploy one of the bridges. | 2009-06-19 09:43:40,373 DEBUG [org.jboss.remoting.Client] (http-0.0.0.0-8080-1) starting callback Connector: InvokerLocator [bisocket://172.16.113.11:871825415/callback?callbackServerHost=172.16.113.11&callbackServerPort=871825415&callbackServerProtocol=bisocket&clientMaxPoolSize=1&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&datatype=jms&guid=4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jq&isCallbackServer=true&onewayThreadPool=org.jboss.jms.server.remoting.DirectThreadPool&serverSocketClass=org.jboss.jms.server.remoting.ServerSocketWrapper] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] did not find server socket factory configuration as mbean service or classname. Creating default server socket factory. | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] created server socket factory javax.net.defaultserversocketfact...@87bf5 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] setting pingFrequency to 214748364 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.bisocket.BisocketServerInvoker] (http-0.0.0.0-8080-1) SocketServerInvoker[172.16.113.11:871825415] setting pingWindowFactor to 10 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.transport.Connector] (http-0.0.0.0-8080-1) org.jboss.remoting.transport.connec...@1117568 started | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.ServerInvoker] (http-0.0.0.0-8080-1) ServerInvoker (SocketServerInvoker[172.16.113.11:871825415]) added client callback handler CallbackManager[12d3d44] with session id of 4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr and callback handle object of null. | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.InvokerRegistry] (http-0.0.0.0-8080-1) removed org.jboss.remoting.transport.local.localclientinvo...@1e3ba17 from registry | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-1) Session id for callback handler is 4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.ServerInvokerCallbackHandler] (http-0.0.0.0-8080-1) ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr] using callbackTimeout value 1 | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-1) DefaultCallbackErrorHandler[UNITIALIZED] setting server invoker to SocketServerInvoker[jbdevapp1:4457] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.remoting.callback.DefaultCallbackErrorHandler] (http-0.0.0.0-8080-1) DefaultCallbackErrorHandler[SocketServerInvoker[jbdevapp1:4457]] setting callback handler to ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr] | 2009-06-19 09:43:40,385 DEBUG [org.jboss.jms.server.remoting.JMSServerInvocationHandler] (http-0.0.0.0-8080-1) adding callback handler ServerInvokerCallbackHandler[4sg35b-wu44bh-fw3t9ply-1-fw4nm1g4-jo+4sg35b-wu44bh-fw3t9ply-1-fw4nm1gh-jr]
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Thank's fine, waiting for your result. Thanks. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237774#4237774 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237774 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Ok so if I have this to trace: | | | | | | | | I havn't added security as I think it's under the jms package. If it's something else just post the package name for me and I'll add it in. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237705#4237705 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237705 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hi I think turn on security trace is a good idea, and it would be better if you also trace the remoting logs. Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237673#4237673 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237673 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
I have tested all cases and the only way to recover from these errors is to restart both boxes. I will write a keep alive packet running from a timer and see does it fix the issue. I have added the following to jboss-log4j.xml. Howard, should this be sufficient to see further into the "User null is NOT authenticated" error? Or do I need to trace other packages as well? Maybe security too? | | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237670#4237670 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237670 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
hi, I do have two physical machines setup for the test and my jms-ds.xml is quite the equivalent to yours. To get more log, you can modify the jboss-log4j.xml under /conf dir in your JBOSS_HOME/server/ Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237532#4237532 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237532 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Another point, I ran the same test again. But this time I tried to re-deploy the bridges on box2 (before trying anything else). Strange thing is I get exactly the same errors as if I restarted box1. So now I restart box2, but still the same errors. The "User null is NOT authenticated" error seems to be a coverall for many different types of error. Is there anyway to see the logging at a finer grain to try and find out why this error is being thrown. Tomorrow I will try restarting box1 after idle before I try to send 100 messages. And the following day I will do the same but restart box 2. The only situation I've found so far that fixes the issue is to completely restart both jboss instances. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237488#4237488 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237488 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Howard, Are you running the bridge across two physically different boxes? I have the default JMS Provider (localhost) and a remote JMS Provider to a separate box with a different IP Address. If your remote provider is also localhost you might not see the issue. Here are my JMS providers (jms-ds.xml): | | | | | | | | | | | DefaultJMSProvider | org.jboss.jms.jndi.JNDIProviderAdapter | java:/XAConnectionFactory | java:/XAConnectionFactory | java:/XAConnectionFactory | | | | RemoteJMSProvider | | org.jboss.jms.jndi.JNDIProviderAdapter | | /XAConnectionFactory | /XAConnectionFactory | /XAConnectionFactory | | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces | java.naming.provider.url=jnp://jbdevapp1:1099 | | | | | | JmsXA | | jms-ra.rar | org.jboss.resource.adapter.jms.JmsConnectionFactory | javax.jms.Topic | java:/DefaultJMSProvider | 20 | JmsXARealm | jboss.messaging:service=ServerPeer | | | | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237486#4237486 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237486 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hi, Just tried with 5.1.0.GA (JBM is the same as Beta). Bridge server has been deployed for over 19 hours without sending any messages. Then I tried to send messages and the bridge works normally. Do you have any opinions on how to reproduce it? Thanks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237223#4237223 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237223 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
[jboss-user] [JBoss Messaging] - Re: Serious idle problem with Bridges on AS 5.1.0.Beta
Hi, a jira issue is created: https://jira.jboss.org/jira/browse/JBMESSAGING-1648 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236958#4236958 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236958 ___ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
