[jBPM Development] - java.sql.SQLException: You cannot commit during a managed transaction!
by Abdurrahman Nasr
Abdurrahman Nasr [http://community.jboss.org/people/abdu_nasr] created the discussion
"java.sql.SQLException: You cannot commit during a managed transaction!"
To view the discussion, visit: http://community.jboss.org/message/560029#560029
--------------------------------------------------------------
Dears.
while i'm getting process engine in jbpm 4 using the following line
ProcessEngine processEngine = new Configuration().setResource("my.jbpm.cfg.xml").buildProcessEngine();
I encounter this problem
java.sql.SQLException: You cannot commit during a managed transaction!
at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.jdbcCommit(BaseWrapperManagedConnection.java:659)
at org.jboss.resource.adapter.jdbc.WrappedConnection.commit(WrappedConnection.java:486)
at org.hibernate.transaction.JDBCTransaction.commitAndResetAutoCommit(JDBCTransaction.java:170)
at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:146)
at org.jbpm.pvm.internal.tx.HibernateSessionResource.commit(HibernateSessionResource.java:64)
at org.jbpm.pvm.internal.tx.StandardTransaction.commit(StandardTransaction.java:139)
at org.jbpm.pvm.internal.tx.StandardTransaction.complete(StandardTransaction.java:64)
at org.jbpm.pvm.internal.tx.StandardTransactionInterceptor.execute(StandardTransactionInterceptor.java:57)
at org.jbpm.pvm.internal.svc.EnvironmentInterceptor.executeInNewEnvironment(EnvironmentInterceptor.java:53)
and many more...
does any one know what is that exception about....?!
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/560029#560029]
Start a new discussion in jBPM Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Remoting] - PingTimerTask in JBoss AS 5.0.1.GA EAP
by Kevin Lohmann
Kevin Lohmann [http://community.jboss.org/people/kevin.lohmann] created the discussion
"PingTimerTask in JBoss AS 5.0.1.GA EAP"
To view the discussion, visit: http://community.jboss.org/message/559978#559978
--------------------------------------------------------------
Hi there,
since we switched to JBoss 5.0.1.GA EAP (from 5.1.0.GA), plenty of times we see warnings in server.log like this:
2010-08-31 16:34:37,211 WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Connection reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Or:
2010-08-31 22:18:38,519 WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Socket closed
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Or:
2010-08-31 15:06:24,248 WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.net.SocketException: Software caused connection abort: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(Unknown Source)
at java.net.SocketOutputStream.write(Unknown Source)
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
Or:
2010-08-31 18:38:11,886 WARN [org.jboss.remoting.transport.bisocket.BisocketClientInvoker] (Timer-4) Unable to send ping: shutting down PingTimerTask
java.lang.NullPointerException
at org.jboss.remoting.transport.bisocket.BisocketClientInvoker$PingTimerTask.run(BisocketClientInvoker.java:723)
at java.util.TimerThread.mainLoop(Unknown Source)
at java.util.TimerThread.run(Unknown Source)
I can imagine what the PingTimerTask should do. But I'd like to hear from the experts what they say about it.
How can we handle these warnings?
Sometimes our clients receive warnings like this:
WARNING org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask@1f175da: detected failure on control connection Thread[control: Socket[addr=XXX/yyyy,port=7063,localport=4328],3,main] (a2sc3v-fo68je-gdiugvr5-1-gdjopipw-llpl: requesting new control connection (org.jboss.remoting.transport.bisocket.BisocketServerInvoker)
which we consider to be a part of the warnings the server logs. Can that be? Or is it another phenomenon?
I can't find any informations about these questions. The ones I see are out of date (three years ago)...
Anyone who can help me?
Thanks in advance,
Kevin
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559978#559978]
Start a new discussion in JBoss Remoting at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months
[JBoss Web Services CXF] - Is there a way to set a JaxWS connection timeout which works for CXF and Native
by Andrew Dinn
Andrew Dinn [http://community.jboss.org/people/adinn] created the discussion
"Is there a way to set a JaxWS connection timeout which works for CXF and Native"
To view the discussion, visit: http://community.jboss.org/message/559968#559968
--------------------------------------------------------------
I have been playing with using an RPC MEP to drive transaction completion in the XTS client code. Previously the implementation employed two one way messages, a Commit from the client to the completion services followed by a Comitted or Aborted from the completion service back to the client. Switching to an RPC MEP has the significant advantage that the client does not need to expose a service endpoint.
I now have a working prototype version of the RPC based service but I find that I am hostage to the timeout behaviour of the underlying JaxWS RPC exchange. The transaction completion service may take a long time to implement the termination trequest because it may need to negotiate with a plethora of distributed web services first to prepare them and then to complete them. So, even though the service host is alive and busy processing the request (hence should be able to retain an open TCP connection or answer UDP based pings) my client may time out the request.
I would like to be able to configure my own timeout for the completion request, probably so that it does not actually time out. I found the following thread explaining how to configure the timeout for a WS-Native JaxWS port
> http://community.jboss.org/message/334623#334623 http://community.jboss.org/message/334623#334623
This is fine if you are using Native. However, my code needs both to compile and run using either CXF or Native.
1. Is there also a way of configuring the timeout in JBossWS-CXF?
2. Is there a way of doing this so it runs on either stack
3. Is there a way of doing this so it compiles on either stack?
Ok, one final request (althoguh it is probably a long shot)
It would be useful if this configuration option were defined in the JaxWS standard. Is there any chance of this?
--------------------------------------------------------------
Reply to this message by going to Community
[http://community.jboss.org/message/559968#559968]
Start a new discussion in JBoss Web Services CXF at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]
15 years, 2 months