This content has been marked as final. Show 4 replies
I'm not sure if I understood your case very well...
Are you using the JmsAdapter via JCA or a proxy service with JMS transport?
If you are using JmsAdapter via JCA, better to use the AqAdapter instead...
If you are using a proxy service with JMS transport... OSB doesn't know that's an AQ Topic, it will look like any other JMS implementation from OSB view... I recommend you to mark "Durable Subscription" but even then I'm not sure if that will create rows in aq$my_topic1_s...
Hope this helps...
I am not sure with OSB. I never seen the face of it. But when you say you are not able to see the subscriber in the table then you cannot consume the message.
Can quickly create AQJMS adapter service in bpel and select your topic and deploy the service in SOA server. Once it deploy go to the aq$my_topic1_s check if you able to see or not. And also try de-queue a message from the same topic.
I am using JMS Transport for Proxy Service and i have enabled the durable subscriber option as well. Please tell me how the entries in the subscribers table gets added.
You no need to do any thing. Just deploy your service and after that you should able to see record in the table. If record is not created then connection is not established between Topic and your service.
I have doubt with the endpoints only
Your JNDI name for connection factories given as aqjms/XATopicConnectionFactory and here its aqjms.XATopicConnectionFactory. Can you check it.
Apart of this everthing looks same. Try above and let us know it.
Edited by: Tarak on Nov 1, 2012 3:36 PM