OpenJMS Alpha and JMeter

2006-12-05 Thread Hemant Gaur
Hi,
I am trying to run the jmeter performance tests on the OpenJMS. Though I
am able to get the tests running and results for release version  there
is an exception thrown in the duable/persistant subscriber for the
OpenJMS alpha.
Mismatched destination properties for destination with
name=TOOL.DEFAULT.TOPIC0
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.getDestination(ConsumerMan
agerImpl.java:772)
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.createInactiveDurableConsu
mer(ConsumerManagerImpl.java:571)
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.createDurableConsumer(Cons
umerManagerImpl.java:345)
at
org.exolab.jms.server.ServerSessionImpl.createDurableConsumer(ServerSess
ionImpl.java:343)
at
org.exolab.jms.server.net.RemoteServerSession.createDurableConsumer(Remo
teServerSession.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)


ON searching i found the explaination for this (By Tim Anderson):

The topic you are using doesn't have the same properties as
a destination with the same name, being managed by the server.
This will typically happen if you have used the
TopicSession.createTopic()method giving a name for a topic that is
persistent on the server. For persistent topics, you should look them up
using JNDI.
-Tim
==

As I dont build the JMeter or OpenJMS locally and hence have no control
over the source. I have this topic populated using the OpenJMS config
file using

AdministeredDestinations
  AdministeredTopic name=TOOL.DEFAULT.TOPIC0/
/AdministeredDestinations

Can there be any settings which makes me work this with the alpha
version. Things are already working with the same test case using the
OpenJMS release version.


Relevant code from the openJMS ConsumerManagerImpl.getDestination()

if(!destination.getClass().getName().equals(existing.getClass().getName(
)))
  throw new InvalidDestinationException(Mismatched
destination properties for destination with name= + name);
if(existing.getPersistent() != destination.getPersistent())
throw new InvalidDestinationException(Mismatched
destination properties for destination with name= + name);



Thanks,
Hemant Gaur


Re: OpenJMS Alpha and JMeter

2006-12-05 Thread Peter Lin

I would suggest asking openJMS what the error means.

peter

On 12/5/06, Hemant Gaur [EMAIL PROTECTED] wrote:


Hi,
I am trying to run the jmeter performance tests on the OpenJMS. Though I
am able to get the tests running and results for release version  there
is an exception thrown in the duable/persistant subscriber for the
OpenJMS alpha.
Mismatched destination properties for destination with
name=TOOL.DEFAULT.TOPIC0
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.getDestination(ConsumerMan
agerImpl.java:772)
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.createInactiveDurableConsu
mer(ConsumerManagerImpl.java:571)
at
org.exolab.jms.messagemgr.ConsumerManagerImpl.createDurableConsumer(Cons
umerManagerImpl.java:345)
at
org.exolab.jms.server.ServerSessionImpl.createDurableConsumer(ServerSess
ionImpl.java:343)
at
org.exolab.jms.server.net.RemoteServerSession.createDurableConsumer(Remo
teServerSession.java:245)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
at
EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
Source)
at java.lang.Thread.run(Thread.java:595)


ON searching i found the explaination for this (By Tim Anderson):

The topic you are using doesn't have the same properties as
a destination with the same name, being managed by the server.
This will typically happen if you have used the
TopicSession.createTopic()method giving a name for a topic that is
persistent on the server. For persistent topics, you should look them up
using JNDI.
-Tim
==

As I dont build the JMeter or OpenJMS locally and hence have no control
over the source. I have this topic populated using the OpenJMS config
file using

AdministeredDestinations
  AdministeredTopic name=TOOL.DEFAULT.TOPIC0/
/AdministeredDestinations

Can there be any settings which makes me work this with the alpha
version. Things are already working with the same test case using the
OpenJMS release version.


Relevant code from the openJMS ConsumerManagerImpl.getDestination()

if(!destination.getClass().getName().equals(existing.getClass().getName(
)))
  throw new InvalidDestinationException(Mismatched
destination properties for destination with name= + name);
if(existing.getPersistent() != destination.getPersistent())
throw new InvalidDestinationException(Mismatched
destination properties for destination with name= + name);



Thanks,
Hemant Gaur




RE: OpenJMS Alpha and JMeter

2006-12-05 Thread Hemant Gaur
  The topic you are using doesn't have the same properties as
 a destination with the same name, being managed by the server.
 This will typically happen if you have used the
 TopicSession.createTopic()method giving a name for a topic that is
 persistent on the server. For persistent topics, you should look them
up
 using JNDI.
 -Tim

This is the reply from the OpenJMS folks.
Just thought some one have might come across this error.

Thanks,
Hemant

-Original Message-
From: Peter Lin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, December 05, 2006 5:53 PM
To: JMeter Users List
Subject: Re: OpenJMS Alpha and JMeter

I would suggest asking openJMS what the error means.

peter

On 12/5/06, Hemant Gaur [EMAIL PROTECTED] wrote:

 Hi,
 I am trying to run the jmeter performance tests on the OpenJMS. Though
I
 am able to get the tests running and results for release version
there
 is an exception thrown in the duable/persistant subscriber for the
 OpenJMS alpha.
 Mismatched destination properties for destination with
 name=TOOL.DEFAULT.TOPIC0
 at

org.exolab.jms.messagemgr.ConsumerManagerImpl.getDestination(ConsumerMan
 agerImpl.java:772)
 at

org.exolab.jms.messagemgr.ConsumerManagerImpl.createInactiveDurableConsu
 mer(ConsumerManagerImpl.java:571)
 at

org.exolab.jms.messagemgr.ConsumerManagerImpl.createDurableConsumer(Cons
 umerManagerImpl.java:345)
 at

org.exolab.jms.server.ServerSessionImpl.createDurableConsumer(ServerSess
 ionImpl.java:343)
 at

org.exolab.jms.server.net.RemoteServerSession.createDurableConsumer(Remo
 teServerSession.java:245)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
 a:39)
 at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
 Impl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at
 org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:553)
 at org.exolab.jms.net.orb.DefaultORB$1.run(DefaultORB.java:511)
 at
 EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown
 Source)
 at java.lang.Thread.run(Thread.java:595)


 ON searching i found the explaination for this (By Tim Anderson):
 
 The topic you are using doesn't have the same properties as
 a destination with the same name, being managed by the server.
 This will typically happen if you have used the
 TopicSession.createTopic()method giving a name for a topic that is
 persistent on the server. For persistent topics, you should look them
up
 using JNDI.
 -Tim
 ==

 As I dont build the JMeter or OpenJMS locally and hence have no
control
 over the source. I have this topic populated using the OpenJMS config
 file using

 AdministeredDestinations
   AdministeredTopic name=TOOL.DEFAULT.TOPIC0/
 /AdministeredDestinations

 Can there be any settings which makes me work this with the alpha
 version. Things are already working with the same test case using the
 OpenJMS release version.


 Relevant code from the openJMS ConsumerManagerImpl.getDestination()
 

if(!destination.getClass().getName().equals(existing.getClass().getName(
 )))
   throw new InvalidDestinationException(Mismatched
 destination properties for destination with name= + name);
 if(existing.getPersistent() !=
destination.getPersistent())
 throw new InvalidDestinationException(Mismatched
 destination properties for destination with name= + name);

 

 Thanks,
 Hemant Gaur



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]