Hello,
I have done already the scenario you specified as moving jndi.properties to
conf/ directory and remove the provider.url line.
But, No effects.
It gives the same error as I mensioned my previous post.
Is it need to set any Interceptors in the Application code?
Since, the appli
Try this really quick and let me know if you still have this problem. Then
we'll try to simplify scenario to see what is wrong.
1. Move jndi.properties file back into the /conf directory of bothe servers
(that is where JBoss is expecting it!!!).
2. From that file remove provider.url property (o
Hello,
Thanks once again for ur quick response.
"azhurakousky" wrote : 1. What was the reason for moving jndi.properties file
from "conf" to "lib" directory?
I assumed that the application needs jndi.properties for looking up the JNDI
Name. So, I thought the application will look on to the
1. What was the reason for moving jndi.properties file from "conf" to "lib"
directory?
2. Is node1 and node2 joined in JBoss Cluster or they are just two independent
nodes under RoundRobin controll of mod_jk? Seem to me you do not have JBoss
Cluster estalished and node1 and node2 are independent
Hello,
Thanks for your reply.
Actually, I have run the two servers named node1 and node2 with Apache modjk
load balancer by keeping node1 as the main node and it only bound the
queue/order and queue/mail.
I have did the below modification in both the server machines node1 as well as
node
NameNotFound is understandable since JBossMQ is deployed as singleton and I bet
this exception happens on the Node that does not have JBossMQ started. If you
were to look at the JndiView (via JMX console) you won't find any Queues and/or
Topics deployed. In oher words it is expected result if. .
