0 Replies Latest reply on Jun 19, 2008 4:02 AM by 666705

    Weblogic 9.2MP2 creating JMS object failed with Deployer error

    666705
      I'm not sure which forum I should post this question. I thought I'll start with this one.

      During our product installation, we have a script that creates a bunch of JMS objects (Queues, Topics, DistributedQueueMembers, etc) using weblogic.Admin commands (a combindation of CREATE -mbean and BATCHUPDATE).

      After all these are done, the script starts the Managed Server.

      When we try to do simultaneous installations on multiple machines, everything works great up to the point where one of the installation script will start the Managed Server on that machine. The command it's using is:

      weblogic.Admin START

      At this point, the 2nd installation (still doing JMS object creations) would fail with this error.

      Executing command: SET -mbean HDMDomain:JMSDistributedQueue=alcatel/jms/snmpTriggerQueue,Name=alcatel/jms/snmpTriggerQueue@c1521_37004,Type=JMSDistributedQueueMember -property JMSQueue "HDMDomain:JMSServer=c1521_37004_jms,Name=alcatel/jms/snmpTriggerQueue@c1521_37004,Type=JMSQueue"

      java.rmi.RemoteException : [Deployer:149150]An IOException occured while reading input. : with response code '404' : with response message 'Not Found'

      The stack dump in Admin server log is:

      ####<Jun 18, 2008 9:24:06 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACT
      IVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <hdm_admin> <> <> <1213842246921> <BEA-149172> <Deployment request 1,213,842,246,896 affecting system resource interop-jms involves a non dynamic property TemplateBean in weblogic.j2ee.descriptor.wl.ThresholdParamsBeanImpl@84ed25(/Queues[alcatel/jms/snmpTrigge
      rQueue@c1521_37004]/Thresholds) and hence will require a restart of the resource or the appropriate server targets for the changes to be active.>
      ####<Jun 18, 2008 9:24:06 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <hdm_admin> <> <> <1213842246930> <BEA-149038> <Initiating Task for interop-jms : [Deployer:149026]redeploy application interop-jms on c1521_37004,AdminServer_39002,c1522_37004,data_37004.>
      ####<Jun 18, 2008 9:24:07 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1213842247870> <BEA-149171> <Deferred deployment task: [Deployer:149026]redeploy application interop-jms on c1521_37004,AdminServer_39002,c1522_37004,data_37004.>
      ####<Jun 18, 2008 9:24:08 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <hdm_admin> <> <> <1213842248621> <BEA-149038> <Initiating Task for interop-jms : [Deployer:149026]redeploy application interop-jms on c1521_37004,AdminServer_39002,c1522_37004,data_37004.>
      ####<Jun 18, 2008 9:24:09 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1213842249591> <BEA-149171> <Deferred deployment task: [Deployer:149026]redeploy application interop-jms on c1521_37004,AdminServer_39002,c1522_37004,data_37004.>
      ####<Jun 18, 2008 9:24:10 PM CDT> <Info> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <hdm_admin> <> <> <1213842250292> <BEA-149038> <Initiating Task for interop-jms : [Deployer:149026]redeploy application interop-jms on c1521_37004,AdminServer_39002,c1522_37004,data_37004.>
      ####<Jun 18, 2008 9:24:13 PM CDT> <Warning> <Deployer> <data> <AdminServer_39002> <[ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1213842253870> <BEA-149004> <Failures were detected while initiating redeploy task for application 'interop-jms'.>
      ####<Jun 18, 2008 9:24:13 PM CDT> <Warning> <Deployer> <data> <AdminServer_39002> <[
      ACTIVE] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
      Kernel>> <> <> <1213842253872> <BEA-149078> <Stack trace for message 149004
      java.rmi.RemoteException: [Deployer:149150]An IOException occured while reading inpu
      t. : with response code '404' : with response message 'Not Found'
      at weblogic.deploy.service.internal.transport.http.HTTPMessageSender.sendMes
      sageToServerURL(HTTPMessageSender.java:297)
      at weblogic.deploy.service.internal.transport.http.HTTPMessageSender.sendMes
      sageToTargetServer(HTTPMessageSender.java:123)
      at weblogic.deploy.service.internal.transport.CommonMessageSender$1.run(Comm
      onMessageSender.java:281)
      at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManager
      Impl.java:518)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
      >

      My questions are:
      1) Why would starting the managed server have anything to do with and why would it interfere with JMS object creations?

      2) How do I get around this problem? Our customers have existing 20+ managed servers. To do our product install on all 20+ managed servers serially is not going to fly.