Comments on: Using LoadRunner Java Vusers with WebLogic JMS Queues/Topics

By: James

James — Mon, 29 Jun 2009 07:17:45 +0000

Any suggestions on how to measure the response time for an asynchronous queue? To clarify, the system under test:
- receives a message on one queue (upstream side)
- publishes a message on another queue (downstream side)
- an operation may be performed on a file detailed in the XML of the original message

All I’m measuring at the moment is how long the first queue takes to process the message sent to it and to respond with a green light.

By: hanumanthu

hanumanthu — Tue, 31 Mar 2009 19:15:59 +0000

Hi,
I am facing the problem in Java Vuser.
I need to publish the xml to the QUEUE.when I used the above script and modified accordingly
this is the error I am getting

Error: System.err: java.lang.NullPointerException Error
System.err: at Actions.action(Actions.java:112) Error
Error: java.lang.NullPointerException
Error: at Actions.action(Actions.java:112)

By: Tim

Tim — Fri, 07 Nov 2008 18:38:48 +0000

I wrote it from scratch in a simple java class then transferred the logic to LR. If u were doing soap over jms u would still need to do it in java AFAIK. Webservices typically http…

By: selva

selva — Fri, 07 Nov 2008 09:55:28 +0000

Tim,
An informative post ! I was searching for some information on load testing weblogic messages. This entry is a good starting point.
Did you record these things from the weblogic console or you wrote it from the scratch by understanding the individual calls & by filtering the messages out of them ?
My requirement is that, I need to use Rational Robot & Test Manager to test our weblogic system (Messages). I ‘ve good experience in LR (not with webservices protocol though).
You have used Java Vuser. What about webservices protocol ? Can we use them for testing these messages ? which one would be apt ? Do you have any idea on Rational tools & their support for this kind of testing ?

By: Tim

Tim — Mon, 22 Sep 2008 06:27:25 +0000

No problems. For JMS queue information I would recommend using JMX. Weblogic has its own implementation. For tips on how to do this, just search this blog for JMX.

Cheers
Tim

By: Senthil

Senthil — Mon, 22 Sep 2008 01:56:46 +0000

Awesome ! it worked really well . Thanks TKS !

I am also looking for some monitors which will allow me to monitor the JMS queues that is sent and received from WL using LR .I am thinking about sitescope but not sure if it supports JMS.

By: avinash

avinash — Fri, 15 Aug 2008 21:10:17 +0000

i have tried the topics example given above sun’s mq server. everything compiles and runs from loadrunner side telling that the messsages are sent to the server but the JMS server does not report of any messages reaching it. i have tried another example with the same configuration using jmeter and that works fine.

By: shanthi

shanthi — Fri, 20 Jun 2008 13:39:25 +0000

Error: System.err: javax.naming.NameNotFoundException: Unable to resolve ‘BTQueueConnectionFactory’ Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'BTQueueConnectionFactory' Resolved ]; remaining name ‘BTQueueConnectionFactory’ Error
System.err: at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108) Error
System.err: at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290) Error
System.err: at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248) Error
System.err: at weblogic.jndi.internal.ServerNamingNode_815_WLStub.lookup(Unknown Source) Error
System.err: at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:375) Error
System.err: at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:363) Error
System.err: at javax.naming.InitialContext.lookup(InitialContext.java:351) Error
System.err: at Actions.init(Actions.java:52) Error
Error: System.err: Caused by: javax.naming.NameNotFoundException: Unable to resolve ‘BTQueueConnectionFactory’ Resolved Error
Error: System.err: at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:924) Error
System.err: at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:230) Error
System.err: at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:154) Error
System.err: at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188) Error
System.err: at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source) Error
System.err: at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492) Error
System.err: at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108) Error
System.err: at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435) Error
System.err: at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) Error
System.err: at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147) Error
System.err: at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430) Error
System.err: at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35) Error
System.err: at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224) Error
System.err: at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183) Error
Error: javax.naming.NameNotFoundException: Unable to resolve ‘BTQueueConnectionFactory’ Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'BTQueueConnectionFactory' Resolved ]; remaining name ‘BTQueueConnectionFactory’
Error: at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:290)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:248)
at weblogic.jndi.internal.ServerNamingNode_815_WLStub.lookup(Unknown Source)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:375)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:363)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at Actions.init(Actions.java:52)
Caused by: javax.naming.NameNotFoundException: Unable to resolve ‘BTQueueConnectionFactory’ Resolved
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:924)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:230)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:154)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:188)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
Vuser Terminated.

By: Tim

Tim — Fri, 30 May 2008 06:10:28 +0000

weblogic.jar is available from your Weblogic installation. I can’t post it here for both commercial and size reasons.

Regards,
Tim

By: SER

SER — Thu, 15 May 2008 16:03:37 +0000

Hi!
I couldn’t find the weblogic.jar. Could you please post a link to it?

Thanks