http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_jk1.2WithJBoss
Don't cross post.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137428#4137428
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137428
___
"[EMAIL PROTECTED]" wrote :
|
| Have you tried this solution discussed on the JIRA you linked?
|
|
How interesting... Srini must have discovered that fix after he left our
offices last week (he was helping us set up the Jboss cluster)!
Yes I tried that fix, and the problem has gone.
Sure, binding to an address is valid. If you don't specify an address, for
security reasons all services bind to localhost, which is pretty useless for a
production system.
BTW, setting -Djboss.bind.address with the same value is redundant if you use
-b.
Have you tried this solution discussed
Hmmm.. your reply got me thinking about the way I'm starting up the cluster
though. If I simply start up with
./run.sh -c all
I get no StackOverflowError. Before I go down any blind alleys here, can I
just confirm whether or not binding to a specific IP address is a valid
practice with JBos
"[EMAIL PROTECTED]" wrote : Have you edited conf/jndi.properties?
|
No, I haven't altered this file at all.
"[EMAIL PROTECTED]" wrote :
| Or, do any of your deployments package a jndi.properties file?
|
I haven't deployed anything of my own yet - I've just got a fresh copy of JBoss
4.2
Have you edited conf/jndi.properties? Or, do any of your deployments package a
jndi.properties file? Or, do you in any way set the java.naming.url system
property?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136324#4136324
Reply to the post :
http://www
