Forget my last post. I used by mistake jboss 4.0.2 which has a bug
that causes the problem in my first post.
Version 4.0.3 RC1 fixes the problem
of just being able to use new InitialContext
and not generating the JNDI error...
[JBAS-1892] - hajndi-jms-ds.xml uses the wrong connection factory
I found the problem.
The MDB described above can reply to messages whose
replyTo field is set. To get the connection factory to create
a connection to that replyTo destination, it does a new InitialContext()
in the MDB. This worked in non-clustered environments, but
as I pointed out, not in a
Hello,
I have jboss-4.0.3RC1 installed on 2 machines. I do a "run -c all"
to both and get a cluster of nodes going. I deploy an MDB to
the farm folder in one and it gets distributed to the other node fine.
I fire up a client to send 10 JMS messages to the MDB queue on
one of the machines. Some
One requirement we have is to authenticate using LDAP
and as I understand, this is possible with JBoss. But from
what I read so far, roles are also assumed to reside in
LDAP. What if roles are stored in some other place?
What are the plug in points in JBossSX to extend to
be able to accomplish
