Hi,
I have a question regarding securing JBoss Messaging. Is it enough to secure
the naming provider aka initial context factory? In this scenario the
credentials would be provided in the properties java.naming.security.principal
and
java.naming.security.credentials passed to the initial conte
Thanks for the tip. However I can't do anything on the side of the application
which uses the odd correlation id or the selector as it is closed source. So I
have to deal with that in JBoss messaging. Any ideas to that?
I guess that the correlation id is a string is part of Sun's JMS spec?
View
Hi all,
I got following error with JBoss messaging:
| 15:29:00,896 WARN [Selector] Invalid selector:
JMSCorrelationID=1179926940029
| java.lang.Exception: Bad Object: expected 'String' got 'Long' for
operation: 0:EQUAL(
| [EMAIL PROTECTED]
| 1179926940029
| )
|
| at
Hi Peter,
thanks that helped. I also had to add trove.jar in the same directory.
Thanks!
Sebastian
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025485#4025485
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025485
_
Hi!
I#ve got a problem with a test application I try to write. If I execute the
following piece of code, I get the exception "java.lang.NoClassDefFoundError:
org/jboss/aop/WeavingStrategy" on the last line. I don't know at all what to do
with it. Google and a forum search didn't turn up anythin