1 2 Previous Next 16 Replies Latest reply on Nov 21, 2013 2:38 AM by sesharao_n

    Error when running domain.bat for cluster

    mike just Master

      I am trying to configure the cluster on Jboss EAP 6.1.0.Alpha1 version. And got following errors when running domain.bat.

       

      [Host Controller] 15:22:47,792 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on 192.168.1.2:9999
      [Host Controller] 15:22:49,409 INFO  [org.jboss.as.host.controller] (Controller Boot Thread) JBAS010922: Starting server server-one
      15:22:49,421 INFO  [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) JBAS012017: Starting process 'Server:server-one'
      [Server:server-one] Error occurred during initialization of VM
      [Server:server-one] Could not reserve enough space for object heap
      15:22:49,488 ERROR [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 3) JBAS012006: Failed to send data bytes to process 'S
      erver:server-one' input stream: java.io.IOException: 管道已结束。
              at java.io.FileOutputStream.writeBytes(Native Method) [rt.jar:1.6.0_07]
              at java.io.FileOutputStream.write(FileOutputStream.java:260) [rt.jar:1.6.0_07]
              at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) [rt.jar:1.6.0_07]
              at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) [rt.jar:1.6.0_07]
              at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:160) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-
      redhat-4]
              at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:183) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.A
      lpha1-redhat-4]
              at org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler
      .java:140) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
              at org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.
      jar:7.2.0.Alpha1-redhat-4]
              at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.
      Alpha1-redhat-4]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [rt.jar:1.6.0_07]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [rt.jar:1.6.0_07]
              at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_07]
              at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
      
      
      15:22:49,498 INFO  [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished wit
      h an exit status of 1
      15:22:49,496 ERROR [org.jboss.as.protocol.connection] (ProcessController-threads - 3) JBAS016610: Failed to read a message: java.io.IOException: 管道
      已结束。
              at java.io.FileOutputStream.writeBytes(Native Method) [rt.jar:1.6.0_07]
              at java.io.FileOutputStream.write(FileOutputStream.java:260) [rt.jar:1.6.0_07]
              at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) [rt.jar:1.6.0_07]
              at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) [rt.jar:1.6.0_07]
              at org.jboss.as.process.ManagedProcess.sendStdin(ManagedProcess.java:160) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-
      redhat-4]
              at org.jboss.as.process.ProcessController.sendStdin(ProcessController.java:183) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.A
      lpha1-redhat-4]
              at org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler
      .java:140) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4]
              at org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.
      jar:7.2.0.Alpha1-redhat-4]
              at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223) [jboss-as-process-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.
      Alpha1-redhat-4]
              at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) [rt.jar:1.6.0_07]
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) [rt.jar:1.6.0_07]
              at java.lang.Thread.run(Thread.java:619) [rt.jar:1.6.0_07]
              at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
      
      
      [Host Controller] 15:22:49,500 INFO  [org.jboss.as.host.controller] (ProcessControllerConnection-thread - 2) JBAS010926: Unregistering server server-o
      ne
      

       

       

      I did not modify any java heap paramter and the default options are being used.

       

      in domain.conf.bat:

      set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M"
      

       

      in host.xml:

       

      <jvms>
          <jvm name="default">
                <heap size="64m" max-size="512m"/>
                <permgen size="256m" max-size="256m"/>
                  <jvm-options>
                      <option value="-server"/>
                  </jvm-options>
             </jvm>
        </jvms>
      
      
          <servers>
              <server name="server-one" group="main-server-group">
                  <!-- Remote JPDA debugging for a specific server
                  <jvm name="default">
                    <jvm-options>
                      <option value="-agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"/>
                    </jvm-options>
                 </jvm>
                 -->
              </server>
              <server name="server-two" group="main-server-group" auto-start="true">
                  <!-- server-two avoids port conflicts by incrementing the ports in
                       the default socket-group declared in the server-group -->
                  <socket-bindings port-offset="150"/>
              </server>
              <server name="server-three" group="other-server-group" auto-start="false">
                  <!-- server-three avoids port conflicts by incrementing the ports in
                       the default socket-group declared in the server-group -->
                  <socket-bindings port-offset="250"/>
              </server>
          </servers>
      

       

      Any place needs to be modified to eliminatethis kind of error?

        • 1. Re: Error when running domain.bat for cluster
          Tomaz Cerar Master

          What exact version of OS are you using?

          • 3. Re: Error when running domain.bat for cluster
            Nicklas Karlsson Master

            Can you see from the logs which memory parameters are being used? Any chance it's picking up some other instances settings?

            • 4. Re: Re: Error when running domain.bat for cluster
              mike just Master

              Here it is;

               

              ===============================================================================
              
              
                JBoss Bootstrap Environment
              
              
                JBOSS_HOME: D:\server\jboss-eap-6.1\jboss\server
              
              
                JAVA: C:\Program Files\Java\jdk1.6.0_07\bin\java
              
              
                JAVA_OPTS: -Dprogram.name=domain.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byt
              eman
              
              
              ===============================================================================
              
              
              18:13:25,860 INFO  [org.jboss.modules] (main) JBoss Modules version 1.2.0.CR1
              

               

              I do not think "-Xms64M -Xmx512M -XX:MaxPermSize=256M " can produce this error "Could not reserve enough space for object heap  ". Any idea?

              • 5. Re: Error when running domain.bat for cluster
                sesharao_n Newbie

                Even i am facing same problem.

                • 6. Re: Error when running domain.bat for cluster
                  Wolf-Dieter Fink Master

                  How much memory you have installed at this machine, or do you use a VM?

                  Could you start the domain without any server configured or with only one?

                  I don't see ATM that this is cluster related.

                  • 7. Re: Error when running domain.bat for cluster
                    mike just Master

                    This error happens without starting a VM. I just run domain.bat and then this error occurs. And I have 4G memory at my machine.

                    • 8. Re: Error when running domain.bat for cluster
                      sesharao_n Newbie

                      My System configuration is:

                      8GB RAM, 500GB hardDisk, i7 processor and windows7 OS.

                      When i start domain with only one server --> then its giving same error message.

                      I tried to start the domain without any server configurations then --> the server is started successfully but its showing (0 services are passive or on-demand).

                      Thanks for your replys.

                      • 9. Re: Error when running domain.bat for cluster
                        Wolf-Dieter Fink Master

                        Do you run any other application which consume memory?

                        Sometimes restarting windows helps.

                        Could you show/attach the domain.conf.bat and the domain/host.xml?

                        • 10. Re: Error when running domain.bat for cluster
                          Wolf-Dieter Fink Master

                          What if you start without a server, do you see how much memory is consumed by the runing JVM's?

                          You do not need a huge amount of memory for the domain/process controller in the domain.conf.bat.

                          • 11. Re: Re: Error when running domain.bat for cluster
                            mike just Master

                            domain.conf.bat:

                            rem ### -*- batch file -*- ######################################################
                            rem #                                                                          ##
                            rem #  JBoss Bootstrap Script Configuration                                    ##
                            rem #                                                                          ##
                            rem #############################################################################
                            
                            
                            rem # $Id: domain.conf.bat,v 1.1 2013/04/19 06:06:23 leo Exp $
                            
                            
                            rem #
                            rem # This batch file is executed by run.bat to initialize the environment
                            rem # variables that run.bat uses. It is recommended to use this file to
                            rem # configure these variables, rather than modifying run.bat itself.
                            rem #
                            
                            
                            if not "x%JAVA_OPTS%" == "x" (
                              echo "JAVA_OPTS already set in environment; overriding default settings with values: %JAVA_OPTS%"
                              goto JAVA_OPTS_SET
                            )
                            
                            
                            rem #
                            rem # Specify the JBoss Profiler configuration file to load.
                            rem #
                            rem # Default is to not load a JBoss Profiler configuration file.
                            rem #
                            rem set "PROFILER=%JBOSS_HOME%\bin\jboss-profiler.properties"
                            
                            
                            rem #
                            rem # Specify the location of the Java home directory (it is recommended that
                            rem # this always be set). If set, then "%JAVA_HOME%\bin\java" will be used as
                            rem # the Java VM executable; otherwise, "%JAVA%" will be used (see below).
                            rem #
                            rem set "JAVA_HOME=C:\opt\jdk1.6.0_23"
                            
                            
                            rem #
                            rem # Specify the exact Java VM executable to use - only used if JAVA_HOME is
                            rem # not set. Default is "java".
                            rem #
                            rem set "JAVA=C:\opt\jdk1.6.0_23\bin\java"
                            
                            
                            rem #
                            rem # Specify options to pass to the Java VM. Note, there are some additional
                            rem # options that are always passed by run.bat.
                            rem #
                            
                            
                            rem # JVM memory allocation pool parameters - modify as appropriate.
                            set "JAVA_OPTS=-Xms64M -Xmx512M -XX:MaxPermSize=256M"
                            
                            
                            rem # Prefer IPv4
                            set "JAVA_OPTS=%JAVA_OPTS% -Djava.net.preferIPv4Stack=true"
                            
                            
                            rem # Make Byteman classes visible in all module loaders
                            rem # This is necessary to inject Byteman rules into AS7 deployments
                            set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.system.pkgs=org.jboss.byteman"
                            
                            
                            rem # Use JBoss Modules lockless mode
                            rem set "JAVA_OPTS=%JAVA_OPTS% -Djboss.modules.lockless=true"
                            
                            
                            rem The ProcessController process uses its own set of java options
                            set "PROCESS_CONTROLLER_JAVA_OPTS=%JAVA_OPTS%"
                            
                            
                            rem The HostController process uses its own set of java options
                            set "HOST_CONTROLLER_JAVA_OPTS=%JAVA_OPTS%"
                            
                            
                            rem # Sample JPDA settings for remote socket debugging
                            rem set "PROCESS_CONTROLLER_JAVA_OPTS=%PROCESS_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8788,server=y,suspend=n"
                            rem set "HOST_CONTROLLER_JAVA_OPTS=%HOST_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"
                            
                            
                            rem # Sample JPDA settings for shared memory debugging
                            rem set "PROCESS_CONTROLLER_JAVA_OPTS=%PROCESS_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
                            rem set "HOST_CONTROLLER_JAVA_OPTS=%HOST_CONTROLLER_JAVA_OPTS% -agentlib:jdwp=transport=dt_shmem,address=jboss,server=y,suspend=n"
                            
                            
                            :JAVA_OPTS_SET
                            
                            

                             

                            host.xml:

                            <?xml version='1.0' encoding='UTF-8'?>
                            
                            
                            <host name="master" xmlns="urn:jboss:domain:1.4">
                            
                            
                                <management>
                                    <security-realms>
                                        <security-realm name="ManagementRealm">
                                            <authentication>
                                                <local default-user="$local" />
                                                <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir"/>
                                            </authentication>
                                        </security-realm>
                                        <security-realm name="ApplicationRealm">
                                            <authentication>
                                                <local default-user="$local" allowed-users="*" />
                                                <properties path="application-users.properties" relative-to="jboss.domain.config.dir" />
                                            </authentication>
                                            <authorization>
                                                <properties path="application-roles.properties" relative-to="jboss.domain.config.dir"/>
                                            </authorization>
                                        </security-realm>
                                    </security-realms>
                                    <management-interfaces>
                                        <native-interface security-realm="ManagementRealm">
                                            <socket interface="management" port="${jboss.management.native.port:9999}"/>
                                        </native-interface>
                                        <http-interface security-realm="ManagementRealm">
                                            <socket interface="management" port="${jboss.management.http.port:9990}"/>
                                        </http-interface>
                                    </management-interfaces>
                                </management>
                            
                            
                                <domain-controller>
                                   <local/>
                                   <!-- Alternative remote domain controller configuration with a host and port -->
                                   <!-- <remote host="${jboss.domain.master.address}" port="${jboss.domain.master.port:9999}" security-realm="ManagementRealm"/> -->
                                </domain-controller>
                            
                            
                                <interfaces>
                                    <interface name="management">
                                        <inet-address value="${jboss.bind.address.management:192.168.1.2}"/>
                                    </interface>
                                    <interface name="public">
                                       <inet-address value="${jboss.bind.address:192.168.1.2}"/>
                                    </interface>
                                    <interface name="unsecure">
                                        <!-- Used for IIOP sockets in the standard configuration.
                                             To secure JacORB you need to setup SSL -->
                                        <inet-address value="${jboss.bind.address.unsecure:192.168.1.2}"/>
                                    </interface>
                                </interfaces>
                            
                            
                              <jvms>
                                <jvm name="default">
                                      <heap size="64m" max-size="512m"/>
                                      <permgen size="256m" max-size="256m"/>
                                        <jvm-options>
                                            <option value="-server"/>
                                        </jvm-options>
                                   </jvm>
                              </jvms>
                            
                            
                                <servers>
                                    <server name="server-one" group="main-server-group">
                                        <!-- Remote JPDA debugging for a specific server
                                        <jvm name="default">
                                          <jvm-options>
                                            <option value="-agentlib:jdwp=transport=dt_socket,address=8787,server=y,suspend=n"/>
                                          </jvm-options>
                                       </jvm>
                                       -->
                                    </server>
                                    <server name="server-two" group="main-server-group" auto-start="true">
                                        <!-- server-two avoids port conflicts by incrementing the ports in
                                             the default socket-group declared in the server-group -->
                                        <socket-bindings port-offset="150"/>
                                    </server>
                                    <server name="server-three" group="other-server-group" auto-start="false">
                                        <!-- server-three avoids port conflicts by incrementing the ports in
                                             the default socket-group declared in the server-group -->
                                        <socket-bindings port-offset="250"/>
                                    </server>
                                </servers>
                            </host>
                            
                            • 12. Re: Error when running domain.bat for cluster
                              Wolf-Dieter Fink Master

                              That configuration looks very similar to the defaults. I can start the server with that on my local Windows with 4GB without any issue.

                              I use a Java1.7_21@Windows7, the memory consumption is 20M/120M/310M/310M if I start the default domain configuration of EAP6.1.0.Alpha.

                               

                              I would recommend to use a uptodate JVM (I saw a 1.6.0_07 in the log)

                               

                              BTW, you should attach the files instead of copy'n'paste to prevent from a long scrolling . You can do that by editing your comment, only here you see the attach link.

                              • 13. Re: Error when running domain.bat for cluster
                                sesharao_n Newbie

                                Probably we need to use Java1.7.

                                 

                                I am using java1.6 on Windows7, directly i can't migrate to Java7 because i have some other dependencies.

                                 

                                below you can find My JVM details,

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

                                 

                                  JBoss Bootstrap Environment

                                 

                                  JBOSS_HOME: C:\DEV\server\jboss-eap-6.1

                                 

                                  JAVA: C:\Program Files (x86)\Java\jdk1.6.0_24\bin\java

                                 

                                  JAVA_OPTS: -Dprogram.name=domain.bat -Xms64M -Xmx512M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman

                                 

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

                                • 14. Re: Error when running domain.bat for cluster
                                  Wolf-Dieter Fink Master

                                  You might install/copy a JRE1.7 to the system and set the JAVA_HOME before you start the test instance to see whether Java7 helps

                                  1 2 Previous Next