May 2010 - jboss-dev-forums - Jboss List Archives

[EJB 3.0 Development] - enabling org.jboss.ejb3 tracing causes ajuna error : The transaction is not active!

by Daniel Cullender

Daniel Cullender [http://community.jboss.org/people/cullendw] created the discussion "enabling org.jboss.ejb3 tracing causes ajuna error : The transaction is not active!" To view the discussion, visit: http://community.jboss.org/message/545043#545043 -------------------------------------------------------------- Hi, We are using jboss 4.2.3 and we noticed a really bizarre bug. When we enable tracing for org.jboss.ejb3 in the jboss-log4j.xml file with the following entry: <category name="org.jboss.ejb3"> <priority value="TRACE"/> </category> We start getting this arjuna exception every time we put a message on our topic. It seems like the transaction changes mid transaction, causing an inconsistent state which arjuna does not like : 12:10:06,247 WARN [MessageInflowLocalProxy] Current transaction TransactionImple < ac, BasicAction: -53ec9f29:d858:4bfe44ad:ca2 status: ActionStatus.RUNNING > is not the expected transaction. 12:10:06,247 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_34] - End called on already committed atomic action -53ec9f29:d858:4bfe44ad:434 12:10:06,247 ERROR [JmsServerSession] Unexpected error delivering message org.jboss.mq.SpyObjectMessage { Header { jmsDestination : TOPIC.XXXXXX jmsDeliveryMode : 1 jmsExpiration : 1274955064906 jmsPriority : 4 jmsMessageID : ID:2-12749550049061 jmsTimeStamp : 1274955004906 jmsCorrelationID: null jmsReplyTo : null jmsType : null jmsRedelivered : true jmsProperties : {JMSXDeliveryCount=484, JMS_JBOSS_REDELIVERY_LIMIT=0, JMS_JBOSS_REDELIVERY_COUNT=483} jmsPropReadWrite: false msgReadOnly : true producerClientId: ID:2 } } javax.resource.ResourceException: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active! at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:232) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:134) at $Proxy153.afterDelivery(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:183) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:906) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170) at org.jboss.mq.SpySession.run(SpySession.java:323) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:237) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:761) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalStateException: [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] [com.arjuna.ats.internal.jta.transaction.arjunacore.inactive] The transaction is not active! at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1385) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.endTransaction(MessageInflowLocalProxy.java:433) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.finish(MessageInflowLocalProxy.java:312) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.after(MessageInflowLocalProxy.java:228) Any ideas why this is happening (or if a jira bug has been opened for this)? We have other classes set to TRACE in a similar fashion which work 100%. The good news is that the trace is definitely activated for org.jboss.ejb3. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545043#545043] Start a new discussion in EJB 3.0 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545036#545036 -------------------------------------------------------------- It looks like we are talking about two different things ;) What I am trying to say is that I would like to ensure that signalExecutionById(mainProcessId) will not signal running but not yet finished sub process. At the moment when your process has a sub process in a wait state and you signal as above then will signal sub process activity regardless of the state it currently is. Result of it will be: - main process will move on - sub process will be left unfinished - end method will not be invoked and this execution will not be deleted My suggestion is to prevent of signaling sub process activity when it is running. You don't need to fetch it from db since when signal method is executed you have access to both main and sub process instances. Will attach a patch today to jira. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545036#545036] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545028#545028 -------------------------------------------------------------- Hi Maciej, There is an issue for what you said. Please refer this https://jira.jboss.org/browse/JBPM-2856 https://jira.jboss.org/browse/JBPM-2856. In my opinion, when a sub process ended, we should delete it and signal the super process. So there will be no process with ended state in database. If you cannot find a process intance, it means that it has already ended. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545028#545028] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545024#545024 -------------------------------------------------------------- As I understand this, sub process must contain an end activity to be able to signal main process to move on. So my idea was to check in signal method of SubProcessActivity if sub process instance is in state ended, if so signaling is allowed otherwise throw an exception. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545024#545024] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545022#545022 -------------------------------------------------------------- Hi Maciej, Yes, you are right for the inactive-scope. But we still have no way to find whether the super-process has active state sub process. Maybe could decide by this? if (execution.getSubProcessInstance() != null) -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545022#545022] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

[jBPM Development] - JBPM-2875 enhance classloader strategy for OSGi

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] created the discussion "JBPM-2875 enhance classloader strategy for OSGi" To view the discussion, visit: http://community.jboss.org/message/545020#545020 -------------------------------------------------------------- Hi guys, I really need this feature to let jbpm4 run in an OSGi envrionment. Now jBPM4 only use Thread.currentThread().getContextClassLoader() to load resources or class. But in an OSGi environment, the contextClassLoader may be not for the jbpm4 bundle, So jBPM4 won't find any xml configuration resource from classloader, then lots of errors occured. So I need when jbpm4 find resource or class, it not only use contextClassLoader, but also use it's owner classloader, e.g. JpdlParser.class.getClassLoader(). Any opinions are appreciated. Thank you very much. https://jira.jboss.org/browse/JBPM-2875 https://jira.jboss.org/browse/JBPM-2875 -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545020#545020] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545012#545012 -------------------------------------------------------------- you mean that when we enter sub process the main process should be in state inactive-scope? If so, I am afraid it won't work as expected, I really liked the idea though. The reason of this is if you mark main execution as inactive-scope when sub process activity is executed then automatic signal after sub process ends will fail since checkActive is executed in end activity which is prior to signal of sub process activity. Of course end activity code can be modified as well but I don't think it is a good idea. In my opinion engine should prevent of signaling main process while sub process is active, otherwise we could end up in really weird situations where some of the executions are left and main process is finished. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545012#545012] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/545004#545004 -------------------------------------------------------------- Hi Maciej, Get an exception for signaling a waiting super-process would be nice. But I don't know why there is no state for this scenario? If there is a particular state for waiting super-process, then we needn't to throw an exception by hand. -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/545004#545004] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by Maciej Swiderski

Maciej Swiderski [http://community.jboss.org/people/swiderski.maciej] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/544997#544997 -------------------------------------------------------------- Hi HuiSheng, thanks for your comment. I would go for option 1 (in fact has already tested that and it seems to work properly for signaling). Another thing is to keep the approuch consistent since we expose main process instance as Execution I would say we shall give same type for sub process instance. Another question was about securing SubProcessActivity to do not signal it while sub process is still active. I did a small fix that throws an exception when user tries to signal sub process while it is not finished. Do you think it is right way to do? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544997#544997] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

Re: [jboss-dev-forums] [jBPM Development] - SubProcess signaling issue

by HuiSheng Xu

HuiSheng Xu [http://community.jboss.org/people/rebody] replied to the discussion "SubProcess signaling issue" To view the discussion, visit: http://community.jboss.org/message/544966#544966 -------------------------------------------------------------- Hi Maceij, It is a very common problem when we use sub-process, because there is no way to get a sub-process from it's super-process. Consider about which of using is better: 1. // // Is there any risk for a session already closed exception? // ProcesssInstance subProcessInstance = execution.getSubProcessInstance(); if (subProcessInstance != null) { executionService.signalExecutionById(subProcessInstance.getId()); }. 2. String subProcessInstanceId = execution.getSubProcessInstanceId(); if (subProcessInstanceId != null) { executionService.signalExecutionById(subProcessInstanceId); } 3. if (execution.hasSubProcessInstance()) { executionService.signalExecutionById(execution.getSubProcessInstanceId()); } 4. // Don't like this way, need to add too much methods in API. executionService.signalSubProcessInstance(executionId); -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/544966#544966] Start a new discussion in jBPM Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

14 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2010