Problem getting access to a JMS queue after being authenticated using JMS Point-to-Point

[David McInerney]

Hi All,

I am trying to send JMS messages to a JMS queue using JMeter (JMS
Point-to-Point)
I am using weblogic92 and the queue is secured.

I have been looking through the logs & I can see the user being
secured but i'm not able to get access to the queues

I have set the:
Java.naming.security.principal to the correct username &
Java.naming.security.credentials to the correct password
under the JNDI Properties

I don't know where to go from here to allow my message access to the queues.
Any help would be greatly apprieciated.

Kind Regards,
David.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[sebb-2-2]

On 08/07/2008, David McInerney <[hidden email]> wrote:
> Hi All,
>
>  I am trying to send JMS messages to a JMS queue using JMeter (JMS
>  Point-to-Point)
>  I am using weblogic92 and the queue is secured.
>
>  I have been looking through the logs & I can see the user being
>  secured but i'm not able to get access to the queues

Which logs are those?

>  I have set the:
>  Java.naming.security.principal to the correct username &
>  Java.naming.security.credentials to the correct password
>  under the JNDI Properties
>
>  I don't know where to go from here to allow my message access to the queues.
>  Any help would be greatly apprieciated.
>

Are there any error messages in the jmeter log?

>  Kind Regards,
>  David.
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[david.mc.inerney]

Hi Sebb,

I am could see the user being authenticated in the weblogic logs.

The error in the Jmeter log is outlined below.

Thanks again.

2008/07/11 09:29:34 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(true,*local*)
2008/07/11 09:29:39 INFO  - jmeter.engine.StandardJMeterEngine: Starting
1
threads for group Thread Group. Ramp up = 1.
2008/07/11 09:29:39 INFO  - jmeter.engine.StandardJMeterEngine: Continue
on
error
2008/07/11 09:29:39 INFO  - jmeter.threads.JMeterThread: Thread Thread
Group
1-1 started
2008/07/11 09:29:40 WARN  - jmeter.protocol.jms.sampler.JMSSampler:
Access
denied to resource: type=<jms>, application=IT_JMS_MODULE_TEST,
destinationType=queue, resource=TEST intput queue, action=send
weblogic.jms.common.JMSSecurityException: Access denied to resource:
type=<jms>, application=IT_JMS_MODULE_TEST, destinationType=queue,
resource=TEST intput queue, action=send
       at
weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(
Dispa
tcherAdapter.java:110)
       at
weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherA
dapte
r.java:61)
       at
weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1061)
       at
weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
       at
weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
       at weblogic.jms.client.JMSProducer.send(JMSProducer.java:337)
       at
weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:966)
       at
org.apache.jmeter.protocol.jms.sampler.JMSSampler.sample(JMSSampler.java
:131)
       at
org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:300)
       at java.lang.Thread.run(Thread.java:595)
Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
resource: type=<jms>, application=IT_JMS_MODULE_TEST,
destinationType=queue,
resource=TEST intput queue, action=send
       at
weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
       at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
       at
weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:10
18)
       at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1358)
       at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1419)
       at
weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.
java:
759)
       at
weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsyncInternal(Dispa
tcher
Impl.java:129)
       at
weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImp
l.jav
a:112)
       at
weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapte
r.jav
a:84)
       at weblogic.jms.dispatcher.Request.run(Request.java:77)
       at
weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManage
rImpl
.java:518)
       at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
       at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
resource: type=<jms>, application=IT_JMS_MODULE_TEST,
destinationType=queue,
resource=TEST intput queue, action=send
       at
weblogic.messaging.dispatcher.Request.getResult(Request.java:291)
       at weblogic.jms.dispatcher.Request.getResult(Request.java:49)
       ... 11 more
Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
resource: type=<jms>, application=IT_JMS_MODULE_TEST,
destinationType=queue,
resource=TEST intput queue, action=send
       at
weblogic.jms.common.JMSSecurityHelper.checkPermission(JMSSecurityHelper.
java:
157)
       at
weblogic.jms.common.JMSSecurityHelper.checkPermission(JMSSecurityHelper.
java:
131)
       at
weblogic.jms.backend.BEDestinationSecurityImpl.checkSendPermission(BEDes
tinat
ionSecurityImpl.java:80)
       at
weblogic.jms.backend.BEDestinationImpl.checkPermission(BEDestinationImpl
.java
:2444)
       at
weblogic.jms.backend.BEDestinationImpl.sendInitialize(BEDestinationImpl.
java:
1520)
       at
weblogic.jms.backend.BEDestinationImpl.send(BEDestinationImpl.java:2026)
       at
weblogic.jms.backend.BEDestinationImpl.wrappedSend(BEDestinationImpl.jav
a:199
8)
       at
weblogic.jms.backend.BEDestinationImpl.invoke(BEDestinationImpl.java:149
4)
       at
weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.
java:
759)
       at
weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServe
rRef.
java:276)
       at
weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(Dispatch
erSer
verRef.java:141)
       at
weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherS
erver
Ref.java:36)
       at
weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServer
Ref.j
ava:112)
       ... 2 more

2008/07/11 09:29:40 INFO  - jmeter.threads.JMeterThread: Thread Thread
Group
1-1 is done
2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Ending
thread
Thread Group 1-1
2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Stopping
test

2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine:
Notifying
test listeners of end of test
2008/07/11 09:29:40 INFO  - jmeter.gui.util.JMeterMenuBar:
setRunning(false,*local*)
2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Test has
ended

-----Original Message-----
From: sebb [mailto:[hidden email]]
Sent: 10 July 2008 14:36
To: JMeter Users List
Subject: Re: Problem getting access to a JMS queue after being
authenticated using JMS Point-to-Point

On 08/07/2008, David McInerney <[hidden email]> wrote:
> Hi All,
>
>  I am trying to send JMS messages to a JMS queue using JMeter (JMS
>  Point-to-Point)
>  I am using weblogic92 and the queue is secured.
>
>  I have been looking through the logs & I can see the user being
>  secured but i'm not able to get access to the queues

Which logs are those?

>  I have set the:
>  Java.naming.security.principal to the correct username &
>  Java.naming.security.credentials to the correct password
>  under the JNDI Properties
>
>  I don't know where to go from here to allow my message access to the
queues.
>  Any help would be greatly apprieciated.
>

Are there any error messages in the jmeter log?

>  Kind Regards,
>  David.
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]




This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[sebb-2-2]

On 11/07/2008, [hidden email]
<[hidden email]> wrote:

> Hi Sebb,
>
>  I am could see the user being authenticated in the weblogic logs.
>
>  The error in the Jmeter log is outlined below.
>
>  Thanks again.
>
>  2008/07/11 09:29:34 INFO  - jmeter.gui.util.JMeterMenuBar:
>  setRunning(true,*local*)
>  2008/07/11 09:29:39 INFO  - jmeter.engine.StandardJMeterEngine: Starting
>  1
>  threads for group Thread Group. Ramp up = 1.
>  2008/07/11 09:29:39 INFO  - jmeter.engine.StandardJMeterEngine: Continue
>  on
>  error
>  2008/07/11 09:29:39 INFO  - jmeter.threads.JMeterThread: Thread Thread
>  Group
>  1-1 started
>  2008/07/11 09:29:40 WARN  - jmeter.protocol.jms.sampler.JMSSampler:
>  Access
>  denied to resource: type=<jms>, application=IT_JMS_MODULE_TEST,
>  destinationType=queue, resource=TEST intput queue, action=send
>  weblogic.jms.common.JMSSecurityException: Access denied to resource:
>  type=<jms>, application=IT_JMS_MODULE_TEST, destinationType=queue,
>  resource=TEST intput queue, action=send
>        at

I don't know much about JMS, but the queue name looks a bit odd:

TEST intput queue

should that be:

TEST input queue

instead?

If the queue name is correct, then perhaps JMeter needs to do
something else to authorize itself - but I've no idea what.

If anyone can provide details of what is missing, it can be added to JMeter.

>  weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(
>  Dispa
>  tcherAdapter.java:110)
>        at
>  weblogic.jms.dispatcher.DispatcherAdapter.dispatchSyncNoTran(DispatcherA
>  dapte
>  r.java:61)
>        at
>  weblogic.jms.client.JMSProducer.toFEProducer(JMSProducer.java:1061)
>        at
>  weblogic.jms.client.JMSProducer.deliveryInternal(JMSProducer.java:670)
>        at
>  weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:455)
>        at weblogic.jms.client.JMSProducer.send(JMSProducer.java:337)
>        at
>  weblogic.jms.client.WLProducerImpl.send(WLProducerImpl.java:966)
>        at
>  org.apache.jmeter.protocol.jms.sampler.JMSSampler.sample(JMSSampler.java
>  :131)
>        at
>  org.apache.jmeter.threads.JMeterThread.run(JMeterThread.java:300)
>        at java.lang.Thread.run(Thread.java:595)
>  Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
>  resource: type=<jms>, application=IT_JMS_MODULE_TEST,
>  destinationType=queue,
>  resource=TEST intput queue, action=send
>        at
>  weblogic.jms.dispatcher.Request.handleThrowable(Request.java:63)
>        at weblogic.jms.dispatcher.Request.getResult(Request.java:51)
>        at
>  weblogic.jms.frontend.FEProducer.sendRetryDestination(FEProducer.java:10
>  18)
>        at weblogic.jms.frontend.FEProducer.send(FEProducer.java:1358)
>        at weblogic.jms.frontend.FEProducer.invoke(FEProducer.java:1419)
>        at
>  weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.
>  java:
>  759)
>        at
>  weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsyncInternal(Dispa
>  tcher
>  Impl.java:129)
>        at
>  weblogic.messaging.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImp
>  l.jav
>  a:112)
>        at
>  weblogic.jms.dispatcher.DispatcherAdapter.dispatchAsync(DispatcherAdapte
>  r.jav
>  a:84)
>        at weblogic.jms.dispatcher.Request.run(Request.java:77)
>        at
>  weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManage
>  rImpl
>  .java:518)
>        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
>        at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
>  Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
>  resource: type=<jms>, application=IT_JMS_MODULE_TEST,
>  destinationType=queue,
>  resource=TEST intput queue, action=send
>        at
>  weblogic.messaging.dispatcher.Request.getResult(Request.java:291)
>        at weblogic.jms.dispatcher.Request.getResult(Request.java:49)
>        ... 11 more
>  Caused by: weblogic.jms.common.JMSSecurityException: Access denied to
>  resource: type=<jms>, application=IT_JMS_MODULE_TEST,
>  destinationType=queue,
>  resource=TEST intput queue, action=send
>        at
>  weblogic.jms.common.JMSSecurityHelper.checkPermission(JMSSecurityHelper.
>  java:
>  157)
>        at
>  weblogic.jms.common.JMSSecurityHelper.checkPermission(JMSSecurityHelper.
>  java:
>  131)
>        at
>  weblogic.jms.backend.BEDestinationSecurityImpl.checkSendPermission(BEDes
>  tinat
>  ionSecurityImpl.java:80)
>        at
>  weblogic.jms.backend.BEDestinationImpl.checkPermission(BEDestinationImpl
>  .java
>  :2444)
>        at
>  weblogic.jms.backend.BEDestinationImpl.sendInitialize(BEDestinationImpl.
>  java:
>  1520)
>        at
>  weblogic.jms.backend.BEDestinationImpl.send(BEDestinationImpl.java:2026)
>        at
>  weblogic.jms.backend.BEDestinationImpl.wrappedSend(BEDestinationImpl.jav
>  a:199
>  8)
>        at
>  weblogic.jms.backend.BEDestinationImpl.invoke(BEDestinationImpl.java:149
>  4)
>        at
>  weblogic.messaging.dispatcher.Request.wrappedFiniteStateMachine(Request.
>  java:
>  759)
>        at
>  weblogic.messaging.dispatcher.DispatcherServerRef.invoke(DispatcherServe
>  rRef.
>  java:276)
>        at
>  weblogic.messaging.dispatcher.DispatcherServerRef.handleRequest(Dispatch
>  erSer
>  verRef.java:141)
>        at
>  weblogic.messaging.dispatcher.DispatcherServerRef.access$000(DispatcherS
>  erver
>  Ref.java:36)
>        at
>  weblogic.messaging.dispatcher.DispatcherServerRef$2.run(DispatcherServer
>  Ref.j
>  ava:112)
>        ... 2 more
>
>  2008/07/11 09:29:40 INFO  - jmeter.threads.JMeterThread: Thread Thread
>  Group
>  1-1 is done
>  2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Ending
>  thread
>  Thread Group 1-1
>  2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Stopping
>  test
>
>  2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine:
>  Notifying
>  test listeners of end of test
>  2008/07/11 09:29:40 INFO  - jmeter.gui.util.JMeterMenuBar:
>  setRunning(false,*local*)
>  2008/07/11 09:29:40 INFO  - jmeter.engine.StandardJMeterEngine: Test has
>  ended
>
>
>  -----Original Message-----
>  From: sebb [mailto:[hidden email]]
>  Sent: 10 July 2008 14:36
>  To: JMeter Users List
>  Subject: Re: Problem getting access to a JMS queue after being
>  authenticated using JMS Point-to-Point
>
>  On 08/07/2008, David McInerney <[hidden email]> wrote:
>  > Hi All,
>  >
>  >  I am trying to send JMS messages to a JMS queue using JMeter (JMS
>  >  Point-to-Point)
>  >  I am using weblogic92 and the queue is secured.
>  >
>  >  I have been looking through the logs & I can see the user being
>  >  secured but i'm not able to get access to the queues
>
>  Which logs are those?
>
>  >  I have set the:
>  >  Java.naming.security.principal to the correct username &
>  >  Java.naming.security.credentials to the correct password
>  >  under the JNDI Properties
>  >
>  >  I don't know where to go from here to allow my message access to the
>  queues.
>  >  Any help would be greatly apprieciated.
>  >
>
>  Are there any error messages in the jmeter log?
>
>  >  Kind Regards,
>  >  David.
>  >
>  >  ---------------------------------------------------------------------
>  >  To unsubscribe, e-mail: [hidden email]
>  >  For additional commands, e-mail: [hidden email]
>  >
>  >
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>
>
>
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information.  If you have received it in error, please notify the sender immediately and delete the original.  Any other use of the email by you is prohibited.
>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]