when starting glassfish, it fails when it attempts to initialize the AMX and JMX stuff. You get a connection refused because the jmx stuff is trying to connect to 169.254.x.x
I guess leopard uses this for it's wireless stuff now (the ip) and no amount of altering of network settings will work. I even tried routing all traffic to localhost from 169... No dice.
The fix: in the
jmx-connector accept-all="false" address="localhost" auth-realm-name="admin-realm" enabled="true" name="system" port="8686" protocol="rmi_jrmp" security-enabled="false"
line. By default, the enabled="true" is set. change this to enabled="false" You lose the ability to administer glassfish remotely, but at least it will start.
I'm sure glassfish will work on a patch, eventually.
5 comments:
Thanks ! :)
Thank you !!!
Thanks!
Works in debian lenny too.
Thanks,
works great for Win7/Sun App Server V8.2.
really nice :)
worked very well...
Post a Comment