Skip to main content

Wierd problem trying to start domain with soylatte jdk 6 ....

2 replies [Last post]
curtisa
Offline
Joined: 2006-07-03
Points: 0

Hi,
I'm using Mac 10.4 with soylatte jdk 6, Netbeans 6.5 and Glassfish v2.1 and I'm trying to deploy a web app which needs jdk 6 (hence the soylatte JDK).

Firstly I assume that since my app needs jdk 6, I need to start the glassfish domain with java 6. So ../config/asenv.conf has env 'AS_JAVA' pointing to my soylatte JDK. I'm assuming this because if I start with 1.5 and try to deploy my app, I get the old 'wrong major / minor version number' error message.

But then the problem I'm seeing is that when I try to start the domain with the 1.6 jdk it falls over at the point where it's initializing the AMX Beans. Specifically, it looks like it's trying to bind the rmi-jmx-connector to an external IP address rather than (presumably) localhost.

The error is ...

[#|2009-05-07T17:13:19.464+0200|SEVERE|sun-appserver9.1|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@1d0bc85;com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://67.215.65.132:8686/management/rmi-jmx-connector]: javax.naming.CommunicationException ............

After checking that IP address, it seems it's actually an opendns address (and I use opendns for external dns resolution).

So does anyone know what's going wrong here please (the domain starts fine when I have AS_JAVA set to the 1.5 JDK but not when I try to start with 1.6. Is there some AMX config setting somewhere ?

Any ideas please?

Thanks,
Alex

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Wolfram Rittmeyer

glassfish@javadesktop.org wrote:
> Hi,
> I'm using Mac 10.4 with soylatte jdk 6, Netbeans 6.5 and Glassfish v2.1 and I'm trying to deploy a web app which needs jdk 6 (hence the soylatte JDK).

Whow this really works I sometimes use Tiger and would like to use
Soylatte myself. I had some difficulties some time ago and from the
messages Soylatte printed (which I do not recall) I assumed even
Soylatte would run on Leopard only. This is really interesting.

...

I have just started GlassFish v2UR2 using Soylatte and noticed the same
behaviour you have posted. While Soylatte uses the IP address in my
case, the Mac JDK uses the hostname. BTW: Soylatte uses the IP address
with v3 as well. Of course I cannot compare v3 with Tigers JDK 5
implementation since v3 needs JDK 6.

Thanks, curtisa, for reminding me of Soylatte. Now I can use v3 on Tiger
again ;-)

--
Wolfram

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: users-help@glassfish.dev.java.net

curtisa
Offline
Joined: 2006-07-03
Points: 0

Ok I've fixed it so just in case anyone else has something similar ....

There must be some difference between the two jdks with picking up system envs because when I started glassfish with 1.5 I could see it was using a hostname which *wasn't* in my /etc/hosts/ file. So, I added this same name as an alias in there and now it works. (ie I'm gussing soylatte looks in there but sun jdk doesn't)