Hello,

we have SUSE-Linux Enterprise Server 9 for PowerPC running on a IBM-iSeries. 
The JDK ist the IBMJava2-ppc64-142-3.
I tried jBoss-3.2.7 and jBoss 4.0.2. I changed the run.conf by 4.0.2. The 
'-server' Option is unknown by IBM-VM.
There are no other changes.
Both jBoss hang when starting. I must end them by CRTL-C.

boot.log from 3.2.7:

09:38:25,290 INFO  [Server] Starting JBoss (MX MicroKernel)...
  | 09:38:25,329 INFO  [Server] Release ID: JBoss [WonderLand] 3.2.7 (build: 
CVSTag=JBoss_3_2_7 date=200501280217)
  | 09:38:25,329 DEBUG [Server] Using config: [EMAIL PROTECTED]
  | 09:38:25,329 DEBUG [Server] Server type: class 
org.jboss.system.server.ServerImpl
  | 09:38:25,329 INFO  [Server] Home Dir: /home/bantest/jboss-3.2.7
  | 09:38:25,330 INFO  [Server] Home URL: file:/home/bantest/jboss-3.2.7/
  | 09:38:25,338 INFO  [Server] Library URL: file:/home/bantest/jboss-3.2.7/lib/
  | 09:38:25,340 INFO  [Server] Patch URL: null
  | 09:38:25,340 INFO  [Server] Server Name: default
  | 09:38:25,348 INFO  [Server] Server Home Dir: 
/home/bantest/jboss-3.2.7/server/default
  | 09:38:25,349 INFO  [Server] Server Home URL: 
file:/home/bantest/jboss-3.2.7/server/default/
  | 09:38:25,350 INFO  [Server] Server Data Dir: 
/home/bantest/jboss-3.2.7/server/default/data
  | 09:38:25,350 INFO  [Server] Server Temp Dir: 
/home/bantest/jboss-3.2.7/server/default/tmp
  | 09:38:25,359 INFO  [Server] Server Config URL: 
file:/home/bantest/jboss-3.2.7/server/default/conf/
  | 09:38:25,359 INFO  [Server] Server Library URL: 
file:/home/bantest/jboss-3.2.7/server/default/lib/
  | 09:38:25,359 INFO  [Server] Root Deployment Filename: jboss-service.xml
  | 09:38:25,379 INFO  [Server] Starting General Purpose Architecture (GPA)... 
  | 

boot.log from 4.0.2:

11:46:18,664 INFO  [Server] Starting JBoss (MX MicroKernel)...
  | 11:46:18,683 INFO  [Server] Release ID: JBoss [Zion] 4.0.2 (build: 
CVSTag=JBoss_4_0_2 date=200505022023)
  | 11:46:18,683 DEBUG [Server] Using config: [EMAIL PROTECTED]
  | 11:46:18,684 DEBUG [Server] Server type: class 
org.jboss.system.server.ServerImpl
  | 11:46:18,684 INFO  [Server] Home Dir: /home/bantest/jboss-4.0.2
  | 11:46:18,692 INFO  [Server] Home URL: file:/home/bantest/jboss-4.0.2/
  | 11:46:18,693 INFO  [Server] Library URL: file:/home/bantest/jboss-4.0.2/lib/
  | 11:46:18,702 INFO  [Server] Patch URL: null
  | 11:46:18,702 INFO  [Server] Server Name: default
  | 11:46:18,703 INFO  [Server] Server Home Dir: 
/home/bantest/jboss-4.0.2/server/default
  | 11:46:18,703 INFO  [Server] Server Home URL: 
file:/home/bantest/jboss-4.0.2/server/default/
  | 11:46:18,704 INFO  [Server] Server Data Dir: 
/home/bantest/jboss-4.0.2/server/default/data
  | 11:46:18,712 INFO  [Server] Server Temp Dir: 
/home/bantest/jboss-4.0.2/server/default/tmp
  | 11:46:18,713 INFO  [Server] Server Config URL: 
file:/home/bantest/jboss-4.0.2/server/default/conf/
  | 11:46:18,713 INFO  [Server] Server Library URL: 
file:/home/bantest/jboss-4.0.2/server/default/lib/
  | 11:46:18,714 INFO  [Server] Root Deployment Filename: jboss-service.xml
  | 11:46:18,734 INFO  [Server] Starting General Purpose Architecture (GPA)... 
  | 

If I changed the IBM-JDK to the 32-bit version, both jboss running fine.

Is this an IBM-JDK problem or need I a special jboss configuration for running 
under 64-bit IBM-VM.

Thanks for help.
Kind regards.

Stefan




View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926765#3926765

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3926765


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to