5 Replies Latest reply on Dec 20, 2006 11:53 AM by jangeysen

    Error while starting the Jboss Application Server.

    anand_anan2k

      Hello,

      I installed jboss application server 4.0.5. But when i tried to execute the run.sh, getting the following errr:

      18:07:59,047 INFO [JkMain] Jk running ID=0 time=0/120 config=null
      18:07:59,061 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 28s:593ms
      18:08:06,177 WARN [UDP] packet from /17.128.106.51:64550 has different version (0227?) from ours (02271). This may cause problems
      18:08:06,178 ERROR [UDP] exception=java.io.StreamCorruptedException: invalid stream header
      at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:753)
      at java.io.ObjectInputStream.(ObjectInputStream.java:268)
      at org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:670)
      at org.jgroups.protocols.UDP.run(UDP.java:249)
      at java.lang.Thread.run(Thread.java:613)

      ^C18:08:12,169 INFO [Server] Runtime shutdown hook called, forceHalt: true
      18:08:12,171 INFO [Server] JBoss SHUTDOWN: Undeploying all packages
      18:08:13,766 INFO [TomcatDeployer] undeploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
      18:08:13,790 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' from JNDI name 'java:JmsXA'
      18:08:13,820 INFO [testTopic] Unbinding JNDI name: topic/testTopic
      18:08:13,822 INFO [securedTopic] Unbinding JNDI name: topic/securedTopic
      18:08:13,823 INFO [testDurableTopic] Unbinding JNDI name: topic/testDurableTopic
      18:08:13,827 INFO [testQueue] Unbinding JNDI name: queue/testQueue
      18:08:13,843 INFO [A] Unbinding JNDI name: queue/A
      18:08:13,845 INFO [B] Unbinding JNDI name: queue/B
      18:08:13,849 INFO [C] Unbinding JNDI name: queue/C
      18:08:13,851 INFO [D] Unbinding JNDI name: queue/D
      18:08:13,853 INFO [ex] Unbinding JNDI name: queue/ex
      18:08:13,859 INFO [DLQ] Unbinding JNDI name: queue/DLQ
      18:08:13,864 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' from JNDI name 'java:DefaultDS'
      18:08:15,180 WARN [UDP] packet from /17.128.106.51:51491 has different version (0227?) from ours (02271). This may cause problems
      18:08:15,182 ERROR [UDP] exception=java.io.StreamCorruptedException: invalid stream header
      at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:753)
      at java.io.ObjectInputStream.(ObjectInputStream.java:268)
      at org.jgroups.protocols.UDP.handleIncomingUdpPacket(UDP.java:670)
      at org.jgroups.protocols.UDP$IncomingPacketHandler.run(UDP.java:1332)
      at java.lang.Thread.run(Thread.java:613)


      Machine details:

      OS - mac os 10.4.8.
      Java - 1.5

      Please let me know if i missed anything on this.

      Thanks again,
      Elangovan.

        • 1. Re: Error while starting the Jboss Application Server.
          ip0

          Do you need clustering? If not, try to start the default config.

          Will look at it tonight again when on my mac box.

          • 2. Re: Error while starting the Jboss Application Server.
            anand_anan2k

            I used JBOSS portal bundle version. It is working fine.

            Thank u,
            Elangovan.

            • 3. Re: Error while starting the Jboss Application Server.
              manjunath_n156

              Hi,
              I am getting the same error and i am trying to enable clustering to my jboss AS. Can any one tell me how can i overcome this error?

              Regards
              Manjunath

              • 4. Re: Error while starting the Jboss Application Server.
                kircuv

                I'm having the same problem.
                In my configuration, I'm using JGroups in addition to standard JBoss clustering.

                • 5. Re: Error while starting the Jboss Application Server.

                  you have conflict with another jboss (version < 4.0.5) server running

                  change your messaging ip addresses (or ports) for clustering

                  1 For EJB clustering

                  In the file <JBOSS_HOME> \server\\deploy\cluster-service.xml, change in the mbean jboss:service=${jboss.partition.name:DefaultPartition}" the UDP entry:
                  <UDP mcast_addr="${jboss.partition.udpGroup:228.1.2.3}" mcast_port="45566"

                  Adapt the ClusteredConsoleServlet in the console accordingly. In <JBOSS_HOME> \server\\deploy\jmx-console.war\WEB-INF\web.xml? change the line <param-value> UDP(ip_mcast=true;ip_ttl=16; loopback=false; mcast_addr= ${jboss.partition.udpGroup:228.1.2.3};mcast_port=45566):

                  2 For JNDI clustering

                  In the same file <JBOSS_HOME> \server\\deploy\cluster-service.xml, change the entry ${jboss.partition.udpGroup:230.0.0.4} .. This address should also be used by the HA-JNDIJMS provider in <JBOSS_HOME> \server\\deploy \jms \hajndi-jms-ds.xml , line jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4}
                  3 For Tomcat clustering
                  In the file <JBOSS_HOME> \server\\deploy \tc5-cluster.sar\META-INF\jboss-service.xml", change the entry <UDP mcast_addr= "${jboss.partition.udpGroup: 230.1.2.7}".