Bug 51667 - Weblogic 10.3.4, Access denied to resource
Summary: Weblogic 10.3.4, Access denied to resource
Status: RESOLVED DUPLICATE of bug 51691
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.4
Hardware: HP HP-UX
: P2 normal (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
Depends on:
Reported: 2011-08-16 20:25 UTC by thorsten
Modified: 2011-09-18 08:39 UTC (History)
1 user (show)

Updated JMSSampler code (19.15 KB, application/octet-stream)
2011-08-16 20:25 UTC, thorsten
jmeter log file (10.22 KB, application/octet-stream)
2011-08-16 20:26 UTC, thorsten

Note You need to log in before you can comment on or make changes to this bug.
Description thorsten 2011-08-16 20:25:48 UTC
Created attachment 27393 [details]
Updated JMSSampler code

During testing with Weblogic 10.3.4 the following error occured:

2011/08/02 16:52:20 WARN  - jmeter.protocol.jms.sampler.JMSSampler: Access denied to resource: type=<jms>, application=*************SystemModule, destinationType=queue, resource=*************Queue, action=send weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>, application=*************SystemModule, destinationType=queue, resource=*************Queue, action=send
	at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
	at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncTran(DispatcherAdapter.java:53)
	at weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1284)
	at weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:796)
	at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:541)
	at weblogic.jms.client.JMSProducer.sendWithListener(JMSProducer.java:394)
	at weblogic.jms.client.JMSProducer.send(JMSProducer.java:384)
	at weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:970)
	at org.apache.jmeter.protocol.jms.sampler.JMSSampler.sample(JMSSampler.java:139)
	at org.apache.jmeter.threads.JMeterThread.process_sampler(JMeterThread.java:348)
	at org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:243)
	at java.lang.Thread.run(Thread.java:662)

JMS user authentication was enabled (principals and credentials had to be set to connect to the JMS queue). This was solved by changing the initialisation and sending flow in the JMSSampler. The Attached JMSSampler is for sure not as good as the current implementation so it should not be changed. But the question is why this exception occurs with the current implementation in combination with Weblogic 10.3.4 and JMS user authentication? Maybe this is a weblogic issue and it should be reported to Weblogic (In that case please just close the issue). In case someone experiences a similar issue during testing with Weblogic 10.3.4 this code can maybe help in the situation.
Comment 1 thorsten 2011-08-16 20:26:49 UTC
Created attachment 27394 [details]
jmeter log file
Comment 2 Yaroslav 2011-08-21 06:16:33 UTC
I think your issue is related to 51691.
Comment 3 Philippe Mouawad 2011-09-18 08:38:11 UTC

*** This bug has been marked as a duplicate of bug 51691 ***
Comment 4 Philippe Mouawad 2011-09-18 08:38:54 UTC
If issue is still met with coming release 2.5.1 please reopen the bug.