openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Chauvet (Created) (JIRA)" <>
Subject [jira] [Created] (OPENJPA-2106) JORAM and OpenJPA remote event notification framework‏
Date Wed, 11 Jan 2012 11:03:39 GMT
JORAM and OpenJPA remote event notification framework‏

                 Key: OPENJPA-2106
             Project: OpenJPA
          Issue Type: Bug
    Affects Versions: 2.1.0
         Environment: Windows XP 32 bits, Java SE (JRE 1.6.0_29 / JDK 1.6.0_26),  NetBeans
            Reporter: Guillaume Chauvet


I have a serious error with Joram and OpenJPA. When I start my collocated Joram Server and
start my mockup OpenJPA client, I have this exception :

134484  TEST  WARN   [main] openjpa.Runtime - Error broadcasting JMS update to topic "OpenJPACommitProviderTopic".
Remote BrokerFactories may be out-of-date.
javax.jms.IllegalStateException: Illegal control thread
	at org.objectweb.joram.client.jms.Session.checkThreadOfControl(
	at org.objectweb.joram.client.jms.Session.send(
	at org.objectweb.joram.client.jms.MessageProducer.doSend(
	at org.objectweb.joram.client.jms.MessageProducer.send(
	at org.objectweb.joram.client.jms.TopicPublisher.publish(
	at org.apache.openjpa.event.JMSRemoteCommitProvider.broadcast(
	at org.apache.openjpa.event.RemoteCommitEventManager.afterCommit(
	at org.apache.openjpa.event.TransactionEventManager.fireEvent(
	at org.apache.openjpa.lib.util.concurrent.AbstractConcurrentEventManager.fireEvent(
	at org.apache.openjpa.kernel.BrokerImpl.fireTransactionEvent(
	at org.apache.openjpa.kernel.BrokerImpl.endTransaction(
	at org.apache.openjpa.kernel.BrokerImpl.afterCompletion(
	at org.apache.openjpa.kernel.LocalManagedRuntime.commit(
	at org.apache.openjpa.kernel.BrokerImpl.commit(
	at org.apache.openjpa.kernel.DelegatingBroker.commit(
	at org.apache.openjpa.persistence.EntityManagerImpl.commit(

You can found the maven mock-up project, with 2 module : MOM server and MOM client :

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message