Solved

Users Cannot compile under shared tomcat 5.9

Posted on 2006-07-05
17
368 Views
Last Modified: 2008-01-09
Hi

I have a dedicated UNIX server that is running a shared tomcat environment.

If a user tries to compile a class file he gets an error Error occurred during initialization of VM, Could not reserve enough space for object heap, Could not create the Java virtual machine.  The compile code is below;

username [~]# javac -cp /home/mikeippo/www/WEB-INF/classes/beans/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/beans -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar -J-Xms60m

If I increase the xms size to 66m I get this error
Error occurred during initialization of VM
Incompatible initial and maximum heap sizes specified

If I log on as root I can compile the classes without any -J-Xms60m entries

What am I doing wrong.  I need users to compile their own classes.  

would appreciate your help in resolving this

Regards

Ken



0
Comment
Question by:kwwells
  • 8
  • 8
17 Comments
 
LVL 19

Expert Comment

by:actonwang
ID: 17052228
could you try to compile just one java file in user side?
0
 

Author Comment

by:kwwells
ID: 17052336
Yes same problem, gives the same message

Ken
0
 

Author Comment

by:kwwells
ID: 17052371
here is the single compile

]# javac -cp /home/mikeippo/www/WEB-INF/classes/util/UserControl.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
0
 

Author Comment

by:kwwells
ID: 17052394
I do not know if this helps , the jvm memory assignments are Free memory: 20.35 MB Total memory: 53.87 MB Max memory: 63.56 MB  ken
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17052527
>> -J-Xms60m

      You might need to use sth like :

       -J-Xms60m  -J-Xmx80m
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17052536
by default, heap max size is about 16M (or sth like this depending on OS), so your Xms setting was greater which triggers the problem.
0
 

Author Comment

by:kwwells
ID: 17060841
Hi

Seems this does not work.  Tried to compile using different values which return the same error

[~]# javac -J-Xms60m  -J-Xmx80m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.


[~]# javac -J-Xms100m  -J-Xmx120m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

[~]# javac -J-Xms160m  -J-Xmx180m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

[~]# javac -J-Xms60m  -J-Xmx80m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.


[~]# javac -J-Xms100m  -J-Xmx120m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

Any idea's

Regards

Ken
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17060879
>>Could not reserve enough space for object heap

     user doesn't have much memory left. any memory limitation imposed on user?

     try to use less amount of memory as:

      javac -J-Xms30m  -J-Xmx40m
0
6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

 

Author Comment

by:kwwells
ID: 17063347
Hi

no matter what I try it fails.  Here are the variation I just ran

[~]# javac -javac -J-Xms30m  -J-Xmx40m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

[~]# javac -J-Xms10m  -J-Xmx15m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

# javac -J-Xms2m  -J-Xmx5m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread

[~]# javac -J-Xms2m  -J-Xmx5m -cp /hINF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread

[~]# javac -J-Xms3m  -J-Xmx5m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread

[~]# javac -J-Xms3m  -J-Xmx5m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread

[~]# javac -J-Xms5m  -J-Xmx10m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread

[~]# javac -J-Xms10m  -J-Xmx15m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.

[~]# javac -J-Xms8m  -J-Xmx15m -cp /home/mikeippo/www/WEB-INF/classes/util/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/util -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.


Ken
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17063395
>>Could not reserve enough space for object heap

     any memory limitation imposed on user? The error clearly state that the user can not get more memory.
0
 

Author Comment

by:kwwells
ID: 17067779
How do I tell if there is any memory limitation imposed on the user?
0
 

Author Comment

by:kwwells
ID: 17067904
Here is the server.xml for the server

<!-- Example Server Configuration File -->
<!-- Note that component elements are nested corresponding to their
     parent-child relationships with each other -->

<!-- A "Server" is a singleton element that represents the entire JVM,
     which may contain one or more "Service" instances.  The Server
     listens for a shutdown command on the indicated port.

     Note:  A "Server" is not itself a "Container", so you may not
     define subcomponents such as "Valves" or "Loggers" at this level.
 -->

<Server port="8005" shutdown="SHUTDOWN">

  <!-- Comment these entries out to disable JMX MBeans support used for the
       administration web application -->
  <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>

  <!-- Global JNDI resources -->
  <GlobalNamingResources>

    <!-- Test entry for demonstration purposes -->
    <Environment name="simpleValue" type="java.lang.Integer" value="30"/>

    <!-- Editable user database that can also be used by
         UserDatabaseRealm to authenticate users -->
    <Resource name="UserDatabase" auth="Container"
              type="org.apache.catalina.UserDatabase"
       description="User database that can be updated and saved"
           factory="org.apache.catalina.users.MemoryUserDatabaseFactory"
          pathname="conf/tomcat-users.xml" />

  </GlobalNamingResources>

  <!-- A "Service" is a collection of one or more "Connectors" that share
       a single "Container" (and therefore the web applications visible
       within that Container).  Normally, that Container is an "Engine",
       but this is not required.

       Note:  A "Service" is not itself a "Container", so you may not
       define subcomponents such as "Valves" or "Loggers" at this level.
   -->

  <!-- Define the Tomcat Stand-Alone Service -->
  <Service name="Catalina">

    <!-- A "Connector" represents an endpoint by which requests are received
         and responses are returned.  Each Connector passes requests on to the
         associated "Container" (normally an Engine) for processing.

         By default, a non-SSL HTTP/1.1 Connector is established on port 8443.
         You can also enable an SSL HTTP/1.1 Connector on port 8443 by
         following the instructions below and uncommenting the second Connector
         entry.  SSL support requires the following steps (see the SSL Config
         HOWTO in the Tomcat 5 documentation bundle for more detailed
         instructions):
         * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
           later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
         * Execute:
             %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
             $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
           with a password value of "changeit" for both the certificate and
           the keystore itself.

         By default, DNS lookups are enabled when a web application calls
         request.getRemoteHost().  This can have an adverse impact on
         performance, so you can disable it by setting the
         "enableLookups" attribute to "false".  When DNS lookups are disabled,
         request.getRemoteHost() will return the String version of the
         IP address of the remote client.
    -->

    <!-- Define a non-SSL HTTP/1.1 Connector on port 4643 -->
    <Connector port="4643" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" redirectPort="8443" acceptCount="100"
               connectionTimeout="20000" disableUploadTimeout="true" />
    <!-- Note : To disable connection timeouts, set connectionTimeout value
     to 0 -->
      
      <!-- Note : To use gzip compression you could set the following properties :
      
                     compression="on"
                     compressionMinSize="2048"
                     noCompressionUserAgents="gozilla, traviata"
                     compressableMimeType="text/html,text/xml"
      -->

    <!-- Define a SSL HTTP/1.1 Connector on port 4643 -->
    <!--
    <Connector port="4643" maxHttpHeaderSize="8192"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" disableUploadTimeout="true"
               acceptCount="100" scheme="https" secure="true"
               clientAuth="false" sslProtocol="TLS" />
    -->

    <!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009"
               enableLookups="false" redirectPort="4643" protocol="AJP/1.3" />

    <!-- Define a Proxied HTTP/1.1 Connector on port 4643 -->
    <!-- See proxy documentation for more information about using this. -->
    <!--
    <Connector port="4643"
               maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
               enableLookups="false" acceptCount="100" connectionTimeout="20000"
               proxyPort="80" disableUploadTimeout="true" />
    -->

    <!-- An Engine represents the entry point (within Catalina) that processes
         every request.  The Engine implementation for Tomcat stand alone
         analyzes the HTTP headers included with the request, and passes them
         on to the appropriate Host (virtual host). -->

    <!-- You should set jvmRoute to support load-balancing via AJP ie :
    <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">        
    -->
         
    <!-- Define the top level container in our container hierarchy -->
    <Engine name="Catalina" defaultHost="localhost">

      <!-- The request dumper valve dumps useful debugging information about
           the request headers and cookies that were received, and the response
           headers and cookies that were sent, for all requests received by
           this instance of Tomcat.  If you care only about requests to a
           particular virtual host, or a particular application, nest this
           element inside the corresponding <Host> or <Context> entry instead.

           For a similar mechanism that is portable to all Servlet 2.4
           containers, check out the "RequestDumperFilter" Filter in the
           example application (the source for this filter may be found in
           "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").

           Request dumping is disabled by default.  Uncomment the following
           element to enable it. -->
      <!--
      <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
      -->

      <!-- Because this Realm is here, an instance will be shared globally -->

      <!-- This Realm uses the UserDatabase configured in the global JNDI
           resources under the key "UserDatabase".  Any edits
           that are performed against this UserDatabase are immediately
           available for use by the Realm.  -->
      <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
             resourceName="UserDatabase"/>

      <!-- Comment out the old realm but leave here for now in case we
           need to go back quickly -->
      <!--
      <Realm className="org.apache.catalina.realm.MemoryRealm" />
      -->

      <!-- Replace the above Realm with one of the following to get a Realm
           stored in a database and accessed via JDBC -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="org.gjt.mm.mysql.Driver"
          connectionURL="jdbc:mysql://localhost/authority"
         connectionName="test" connectionPassword="test"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="oracle.jdbc.driver.OracleDriver"
          connectionURL="jdbc:oracle:thin:@ntserver:1521:ORCL"
         connectionName="scott" connectionPassword="tiger"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!--
      <Realm  className="org.apache.catalina.realm.JDBCRealm"
             driverName="sun.jdbc.odbc.JdbcOdbcDriver"
          connectionURL="jdbc:odbc:CATALINA"
              userTable="users" userNameCol="user_name" userCredCol="user_pass"
          userRoleTable="user_roles" roleNameCol="role_name" />
      -->

      <!-- Define the default virtual host
           Note: XML Schema validation will not work with Xerces 2.2.
       -->
      <Host name="localhost" appBase="webapps"
       unpackWARs="true" autoDeploy="true"
       xmlValidation="false" xmlNamespaceAware="false">

        <!-- Defines a cluster for this node,
             By defining this element, means that every manager will be changed.
             So when running a cluster, only make sure that you have webapps in there
             that need to be clustered and remove the other ones.
             A cluster has the following parameters:

             className = the fully qualified name of the cluster class

             name = a descriptive name for your cluster, can be anything

             mcastAddr = the multicast address, has to be the same for all the nodes

             mcastPort = the multicast port, has to be the same for all the nodes
             
             mcastBindAddr = bind the multicast socket to a specific address
             
             mcastTTL = the multicast TTL if you want to limit your broadcast
             
             mcastSoTimeout = the multicast readtimeout

             mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat

             mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received

             tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes

             tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
                                in case of multiple ethernet cards.
                                auto means that address becomes
                                InetAddress.getLocalHost().getHostAddress()

             tcpListenPort = the tcp listen port

             tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                  has a wakup bug in java.nio. Set to 0 for no timeout

             printToScreen = true means that managers will also print to std.out

             expireSessionsOnShutdown = true means that

             useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                            false means to replicate the session after each request.
                            false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
                            <%
                            HashMap map = (HashMap)session.getAttribute("map");
                            map.put("key","value");
                            %>
             replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                               * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
                               * Synchronous means that the thread that executes the request, is also the
                               thread the replicates the data to the other nodes, and will not return until all
                               nodes have received the information.
                               * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                               so the request thread will queue the replication request into a "smart" queue,
                               and then return to the client.
                               The "smart" queue is a queue where when a session is added to the queue, and the same session
                               already exists in the queue from a previous request, that session will be replaced
                               in the queue instead of replicating two requests. This almost never happens, unless there is a
                               large network delay.
        -->            
        <!--
            When configuring for clustering, you also add in a valve to catch all the requests
            coming in, at the end of the request, the session may or may not be replicated.
            A session is replicated if and only if all the conditions are met:
            1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
            2. a session exists (has been created)
            3. the request is not trapped by the "filter" attribute

            The filter attribute is to filter out requests that could not modify the session,
            hence we don't replicate the session after the end of this request.
            The filter is negative, ie, anything you put in the filter, you mean to filter out,
            ie, no replication will be done on requests that match one of the filters.
            The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.

            filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
            ending with .gif and .js are intercepted.
           
            The deployer element can be used to deploy apps cluster wide.
            Currently the deployment only deploys/undeploys to working members in the cluster
            so no WARs are copied upons startup of a broken node.
            The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
            When a new war file is added the war gets deployed to the local instance,
            and then deployed to the other instances in the cluster.
            When a war file is deleted from the watchDir the war is undeployed locally
            and cluster wide
        -->
       
        <!--
        <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                 managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                 expireSessionsOnShutdown="false"
                 useDirtyFlag="true"
                 notifyListenersOnReplication="true">

            <Membership
                className="org.apache.catalina.cluster.mcast.McastService"
                mcastAddr="228.0.0.4"
                mcastPort="45564"
                mcastFrequency="500"
                mcastDropTime="3000"/>

            <Receiver
                className="org.apache.catalina.cluster.tcp.ReplicationListener"
                tcpListenAddress="auto"
                tcpListenPort="4001"
                tcpSelectorTimeout="100"
                tcpThreadCount="6"/>

            <Sender
                className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                replicationMode="pooled"
                ackTimeout="15000"/>

            <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                   filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
                   
            <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                      tempDir="/tmp/war-temp/"
                      deployDir="/tmp/war-deploy/"
                      watchDir="/tmp/war-listen/"
                      watchEnabled="false"/>
        </Cluster>
        -->        



        <!-- Normally, users must authenticate themselves to each web app
             individually.  Uncomment the following entry if you would like
             a user to be authenticated the first time they encounter a
             resource protected by a security constraint, and then have that
             user identity maintained across *all* web applications contained
             in this virtual host. -->
        <!--
        <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.AccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->

        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
             This access log implementation is optimized for maximum performance,
             but is hardcoded to support only the "common" and "combined" patterns.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->
        <!-- Access log processes all requests for this virtual host.  By
             default, log files are created in the "logs" directory relative to
             $CATALINA_HOME.  If you wish, you can specify a different
             directory with the "directory" attribute.  Specify either a relative
             (to $CATALINA_HOME) or absolute path to the desired directory.
             This access log implementation is optimized for maximum performance,
             but is hardcoded to support only the "common" and "combined" patterns.

             This valve use NIO direct Byte Buffer to asynchornously store the
             log.
        -->
        <!--
        <Valve className="org.apache.catalina.valves.ByteBufferAccessLogValve"
                 directory="logs"  prefix="localhost_access_log." suffix=".txt"
                 pattern="common" resolveHosts="false"/>
        -->


       <Host name="xxxxxxxx.com" appBase="/home/mikeippo/public_html">
          <Context path="" reloadable="true" docBase="/home/mikeippo/public_html" debug="1"/>
          <Context path="/manager" debug="0" privileged="true"
              docBase="/usr/local/jakarta/tomcat/server/webapps/manager">
          </Context>
       </Host>

       <Host name="www.xxxxxxxx.com" appBase="/home/mikeippo/public_html">
          <Context path="" reloadable="true" docBase="/home/mikeippo/public_html" debug="1"/>
          <Context path="/manager" debug="0" privileged="true"
              docBase="/usr/local/jakarta/tomcat/server/webapps/manager">
          </Context>
       </Host>

    </Engine>

  </Service>

</Server>
0
 

Author Comment

by:kwwells
ID: 17107432
I am able to compile a class under our shared tomcat 5.9 environment as long as I log on as root. If I log on as a shared user and submit the same compile options, I receive

"Error occurred during initialization of VM, Could not reserve enough space for object heap, Could not create the Java virtual machine."  

The compile code is below;

javac -J-Xms30m  -J-Xmx40m -cp /home/mikeippo/www/WEB-INF/classes/beans/*.java -sourcepath /home/mikeippo/www/WEB-INF/classes/beans -classpath /home/mikeippo/www/WEB-INF/classes/beans:/home/mikeippo/www/WEB-INF/classes:/home/mikeippo/www/WEB-INF/lib/servlet.jar:/home/mikeippo/www/WEB-INF/lib/mail.jar

We have tried just about every combination of xms / xmx memory values and always get the same results.  This leads us to the conclusion that there is no xms/xmx memory assigned to a shared user.


Question:

Where do we assign xms/xmx memory to a shared user in our configuration. I believe that it is in the server.xml but cannot find the parameters

Your help is much appreciated

Ken
 
0
 
LVL 19

Accepted Solution

by:
actonwang earned 500 total points
ID: 17109555
just try:

javac  -J-Xmx40m ...


to see how it goes?
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17109559
also make sure users have access to java folder and all necessary files.
0
 
LVL 19

Expert Comment

by:actonwang
ID: 17109582
also what unix server are you on? Solaris?

on user's account, can you run:

java -version

?
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Suggested Solutions

This article will show you how to create an ISO CD-ROM/DVD-ROM image (*.iso), and MD5 checksum signature, for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5). It's a good idea to compare checksums, because many installations fail because of a corr…
We have come a long way with backup and data protection — from backing up to floppies, external drives, CDs, Blu-ray, flash drives, SSD drives, and now to the cloud.
This video discusses moving either the default database or any database to a new volume.
This tutorial demonstrates a quick way of adding group price to multiple Magento products.

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now