Not able to publish message into JMS Topic ( OJMS ) from my BPEL proce
674992Jun 18 2009 — edited Jun 18 2009I am not able to publish message into JMS Topic ( OJMS ) from my BPEL process.
I have tested this by giving single record , able to insert the single record in the JMS topic. But if try to publish around 2000 records it gives below error.
Local logs it was showing following logs.
009-06-18 17:34:11,440> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user jmsuser
<2009-06-18 17:34:11,486> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #136
<2009-06-18 17:34:41,643> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user jmsuser
<2009-06-18 17:34:41,658> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #137
<2009-06-18 17:35:12,080> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user jmsuser
<2009-06-18 17:35:12,111> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #138
<2009-06-18 17:35:42,221> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user jmsuser
<2009-06-18 17:35:42,252> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #139
<2009-06-18 17:36:12,315> <INFO> <default.collaxa.cube.ws> <JMSAdapter::Outbound> Created new managed connection for JMS user jmsuser
<2009-06-18 17:36:12,361> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JMSMessageConsumer_init: Retrying connection; attempt #140
<2009-06-18 17:36:12,361> <WARN> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12134
ERRJMS_ERR_CR_TOPIC_CONS.
Error while creating Topic consumer:.
Please examine the log file to determine the problem.
What is the threshold, what should be the size of the message that can be published on JMS topic or this is different error.
Thanks for your help.
Keviv