12 Replies Latest reply on Dec 3, 2009 8:25 AM by Rasa Here

    Jboss Upgradation

    Rasa Here Novice

      Hi,

      I am trying to upgrade my jboss version frm 3.2.x to 4.2.3 GA. Setup made and deployed ear file. But when i started the server using run.sh its giving following error.

      1.

       [ServiceController] Problem starting service jboss:service=WebService
      java.lang.Exception: Port 8083 already in use.
       at org.jboss.web.WebServer.start(WebServer.java:233)
       at org.jboss.web.WebService.startService(WebService.java:322)
       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:585)
       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 org.jboss.system.ServiceController.start(ServiceController.java:435)
       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:585)
      

      2.
       [ServiceController] Problem starting service jboss:service=Naming
      java.rmi.server.ExportException: Port already in use: 1098; nested exception is:
       java.net.BindException: Address already in use
       at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:249)
       at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:184)
       at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
       at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
       at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
       at org.jnp.server.Main.initJnpInvoker(Main.java:354)
       at org.jnp.server.Main.start(Main.java:316)
       at org.jboss.naming.NamingService.startService(NamingService.java:284)
      

      3.

       [ServiceController] Problem starting service jboss:service=invoker,type=jrmp
      java.rmi.server.ExportException: Port already in use: 4444; nested exception is:
       java.net.BindException: Address already in use
       at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:249)
       at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:184)
       at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
       at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
       at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:180)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:293)
       at java.rmi.server.UnicastRemoteObject.exportObject(UnicastRemoteObject.java:256)
       at org.jboss.invocation.jrmp.server.JRMPInvoker.exportCI(JRMPInvoker.java:450)
       at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:372)
       at org.jboss.invocation.jrmp.server.JRMPInvoker$1.startService(JRMPInvoker.java:150)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
       at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245)
       at org.jboss.invocation.jrmp.server.JRMPInvoker.jbossInternalLifecycle(JRMPInvoker.java:644)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      


      In which xml file this port no are being configured. I think the 2nd is jboss-service.xml, but the issue is i have 2 more jboss of version 3.2.* in the server so that's giving error for 1098. If i will change in to some other hope that will work. But what about others ?

      Please guide me to find out a solution.

      Thanks and Regards
      Rasa.

        • 1. Re: Jboss Upgradation
          Peter Johnson Master

           

          i have 2 more jboss of version 3.2.* in the server


          This tells me that you must already know about the binding manager service; you can use the same mechanism in 4.2.3.
          https://www.jboss.org/community/docs/DOC-9520
          http://www.jboss.org/community/docs/DOC-9038

          • 2. Re: Jboss Upgradation
            Rasa Here Novice

            I have some idea, but if there is any document available for 4.2.3 GA pls give me thie link.
            Actually in a standalone setup itself its not working. We usually have jbosswebtomcat.sar file in 3.2.5 but in the 4.2* version its not there. Please provide a line by line configurattion doc.

            Thanks and Regards
            Rasa

            • 3. Re: Jboss Upgradation
              Peter Johnson Master

              In 4.2.x, the jbossweb-tomcat SAR was replaced with jboss-web.deployer, the server.xml file is in there.

              The second link I gave you has port binding configuration instructions for 4.x (works in 4.0.x and 4.2.x)

              • 4. Re: Jboss Upgradation
                Rasa Here Novice

                ok thanks for your kind support.

                Now i have only one jboss in my machine and the server.xml configuration in jboss.we.deployer is as follows

                 <Connector port="8080" address="${jboss.bind.address}"
                 maxThreads="250" maxHttpHeaderSize="8192"
                 emptySessionPath="true" protocol="HTTP/1.1"
                 enableLookups="false" redirectPort="8443" acceptCount="100"
                 connectionTimeout="20000" disableUploadTimeout="true" />
                


                So my port is 8080, i have started my jboss server using sh run.sh & command then i tried http://myIp:8080/ i am not able to get the expected result. In Console there is no error at all. I haven't deployed my application in the deploy dir. I just want to see whether the jboss is up or not. The process is running properly i have checked it by using ps -eaf |grep java and it gives the out put.

                I am not able to guess what is the issue??

                Please guide me to find the actual problem. If you need my log file i will give that also.

                Thanks and Regards
                Rasa

                • 5. Re: Jboss Upgradation
                  jaikiran pai Master

                   

                  my jboss server using sh run.sh & command then i tried http://myIp:8080/ i am not able to get the expected result. In Console there is no error at all.


                  See this http://www.jboss.org/community/docs/DOC-10179. Use -b option to start the server.

                  • 6. Re: Jboss Upgradation
                    Rasa Here Novice

                    Thnks for your support.

                    I tried as you suggested.

                    ./run.sh -b localhost
                    and
                    
                     ./run.sh -b 0.0.0.0

                    But the result is same. That is when i am trying to connect through browser it gives error Unable to connect Firefox can't establish a connection to the server at IP and port.

                    In the console i am getting following message and stops there itself
                    1:02:44,192 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
                    21:02:44,261 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
                    21:02:44,645 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
                    21:02:44,685 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-6009
                    21:02:44,705 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181417)] Started in 37s:557ms


                    Actually my application is not deployed yet. The reason is its not compatible with 1.5 java version. Is there any relation with that, as far as i know nothing. If everything is started properly then i should get the web-console rt ? Anything i have missed out. I am checking everything based on 3.2.5 version. Something else i need to do ???
                    Please help me to solve this issue.

                    Thanks and Regards
                    Rasa

                    • 7. Re: Jboss Upgradation
                      Peter Johnson Master

                      According to this line:

                      21:02:44,645 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080

                      the hTTP port is bound to 8080 on all IP addresses. So you should get back a response when doing http://hostname:8080

                      The only other thing to check is the firewall - make sure that port 8080 is accessible. One way of verifying that it to run "telnet hostname 8080" and see what you get back.

                      • 8. Re: Jboss Upgradation
                        Rasa Here Novice

                        Yes i tried the same and its working fine. But still its not giving the requested page. But still its not working. One thing i have noticed is one tomcat is configured in the same machine for the same port but now that process is not running. So please guide me to find the solution.

                        Thanks and Regards
                        Rasa

                        • 9. Re: Jboss Upgradation
                          Rasa Here Novice

                          I have changed my port no as 8585 and when i gone through the log i got following error.

                          [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /home/java5/jdk1.5.0_18/jre/lib/i386/server:/home/java5/jdk1.5.0_18/jre/lib/i386:/home/java5/jdk1.5.0_18/jre/../lib/i386
                          


                          May be this is the issue. Please help me to solve the issue.

                          Thanks and Regards
                          Rasa

                          • 10. Re: Jboss Upgradation
                            jaikiran pai Master

                            That log is just a INFO message. That won't come into picture for what you are running into.

                            I have changed my port no as 8585


                            Let's not make a lot of changes, since it becomes difficult to track what might be wrong. Switch back to 8080 since we saw that the server was starting up fine with that port.

                            As Peter suggested,
                            "PeterJ" wrote:
                            One way of verifying that it to run "telnet hostname 8080" and see what you get back.


                            what output did you get with

                            telnet your-server-ip-address 8080


                            on the system where you are trying to access the server.



                            • 11. Re: Jboss Upgradation
                              Peter Johnson Master

                              The AprLifecycleListener log entry is not a problem. This simply means that APR will not be used, and you do not need it.

                              With JBoss AS running, run netstat and determine which ports JBoss AS had open.

                              Yes i tried the same and its working fine.


                              Please define "the same". My prior post contained several things for you to try, which one did you try that worked? I am especially interested in the results of running telnet.

                              • 12. Re: Jboss Upgradation
                                Rasa Here Novice

                                The issue got solved. One tomcat process is running in that port.