[JBoss Messaging] - Weird transaction error
by TheOverlord
I'm getting these strange transaction related errors from an MDB consuming messages from queue:
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.jta.logging.loggerI18N - [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] [com.arjuna.ats.internal.jta.resources.arjunacore.preparefailed] XAResourceRecord.prepare - prepare failed with exception java.lang.IllegalMonitorStateException
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.BasicAction_36] - BasicAction.End() - prepare phase of action-id -53eef977:b8fd:489b9f66:dea failed.
| 2008-08-07 18:22:42,414 [JMS SessionPool Worker-5] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.arjuna.coordinator.BasicAction_38] - Action Aborting
| 2008-08-07 18:22:42,419 [JMS SessionPool Worker-5] ERROR org.jboss.jms.asf.StdServerSession - failed to commit/rollback
| javax.transaction.RollbackException: [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] [com.arjuna.ats.internal.jta.transaction.arjunacore.commitwhenaborted] Can't commit because the transaction is in aborted state
| at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1394)
| 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.jms.asf.StdServerSession.onMessage(StdServerSession.java:351)
| at org.jboss.jms.client.container.ClientConsumer.callOnMessage(ClientConsumer.java:160)
| at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
| at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect14.invoke(SessionAspect14.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
| at org.jboss.jms.client.delegate.ClientSessionDelegate$run_N8003352271541955702.invokeNext(ClientSessionDelegate$run_N8003352271541955702.java)
| at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
| at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
| at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:194)
|
I've already opened a support ticket on this but I just wanted to know what you think about this.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169483#4169483
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169483
17 years, 11 months
[JBoss jBPM] - Re: Getting comments through command object ?
by lblaauw
Hey vtysh,
Well my usecase is actually quite simple, i just need global comments per process instance, so any task user can add comments to the whole process instance. So when i collect a users tasks per task i also collect the process instance comments for that task. Therefore i decided to use the rootToken for this. The processes are actually quite simple so no subprocesses branching etc etc. So i figured i could get away with how i did things.. ;-)
Regards and thanks for your reply,
Leo
"vtysh" wrote : Oh, i am sorry, you didn't write anything about jbpm-console. But all other recommendations are still actual. You need to find all process instance tokens with the method findAllTokens(). Then iterate through tokens and get their comments with the method token.getComments() and add all comments to some comments list which will contain all process comments. For a knowledge whether the comment is related to some task instance you can use expression comment.getTaskInstance()!=null
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169476#4169476
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169476
17 years, 11 months
[JBoss Messaging] - Invalid authentication attempt, principal=null error...
by pkorros
Our production server after running for many weeks without problems, suddenly started to throw the following SecurityException every time the system tries to connect to a jms queue.
A reboot solved the problem but i am trying to find a better solution.
I had the same problem before, when running with JBossMQ but I was able to solve it by disabling the SecurityInterceptor in the jbossmq-service.xml.
Can this be done with the JBoss Messaging implementation?
java.lang.SecurityException: Invalid authentication attempt, principal=null
at org.jboss.resource.connectionmanager.BaseConnectionManager2.getSubject(BaseConnectionManager2.java:589)
at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:395)
at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.allocateConnection(JmsSessionFactoryImpl.java:389)
at org.jboss.resource.adapter.jms.JmsSessionFactoryImpl.createQueueSession(JmsSessionFactoryImpl.java:144)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169472#4169472
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169472
17 years, 11 months