Re: Glassfish 3.0.1 on the AS/400.

Thorbjorn,
I did get it running under the Classic JVM, but I probably didn't wait long
enough to get the admin console up. I had to comment out all the -XX
arguments and one that started with -client.

I've had problems getting working with the J9 JVM. It brings the system to
it's knees. Takes about 10-15 minutes to even sign-on. It's our development
partition so it doesn't have tons of memory, but it's usually pretty fast. I
might try to add some of the -XX arguments back to see if the work with the
J9 JVM. I think most of those are for performance.

I did just notice something too. I went to see which JVM arguments I
commented out and they have been deleted. GlassFish must update the
domain.xml file on boot-up. I'm definitely not a GlassFish pro so I should
probably read about that.

--
James R. Perkins


2010/9/16 Thorbjørn Ravn Andersen <thunderaxiom@xxxxxxxxxxx>

I am currently looking into what OSGi could buy us (oh, library lists :) )
so I found that Glassfish can run in other OSGi containers than the default
Apache Felix.

Here the --verbose flag to asadmin was mentioned so it shows the JVM
invocation command which might make your investigation easier :)

C:\Users\TRA\Downloads\x\glassfish-3.0.1\glassfishv3\glassfish>bin\asadmin
start-domain --verbose
16-09-2010 15:06:29 com.sun.enterprise.admin.launcher.GFLauncherLogger info
INFO: JVM invocation command line:
C:\Program Files\Java\jre6\bin\java.exe
-cp

C:/Users/TRA/Downloads/x/glassfish-3.0.1/glassfishv3/glassfish/modules/glass
fish.jar
-XX:+UnlockDiagnosticVMOptions
-XX:MaxPermSize=192m
-XX:NewRatio=2
-XX:+LogVMOutput

-XX:LogFile=C:\Users\TRA\Downloads\x\glassfish-3.0.1\glassfishv3\glassfish\d
omains\domain1/logs/jvm.log
-Xmx512m

-javaagent:C:/Users/TRA/Downloads/x/glassfish-3.0.1/glassfishv3/glassfish/li
b/monitor/btrace-agent.jar=unsafe=true,noServer=true
.....

Did you make further progress?

/Thorbjørn