OSB - Problems connecting sync business service to resp. queue with login

Question

Hello,
I have a synchronous JMS business service which uses the MessageID correlation pattern with statically configured request and response JMS queues. The JMS queues are imported using a foreign JMS and a connection factory with credentials (username and password). The requests seem to work just fine (they are received at the foreign JMS) but I still have problems with the responses. I get the following log entries:
<Mar 31, 2010 1:50:10 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: ResponseEJB-8048850762288479454-46349ef3.127b3dbbff1.-7fe6 is unable to connect to the JMS destination: queue.local.name. The Error was:
javax.jms.JMSSecurityException: User: null is not authorized to read from destination queue.external.name>
It seems that the response is handled by a MDB which does not seem to use the username and password configured in the connection factory. Any ideas how to make it use the username and password of the connection factory to receive the response? I have tried both providing the connection factory for the response and leaving it empty (which would cause it to use the one from the request) - both with no success.
I am really stuck here..
Thanks,
Dimo

Answer 1

Alternatively you can try a very dirty way to make this work I think. The reason why the username in foreign server CF's username crednetials are not recognized is due to the fact that the deployment descriptors for the MDB should not specify a provider-URL and there should be a resource reference for the CF.
Business service with reply queues generate a MDB under the hood . You can try to edit the deployment descriptors for this MDB to make this to work.
Sample MDB weblogic-ejb-jar.xml for recognizing the foreign jms username
Foreign JMS
<foreign-server name=”ForeignServer”>
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name=”A”>
<local-jndi-name>A</local-jndi-name>
<remote-jndi-name>queue/A</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name=”FConf”>
<local-jndi-name>FConf</local-jndi-name>
<remote-jndi-name>ConnectionFactory</remote-jndi-name>
<username>esbuser</username>
<password-encrypted>{3DES}90sIZwo6Llr9r73p+VXkvQ==</password-encrypted>
</foreign-connection-factory>
<initial-context-factory>org.jnp.interfaces.NamingContextFactory</initial-context-factory>
<connection-url>jnp://localhost:1099</connection-url>
</foreign-server>
weblogic-ejb-jar.xml
<?xml version=’1.0′ encoding=’UTF-8′?>
<web:weblogic-ejb-jar xmlns:web=”http://www.bea.com/ns/weblogic/weblogic-ejb-jar”>
<web:weblogic-enterprise-bean>
<web:ejb-name>RequestEJB-2518965873970113789–2352f820.127bd3f293c.-7fdb</web:ejb-name>
<web:message-driven-descriptor>
<web:pool>
<web:max-beans-in-free-pool>1000</web:max-beans-in-free-pool>
<web:initial-beans-in-free-pool>1</web:initial-beans-in-free-pool>
</web:pool>
<web:destination-jndi-name>A</web:destination-jndi-name>
<web:connection-factory-jndi-name>FConf</web:connection-factory-jndi-name>
</web:message-driven-descriptor>
<web:transaction-descriptor>
<web:trans-timeout-seconds>600</web:trans-timeout-seconds>
</web:transaction-descriptor>
<web:resource-description>
<web:res-ref-name>jms/ConnectionFactory</web:res-ref-name>
<web:jndi-name>FConf</web:jndi-name>
</web:resource-description>
<web:resource-description>
<web:res-ref-name>jms/QueueName</web:res-ref-name>
<web:jndi-name>A</web:jndi-name>
</web:resource-description>
</web:weblogic-enterprise-bean>
</web:weblogic-ejb-jar>
This needs to be done each time OSB generates a new MDB for the business service - eg. when the business service definition changes.
Regards,
Atheek