[JBoss Messaging] - JBoss Messaging consumer connetion unable to receive any exception while JBoss server is able to Receives Event on ConnectionListener and handle connection (subscriptions) cleanup and other stuff.
by Jagan Rao
Jagan Rao [http://community.jboss.org/people/NJaganMohanRao] created the discussion
"JBoss Messaging consumer connetion unable to receive any exception while JBoss server is able to Receives Event on ConnectionListener and handle connection (subscriptions) cleanup and other stuff."
To view the discussion, visit: http://community.jboss.org/message/565075#565075
--------------------------------------------------------------
Hello All,
I am facing a problem with JBoss Messaging,
Environment:
JBoss Server Version: Jboss 4.2.3 GA
JMS Messaging Version: 1.4.2.GA-SP1
Our JMS Messaging remote clients need to receive Messages 24X7, so this process or client need to be reliable in receiving messages.
Problem Area:
At production Environment After few hours clients stop receiving Messages automatically, at the server side we receive warning as below:
Level
WARN
Logger
org.jboss.jms.server.connectionmanager.SimpleConnectionManager
Time
2010-10-06 11:47:16,812
Thread
Timer-18
Message
A problem has been detected with the connection to remote client 464e206d-19g03s-gexoqzvj-1-gexor8fa-2f, jmsClientID=null. 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.
So we started digging into the problem and we found that underlying connection (socket) terminated and JBoss server recived an Event on her ConnectionListener and hadled all necessary stuff on server like removing all subscriptions corresponding to this client and logged above WARN but surprizingly didn't rasied any JMSException or Exception so that clents can heal or act accordingly.
After this situation JMS Client don't receive any messages because underlying connection lost somehow and JMSClient couldn't able to identify its connection loss because no exception from server.
and we are unable to find any root cause for the connection loss but we found a simple way to reproduce the cinario, and the reproduciton scheme was simply change the timestamp or time of the machine to 1hour back where JMS Remote Client is running.
If anyone knows the root cause or solution to the problem please let me know - I need solution immediatly.
Is there any way from the JBoss remoting side to identify connection loses and so that JMS remote client can listen on any listener so that JMS remote client can heal her self.
Thanks in Advance,
Jagan.
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/565075#565075]
Start a new discussion in JBoss Messaging at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[Beginner's Corner] - DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
by Deepan Chakravarthy
Deepan Chakravarthy [http://community.jboss.org/people/dareboy] created the discussion
"DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000"
To view the discussion, visit: http://community.jboss.org/message/565047#565047
--------------------------------------------------------------
Im using Jboss 4.0.5 for my web application. My site is running from Mochahost host provider. The site is frequently down for a specific time (mostly 30min to 1hr). The host provider said that there is no problem from their side. From my knowledge I didnt find any problem from my side. I think the problem is in JBOSS. The following logs shows the debug thrown at the time of site downtime,
2010-10-06 01:17:12,392 INFO [STDOUT] rConnection...
2010-10-06 01:17:12,493 INFO [STDOUT] rConnection...
2010-10-06 01:17:12,493 INFO [STDOUT] rdataSource...org.jboss.resource.adapter.jdbc.WrapperDataSource@4eb471
2010-10-06 01:17:12,493 INFO [STDOUT] rConnection...org.jboss.resource.adapter.jdbc.WrappedConnection@e671de
2010-10-06 01:19:30,238 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2010-10-06 01:20:15,632 INFO [STDOUT] rConnection...
2010-10-06 01:20:15,662 INFO [STDOUT] rConnection...
2010-10-06 01:20:15,663 INFO [STDOUT] rdataSource...org.jboss.resource.adapter.jdbc.WrapperDataSource@4eb471
2010-10-06 01:20:15,663 INFO [STDOUT] rConnection...org.jboss.resource.adapter.jdbc.WrappedConnection@1826b7a
2010-10-06 01:21:16,011 INFO [STDOUT] rConnection...
2010-10-06 01:21:18,369 INFO [STDOUT] rConnection...
2010-10-06 01:21:18,370 INFO [STDOUT] rdataSource...org.jboss.resource.adapter.jdbc.WrapperDataSource@4eb471
2010-10-06 01:21:18,370 INFO [STDOUT] rConnection...org.jboss.resource.adapter.jdbc.WrappedConnection@1c93f91
2010-10-06 01:26:18,465 INFO [STDOUT] rConnection...
2010-10-06 01:26:18,489 INFO [STDOUT] rConnection...
2010-10-06 01:26:18,685 INFO [STDOUT] rdataSource...org.jboss.resource.adapter.jdbc.WrapperDataSource@4eb471
2010-10-06 01:26:18,685 INFO [STDOUT] rConnection...org.jboss.resource.adapter.jdbc.WrappedConnection@e0e49f
2010-10-06 01:27:00,330 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] run: IdleRemover notifying pools, interval: 450000
2010-10-06 01:27:18,826 INFO [STDOUT] rConnection...
2010-10-06 01:27:18,968 INFO [STDOUT] rConnection...
2010-10-06 01:27:18,968 INFO [STDOUT] rdataSource...org.jboss.resource.adapter.jdbc.WrapperDataSource@4eb471
2010-10-06 01:27:18,969 INFO [STDOUT] rConnection...org.jboss.resource.adapter.jdbc.WrappedConnection@36019a
Do I need any changes in JBOSS configuration?
Im not good in JBOSS and I dono how to fix the problem. Any solution is hardly appreciable.....
Many Thanks,
Deepan
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/565047#565047]
Start a new discussion in Beginner's Corner at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months
[EJB 3.0] - Lock wait timeout exceeded; try restarting transaction
by Agustin Sivoplás
Agustin Sivoplás [http://community.jboss.org/people/SpiritFox26] created the discussion
"Lock wait timeout exceeded; try restarting transaction"
To view the discussion, visit: http://community.jboss.org/message/564761#564761
--------------------------------------------------------------
Hi all, I'm having this problem and can not really be, is that I have a table called tickets and another table called historia_estados_tickets where are saved the various states through which passes the ticket, within the table I have a ticket id_historia_estado_vigente column each time you change a status is updated with the latest id been in effect, is happening to me, when i change the status (insert into historia_estados_ticket) not update the table tickets. I have reviewed the log and I found this bug that could be causing this behavior.
[JDBCExceptionReporter] SQL Error: 1205, SQLState: 41000
17:53:11,838 ERROR [JDBCExceptionReporter] Lock wait timeout exceeded; try restarting transaction
17:53:11,838 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:253)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:266)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:172)
at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298)
at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27)
at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000)
at org.hibernate.ejb.AbstractEntityManagerImpl.flush(AbstractEntityManagerImpl.java:304)
at uy.com.its.itil.view.IncidenteEditBean.borrarDatos(IncidenteEditBean.java:2294)
at uy.com.its.itil.view.IncidenteEditBean.editarTicket(IncidenteEditBean.java:1305)
at uy.com.its.itil.view.IncidenteEditBean.editarTicketyListar(IncidenteEditBean.java:2435)
at sun.reflect.GeneratedMethodAccessor2362.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.el.parser.AstValue.invoke(AstValue.java:131)
at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276)
at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
at javax.faces.component.UICommand.broadcast(UICommand.java:387)
at org.ajax4jsf.component.AjaxViewRoot.processEvents(AjaxViewRoot.java:324)
at org.ajax4jsf.component.AjaxViewRoot.broadcastEvents(AjaxViewRoot.java:299)
at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:256)
at org.ajax4jsf.component.AjaxViewRoot.processApplication(AjaxViewRoot.java:469)
at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:82)
at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:100)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
att org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:178)
at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:290)
at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:388)
at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:515)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at uy.com.its.util.AuthenticationFilter.doFilter(AuthenticationFilter.java:82)
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:230)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
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:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.sql.BatchUpdateException: Lock wait timeout exceeded; try restarting transaction
at com.mysql.jdbc.ServerPreparedStatement.executeBatch(ServerPreparedStatement.java:665)
at org.jboss.resource.adapter.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:774)
at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:48)
at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:246)
I need help!
Thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/564761#564761]
Start a new discussion in EJB 3.0 at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
14 years, 3 months