Remote start petstore using NodeManager

Question

          Hi,
          I am using weblogic 6.1 and remotely deployed pet store application on a different
          machine using NodeManager. When I try to start the petStoreServer from local admin
          console, I got following error:
          Could not create pool connection. The DBMS driver exception was:
          SQL Exception: Database 'petStore' not found.
               at c8e.k.j.l_(Unknown Source)
               at c8e.k.j.l_(Unknown Source)
               at c8e.k.j.n(Unknown Source)
               at c8e.k.q.<init>(Unknown Source)
               at c8e._b.e.<init>(Unknown Source)
               at c8e._b.c.getNewLocalConnection(Unknown Source)
               at c8e.k.v.connect(Unknown Source)
               at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:193)
               at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:134)
               at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:698)
               at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:282)
               at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:623)
               at weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
               at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:233)
               at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy0.updateDeployments(Unknown Source)
               at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub.java:2761)
               at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:370)
               at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:160)
               at java.lang.reflect.Method.invoke(Native Method)
               at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
               at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
               at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
               at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
               at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
               at $Proxy47.start(Unknown Source)
               at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean_CachingStub.java:480)
               at weblogic.management.Admin.startApplicationManager(Admin.java:1180)
               at weblogic.management.Admin.finish(Admin.java:590)
               at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
               at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          Any hint?
          Thanks,
          Cathy
          Covasoft, Inc.
          1250 S. Capital of Texas Hwy.
          Bldg. 1, Suite 240
          Austin, Texas 78746
          Office: 512.732.7860
          Fax: [phone]
          

Answer 1

Just add the property (-Dcloudscape....) as an extra argument to the jvm
          startup parameters in the remote start tab of the remote server. That should
          work as hte nodemanager just uses what settings are there in hte remote
          start to create a server instance.
          -Sabha
          "Cathy" <[email protected]> wrote in message
          news:[email protected]...
          >
          > Thanks for the quick reply. The directory for the petStore database is
          there on
          > the remote machine. I can't deloy datasource to the target server, since
          the connection
          > pool is not created yet due to the database error.
          >
          > The problem I found was that the remote server I started was not the one
          from
          > remote startPetStore.cmd, since the properties from that script is not
          overrided
          > or picked up ( including the cloudscape.system.home). I set up the remote
          server
          > from the admin server console "remote start". Ant hint to make sure the
          admin
          > server remote start use the correct script on the remote machine?
          >
          > Thanks,
          > Cathy
          >
          >
          >
          > "Anand Byrappagari" <[email protected]> wrote:
          > >Cathy,
          > >
          > > If you
          > >have -Dcloudscape.system.home=<BEA_HOME>\samples\eval\cloudscape\data
          > >set
          > >then is there a directory called
          > ><BEA_HOME>\samples\eval\cloudscape\data\petStore present on the remote
          > >server machine? If not you have not created the petStore database.
          > >
          > > The only other thing I can think of is that the connection
          > >pool/datasource are not targeted to the remote server but these errors
          > >usually throw a different exception.
          > >
          > >-- Anand
          > >
          > >
          > >"Cathy" <[email protected]> wrote in message
          > >news:[email protected]...
          > >>
          > >> Thanks for the reply. Actually, I have set this property for the remote
          > >server
          > >> with the right path. But I still got the same error. Any other hints?
          > >>
          > >> Thanks,
          > >> Cathy
          > >>
          > >> "Sabha" <[email protected]> wrote:
          > >> >Make sure you have set the cloudscape home directory in the startup
          > >script:
          > >> >
          > >> >-Dcloudscape.system.home=<BEA_HOME>\samples\eval\cloudscape\data
          > >> >
          > >> >-Sabha
          > >> >
          > >> >
          > >> >"Cathy" <[email protected]> wrote in message
          > >> >news:[email protected]...
          > >> >>
          > >> >> Hi,
          > >> >>
          > >> >> I am using weblogic 6.1 and remotely deployed pet store application
          > >> >on a
          > >> >different
          > >> >> machine using NodeManager. When I try to start the petStoreServer
          > >from
          > >> >local admin
          > >> >> console, I got following error:
          > >> >>
          > >> >> Could not create pool connection. The DBMS driver exception was:
          > >> >> SQL Exception: Database 'petStore' not found.
          > >> >> at c8e.k.j.l_(Unknown Source)
          > >> >> at c8e.k.j.l_(Unknown Source)
          > >> >> at c8e.k.j.n(Unknown Source)
          > >> >> at c8e.k.q.<init>(Unknown Source)
          > >> >> at c8e._b.e.<init>(Unknown Source)
          > >> >> at c8e._b.c.getNewLocalConnection(Unknown Source)
          > >> >> at c8e.k.v.connect(Unknown Source)
          > >> >> at
          > >>
          >
          >>weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(Connecti
          o
          > >n
          > >> >EnvFactory.java:193)
          > >> >> at
          > >>
          >
          >>weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(Connecti
          o
          > >n
          > >> >EnvFactory.java:134)
          > >> >> at
          > >>
          >
          >>weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator
          > >j
          > >> >ava:698)
          > >> >> at
          > >>
          >
          >>weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:2
          8
          > >2
          > >> >)
          > >> >> at
          > >>
          >
          >>weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:6
          2
          > >3
          > >> >)
          > >> >> at
          weblogic.jdbc.common.JDBCService.addDeployment(JDBCService.java:107)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(Deploymen
          t
          > >T
          > >> >arget.java:329)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(Deployme
          n
          > >t
          > >> >Target.java:279)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments
          > >D
          > >> >eploymentTarget.java:233)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(Deplo
          y
          > >m
          > >> >entTarget.java:193)
          > >> >> at java.lang.reflect.Method.invoke(Native Method)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
          p
          > >l
          > >> >..java:636)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
          > >6
          > >> >21)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
          e
          > >a
          > >> >nImpl.java:359)
          > >> >> at
          > >>
          >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > >> >> at
          > >>
          >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > >> >> at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > >> >> at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > >> >> at $Proxy0.updateDeployments(Unknown Source)
          > >> >> at
          > >>
          >
          >>weblogic.management.configuration.ServerMBean_CachingStub.updateDeployment
          s
          > >(
          > >> >ServerMBean_CachingStub.java:2761)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(Ap
          p
          > >l
          > >> >icationManager.java:370)
          > >> >> at
          > >>
          >
          >>weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationMana
          g
          > >e
          > >> >r.java:160)
          > >> >> at java.lang.reflect.Method.invoke(Native Method)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanIm
          p
          > >l
          > >> >..java:636)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java
          > >6
          > >> >21)
          > >> >> at
          > >>
          >
          >>weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMB
          e
          > >a
          > >> >nImpl.java:359)
          > >> >> at
          > >>
          >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          > >> >> at
          > >>
          >com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          > >> >> at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
          > >> >> at
          weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
          > >> >> at $Proxy47.start(Unknown Source)
          > >> >> at
          > >>
          >
          >>weblogic.management.configuration.ApplicationManagerMBean_CachingStub.star
          t
          > >(
          > >> >ApplicationManagerMBean_CachingStub.java:480)
          > >> >> at
          weblogic.management.Admin.startApplicationManager(Admin.java:1180)
          > >> >> at weblogic.management.Admin.finish(Admin.java:590)
          > >> >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:518)
          > >> >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          > >> >>
          > >> >> Any hint?
          > >> >>
          > >> >> Thanks,
          > >> >> Cathy
          > >> >>
          > >> >> Covasoft, Inc.
          > >> >> 1250 S. Capital of Texas Hwy.
          > >> >> Bldg. 1, Suite 240
          > >> >> Austin, Texas 78746
          > >> >> Office: 512.732.7860
          > >> >> Fax: [phone]
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >>
          > >> >
          > >> >
          > >>
          > >
          > >
          >