Lars,
I am not sure to know your exact problem, so just a few things that made
me think reading your logs:
- Overally, the apache2 startup seems fine to me, I'd blame the fact
that glassfish is not up and running well yet to be the reason for the
"Connection reset" entries regarding the apache2 proxying functionality.
This is more or less similar to what happens here on our apache2 reverse
proxy once glassfish is not running.
- In the glassfish log file, the
[...]
com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL
[rmi://rthus8026.rintra.ruag.com:8686/management/rmi-jmx-connector]:
javax.naming.CommunicationException [Root exception is
java.rmi.ConnectIOException: error during JRMP connection establishment;
nested exception is:
java.net.SocketTimeoutException: Read timed out]
[...]
seem to me to be the cause for your server not correctly comin' up.
Though I don't have a clue what exactly does happen here, I have seen
JMX related connection issues on Linux machines when, on the JMX server
host, the machine couldn't eventually resolve its own host name. Looking
at the fact that it seems to work once the server is running (how do you
get it started by the way, then?), and looking at where in the sysvinit
procedure you're starting it (not sure about where in the SuSE 10 sort
order S13 is to be found), I'd have a look at whether or not, the time
you're trying to start glassfish, your machine already is "online" and
"knows" both its host name and its IP address.
Maybe I am completely wrong on that, though, so wishing you good luck on
getting this fixed. If there's anything else I can do for you... :)
Cheers,
Kristian
--
Kristian Rink
cell : +49 176 2447 2771
business: http://www.planconnect.de
personal: http://pictorial.zimmer428.net
"we command the system. calling all recievers.
we are noisy people for a better living".
(covenant - "monochrome")