Hello all, I've been attempting to use Camel/Spring JMS with Weblogic Server (10.3.6) JMS destinations and it works just fine without secure destinations, but using secure destinations results in the exception: /weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>, application=jms_module, destinationType=queue, resource=jms_response, action=receive /
It appears that others in the Camel/Spring community have had similar issues (e.g. here <http://camel.465427.n5.nabble.com/JMS-message-to-Weblogic-gt-Security-Exception-Access-denied-to-resource-td1438688.html> ). Since there was no reasonable solution to this problem I did some research and created a new thread factory that creates Threads with the passed-in Runnable.run proxied through a Weblogic secured PrivilegedAction. The task executor for Camel and Spring JMS listeners is modified to use the new task factory to ensure all subscribing threads are 'privileged'. I've provided some code on github <https://github.com/dmacdonald2013/weblogic-jms-spring> with an example/test of publishing and subscribing to a secure WebLogic JMS destination using both Camel and Spring Stand-alone. Hopefully someone else in the Camel/Spring community benefits from this (and feedback is welcome!) - we needed Camel to do some things that Oracle Service Bus just isn't cut out for and the inability to use secure destination was a big blocker. Cheers, David -- View this message in context: http://camel.465427.n5.nabble.com/Weblogic-JMS-Security-Issues-A-possible-resolution-tp5735108.html Sent from the Camel - Users mailing list archive at Nabble.com.
