1 Reply Latest reply on Apr 16, 2007 1:33 PM by 666705

    WLST: Deleting JMSDestination on managed server

    666705
      Hi again,

      When trying to delete a JMSQueue/JMSTopic targeted to a managed sever, WLST "hangs" and the admin server stops listening for requests.

      I have a JMSQueue assigned to a JMSServer targeted to a managed server.

      When I want to delete the queue I connect to the Admin server and try to delete it using WLST:

      cd('JMSServers/'+jmsServerName)
      delete('MyQueue', 'JMSQueue')

      The delete()-call will hang and the admin server stops listening for requests. Once I received this message after several minutes in the WLST-output:

      'Error occured while performing delete : Unknown Error. Use dumpStack() to view
      the error stack trace'
      <Oct 19, 2004 9:46:04 AM CEST> <Info> <RJVM> <BEA-000513> <Failure in heartbeat
      trigger for RJVM: 9050020159100362840S:hfldc-ws07.ericsson.se:
      [34088,34088,34288,34288,34088,34288,-1,0,0]:IntegrationTest:AdminServer
      {N:AdminServer_127.0.0.1:t3:127.0.0.1:[34088]:60:127.0.0.1:[-1]}
      java.io.IOException: The connection manager to ConnectionManager
      for: 'weblogic.rjvm.RJVMImpl@b76db4 - id: '9050020159100362840S:hfldc-
      ws07.ericsson.se:[34088,34088,34288,34288,34088,34288,-
      1,0,0]:IntegrationTest:AdminServer{N:AdminServer_127.0.0.1:t3:127.0.0.1:
      [34088]:60:127.0.0.1:[-1]}' connect time: 'Tue Oct 19 09:41:02 CEST 2004'' has
      already been shut down.
      java.io.IOException: The connection manager to ConnectionManager
      for: 'weblogic.rjvm.RJVMImpl@b76db4 - id: '9050020159100362840S:hfldc-
      ws07.ericsson.se:[34088,34088,34288,34288,34088,34288,-
      1,0,0]:IntegrationTest:AdminServer{N:AdminServer_127.0.0.1:t3:127.0.0.1:
      [34088]:60:127.0.0.1:[-1]}' connect time: 'Tue Oct 19 09:41:02 CEST 2004'' has
      already been shut down
           at weblogic.rjvm.ConnectionManager.getOutputStream
      (ConnectionManager.java:1587)
           at weblogic.rjvm.ConnectionManager.createHeartbeatMsg
      (ConnectionManager.java:1536)
           at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg
      (ConnectionManager.java:555)
           at weblogic.rjvm.RJVMImpl$HeartbeatChecker.trigger(RJVMImpl.java:1354)
           at weblogic.time.common.internal.ScheduledTrigger.run
      (ScheduledTrigger.java:243)
           at weblogic.security.acl.internal.AuthenticatedSubject.doAs
      (AuthenticatedSubject.java:317)
           at weblogic.security.service.SecurityManager.runAs
      (SecurityManager.java:118)
           at weblogic.time.common.internal.ScheduledTrigger.executeLocally
      (ScheduledTrigger.java:229)
           at weblogic.time.common.internal.ScheduledTrigger.execute
      (ScheduledTrigger.java:223)
           at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
           at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
      >


      What is the solution for this? How do I remove a JMSDestination located on a managed server?

      I use WLS 8.1SP2 and WLSTv3. I have a node manager running and everything works fine until I want to remove the queue.
        • 1. Re: WLST: Deleting JMSDestination on managed server
          666705
          i am also getting the same error at different case
          i am trying to retrieve huge amount of data it may take arround 10mins to process at the 5 min i am getting an following exception
          weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
          at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
          at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
          .java:315)
          at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
          .java:250)
          at com.nybot.prd.businesscomponent.ProductDictionaryMaintenanceBean_etiu
          ur_EOImpl_910_WLStub.retrieveInstruments(Unknown Source)
          at RetrieveFuturesInstruments.testInstruments(RetrieveFuturesInstruments
          .java:67)
          at RetrieveFuturesInstruments.main(RetrieveFuturesInstruments.java:87)


          At the rare case i got the following exception for the same above trials


          <Apr 16, 2007 10:09:01 AM EDT> <Info> <RJVM> <BEA-000513> <Failure in heartbeat
          trigger for RJVM: 6496554247118500393S:nyepsdev:[7005,-1,-1,-1,-1,-1,-1]:Test_domain:TEST1 java.io.IOException: The connection manager to ConnectionManager for: 'weblogic
          .rjvm.RJVMImpl@9df6f1 - id: '6496554247118500393S:nyepsdev:[7005,-1,-1,-1,-1,-1,
          -1]:Test_domain:TEST1' connect time: 'Mon Apr 16 10:04:01 EDT 2007'' has already
          been shut down.
          java.io.IOException: The connection manager to ConnectionManager for: 'weblogic.
          rjvm.RJVMImpl@9df6f1 - id: '6496554247118500393S:nyepsdev:[7005,-1,-1,-1,-1,-1,-
          1]:Test_domain:TEST1' connect time: 'Mon Apr 16 10:04:01 EDT 2007'' has already b
          een shut down
          at weblogic.rjvm.ConnectionManager.getOutputStream(ConnectionManager.jav
          a:1614)
          at weblogic.rjvm.ConnectionManager.createHeartbeatMsg(ConnectionManager.
          java:1558)
          at weblogic.rjvm.ConnectionManager.sendHeartbeatMsg(ConnectionManager.ja
          va:600)
          at weblogic.rjvm.RJVMImpl$HeartbeatChecker.timerExpired(RJVMImpl.java:14
          88)
          at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
          at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.jav
          a:21)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
          >
          weblogic.rjvm.PeerGoneException: No message was received for: '240' seconds
          at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
          at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
          .java:315)
          at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef
          .java:250)
          at com.nybot.prd.businesscomponent.ProductDictionaryMaintenanceBean_etiu
          ur_EOImpl_910_WLStub.retrieveInstruments(Unknown Source)
          at RetrieveFuturesInstruments.testInstruments(RetrieveFuturesInstruments
          .java:67)
          at RetrieveFuturesInstruments.main(RetrieveFuturesInstruments.java:87)

          --
          S.Prabhu