Spring jms jca-listener

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Spring jms jca-listener

tranchida
Is someone use spring jca-listener and bitronix sucessfully

I have the following error at startup

DEBUG BitronixTransaction - creating new transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000]
DEBUG BitronixTransaction - creating new transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001]
DEBUG TaskScheduler - scheduling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) for Sat Sep 12 01:30:48 CEST 2009
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TaskScheduler - scheduled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) scheduled for Sat Sep 12 01:30:48 CEST 2009, total task(s) queued: 3
DEBUG ThreadContext - assigning  to
DEBUG SeamUtilities - Spring webflow 1.x not detected: java.lang.ClassNotFoundException: org.springframework.webflow.executor.jsf.FlowVariableResolver
DEBUG SeamUtilities - Spring webflow 2.x not detected: java.lang.ClassNotFoundException: org.springframework.webflow.execution.RequestContextHolder
DEBUG TaskScheduler - scheduling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) for Sat Sep 12 01:30:48 CEST 2009
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TaskScheduler - scheduled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) scheduled for Sat Sep 12 01:30:48 CEST 2009, total task(s) queued: 4
DEBUG ThreadContext - assigning
 to
DEBUG BitronixTransaction - changing transaction status to ACTIVE
DEBUG TransactionLogAppender - between 1963190 and 1963249, writing a Bitronix TransactionLogRecord with status=ACTIVE, recordLength=51, headerLength=28, time=1252711788176, sequenceNumber=2, crc32=666737423, gtrid=737072696E672D62746D00000123AB70EE7F00000000, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963249
DEBUG BitronixTransaction - changing transaction status to ACTIVE
DEBUG TransactionLogAppender - between 1963249 and 1963308, writing a Bitronix TransactionLogRecord with status=ACTIVE, recordLength=51, headerLength=28, time=1252711788177, sequenceNumber=3, crc32=-239112107, gtrid=737072696E672D62746D00000123AB70EE7F00000001, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963308
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@3e9f26c7 does not belong to any resource of a PoolingDataSource containing an XAPool of resource jdbc/mysqldb with 1 connection(s) (1 still available)
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@3e9f26c7 does not belong to any resource of a PoolingConnectionFactory with an XAPool of resource jms/activemq with 1 connection(s) (1 still available)
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@68cab3bf does not belong to any resource of a PoolingDataSource containing an XAPool of resource jdbc/mysqldb with 1 connection(s) (1 still available)
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@68cab3bf does not belong to any resource of a PoolingConnectionFactory with an XAPool of resource jms/activemq with 1 connection(s) (1 still available)
DEBUG TaskScheduler - cancelling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TaskScheduler - cancelled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) scheduled for Sat Sep 12 01:30:48 CEST 2009, total task(s) still queued: 3
DEBUG BitronixTransaction - rolling back, 0 enlisted resource(s)
DEBUG BitronixTransaction - changing transaction status to ROLLING_BACK
DEBUG TransactionLogAppender - between 1963308 and 1963367, writing a Bitronix TransactionLogRecord with status=ROLLING_BACK, recordLength=51, headerLength=28, time=1252711788179, sequenceNumber=4, crc32=-1488803906, gtrid=737072696E672D62746D00000123AB70EE7F00000000, uniqueNames=
DEBUG TaskScheduler - cancelling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG TransactionLogAppender - disk journal appender now at position 1963367
DEBUG TaskScheduler - cancelled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) scheduled for Sat Sep 12 01:30:48 CEST 2009, total task(s) still queued: 2
DEBUG BitronixTransaction - rolling back, 0 enlisted resource(s)
DEBUG BitronixTransaction - changing transaction status to ROLLING_BACK
DEBUG AbstractPhaseEngine - executing phase on 0 resource(s) enlisted in 0 position(s) in reverse position order
DEBUG BitronixTransaction - changing transaction status to ROLLEDBACK
DEBUG TransactionLogAppender - between 1963367 and 1963426, writing a Bitronix TransactionLogRecord with status=ROLLING_BACK, recordLength=51, headerLength=28, time=1252711788179, sequenceNumber=5, crc32=-1092723924, gtrid=737072696E672D62746D00000123AB70EE7F00000001, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963426
DEBUG TransactionLogAppender - between 1963426 and 1963485, writing a Bitronix TransactionLogRecord with status=ROLLEDBACK, recordLength=51, headerLength=28, time=1252711788179, sequenceNumber=6, crc32=166249628, gtrid=737072696E672D62746D00000123AB70EE7F00000000, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963485
DEBUG BitronixTransaction - successfully rolled back a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG BitronixTransaction - after completion, 1 synchronization(s) to execute
DEBUG BitronixTransaction - executing synchronization a ClearContextSynchronization for a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) with status=ROLLEDBACK
DEBUG BitronixTransactionManager - clearing thread context: a ThreadContext with transaction a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000000], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009), default timeout 60s
INFO  ServerSessionImpl:0 - Endpoint failed to process message. Reason: Endpoint before delivery notification failure
DEBUG ServerSessionImpl:0 - run loop end
DEBUG AbstractPhaseEngine - executing phase on 0 resource(s) enlisted in 0 position(s) in reverse position order
DEBUG BitronixTransaction - changing transaction status to ROLLEDBACK
DEBUG TransactionLogAppender - between 1963485 and 1963544, writing a Bitronix TransactionLogRecord with status=ROLLEDBACK, recordLength=51, headerLength=28, time=1252711788180, sequenceNumber=7, crc32=322786741, gtrid=737072696E672D62746D00000123AB70EE7F00000001, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963544
DEBUG BitronixTransaction - successfully rolled back a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009)
DEBUG BitronixTransaction - after completion, 1 synchronization(s) to execute
DEBUG BitronixTransaction - executing synchronization a ClearContextSynchronization for a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009) with status=ROLLEDBACK
DEBUG BitronixTransactionManager - clearing thread context: a ThreadContext with transaction a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB70EE7F00000001], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:29:48 CEST 2009), default timeout 60s
INFO  ServerSessionImpl:1 - Endpoint failed to process message. Reason: Endpoint before delivery notification failure
DEBUG ServerSessionImpl:1 - run loop end
DEBUG ServerSessionImpl:0 - Endpoint did not release properly: null
org.apache.activemq.ra.InvalidMessageEndpointException
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointDead.release(MessageEndpointProxy.java:159)
        at org.apache.activemq.ra.MessageEndpointProxy.release(MessageEndpointProxy.java:74)
        at org.apache.activemq.ra.ServerSessionImpl.close(ServerSessionImpl.java:263)
        at org.apache.activemq.ra.ServerSessionPoolImpl.removeFromPool(ServerSessionPoolImpl.java:230)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:188)
        at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:232)
        at java.lang.Thread.run(Thread.java:637)
DEBUG ServerSessionImpl:0 - Run finished
DEBUG ServerSessionImpl:0 - Work completed: javax.resource.spi.work.WorkEvent[source=org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter@30813486]
DEBUG ServerSessionImpl:1 - Endpoint did not release properly: null
org.apache.activemq.ra.InvalidMessageEndpointException
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointDead.release(MessageEndpointProxy.java:159)
        at org.apache.activemq.ra.MessageEndpointProxy.release(MessageEndpointProxy.java:74)
        at org.apache.activemq.ra.ServerSessionImpl.close(ServerSessionImpl.java:263)
        at org.apache.activemq.ra.ServerSessionPoolImpl.removeFromPool(ServerSessionPoolImpl.java:230)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:188)
        at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:232)
        at java.lang.Thread.run(Thread.java:637)
DEBUG ServerSessionImpl:1 - Run finished
DEBUG ServerSessionImpl:1 - Work completed: javax.resource.spi.work.WorkEvent[source=org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter@596e0123]

on each message
===========

DEBUG ServerSessionPoolImpl - ServerSession requested.
DEBUG ServerSessionPoolImpl - Created a new session: ServerSessionImpl:2
DEBUG ServerSessionImpl:2 - Starting run.
DEBUG ServerSessionImpl:2 - Work accepted: javax.resource.spi.work.WorkEvent[source=org.springframework.jca.work.SimpleTaskWorkManager@73f378c8]
DEBUG ServerSessionImpl:2 - Work started: javax.resource.spi.work.WorkEvent[source=org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter@34faaa93]
DEBUG ServerSessionImpl:2 - Running
DEBUG ServerSessionImpl:2 - run loop start
DEBUG BitronixTransactionManager - beginning a new transaction
DEBUG BitronixTransactionManager - dumping 0 transaction context(s)
DEBUG BitronixTransactionManager - creating new thread context
DEBUG BitronixTransactionManager - changing current thread context to a ThreadContext with transaction null, default timeout 60s
DEBUG BitronixTransaction - creating new transaction with GTRID [737072696E672D62746D00000123AB7371E800000008]
DEBUG TaskScheduler - scheduling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009) for Sat Sep 12 01:33:32 CEST 2009
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009)
DEBUG TaskScheduler - scheduled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=NO_TRANSACTION, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009) scheduled for Sat Sep 12 01:33:32 CEST 2009, total task(s) queued: 3
DEBUG ThreadContext - assigning
 to
DEBUG BitronixTransaction - changing transaction status to ACTIVE
DEBUG TransactionLogAppender - between 1963544 and 1963603, writing a Bitronix TransactionLogRecord with status=ACTIVE, recordLength=51, headerLength=28, time=1252711952872, sequenceNumber=9, crc32=1030254674, gtrid=737072696E672D62746D00000123AB7371E800000008, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963603
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@715a64e6 does not belong to any resource of a PoolingDataSource containing an XAPool of resource jdbc/mysqldb with 0 connection(s) (0 still available)
DEBUG ResourceRegistrar - XAResource org.apache.activemq.ra.LocalAndXATransaction@715a64e6 does not belong to any resource of a PoolingConnectionFactory with an XAPool of resource jms/activemq with 0 connection(s) (0 still available)
DEBUG TaskScheduler - cancelling transaction timeout task on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009)
DEBUG TaskScheduler - removing task by a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009)
DEBUG TaskScheduler - cancelled a TransactionTimeoutTask on a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ACTIVE, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009) scheduled for Sat Sep 12 01:33:32 CEST 2009, total task(s) still queued: 2
DEBUG BitronixTransaction - rolling back, 0 enlisted resource(s)
DEBUG BitronixTransaction - changing transaction status to ROLLING_BACK
DEBUG TransactionLogAppender - between 1963603 and 1963662, writing a Bitronix TransactionLogRecord with status=ROLLING_BACK, recordLength=51, headerLength=28, time=1252711952873, sequenceNumber=10, crc32=-861786457, gtrid=737072696E672D62746D00000123AB7371E800000008, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963662
DEBUG AbstractPhaseEngine - executing phase on 0 resource(s) enlisted in 0 position(s) in reverse position order
DEBUG BitronixTransaction - changing transaction status to ROLLEDBACK
DEBUG TransactionLogAppender - between 1963662 and 1963721, writing a Bitronix TransactionLogRecord with status=ROLLEDBACK, recordLength=51, headerLength=28, time=1252711952873, sequenceNumber=11, crc32=1897952502, gtrid=737072696E672D62746D00000123AB7371E800000008, uniqueNames=
DEBUG TransactionLogAppender - disk journal appender now at position 1963721
DEBUG BitronixTransaction - successfully rolled back a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009)
DEBUG BitronixTransaction - after completion, 1 synchronization(s) to execute
DEBUG BitronixTransaction - executing synchronization a ClearContextSynchronization for a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009) with status=ROLLEDBACK
DEBUG BitronixTransactionManager - clearing thread context: a ThreadContext with transaction a Bitronix Transaction with GTRID [737072696E672D62746D00000123AB7371E800000008], status=ROLLEDBACK, 0 resource(s) enlisted (started Sat Sep 12 01:32:32 CEST 2009), default timeout 60s
INFO  ServerSessionImpl:2 - Endpoint failed to process message. Reason: Endpoint before delivery notification failure
DEBUG ServerSessionImpl:2 - run loop end
DEBUG ServerSessionImpl:2 - Endpoint did not release properly: null
org.apache.activemq.ra.InvalidMessageEndpointException
        at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointDead.release(MessageEndpointProxy.java:159)
        at org.apache.activemq.ra.MessageEndpointProxy.release(MessageEndpointProxy.java:74)
        at org.apache.activemq.ra.ServerSessionImpl.close(ServerSessionImpl.java:263)
        at org.apache.activemq.ra.ServerSessionPoolImpl.removeFromPool(ServerSessionPoolImpl.java:230)
        at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:188)
        at org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter.run(SimpleTaskWorkManager.java:232)
        at java.lang.Thread.run(Thread.java:637)
DEBUG ServerSessionImpl:2 - Run finished
DEBUG ServerSessionImpl:2 - Work completed: javax.resource.spi.work.WorkEvent[source=org.springframework.jca.work.SimpleTaskWorkManager$DelegatingWorkAdapter@34faaa93]



my config
======

        <bean id="resourceAdapter"
                class="org.springframework.jca.support.ResourceAdapterFactoryBean">

                <property name="resourceAdapter">
                        <bean class="org.apache.activemq.ra.ActiveMQResourceAdapter">
                                <property name="serverUrl" value="tcp://solaris:4500" />
                        </bean>
                </property>
                <property name="workManager">
                        <bean class="org.springframework.jca.work.SimpleTaskWorkManager"/>
                </property>
        </bean>

        <jms:jca-listener-container
                transaction-manager="BitronixTransactionManager">
                <jms:listener destination="testIn" ref="myListener" />
        </jms:jca-listener-container>
Reply | Threaded
Open this post in threaded view
|

Re: Spring jms jca-listener

Ludovic Orban
Administrator
Hi,

Unfortunately BTM does not support JCA, it's documented here: http://docs.codehaus.org/display/BTM/Overview#Overview-JCA

On the other hand I see stat you're trying to use ActiveMQ's JCA connector. Why not directly using it via BTM's JMS support then?
Reply | Threaded
Open this post in threaded view
|

Re: Spring jms jca-listener

Simon-2745

Tranchida,

Perhaps you could consider using spring message driven pojos with
bitronix as an alternative? There are working configurations and sample
code on this thread:

http://forum.springsource.org/showthread.php?p=216714

Simon

Ludovic Orban wrote:
> Hi,
>
> Unfortunately BTM does not support JCA, it's documented here:
> http://docs.codehaus.org/display/BTM/Overview#Overview-JCA
>
> On the other hand I see stat you're trying to use ActiveMQ's JCA connector.
> Why not directly using it via BTM's JMS support then?
>
>  


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email