-
15. Re: How to switch to MySQL?
I executed the following command in MySQL:
CREATE TABLE JBM_POSTOFFICE (POSTOFFICE_NAME VARCHAR(255), NODE_ID INTEGER, QUEUE_NAME VARCHAR(255), COND VARCHAR(1023), SELECTOR VARCHAR(1023), CHANNEL_ID BIGINT, CLUSTERED CHAR(1), ALL_NODES CHAR(1), PRIMARY KEY(POSTOFFICE_NAME, NODE_ID, QUEUE_NAME)) ENGINE = INNODB
And I got this in return:Error code 1071, SQL state 42000: Specified key was too long; max key length is 1024 bytes
-
16. Re: How to switch to MySQL?
Can you just check that this log level for this statement is not DEBUG:
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Table 'juddidb.jbm_postoffice' doesn't exist
I havn't seen the other problem before, but then again I havn't used mysql. You might want to post this question about the jbm database in the jboss messaging user forum. They will probably be able to help you with this issue.
Regards,
Daniel -
-
18. Re: How to switch to MySQL?
Guys-
The JBM user guide explains how to configure JBM to run with mysql. -
19. Re: How to switch to MySQL?
"haagenhasle" wrote:
I edited the URL a little bit, so now I found the GA-version as well. So I'll use that one! :)
SP1 is more recent than the GA! (SP= service pack) -
20. Re: How to switch to MySQL?
With the mysql-persistence-service.xml-file from SP1, I get
java.lang.IllegalArgumentException: No such SQL statement: DELETE_MESSAGE
at org.jboss.messaging.core.impl.JDBCSupport.getSQLStatement(JDBCSupport.java:183)
With the mysql-persistence-service.xml-file from GA, I get the error already described.
I have done everything that is described in the installation guide, as far as I can see. It tells me to use the mysql-persistence-service.xml that I find in examples/config, and I've done that.
Regards, Haagen -
21. Re: How to switch to MySQL?
I upgraded my MySQL to 5.0 again, and that did the trick - the server starts up without any errormessages now! :-D
Thank you Daniel for very good help, I really appreciate it! (Which is more than I can say about the "help" I got on the JBoss Messaging forum...)
Regards, Haagen -
22. Re: How to switch to MySQL?
One last question about this... I get this one at startup now:
19:28:26,026 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS' 19:28:26,511 WARN [JDBCPersistenceManager] JBoss Messaging Warning: DataSource connection transaction isolation should be READ_COMMITTED, but it is currently REPEATABLE_READ. Using an isolation level less strict than READ_COMMITTED may lead to data consistency problems. Using an isolation level more strict than READ_COMMITTED may lead to deadlock.
I haven't been able to figure out where to change this.. I tried to put <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation> into my mysql-ds.xml file, but that didn't seem to work. Where do I change this?
Regards, Haagen -
23. Re: How to switch to MySQL?
We're rolling our own transactions, please don't use a tx datasource, it won't do you any good.
--K -
24. Re: How to switch to MySQL?
Does that mean I should use <no-tx-datasource> instead of <local-tx-datasource>, or does it mean that I can just ignore the warning message at startup?
Regards, Haagen -
25. Re: How to switch to MySQL?
When I shutdown my server I get an error. I write "shutdown.bat -s=localhost" to initiate the shutdown.
12:39:48,557 ERROR [ExceptionUtil] org.jboss.jms.server.connectionfactory.ConnectionFactory@172d19e startService java.lang.IllegalStateException: Cannot find replicant to remove: CF_jboss.messaging.connectionfactory:service=ConnectionFactory at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.unregisterConnectionFactory(ConnectionFactoryJNDIMapper.java:264) at org.jboss.jms.server.connectionfactory.ConnectionFactory.stopService(ConnectionFactory.java:187) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:206) (...)
I think this started happening after I switched to MySQL. Does anyone have an idea what it is and how I can fix it?
Regards, Haagen -
26. Re: How to switch to MySQL?
I recently noticed that I haven't transfered all my database-use to MySQL, there is still a ManagementDS left that use Hypersonic. I tried to edit the management-ds.xml file to point to MySQL as well, but at startup I got an error message. This was because the sql that is defined inside the management.esb-file only works with Hypersonic (or at least it doesn't work with MySQL).
Am I wrong in thinking that I should try to configure my ESB so that Hypersonic isn't used at all? So far all the files I've been edited have been fairly easily available (although I would have prefered it if they were all found in the /conf-directory, and not in different sub-directories of /deploy.. :), but this requires me to unzip the management.esb, edit the files and zip it up again. Should I leave it alone and let it use Hypersonic?
If I decide to change the ManagementDS to MySQL, can anyone help me with translating the SQL in create_database.sql and insert_row.sql (in management.esb) to SQL that works for MySQL?
Regards, Haagen -
27. Re: How to switch to MySQL?
"haagenhasle" wrote:
If I decide to change the ManagementDS to MySQL, can anyone help me with translating the SQL in create_database.sql and insert_row.sql (in management.esb) to SQL that works for MySQL?
Regards, Haagen
Hi Haagen - we actually provide the MySQL versions of these files. You can build a management.esb for MySQL pretty easily - tools/console/MANAGEMENT-README.txt should run you through the complete set of steps.
It is basically just changing a db.properties file though in management-esb : change the "db" property from "hsqldb" to "mysql", and rebuild with "ant clean deploy". That should enable everything to point to MySQL (hibernate, management-ds.xml, etc). -
28. Re: How to switch to MySQL?
Hiya Haagen
"haagenhasle" wrote:
Does that mean I should use <no-tx-datasource> instead of <local-tx-datasource>, or does it mean that I can just ignore the warning message at startup?
You should be using a JTA aware datasource so that it can take part in any transaction that is active on the current thread.
If your datasource is fully XA aware then you should use <xa-datasource>. If the datasource does not support two phase commit then you should use <local-xa-datasource>.
If you choose <local-xa-datasource> then your resource will take part in the JTA transaction using the Last Resource Gambit but only one of these resources should be active within the transaction at a time.
Previous versions of the ESB codebase have had no support for JTA transactions but this has changed in 4.2.1GA. It is now possible to enable transaction support for JMS transports and SQL gateways and have these transactions encompass the processing of the pipeline. Any XA aware resources used within those pipelines can be enlisted within the encompassing transaction (this happens automatically for datasources if they are configured through JCA).
There is still further work required to complete this task but the current codebase goes a long way towards this. -
29. Re: How to switch to MySQL?
"tcunning" wrote:
Hi Haagen - we actually provide the MySQL versions of these files. You can build a management.esb for MySQL pretty easily - tools/console/MANAGEMENT-README.txt should run you through the complete set of steps.
It is basically just changing a db.properties file though in management-esb : change the "db" property from "hsqldb" to "mysql", and rebuild with "ant clean deploy". That should enable everything to point to MySQL (hibernate, management-ds.xml, etc).
Thanks for the tip!
When I did a "ant deploy", I got the following SQL-error. Is it my fault somewhere, or a bug worth reporting?14:35:16,424 WARN [JDBCExceptionReporter] SQL Error: 0, SQLState: 01004 14:35:16,424 ERROR [JDBCExceptionReporter] Data truncation: Data too long for column 'textvalue' at row 1 14:35:16,424 ERROR [DataFiler] Problem saving id [null] time[Fri Nov 09 14:35:12 CET 2007] server [hph-xp:1099] attribute [51 jboss.esb:service-category=JBossESB-Internal,service-name=DeadLetterServic e,listener-name=JMS-DLQListener] count[null] text [<JMS-DLQListener listenerClass="org.jboss.soa.esb.listeners.message.MessageAwareListener" maxThreads="1" mep="OneWay" service-category="JBossESB-I nternal" service-description="Dead Messages can be send to this service, which is configured to store and/or notify" service-name="DeadLetterService"> <EPR acknowledge-mode="AUTO_ACKNOWLEDGE" connection-factory="ConnectionFactory" destination-name="queue/DeadMessageQueue" destination-type="queue" persistent="true" protocol="jms"/> <action action="notificationAction" class="org.jboss.soa.esb.actions.Notifier" okMethod="notifyOK"> <NotificationList> <target class="NotifyConsole"/> </NotificationList> </action> <action action="PersistAction" class="org.jboss.soa.esb.actions.MessagePersister" classification="DLQ" message-store-class="org.jboss.internal.soa.esb.persistence.format.db.DBMessageStoreImpl"/> </JMS-DLQListener>] timevalue [null] org.hibernate.exception.GenericJDBCException: could not insert: [org.jboss.soa.esb.monitoring.pojo.JMXData] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:40) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2158) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2638) at org.hibernate.action.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:48) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:298) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:181) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:107) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:187) at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:172) at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:535) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:523) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:519) at org.jboss.soa.esb.monitoring.server.DataFiler.insertData(DataFiler.java:152) at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:173) at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:201) at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'textvalue' at row 1 at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3374) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3308) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1837) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1961) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2543) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1737) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2022) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1940) at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1925) at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251) at org.hibernate.id.IdentityGenerator$GetGeneratedKeysDelegate.executeAndExtract(IdentityGenerator.java:73) at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:33) ... 30 more 14:35:16,424 ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: null id in org.jboss.soa.esb.monitoring.pojo.JMXData entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:164) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:177) at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:201) at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 14:35:16,439 ERROR [DataFiler] org.hibernate.AssertionFailure: null id in org.jboss.soa.esb.monitoring.pojo.JMXData entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:164) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:177) at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:201) at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 14:35:16,502 ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: null id in org.jboss.soa.esb.monitoring.pojo.JMXData entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:164) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:187) at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:201) at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 14:35:16,502 WARN [ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline: header: [ To: JMSEpr [ PortReference < <wsa:Address jms://localhost/queue/DataFilerQueue />, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFact ory/>, <wsa:ReferenceProperties jbossesb:persistent : true/>, <wsa:ReferenceProperties jbossesb:acknowledge-mode : 1/> > ] MessageID: ID:JBM-57351 RelatesTo: jms:correlationID#b0971261-030a-470f-ac8e- dd8d76a087e9 ] org.jboss.soa.esb.actions.ActionProcessingException: Unexpected invocation target exception from processor at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:127) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:316) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:303) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.hibernate.AssertionFailure: null id in org.jboss.soa.esb.monitoring.pojo.JMXData entry (don't flush the Session after an exception occurs) at org.hibernate.event.def.DefaultFlushEntityEventListener.checkId(DefaultFlushEntityEventListener.java:55) at org.hibernate.event.def.DefaultFlushEntityEventListener.getValues(DefaultFlushEntityEventListener.java:164) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:196) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.jboss.soa.esb.monitoring.server.DataFiler.insertStatistics(DataFiler.java:187) at org.jboss.soa.esb.monitoring.server.DataFiler.persistData(DataFiler.java:201) at org.jboss.soa.esb.monitoring.server.FilerAction.fileMessage(FilerAction.java:70) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) ... 6 more