Diff between AQ & JMS internal listening channel

Question

Hi,
we have configured the oracle b2b 11g server to support ebMS protocol. Tried sending the outbound message from host trading partner to remote trading partner. The outbound message was picked up by the host b2b server over the default queue (IP_OUT_QUEUE) and it had processed the outbound message successfully and send it to remote trading partner. Now i am trying to post a outbound message with the same set of properties over jms queues to host b2b server. It is throwing the following error. Can someone help me out to ounderstand the behaviour between AQ & JMS integration to the Oracle b2b server through internal listening channel?
2009-12-17T10:41:54.406+00:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a59f29] [userId: <anonymous>] [ecid: 0000IMN9ud6Fw000jzwkno1B9Z400000Ia,0] [APP: soa-infra] Error -: B2B-50083: Document protocol identification error.[[
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:4203)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:1850)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1395)
at oracle.tip.b2b.engine.Engine.incomingContinueProcess(Engine.java:3216)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2960)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:540)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:200)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
AS Properties used
user=POC_SOAINFRA
password=poc
url=jdbcracle:thin10.26.248.158:1522rcl
replyToMsgID =
from = BT
to = TP1
doctypeName = bcRequestOrderWLRv13_rs_DT
doctypeRevision = 1.0
payload = ./BT_12345678.xml
attachment =
JMS Properties Used
destination=jms/b2b/B2B_OUT_QUEUE
cf=jms/b2b/B2BQueueConnectionFactory
factory=weblogic.jndi.WLInitialContextFactory
url=t3://10.26.248.244:61001
replyToMsgID =
from = BT
to = TP1
msgType = 2
doctypeName = bcRequestOrderWLRv13_rs_DT
doctypeRevision = 1.0
eventName = rsConfirmOrder
payload = ./BT_12345678.xml
Even i have tried removing the msgType & eventName JMS properties as well but no luck.
Regards,
Bp

Answer 1

Hi Nitesh,
Ok, I have done one change that i have enabled the internal option for the jms listening channel configured for the host application. Now the jms outbound message is getting failed with the following error. So I am thinking that the unsuccessfull message processing is due to the db issue then. Is my understanding correct?
Informational -: B2B-50014: General Error: Informational -: B2B-50025: Repository error: Informational -: B2B-50025: Repository error
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1351)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:738)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3077)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2706)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:540)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:200)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: Informational -: B2B-50025: Repository error: Informational -: B2B-50025: Repository error
at oracle.tip.b2b.msgproc.DbAccess.formExtB2bMsgForBatch(DbAccess.java:1646)
at oracle.tip.b2b.msgproc.DbAccess.formExtB2bMsg(DbAccess.java:1358)
at oracle.tip.b2b.msgproc.Response.outgoingResponsePostColab(Response.java:1053)
at oracle.tip.b2b.msgproc.Response.outgoingResponse(Response.java:948)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1298)
... 8 more
Caused by: Informational -: B2B-50025: Repository error
at oracle.tip.b2b.msgproc.DbAccess.formExtB2bMsgForBatch(DbAccess.java:1383)
... 12 more
Regards,
Baskaran