-
1. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
adrian.brock Mar 13, 2002 6:59 AM (in response to chrisp)Can you post the stack trace?
I guess there is some problem with your ip config?
Regards,
Adrian -
2. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
chrisp Mar 13, 2002 9:46 AM (in response to chrisp)OK - here's the server log. I agree with that it looks like an ipconfig problem, but everything else seems OK.
-
3. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
chrisp Mar 13, 2002 10:02 AM (in response to chrisp)Damn...I meant to yank out a specific stack trace too. Take 2:
From line 371 of server.log:
[11:46:01,215,ClientUserTransactionService] Starting
[11:46:03,543,ClientUserTransactionService] Stopped
java.net.UnknownHostException: file
at java.net.InetAddress.getAllByName0(InetAddress.java:571)
at java.net.InetAddress.getAllByName0(InetAddress.java:540)
at java.net.InetAddress.getByName(InetAddress.java:449)
at java.net.Socket.(Socket.java:100)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:102)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:776)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:293)
at org.jnp.interfaces.NamingContext.bind(NamingContext.java:286)
at javax.naming.InitialContext.bind(InitialContext.java:358)
at org.jboss.tm.usertx.server.ClientUserTransactionService.startService(ClientUserTransactionService.java:73)
at org.jboss.util.ServiceMBeanSupport.start(ServiceMBeanSupport.java:103)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.configuration.ConfigurationService$ServiceProxy.invoke(ConfigurationService.java:967)
at $Proxy0.start(Unknown Source)
at org.jboss.util.ServiceControl.start(ServiceControl.java:79)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.Main.(Main.java:208)
at org.jboss.Main$1.run(Main.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:106) -
4. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
adrian.brock Mar 13, 2002 11:10 AM (in response to chrisp)Why do you have your naming provider url set to
file:/tmp?
Have a look at jndi.properties and remove this line.
This should only be set for clients.
Regards,
Adrian -
5. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
chrisp Mar 13, 2002 12:35 PM (in response to chrisp)Hmmm...that won't help, will it?
It's being picked up from within %JAVA_HOME%/lib or %JAVA_HOME%/jre/lib, so I guess it's the default JRE/JDK install value.
Thanks for your help. I _knew_ it was a dumb question.... -
6. Re: JBoss 2.4.4/Tomcat 4.0.1 bundle woes
chrisp Mar 15, 2002 8:51 AM (in response to chrisp)Following on from what I said - a correction. The default install for the JDK/JRE doesn't set a jndi.properties AFAICS, so _I_ must have put one in at some time.... Bizarre. Must have been a Friday afternoon thing. Either that, or I'm finally going senile! :-7