7 Replies Latest reply: Jun 24, 2006 4:28 PM by 666705 RSS

    Error running Weblogic.Deployer in medrec tutorial (wl9.1)

    666705
      Hi,

      I'm a weblogic newbie and am running through the MedRec tutorial for weblogic 9.1 (on Linux). Everything has gone well until I try to deploy the app using the deployer and the ant wldeploy task.

      Here's what I get:

      ant -f deploy.xml
      Buildfile: deploy.xml

      deploy:
      [wldeploy] weblogic.Deployer -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -password ******** -deploy
      [wldeploy] weblogic.Deployer invoked with options: -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -deploy

      BUILD FAILED
      /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/src/physicianEar/deploy.xml:9: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://127.0.0.1:7101': null. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.

      Total time: 15 seconds

      My deploy.xml is very basic:

      <project name="tutorial" default="deploy">

      <target name="deploy">
      <wldeploy user="weblogic"
      password="weblogic"
      adminurl="t3://127.0.0.1:7101"
      action="deploy"
      name="tutorial_deployment"
      source="/usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar"/>
      </target>
      </project>


      and I've checked that I can connect to 127.0.0.1 and port 7101 from the server. Also, the admin server is running!

      I also tried enabling tunneling in the admin server, but this didn't help.

      So I am stumped. Any ideas what the problem could be?

      Any help would be appreciated...

      Alison
        • 1. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
          666705
          Alison,

          can you cerify that you are able to ping the admin server on 127.0.0.1:7101 using the weblogic.Admin PINg command ?

          http://e-docs.bea.com/wls/docs81/admin_ref/cli17.html#1196567

          Cheers
          Raj
          • 2. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
            666705
            Raj,

            The ping command appears to work. Here's the output:

            java weblogic.Admin -url t3://127.0.0.1:7101 -username weblogic -password weblogic ping 3 100
            Sending 3 pings of 100 bytes.

            RTT = ~16 milliseconds, or ~5 milliseconds/packet
            • 3. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
              666705
              Hi Alison,

              That is strange,

              Can you try adding verbose=true to the deploy target, and also try using localhost instead of 127.0.0.1

              <project name="tutorial" default="deploy">

              <target name="deploy">

              <wldeploy user="weblogic"
              password="weblogic"
              adminurl="t3://127.0.0.1:7101"
              action="deploy"
              verbose="true"
              name="tutorial_deployment"
              source="/usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar"/>
              </target>
              </project>

              Also please confirm is you deploying to the same physical machine

              Thanks
              Raj
              • 4. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
                666705
                Hi Raj,

                Adding verbose="true" doesn't seem to change the output. And yes, I'm running this on/deploying to the same physical machine.

                Alison

                -----------------------------------------------------

                ant -f deploy.xml
                Buildfile: deploy.xml

                deploy:
                [wldeploy] weblogic.Deployer -verbose -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -password ******** -deploy
                [wldeploy] weblogic.Deployer invoked with options: -verbose -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -deploy

                BUILD FAILED
                /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/src/physicianEar/deploy.xml:10: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://127.0.0.1:7101': null. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
                • 5. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
                  666705
                  Raj,

                  I ran the command again using -debug and got the following:

                  java weblogic.Deployer -verbose -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -password weblogic -deploy -debug
                  weblogic.Deployer invoked with options: -verbose -noexit -name tutorial_deployment -source /usr/local/bea/user_projects/domains/medrec_domain/medrec_tutorial/build/physicianEar -adminurl t3://127.0.0.1:7101 -user weblogic -deploy -debug
                  [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
                  [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at 127.0.0.1:7101, as user weblogic
                  [ServerConnectionImpl.getEnvironment():282] : setting environment
                  [ServerConnectionImpl.getEnvironment():285] : getting context using t3://127.0.0.1:7101
                  [ServerConnectionImpl.getMBeanServer():237] : Connecting to MBeanServer at service:jmx:t3://127.0.0.1:7101/jndi/weblogic.management.mbeanservers.domainruntime
                  java.io.IOException
                  at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:133)
                  at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:77)
                  at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
                  at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:238)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:190)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:146)
                  at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
                  at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
                  at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
                  at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:375)
                  at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:294)
                  at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
                  at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
                  at weblogic.utils.compiler.Tool.run(Tool.java:158)
                  at weblogic.utils.compiler.Tool.run(Tool.java:115)
                  at weblogic.Deployer.run(Deployer.java:70)
                  at weblogic.Deployer.main(Deployer.java:54)
                  Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
                          java.io.EOFException]
                  at weblogic.jrmp.Context.lookup(Context.java:189)
                  at weblogic.jrmp.Context.lookup(Context.java:195)
                  at javax.naming.InitialContext.lookup(InitialContext.java:351)
                  at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:124)
                  ... 17 more
                  Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
                  java.io.EOFException
                  at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
                  at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
                  at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
                  at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
                  at weblogic.jrmp.RegistryImpl_Stub.lookup(Ljava.lang.String;)Ljava.rmi.Remote;(Unknown Source)
                  at weblogic.jrmp.Context.lookup(Context.java:185)
                  ... 20 more
                  Caused by: java.io.EOFException
                  at java.io.DataInputStream.readByte(DataInputStream.java:243)
                  at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
                  ... 25 more
                  [ServerConnectionImpl.close():328] : Closing DM connection
                  [ServerConnectionImpl.close():348] : Unregistered all listeners
                  weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://127.0.0.1:7101': null. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
                  at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:306)
                  at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:143)
                  at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:93)
                  at weblogic.utils.compiler.Tool.run(Tool.java:158)
                  at weblogic.utils.compiler.Tool.run(Tool.java:115)
                  at weblogic.Deployer.run(Deployer.java:70)
                  at weblogic.Deployer.main(Deployer.java:54)
                  Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://127.0.0.1:7101' as user, 'weblogic'. Error received: null
                  at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
                  at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
                  at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:375)
                  at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:294)
                  ... 6 more
                  Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://127.0.0.1:7101' as user, 'weblogic'. Error received: null
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:249)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:190)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:146)
                  at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
                  at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
                  ... 9 more
                  Caused by: java.io.IOException
                  at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:133)
                  at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:77)
                  at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:326)
                  at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
                  at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:238)
                  ... 13 more
                  Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
                          java.io.EOFException]
                  at weblogic.jrmp.Context.lookup(Context.java:189)
                  at weblogic.jrmp.Context.lookup(Context.java:195)
                  at javax.naming.InitialContext.lookup(InitialContext.java:351)
                  at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:124)
                  ... 17 more
                  Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
                  java.io.EOFException
                  at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
                  at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
                  at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
                  at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
                  at weblogic.jrmp.RegistryImpl_Stub.lookup(Ljava.lang.String;)Ljava.rmi.Remote;(Unknown Source)
                  at weblogic.jrmp.Context.lookup(Context.java:185)
                  ... 20 more
                  Caused by: java.io.EOFException
                  at java.io.DataInputStream.readByte(DataInputStream.java:243)
                  at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
                  ... 25 more
                  Unexpected Error Initializing Deployer: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://127.0.0.1:7101': null. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.

                  Does this help???

                  Alison
                  • 6. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
                    666705
                    Hi Alison,

                    What flavor and version of Linux are u on ?

                    thanks
                    Raj
                    • 7. Re: Error running Weblogic.Deployer in medrec tutorial (wl9.1)
                      666705
                      Hi Raj

                      I have exactly the same problem. I guess WLDeploy is broken in Weblogic9.1. I spent a full day on this problem and I couldn't fix it. As a work around, If you use ant task, define <wldeploy> task based in the jar files from WebLogic 9.0.

                      I put the ant task here:
                      <target name="deploy-war">
                      <wldeploy adminurl="t3://127.0.0.1:7001" user="..." password="..." debug="true" action="deploy" source="${distribution.dir}/${war.name}" name="mySpring"/>
                      </target>

                      and the task def:

                      <taskdef name="wldeploy" classname="weblogic.ant.taskdefs.management.WLDeploy">
                      <classpath>
                      <path refid="compile.classpath"/>
                      </classpath>
                      </taskdef>

                      in which:

                      <path id="compile.classpath">
                      <pathelement location="${j2ee.jar}"/>
                      <pathelement location="${weblogic.jar}"/>
                      <pathelement location="${wlclient.jar}"/>
                      <pathelement location="${xbean.jar}"/>
                      </path>

                      The jar files above must be from WebLogic 9.0
                      It worked for me, I hope the same for you.