[EJB3] - MDB keep running after transaction timeout
by Bob Kung
Bob Kung [https://community.jboss.org/people/r4_1314] created the discussion
"MDB keep running after transaction timeout"
To view the discussion, visit: https://community.jboss.org/message/727892#727892
--------------------------------------------------------------
Hi all,
I was doing a MDB timeout test
1) I have a stls(ABean) bean and a mdb (BBean).
2) set @ActivationConfigProperty(propertyName = "transactionTimeout", propertyValue = "10") to BBean
3) BBean will reply a message to a queue(replyQueue) at the end of onMessage(), if any exception throws, current message will fall to dlq.
4) ABean will sleep 20 seconds which will cause BBean timeout.
5) Redelivery Delay: 0, Max Delivery Attempts: 1
6) running on JBoss AS 7.1.0 final
Expect result is
Transaction timeout --> transaction rollback --> redelivery ---> transaction timeout again --->transaction rollback again ---> send message to dlq
Actual result is
Transaction timeout --> transaction rollback --> send message to dlq---> ABean and BBean keep running till ABean wake up --> reply message to replyQueue --> exception catch "The transaction is not active!".
Seems the timeout just only rollback the tx transaction, but will not terminal the running thread or trigger redelivery.
Is there something wrong I have? Please help!! Many thanks!
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/727892#727892]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[EJB3] - MDB keep running after transaction timeout
by Bob Kung
Bob Kung [https://community.jboss.org/people/r4_1314] created the document:
"MDB keep running after transaction timeout "
To view the document, visit: https://community.jboss.org/docs/DOC-17845
--------------------------------------------------------------
Hi all,
I was doing a MDB timeout test
1) I have a stls(ABean) bean and a mdb (BBean).
2) set @ActivationConfigProperty(propertyName = "transactionTimeout", propertyValue = "10") to BBean
3) BBean will reply a message to a queue(replyQueue) at the end of onMessage(), if any exception throws, current message will fall to dlq.
4) ABean will sleep 20 seconds which will cause BBean timeout.
5) Redelivery Delay: 0, Max Delivery Attempts: 1
6) running on JBoss AS 7.1.0 final
Expect result is
Transaction timeout --> transaction rollback --> redelivery ---> transaction timeout again --->transaction rollback again ---> send message to dlq
Actual result is
Transaction timeout --> transaction rollback --> send message to dlq---> ABean and BBean keep running till ABean wake up --> reply message to replyQueue --> exception catch "The transaction is not active!".
Seems the timeout just only rollback the tx transaction, but will not terminal the running thread or trigger redelivery.
Is there something wrong I have? Please help!! Many thanks!
--------------------------------------------------------------
Comment by going to Community
[https://community.jboss.org/docs/DOC-17845]
Create a new document in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=102&c...]
13 years, 9 months
[JBoss Web Services] - Problem: Unsupported content type: text/plain
by Nizar Garrache
Nizar Garrache [https://community.jboss.org/people/ngarrache] created the discussion
"Problem: Unsupported content type: text/plain"
To view the discussion, visit: https://community.jboss.org/message/727847#727847
--------------------------------------------------------------
Hello,
We have a working EAR deployed on a JBoss EAP 5.1 and using Seam 2.2.2EAP5 et JBossWS 3.1.2.SP7.
We implemented a Soap Client which doesn't work if the received response has the HTTP header: content-type: text/plain.
If this header is not found or equal to text/xml the soap client works.
Here is the top of the stack trace:
22:52:27,454 ERROR [SOAPMessageUnMarshallerHTTP] Cannot unmarshall SOAPMessage
javax.xml.soap.SOAPException: Unsupported content type: text/plain
at org.jboss.ws.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:272)
at org.jboss.ws.core.soap.SOAPMessageUnMarshallerHTTP.read(SOAPMessageUnMarshallerHTTP.java:82)
at org.jboss.remoting.transport.http.HTTPClientInvoker.readResponse(HTTPClientInvoker.java:584)
at org.jboss.remoting.transport.http.HTTPClientInvoker.useHttpURLConnection(HTTPClientInvoker.java:381)
at org.jboss.remoting.transport.http.HTTPClientInvoker.makeInvocation(HTTPClientInvoker.java:232)
at org.jboss.remoting.transport.http.HTTPClientInvoker.transport(HTTPClientInvoker.java:162)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:167)
at org.jboss.remoting.Client.invoke(Client.java:2034)
at org.jboss.remoting.Client.invoke(Client.java:877)
at org.jboss.remoting.Client.invokeOneway(Client.java:926)
at org.jboss.ws.core.client.HTTPRemotingConnection.invoke(HTTPRemotingConnection.java:228)
at org.jboss.ws.core.client.SOAPProtocolConnectionHTTP.invoke(SOAPProtocolConnectionHTTP.java:71)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:360)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:231)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:171)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:157)
at $Proxy427.beginConversation(Unknown Source)
at com.oberthur.issuersimulator.session.TsmSpSimulatorBean.beginConversationRequest(TsmSpSimulatorBean.java:431)
at com.oberthur.issuersimulator.session.TsmSpSimulatorBean.beginConversationKeyRotation(TsmSpSimulatorBean.java:164)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.jboss.seam.util.Reflections.invoke(Reflections.java:22)
at org.jboss.seam.intercept.RootInvocationCont
Please, can you help me ?
Please note, that we want to accept the text/plain type.
Thanks,
Nizar,
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/727847#727847]
Start a new discussion in JBoss Web Services at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
[jBPM] - Re: Difficult workflow question
by John Bize
John Bize [https://community.jboss.org/people/jbize] created the discussion
"Re: Difficult workflow question"
To view the discussion, visit: https://community.jboss.org/message/727247#727247
--------------------------------------------------------------
I am using the Process Editor in eclipse and am having problems.
* The "Multiple Instances" Component does not have an "Exception Handlers" property. I thought that was where I would specify the handler for the "Yes" event. (the boundary event handler)
* When I create a "Multiple Instances" sub-process, exit, and reenter the editor, all of the components have large negative x & y locations. They aren't even visible. The "Multiple Instances" component becomes a scrolling pane, and I have to drag each embedded component back into position. I thought adding a UniqueId to the enclosing sub-process would help, but there's no MetaData property either.
* I'm using the Error Event to signal the Yes event, again, with no "Exception Handlers," but it looks like I can only use a Signal Event to continue the process outside the sub-process. There doesn't seem to be a "catch" version of the Error Event.
In short, I couldn't draw your diagram. Is there a better editor I should be using?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/727247#727247]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
13 years, 9 months
