Menu

Sipexchange failed to run

2007-10-17
2012-12-17
  • Nobody/Anonymous

    Hi,

    I am using Java version 1.5 and JBoss version 4.2.1
    Installation of sipexchange is done as per the guidelines given in the
    website. But when i start the JBoss server to run the SIPEXCHANGE it
    is failing with the following error log. Attached here below the error
    logs.

    Please help me in this regard.

    Log:
    ----

    at
    org.jboss.ws.metadata.builder.jaxws.JAXWSMetaDataBuilder.createJAXBCo
    ntext(JAXWSMetaDataBuilder.java:875)
    ... 82 more
    10:48:59,933 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

    --- Incompletely deployed packages ---
    org.jboss.deployment.DeploymentInfo@519c3cc4 { url=file:/C:/Program
    Files/jboss-
    4.2.1.GA/server/default/deploy/sipex-inservice.sar }
    deployer: org.jboss.deployment.SARDeployer@164dbd5
    status: Deployment FAILED reason: Trying to install an already registered
    mbea
    n: jboss.remoting:service=NetworkRegistry
    state: FAILED
    watch: file:/C:/Program
    Files/jboss-4.2.1.GA/server/default/deploy/sipex-inser
    vice.sar
    altDD: null
    lastDeployed: 1192598322791
    lastModified: 1192598322416
    mbeans:

    org.jboss.deployment.DeploymentInfo@c15e6f31 { url=file:/C:/Program
    Files/jboss-
    4.2.1.GA/server/default/deploy/sipexchange.esr }
    deployer: org.cafesip.jiplet.jboss.EsrDeployer@10ac2a3
    status: Deployment FAILED reason: Cannot create service endpoint; -
    nested thr
    owable: (java.lang.IllegalStateException: Cannot build JAXB context)
    state: FAILED
    watch: file:/C:/Program
    Files/jboss-4.2.1.GA/server/default/deploy/sipexchange
    .esr
    altDD: null
    lastDeployed: 1192598338308
    lastModified: 1192598334526
    mbeans:

    10:49:00,074 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
    http-127.0.0.1-8
    080
    10:49:00,089 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on
    http-127.0.0.1-8
    443
    10:49:00,121 INFO [AjpProtocol] Starting Coyote AJP/1.3 on
    ajp-127.0.0.1-8009
    10:49:00,214 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build:
    SVNTag=JBos
    s_4_2_1_GA date=200707131605)] Started in 37s:846ms

    Expecting response eagerly.

    Thanks in advance,
    Karthik

     
    • Becky Mc

      Becky Mc - 2007-10-17

      Hi,

      Yes I just saw it too - with the JBoss version 4.2, the NetworkRegistry mbean is already registered so this exception is coming out. You can ignore it, or if you don't want to see it you can comment out/remove these 2 lines from the jboss-service.xml config file:
          <mbean code="org.jboss.remoting.network.NetworkRegistry"
                 name="jboss.remoting:service=NetworkRegistry"/>

      But it doesn't hurt anything.
      ___

      I ran into one other thing that had to be slightly modified for the later Jboss version that you will also run into. In the SipExchange installation instructions (http://www.cafesip.org/projects/sipexchange/installation_howto.html#Installing_SipExchange)
      in step 6 where you are modifying Jboss's SSL access configuration:

         a) the directory name where the server.xml that you need to edit is has been changed from:
      $JBOSS_HOME/server/$RUN/deploy/jbossweb-tomcat55.war
      to:
      $JBOSS_HOME/server/$RUN/deploy/jboss-web.deployer

         b) in step 6.3, use the following code segment instead of the one shown there in the sipexchange installation page:

          <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true"
                     maxThreads="150" scheme="https" secure="true"
                     clientAuth="false" sslProtocol="TLS"
          keystoreFile="${jboss.server.home.dir}/conf/cafesip.keystore"
                 keystorePass="a1b2c3d4" />

      _____

      If you run into any other issues, please post.

      Regards,
      Becky

       
      • Nobody/Anonymous

        Hi becky,

             Thanks a lot for the inputs. I did the same as you mentioned ignoring the networkregistry exception still there is one more error mentioned in the same log.

        org.jboss.deployment.DeploymentInfo@c15e6f31 { url=file:/C:/Program
        Files/jboss-
        4.2.1.GA/server/default/deploy/sipexchange.esr }
        deployer: org.cafesip.jiplet.jboss.EsrDeployer@10ac2a3
        status: Deployment FAILED reason: Cannot create service endpoint; -
        nested thr
        owable: (java.lang.IllegalStateException: Cannot build JAXB context)
        state: FAILED
        watch: file:/C:/Program
        Files/jboss-4.2.1.GA/server/default/deploy/sipexchange
        .esr
        altDD: null
        lastDeployed: 1192598338308
        lastModified: 1192598334526
        mbeans:

        Whether this will also be ignored or how to proceed??

        Please help me.

        Thanks and regards,
        Karthik

         
        • Nobody/Anonymous

          Hi Becky,

              If i try opening the sipexchange console ignoring the above said error in my previous reply am not able to view the sipexchange console page.
          It shows "Page not found" if i type "http:\\localhostipaddress:8080\sipex"

          Please guide me how to go abt it.

          Expecting your response,

          Thanks in advance,
          Karthik

           
          • Becky Mc

            Becky Mc - 2007-10-18

            Hi Karthik,

            Well, you're really forging new ground here. I didn't see the 'Cannot build JAXB context' error maybe because in your case, you are deploying the binary sipexchange load onto your 4.2 JBoss server while in my case, I had built sipexchange from source and then deployed onto the 4.2 JBoss server.

            Officially, we're not there yet for supporting the latest JBoss 4.2 version. There may be many catches like this, that we don't know about yet and have to find and fix. By the time we put out another sipexchange release, in the next 1-2 months, hopefully we will have found and fixed all of these kinds of issues and we can 'officially' support JBoss 4.2.

            Until then, you can do one of two things: go back to JBoss 4.0.5 version that we know works and have verified sipexchange on, or you can build from source (checkout from SVN to get the latest) like I did and continue forth with JBoss 4.2.x but in that case you may (*will probably*) stumble on more issues that we haven't encountered yet, and fixed.

            I would recommend using JBoss 4.0.x until we've worked out the kinks with JBoss 4.2.x so that you don't have to fight these issues.  (Unless you want to help us find and fix them ;=) ...)

            Regards,
            Becky

             
          • Amit Chatterjee

            Amit Chatterjee - 2007-10-19

            Karthick,

            Please try http://localhost:8080/sipex (use forward slash instead of back slash).

            Also, are you getting the JAXB error that you were getting before Jboss startup? Please send the Jboss log message (and please turn off Jboss DEBUG log - it is printing too much information).

            Regards,
            Amit

             
            • Nobody/Anonymous

              Hi Amit,

                  Thanks for the input. But i am very sorry to say that according to Becky's suggestion now am trying install the sipexchange in Jboss Server 4.0.4 version since i get to know from becky is that sipexchange is tested stable with 4.0.X version and not with 4.2.X.

              So once i install and run it and if i face some problem i wll let u know.

              Thanks,
              Karthik

               

Log in to post a comment.