[JBoss Messaging] - Jboss messaging client stops if we set client machine timestap to 1 hr back
by Saurav Kumar
Saurav Kumar [http://community.jboss.org/people/sauravkr] created the discussion
"Jboss messaging client stops if we set client machine timestap to 1 hr back"
To view the discussion, visit: http://community.jboss.org/message/563734#563734
--------------------------------------------------------------
Dear All,
We have client server application based Rich client and Jboss AS. Server components fires events on Topic and clients receives events by implementing messageListener-> onMessage methods
We subscribe to events via ClusteredConnectionFactory.
mTopicConnectionFactory = (ConnectionFactory) CmsServiceLocator.+lookup+(CmsServiceLocator.+JMS_ConnectionFactory);
mTopic = (Topic) CmsServiceLocator.+lookup+(+_DESTINATION_CMS_PUBLIC_);
mTopicConnection = mTopicConnectionFactory.createConnection();
// NOTE: Please don't make use of transacted session on client side, as it will lead to accumulation of event objects
mTopicSession = mTopicConnection.createSession(*false, Session.+SESSION_TRANSACTED);
// Create subscriber
mSubscriber = mTopicSession.createConsumer(mTopic);
mSubscriber.setMessageListener(*this);
mTopicConnection.setExceptionListener(*this);
mTopicConnection.start();
*
*
+*
+
+
..
Now, whenever we set system time of client machine to backdate (server date is untouched) we get a log on the server
<log4j:event logger="org.jboss.jms.server.connectionmanager.SimpleConnectionManager" timestamp="1285072335095" level="WARN" thread="Timer-14">
<log4j:message><![CDATA[A problem has been detected with the connection to remote client abie-3vn1e2-gecoh7dv-1-gecoh7q0-g, jmsClientID=n-7s7hoceg-1-vd7hoceg-2e1nv3-eiba. It is possible the client has exited without closing its connection(s) or the network has failed. All associated connection resources will be cleaned up.]]></log4j:message>
</log4j:event>"
And client stops listing to client events. No log on the client side.
Can any one guide on it?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/563734#563734]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
[Spring Integration] - Problem while migrating from Jboss 4.X to 5.x
by Santosh Maskar
Santosh Maskar [http://community.jboss.org/people/smaskar] created the discussion
"Problem while migrating from Jboss 4.X to 5.x"
To view the discussion, visit: http://community.jboss.org/message/563717#563717
--------------------------------------------------------------
My web application runs fine on Jboss 4.x but when I migrated it to Jboss 5.x I am getting the following exception.
12:44:37,744 ERROR [[StripesDispatcher]] Servlet.service() for servlet StripesDispatcher threw exception
java.lang.IllegalArgumentException: Can only process HttpServletRequest
at org.springframework.security.intercept.web.FilterInvocation.<init>(FilterInvocation.java:53)
at org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:160)
at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:236)
at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:167)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:190)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:92)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
I have attached web.xml and applicationContext.xml for your reference.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/563717#563717]
Start a new discussion in Spring Integration at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
13 years, 8 months
