RE: Glassfish 3.0.1 on the AS/400.

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


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx]
On Behalf Of James Perkins
Sent: 9. september 2010 22:00
To: Java Programming on and around the IBM i
Subject: Re: Glassfish 3.0.1 on the AS/400.

Just a general update. All the errors so far are all JVM command argument
errors. So far I've commented out of the -XX arguments in the
GLASSFISH_HOME/domains/domains1/config/domain.xml. I'm still getting other
errors, but again they are all command line arguments.

Looks like the main issue could be the IBM JVM.
--
James R. Perkins