-
1. Re: Getting QueueDepth with not working on JB400DDR2-3, work
jbossy Apr 28, 2004 1:27 PM (in response to jbossy)The topic title didnt turn out right. It should be:
Getting QueueDepth remotely with 3.2.3 working, not working on JB400DDR2-3 -
2. Re: Getting QueueDepth with not working on JB400DDR2-3, work
genman Apr 28, 2004 4:46 PM (in response to jbossy)
You should file a bug, and include the .jar files in your classpath. This might be an issue in the upcoming JBoss 3.2.4 release. As a work-around, you can always include the appropriate server .jar files in your classpath for your client. -
3. Re: Getting QueueDepth with not working on JB400DDR2-3, work
jbossy Apr 28, 2004 6:24 PM (in response to jbossy)The classpath I believe should be correct, if the new version jars are named the same way. Could it be that I am missing another jar? I guess I searched for the "Lorg..." exception and turned up nothing on google. The same process worked from a working 3.0.7,3.0.8, to 3.2.2 and 3.2.3 and those worked.
I forgot to mention that I did recompile everytime I swapped out the jar versions. I hope this is something trivial. You mentioned 3.2.4, I will see if it remains broken with the RC too.
Can anyone else help me out? Thanks in advance!
R -
4. Re: Getting QueueDepth with not working on JB400DDR2-3, work
genman Apr 28, 2004 7:15 PM (in response to jbossy)
The "Lorg" means it's trying to load the class for an array of them.
What you're really looking for is this file someplace:
org/jboss/mx/util/ObjectNamePatternHelper.class -
5. RE: Missing org/jboss/mx/util/ObjectNamePatternHelper.class
jbossy Apr 28, 2004 8:27 PM (in response to jbossy)"genman" wrote:
The "Lorg" means it's trying to load the class for an array of them.
What you're really looking for is this file someplace:
org/jboss/mx/util/ObjectNamePatternHelper.class
Well, you were right about it not working on 3.2.4RC1 the same way, I also came across another error where the JMS messages seem to have a new file size limit. Once adjusted the messages worked fine for the memory issue but still failed with the same exception. Ive never seen ObjectNamePatternHelper.class before and Im sure I dont reference it explicitly so I assume JBoss needs this for something internally.
Does anyone have a new example of how to access a jms destination object with the newer Jboss's ?
Thanks genman! The next thing I should do is see if I can find this class in other jars in the the client directory. I thought it would have broke in the compile step but it must be a runtime thing. If anyone else has more hints to this I'd appreciate it. If I don't have any success, I'll report a bug like you suggested. -
6. Re: RE: Missing org/jboss/mx/util/ObjectNamePatternHelper.cl
jbossy Apr 28, 2004 8:37 PM (in response to jbossy)"jbossy" wrote:
"genman" wrote:
The "Lorg" means it's trying to load the class for an array of them.
What you're really looking for is this file someplace:
org/jboss/mx/util/ObjectNamePatternHelper.class
Well, you were right about it not working on 3.2.4RC1 the same way, I also came across another error where the JMS messages seem to have a new file size limit. Once adjusted the messages worked fine for the memory issue but still failed with the same exception. Ive never seen ObjectNamePatternHelper.class before and Im sure I dont reference it explicitly so I assume JBoss needs this for something internally.
Does anyone have a new example of how to access a jms destination object with the newer Jboss's ?
Thanks genman! The next thing I should do is see if I can find this class in other jars in the the client directory. I thought it would have broke in the compile step but it must be a runtime thing. If anyone else has more hints to this I'd appreciate it. If I don't have any success, I'll report a bug like you suggested.
I wonder if the /mx should be /jmx perhaps .... still hunting it down ... -
7. RE: Missing org/jboss/mx/util/ObjectNamePatternHelper.class
jbossy Apr 28, 2004 11:11 PM (in response to jbossy)I was able to make things work on 3.2.4RC1 and 4.0.0DR3 but not on 4.0.0DR2 so I dumped DR2. It turns out that the class reported in the exception doesnt exist in a jar in the jboss/client dir, but rather in the jboss-jmx.jar in the jboss/lib dir. I place this jar in my standalone clients lib directory and added to the classpath and it worked. What I dont understand is that none of my code uses that resource, didnt even need to touch the source code.
Genman, thanks for clarifying some things so that I could follow through with a fix. The jboss community continues to impress me, awesome.
Hopefully others trying to access jmx stuff can use this info for the newer jbosses.