aspose file tools*
The moose likes JBoss/WildFly and the fly likes issue with java.home being different to the one I passed in Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "issue with java.home being different to the one I passed in" Watch "issue with java.home being different to the one I passed in" New topic
Author

issue with java.home being different to the one I passed in

Nishanth Alphonse
Greenhorn

Joined: Aug 13, 2010
Posts: 11
Hi There,

I am using jboss5.1.0-jdk6 version and starting the server using the following command:

/bin/ksh
-c
"ulimit
-n
1024;
ulimit
-s
8192;
nohup
/usr/local/java/jdk1.6.0/bin/java
-DALT_GF=/usr/local/bfm/clients/DEV/std/files.dat
-DapplicationName=DEVXindexproX1
-server
-Dprogram.name=/u1/alphjoh/dev/etc/startjboss-5.1.pl
-Denv.name=DEV
-Djava.endorsed.dirs=/local/jboss-5.1.0-jdk6/lib/endorsed
-XX:+UseParallelGC
-DApp.Container=JBOSS
-Damyserver.unique.server.id=indexpro-da01XDEVXindexproX1
-Dbfm.http_retry=2
-Dclient.application.name=indexpro
-Dcom.bfm.app.indexpro.webRoot=/usr/local/bfm/web/htdocs
-Dcom.bfm.app.webRoot=/usr/local/bfm/web/htdocs
-Dcom.sun.management.jmxremote=true
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=50245
-Dcom.sun.management.jmxremote.ssl=false
-XX:+UseAdaptiveSizePolicy
-Xloggc:/local/jbosslogs/indexpro-da01XDEVXindexproX1/logs/jboss.gc.20100816_070616.log
-Xms1g
-XX:MaxPermSize=128m
-Xmx1g
-XX:PermSize=128m
-XX:+DisableExplicitGC
-XX:ParallelGCThreads=8
-XX:+PrintGCDetails
-XX:+PrintHeapAtGC
-XX:+PrintTenuringDistribution
-XX:+PrintGCTimeStamps
-verbose:gc
-Djava.net.preferIPv4Stack=true
-Djava_home=/usr/local/java/jdk1.6.0
-Djboss.bind.address=devnasv009
-Djboss.home.dir=/local/jboss-5.1.0
-Djboss.jboss_home=/local/jboss-5.1.0
-Djboss.jgroups.diagnostics_port=50235
-Djboss.jgroups.tcp.tcp_port=50236
-Djboss.jgroups.tcp_sync.mping_mcast_port=50248
-Djboss.jgroups.tcp_sync.tcp_port=50239
-Djboss.jgroups.udp_async.mcast_port=50237
-Djboss.jmxconsolepartition.mcast_port=50234
-Djboss.messaging.ServerPeerID=1
-Djboss.messaging.connection.wait=30000
-Djboss.messaging.datachanneltcpport=50240
-Djboss.partition.name=DEVindexpro
-Djboss.server.base.dir=/local/jboss_runtime/server/5.1/04-01-2010
-Djboss.server.config.url=file:///local/jboss_runtime/server/5.1/04-01-2010/conf
-Djboss.server.configuration=04-01-2010
-Djboss.server.data.dir=/local/jboss_runtime/tempfiles/indexpro-da01XDEVXindexproX1/data
-Djboss.server.home.dir=/local/jboss_runtime/server/5.1/04-01-2010
-Djboss.server.home.url=file:///local/jboss_runtime/server/5.1/04-01-2010
-Djboss.server.lib.dir=/local/jboss_runtime/server/5.1/04-01-2010/lib
-Djboss.server.log.dir=/local/jbosslogs/indexpro-da01XDEVXindexproX1/logs
-Djboss.server.name=standard
-Djboss.server.temp.base.dir=/local/jboss_runtime/tempfiles/indexpro-da01XDEVXindexproX1
-Djboss.server.temp.dir=/local/jboss_runtime/tempfiles/indexpro-da01XDEVXindexproX1/temp
-Djboss.vfs.forceCopy=false
-Djboss.vfs.forceNoCopy=true
-Djgroups.tcp.mping_mcast_port=50241
-Djgroups.udp.ip_ttl=10
-Dmyserver.apache.workers.properties.file=
-Dmyserver.app.log.level=INFO
-Dmyserver.application.log.name=indexpro_20100816_070616
-Dmyserver.application.properties=file:////u1/alphjoh/dev/clients/DEV/std/jboss/indexpro/indexpro.properties
-Dmyserver.common.deploy.location=/u1/alphjoh/dev/std/jboss/application/config/indexpro
-Dmyserver.db.token.name=SYBDEV
-Dmyserver.deploy.location=file:///local/jboss_runtime/server/5.1/04-01-2010/deploy
-Dmyserver.dswrite.db.token.name=SYBDEV
-Dmyserver.dswrite.jdbc.host.and.port=dummy
-Dmyserver.dswrite.jdbc.max.pool.size=20
-Dmyserver.dswrite.jdbc.min.pool.size=5
-Dmyserver.host.name=devnasv009
-Dmyserver.jboss.console.log.level=INFO
-Dmyserver.jboss.file.log.level=INFO
-Dmyserver.jdbc.db.name=tempdb
-Dmyserver.jdbc.ds1.jndi-name=BFM_DS1
-Dmyserver.jdbc.ds1.username=tsgops
-Dmyserver.jdbc.ds2.jndi-name=BFM_DS2
-Dmyserver.jdbc.ds2.username=tsgops
-Dmyserver.jdbc.ds3.jndi-name=BFM_DS3
-Dmyserver.jdbc.ds3.username=tsgops
-Dmyserver.jdbc.dsread.username=jboss
-Dmyserver.jdbc.dswrite.username=jboss
-Dmyserver.jdbc.host.and.port=dummy
-Dmyserver.jdbc.hrdb.username=jboss
-Dmyserver.jdbc.indexpro-DSWRITE.connectionUrl=jdbc:sybase:Tds:SYBDEV:4100
-Dmyserver.jdbc.max.pool.size=20
-Dmyserver.jdbc.min.pool.size=5
-Dmyserver.log.dir=/local/jbosslogs/indexpro-da01XDEVXindexproX1/logs
-Dmyserver.log.name.suffix=20100816_070807
-Dmyserver.log4j.appender.name=indexpro
-Dmyserver.memory.threshold=1500000
-Dmyserver.memory.thresholdlimit=3500000
-Dmyserver.monitor.alert.group.email=OnCall-
-Dmyserver.node.name=indexpro-da01XDEVXindexproX1
-Dmyserver.service.AxisService.port=50216
-Dmyserver.service.Connector-bisocket.port=50224
-Dmyserver.service.CorbaORB.port=50211
-Dmyserver.service.HAJNDI.AutoDiscovery.port=50222
-Dmyserver.service.HAJNDI.RmiPort=50207
-Dmyserver.service.HAJNDI.port=50208
-Dmyserver.service.JBM2-netty-ssl.port=50226
-Dmyserver.service.JBM2-netty.port=50225
-Dmyserver.service.JMXConnectorServer-rmi.port=50223
-Dmyserver.service.MQ.port=50215
-Dmyserver.service.RMI-Connecter.port=50212
-Dmyserver.service.SnmpAgent-adaptor.port=50214
-Dmyserver.service.SnmpAgent-logger.port=50213
-Dmyserver.service.TransactionManager-recoveryManager.port=50227
-Dmyserver.service.TransactionManager-socketProcessId.port=50230
-Dmyserver.service.TransactionManager-transactionTimeout=3600
-Dmyserver.service.UDP.apptreecache.multicast.port=50231
-Dmyserver.service.UDP.jbosscluster.multicast.port=50232
-Dmyserver.service.UDP.jbosstreecache.multicast.port=50233
-Dmyserver.service.UnifiedInvokerConnector.port=50221
-Dmyserver.service.WebService.port=50204
-Dmyserver.service.connector-transport.port=50219
-Dmyserver.service.ejb3.connector.port=50218
-Dmyserver.service.invoker-jrmp.port=50205
-Dmyserver.service.invoker-jrmpha.port=50209
-Dmyserver.service.invoker-pooled.port=50206
-Dmyserver.service.invoker-pooledha.port=50210
-Dmyserver.service.naming.RmiPort=50203
-Dmyserver.service.naming.port=50202
-Dmyserver.service.tomcat.AJP.maxSpareThreads=10
-Dmyserver.service.tomcat.AJP.maxThreads=25
-Dmyserver.service.tomcat.AJP.minSpareThreads=5
-Dmyserver.service.tomcat.AJP.port=50200
-Dmyserver.service.tomcat.http.port=50201
-Dmyserver.service.tomcat.https.port=50220
-Dmyserver.unique.server.id=indexpro-da01XDEVXindexproX1
-Dmyserver.war.hotdeploy=false
-Dmyserver.war.location=/u1/alphjoh/dev/appl/indexpro/DEV
-Dmyserver.write.jdbc.db.name=misdb
-Dsun.rmi.dgc.client.gcInterval=900000
-Dsun.rmi.dgc.server.gcInterval=900000
-Xdebug
-Xrunjdwp:server=y,transport=dt_socket,address=devnasv009:50231,suspend=n
-classpath
"/local/jboss-5.1.0-jdk6/bin/run.jar"
org.jboss.Main
-b
devnasv009
>
/local/jbosslogs/indexpro-da01XDEVXindexproX1/logs/stdout_20100816_070946.log
2>&1
&"


As you can see the java.home is set up as /usr/local/java/jdk1.6.0. However during start-up I do get messages similar to the following:

07:13:16,212 DEBUG [ServerInfo] Full System Properties Dump
07:13:16,212 DEBUG [ServerInfo] myserver.service.HAJNDI.RmiPort: 50207
07:13:16,212 DEBUG [ServerInfo] file.encoding.pkg: sun.io
07:13:16,212 DEBUG [ServerInfo] myserver.jdbc.ds1.username: tsgops
07:13:16,213 DEBUG [ServerInfo] App.Container: JBOSS
07:13:16,213 DEBUG [ServerInfo] myserver.service.naming.RmiPort: 50203
07:13:16,213 DEBUG [ServerInfo] com.sun.management.jmxremote.authenticate: false
07:13:16,213 DEBUG [ServerInfo] jboss.vfs.forceNoCopy: true
07:13:16,213 DEBUG [ServerInfo] java.home: /usr/local/java/jdk1.6.0_10/jre
07:13:16,213 DEBUG [ServerInfo] myserver.monitor.alert.group.email: OnCall-
07:13:16,213 DEBUG [ServerInfo] myserver.memory.thresholdlimit: 3500000
07:13:16,213 DEBUG [ServerInfo] amyserver.unique.server.id: indexpro-da01XDEVXindexproX1
07:13:16,213 DEBUG [ServerInfo] myserver.dswrite.jdbc.host.and.port: dummy
07:13:16,213 DEBUG [ServerInfo] java.net.preferIPv4Stack: true
07:13:16,213 DEBUG [ServerInfo] jboss.home.url: file:/local/jboss-5.1.0/
07:13:16,213 DEBUG [ServerInfo] myserver.service.JMXConnectorServer-rmi.port: 50223
07:13:16,213 DEBUG [ServerInfo] java.endorsed.dirs: /local/jboss-5.1.0-jdk6/lib/endorsed
07:13:16,213 DEBUG [ServerInfo] client.application.name: indexpro
07:13:16,213 DEBUG [ServerInfo] myserver.jdbc.ds3.jndi-name: BFM_DS3
07:13:16,213 DEBUG [ServerInfo] myserver.service.UnifiedInvokerConnector.port: 50221
07:13:16,213 DEBUG [ServerInfo] jgroups.bind_addr: devnasv009
07:13:16,213 DEBUG [ServerInfo] sun.os.patch.level: unknown
07:13:16,213 DEBUG [ServerInfo] myserver.jdbc.ds2.username: tsgops
07:13:16,213 DEBUG [ServerInfo] java.vendor.url: http://java.sun.com/
07:13:16,213 DEBUG [ServerInfo] myserver.service.ejb3.connector.port: 50218
07:13:16,213 DEBUG [ServerInfo] jboss.messaging.datachanneltcpport: 50240
07:13:16,213 DEBUG [ServerInfo] myserver.db.token.name: SYBDEV
07:13:16,213 DEBUG [ServerInfo] java.version: 1.6.0_10

suggesting that it is infact using the environment /usr/local/java/jdk1.6.0_10.

Do you have any ideas wherelse it coudl be getting it's java home from? The installation of 1.6.0_10 on our box is not ocmplete and therfore, it fails to deploy the admin-console.war. I don't understand why it's not using the java.home variable that I passed in.

Many thanks,
Johny
Nishanth Alphonse
Greenhorn

Joined: Aug 13, 2010
Posts: 11
It's actually when it tries to deploy the /admin-console.
Has this been built with a dependency on jdk1.6.0_10 somehow?

In the manifest file for that war, I see the following entry:

Build-Jdk: 1.6.0_13

Thanks,

Nishanth
Rene Larsen
Ranch Hand

Joined: Oct 12, 2001
Posts: 1179

Is the JAVA_HOME environment variable set on the box ?? - to maybe "/usr/local/java/jdk1.6.0_10" ??


Regards, Rene Larsen
Dropbox Invite
Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5772
    
    7

Could you post the output for:

ls -al /usr/local/java

I suspect that /usr/local/java/jdk1.6.0 is a link to 1.6.0_10

By the way, I would not use 6u10, it has problems. You should really be using the latest update.


JBoss In Action
Nishanth Alphonse
Greenhorn

Joined: Aug 13, 2010
Posts: 11
Hi Peter,

Thanks for your pointer. It was in fact a symlink. So I need to get them to install the latest jdk properly.

Cheers,
Johny
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: issue with java.home being different to the one I passed in
 
Similar Threads
another Eclipse & JBoss question
Why my JBOSS 4.0.2 is running out of memory?
Error while deplloying the application on JBoss.
Running JBoss 5.1.0 All Server
JBoss 4.2.3 having problems on startup