Hitachi Vantara Pentaho Community Forums
Results 1 to 5 of 5

Thread: Linux 32bit, Virtual , Java issues

  1. #1
    Join Date
    Jan 2007
    Posts
    29

    Default Linux 32bit, Virtual , Java issues

    Hi. Unusual case here I think. I have a small business client doing a proof of concept using Pentaho. Problem is their current servers are Siteground VPS pro (virtualized servers from Siteground). I was able to get ssh/ftp access and get Pentaho and the correct Java on there. But I'm having issues starting up. When I run top I see there is 0 swap space allowed. There is 2GB RAM with only 640 Mb guaranteed in their VPS environment (ouch I know). It says there is 1.8Mb free RAM though. So I should have at least >200Mb free RAM guaranteed to play with for Pentaho.

    Are there any other java settings I can play with that might help? Thank you for any help!

    Here is what I get when I start up with 64Mb set in the run.conf. Further down is the result when I set it to just 32Mb RAM. I installed the Pentaho 1.6 demo for this.


    mycom@mycom.com [~/public_html/pentaho]# ./start-pentaho.sh
    JAVA_HOME set to /home/mycom/public_html/jdk1.6.0_02
    JAVA is /home/mycom/public_html/jdk1.6.0_02/bin/java
    =========================================================================

    JBoss Bootstrap Environment

    JBOSS_HOME: /home/mycom/public_html/pentaho/jboss

    JAVA: /home/mycom/public_html/jdk1.6.0_02/bin/java

    JAVA_OPTS: -Dprogram.name=run.sh -Xms64m -Xmx64m -XX:MaxPermSize=64m -Dsun.rmi .dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Djava.io.tmpdir=/tmp/ -Djava.net.preferIPv4Stack=true

    CLASSPATH: /home/mycom/public_html/pentaho/jboss/bin/run.jar:/home/mycom /public_html/jdk1.6.0_02/lib/tools.jar

    =========================================================================

    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    Could not create the Java virtual machine.
    Error occurred during initialization of VM
    java.lang.OutOfMemoryError: unable to create new native thread
    mycom@mycom.com [~/public_html/pentaho]#




    #####RESULT WHEN SET RAM to 32Mb available
    mycom@mycom.com [~/public_html/pentaho]# ./start-pentaho.sh
    JAVA_HOME set to /home/mycom/public_html/jdk1.6.0_02
    JAVA is /home/mycom/public_html/jdk1.6.0_02/bin/java
    =========================================================================

    JBoss Bootstrap Environment

    JBOSS_HOME: /home/mycom/public_html/pentaho/jboss

    JAVA: /home/mycom/public_html/jdk1.6.0_02/bin/java

    JAVA_OPTS: -Dprogram.name=run.sh -Xms32m -Xmx32m -XX:MaxPermSize=32m -Dsun.rmi.dgc.client.gcInterv al=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.awt.headless=true -Djava.io.tmpdir=/tmp/ - Djava.net.preferIPv4Stack=true

    CLASSPATH: /home/mycom/public_html/pentaho/jboss/bin/run.jar:/home/mycom/public_html/jdk1.6. 0_02/lib/tools.jar

    =========================================================================

    Error occurred during initialization of VM
    Could not reserve enough space for object heap
    Could not create the Java virtual machine.
    13:23:38,595 INFO [Server] Starting JBoss (MX MicroKernel)...
    13:23:38,596 INFO [Server] Release ID: JBoss [Trinity] 4.2.1.GA (build: SVNTag=JBoss_4_2_1_GA date= 200707131605)
    13:23:38,598 INFO [Server] Home Dir: /home/mycom/public_html/pentaho/jboss
    13:23:38,633 INFO [Server] Home URL: file:/home/mycom/public_html/pentaho/jboss/
    13:23:38,634 INFO [Server] Patch URL: null
    13:23:38,634 INFO [Server] Server Name: default
    13:23:38,634 INFO [Server] Server Home Dir: /home/mycom/public_html/pentaho/jboss/server/default
    13:23:38,635 INFO [Server] Server Home URL: file:/home/mycom/public_html/pentaho/jboss/server/de fault/
    13:23:38,635 INFO [Server] Server Log Dir: /home/mycom/public_html/pentaho/jboss/server/default/ log
    13:23:38,635 INFO [Server] Server Temp Dir: /home/mycom/public_html/pentaho/jboss/server/default /tmp
    13:23:38,636 INFO [Server] Root Deployment Filename: jboss-service.xml
    13:23:39,090 INFO [ServerInfo] Java version: 1.6.0_02,Sun Microsystems Inc.
    13:23:39,090 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.6.0_02-b05,Sun Microsystems In c.
    13:23:39,091 INFO [ServerInfo] OS-System: Linux 2.6.9-023stab044.4-enterprise,i386
    13:23:39,971 INFO [Server] Core system initialized
    13:23:47,873 INFO [WebService] Using RMI server codebase: http://host.siteground-vps16.com:8083/
    13:23:47,877 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
    13:23:48,393 WARN [ServiceController] Problem starting service jboss:service=NamingBeanImpl
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.getEnvironment(InitialContext.java:525)
    at org.jnp.server.NamingBeanImpl.start(NamingBeanImpl.java:124)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:508)
    at java.lang.Thread.run(Thread.java:619)
    13:23:48,410 WARN [XMLLoginConfigImpl] End loadConfig, failed to load config: file:/home/mycom/public_html/pentaho/jboss/server/default/conf/login-config.xml
    java.io.FileNotFoundException: /home/mycom/public_html/pentaho/jboss/server/default/conf/login-config.xml (Too many open files)
    at java.io.FileInputStream.open(Native Method)
    at java.io.FileInputStream.<init>(FileInputStream.java:106)
    at org.jboss.net.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:105)
    at java.net.URL.openStream(URL.java:1009)
    at org.jboss.security.auth.login.XMLLoginConfigImpl.loadSunConfig(XMLLoginConfigImpl.java:304)
    at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:294)
    at org.jboss.security.auth.login.XMLLoginConfigImpl.loadConfig(XMLLoginConfigImpl.java:268)
    at org.jboss.security.auth.login.XMLLoginConfig.startService(XMLLoginConfig.java:176)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy5.deploy(Unknown Source)
    at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482)
    at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362)
    at org.jboss.Main.boot(Main.java:200)
    at org.jboss.Main$1.run(Main.java:508)
    at java.lang.Thread.run(Thread.java:619)
    13:23:48,451 WARN [ServiceController] Problem starting service jboss.security:service=JaasSecurityManager
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:645)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:325)
    at javax.naming.InitialContext.getNameParser(InitialContext.java:480)
    at org.jboss.security.plugins.JaasSecurityManagerService.startService(JaasSecurityManagerService.java:439)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
    at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978)
    at $Proxy0.start(Unknown Source)
    at org.jboss.system.ServiceController.start(ServiceController.java:417)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
    at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
    at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
    at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
    at $Proxy4.start(Unknown Source)
    at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302)
    at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
    at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
    at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
    at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
    at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
    {message was truncated}

  2. #2
    Join Date
    Jan 2007
    Posts
    29

    Default ps

    PS I'm with BreadBoard BI, a full member of the Pentaho partner program.

    I know this is a highly unusual case trying to use VPS for this. But any help would be greatly appreciated!!

  3. #3
    Join Date
    Jan 2007
    Posts
    29

    Default Followup

    I should have mentioned there should be >200Mb RAM free so Pentaho should start up with the 64Mb setting for Java. I'm wondering if the fact there is 0 swap space in the VPS that is the issue.

  4. #4
    Join Date
    Mar 2003
    Posts
    8,085

    Default

    In java, each thread started eats 1MB by default for its stack. So if your JBoss starts a couple of threads, your RAM will go down pretty quickly. Usually the OS detects this and swaps the unused areas to disk. But not in your case.

    So reduce the stack-size (-Xmss) and try again. Also: Java does *not* use 64MB by default. With JDK 1.4 (or 1.5) these rules changed and now Java takes a certain percentage (the exact number is buried in the JDK docs, I guess) of your RAM. So you better assign the RAM-sizes manually.

    Oh, and JBoss eats RAM like nothing. So you may want to switch to a Tomcat deployment instead. Tomcat is more sane when it comes to consuming resources. JBoss is optimized for the heavy irons, I guess.
    Get the latest news and tips and tricks for Pentaho Reporting at the Pentaho Reporting Blog.

  5. #5
    Join Date
    Jan 2007
    Posts
    29

    Default

    Thanks for the reply Taqua. I actually did try -Xss yesterday and tried to set it down to 128K. It got a little further but still bombed. Tomcat is a very good idea , but I'm worried about having a nightmare time trying to get it configured to run Pentaho1.6. Is there a doc anywhere that might list the necessary config changes.

    I always specify the memory usage in the run.conf as standard practice. -Xss usually isn't defined though. I'll try an even lower setting. Thanks for the ideas.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2019 Hitachi Vantara Corporation. All Rights Reserved.