https://issues.apache.org/bugzilla/show_bug.cgi?id=51667
Bug #: 51667
Summary: Weblogic 10.3.4, Access denied to resource
Product: JMeter
Version: 2.4
Platform: HP
OS/Version: HP-UX
Status: NEW
Severity: normal
Priority: P2
Component: Main
AssignedTo: [email protected]
ReportedBy: [email protected]
Classification: Unclassified
Created attachment 27393
--> https://issues.apache.org/bugzilla/attachment.cgi?id=27393
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.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
