2008-06-25 11:09:09,232 (MuleManager.java:900) INFO org.mule.MuleManager -
**********************************************************************
* Mule ESB and Integration Platform *
* Version: 1.4.4 Build: 11748 *
* MuleSource, Inc. *
* For more information go to
http://mule.mulesource.org *
* *
* Server started: 25/06/08 11:09 *
* Server ID: MAF-config *
* JDK: 1.6.0_04 (mixed mode, sharing) *
* OS: Windows XP - Service Pack 2 (5.1, x86) *
* Host: LGLAIB8HBBJ2J (169.24.29.131) *
* *
* Agents Running: *
* JMX Agent *
* Wrapper Manager: Mule PID #3920, Wrapper PID #3940 *
**********************************************************************
2008-06-25 11:09:09,232 (MuleServer.java:300) INFO org.mule.MuleServer - Mule Server initialized.
2008-06-25 11:09:10,420 (AbstractExceptionListener.java:310) ERROR org.mule.impl.DefaultExceptionStrategy -
********************************************************************************
Message : Mule transaction is null, but enlist method is called
Type : org.mule.transaction.IllegalTransactionStateException
Code : MULE_ERROR-91530
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/transaction/IllegalTransactionStateException.html
********************************************************************************
Exception stack is:
1. Mule transaction is null, but enlist method is called (org.mule.transaction.IllegalTransactionStateException)
org.mule.providers.jdbc.xa.ConnectionWrapper:463 (
http://mule.mulesource.org/docs/apidocs/org/mule/transaction/IllegalTransactionStateException.html)
********************************************************************************
Root Exception stack trace:
org.mule.transaction.IllegalTransactionStateException: Mule transaction is null, but enlist method is called
at org.mule.providers.jdbc.xa.ConnectionWrapper.enlist(ConnectionWrapper.java:463)
at org.mule.providers.jdbc.xa.StatementInvocationHandler.invoke(StatementInvocationHandler.java:40)
at $Proxy0.executeQuery(Unknown Source)
at org.apache.commons.dbutils.QueryRunner.query(QueryRunner.java:236)
at org.mule.providers.jdbc.JdbcMessageReceiver.getMessages(JdbcMessageReceiver.java:154)
at org.mule.providers.TransactedPollingMessageReceiver.poll(TransactedPollingMessageReceiver.java:136)
at org.mule.providers.PollingReceiverWorker.run(PollingReceiverWorker.java:47)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:619)
********************************************************************************
This is typically a misconfiguration. 1.4.4 is more strict with this case, as it's really an error, and proceeding would cause unexpected results. I don't see why you'd use the DataSourceWrapper. What happened when you used OracleDataSource?