This content has been marked as final.
Show 5 replies
-
1. Re: Oracle AQ and JBoss ESB
tschungelbuch Jan 2, 2009 9:56 AM (in response to tschungelbuch)I forgot to mention that for all 3 database schema I have a different ESB, each with an isolated class loader.
So 2 of these 3 ESBs work just fine, but 1 does not.
jms.connectionPool value in jbossesb.sar jbossesb-properties is set to 1000. -
2. Re: Oracle AQ and JBoss ESB
beve Jan 5, 2009 2:41 AM (in response to tschungelbuch)Hi,
So 2 of these 3 ESBs work just fine, but 1 does not.
Is there anything that differs in jboss-esb.xml for the two that work and the one that does not?For 2 schemas all works fine, for the 3rd schema when starting the ESB I get the following two errors and I have no clue why
Did the 3rd one work at one point or has it never worked? You might want to clean out the juddi to make sure that there are no stale eprs in there. This can be set in jbossesb-properties.xml by setting 'org.jboss.soa.esb.failure.detect.removeDeadEPR' in the core section to true.
regards,
/Daniel -
3. Re: Oracle AQ and JBoss ESB
tschungelbuch Jan 5, 2009 6:06 AM (in response to tschungelbuch)Hi Daniel
Thank you for the reply.
Is there anything that differs in jboss-esb.xml for the two that work and the one that does not?
The general structure of the three as well as many of the services are similar, do differ more in the property values than in actions and structures.
I am currently also cleaning the code and spring beans, hoping this may help.
Did the 3rd one work at one point or has it never worked?
No it has never worked.
I set the removeDeadEPR in the core section, but with no effect.
Kind regards
Tschungelbuch -
4. Re: Oracle AQ and JBoss ESB
tschungelbuch Jan 5, 2009 11:35 AM (in response to tschungelbuch)I can also see on the database side that the sessions are created for each of the error message occurences until the number of sessions exceeds.
Further messages between the already show ones are:org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsXAConnectionFactory@2f6e67 to the name XAConnectionFactory org.mockejb.jndi.MockContext] Bound object hello to the name KURTSTAM org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsConnectionFactory@10ca790 to the name ConnectionFactory org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsQueueConnectionFactory@1cd14d1 to the name QueueConnectionFactory org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsXAQueueConnectionFactory@ec8f6e to the name XAQueueConnectionFactory org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsXATopicConnectionFactory@bc8d97 to the name XATopicConnectionFactory org.mockejb.jndi.MockContext] Bound object oracle.jms.AQjmsTopicConnectionFactory@f3ed4d to the name TopicConnectionFactory org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.AQ$_ESB_2_ORACLE_500_E to the name AQ$_ESB_2_ORACLE_500_E org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.AQ$_ORACLE_2_ESB_500_E to the name AQ$_ORACLE_2_ESB_500_E org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.AQ$_ORACLE_ESB_AWARE_500_E to the name AQ$_ORACLE_ESB_AWARE_500_E org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.ESB_2_ORACLE_500 to the name ESB_2_ORACLE_500 org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.ORACLE_2_ESB_500 to the name ORACLE_2_ESB_500 org.mockejb.jndi.MockContext] Bound object SCHEMA_NAME.ORACLE_ESB_AWARE_500 to the name ORACLE_ESB_AWARE_500
and this goes on forever.
Kind regards
Tschungelbuch -
5. Re: Oracle AQ and JBoss ESB
tschungelbuch Jan 6, 2009 12:57 PM (in response to tschungelbuch)I was actually able to solve this issue based on the forum entry of bowlere:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=135536
So I updated my platform toJBoss_SOA_Platform 4.3.GA
and everything runs as expected.
Thanks for help and reviews.
Kind regards
Tschungelbuch