Clovertech

Java Error on QDX-5.3 rev3

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Java Error on QDX-5.3 rev3

  • Creator
    Topic
  • October 25, 2005 at 9:55 pm #48106
    Francis Kalinoski
    Participant

      On our AIX-5.2 Test platform, shcie2, running QDX-5.3 rev3, often when I am in the Integrator Network Monitor GUI for an extended time I will get the following error when I attempt to change to another site, using Server/Change.  When the NWMonitor gui repaints the Monitor Daemon indicator is RED and all of the treads in the site view are displayed as dead.  In this particular instance I was in the test_a site and the error occurred when I attempted to change to the test_an site where the same error occurred.  When I changed to the test_of or the test_ot sites the java error did not occur.

      The only way we can resolve the problem is by rebooting the Host Server.  This is not acceptable.

      What causes this and what can we do to resolve this problem.

      Server access failed

      Can’t access QDX Integratiion Service Environ due to the exception shown below.

      java.lang.NullPointerException  

      Error details  

      at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source)    

      at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source)    

      at sun.rmi.server.UnicastRef.invoke(Unknown Source)    

      at com.hie.cloverleaf.remoteserver.RemoteMonitorDServer_Stub.getMonitorDClientProxy(Unknown Source)    

      at com.hie.cloverleaf.gui.netmon.MonitorDServerFirewall.initMonitorDClientProxy(MonitorDServerFirewall.java:576)    

      at com.hie.cloverleaf.gui.netmon.MonitorDServerFirewall.(MonitorDServerFirewall.java:56)    

      at com.hie.cloverleaf.gui.netmon.NetMonPanel.jbInit(NetMonPanel.java:239)    

      at com.hie.cloverleaf.gui.netmon.NetMonPanel.(NetMonPanel.java:58)    

      at com.hie.cloverleaf.gui.netmon.NetMonTool.jbInit(NetMonTool.java:137)    

      at com.hie.cloverleaf.gui.netmon.NetMonTool.(NetMonTool.java:32)    

      at java.lang.reflect.Constructor.newInstance(Native Method)    

      at com.hie.cloverleaf.gui.launchpad.LaunchpadPanel.startTool(LaunchpadPanel.java:169)    

      at com.hie.cloverleaf.gui.launchpad.LaunchpadPanel.startTool(LaunchpadPanel.java:219)    

      at com.hie.cloverleaf.gui.launchpad.LaunchpadPanel.handleServerChange(LaunchpadPanel.java:804)    

      at com.hie.cloverleaf.gui.StdGuiMainPanel$1.propertyChange(StdGuiMainPanel.java:800)    

      at java.beans.PropertyChangeSupport.firePropertyChange(Unknown Source)    

      at com.hie.cloverleaf.gui.launchpad.LaunchpadMainFrame.changeCloverleafServer(LaunchpadMainFrame.java:207)    

      at com.hie.cloverleaf.gui.StdGuiMainPanel.doServerChangeAction(StdGuiMainPanel.java:283)    

      at java.lang.reflect.Method.invoke(Native Method)    

      at com.hie.cloverleaf.gui.GenericAction.actionPerformed(GenericAction.java:89)    

      at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)    

      at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)    

      at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)    

      at javax.swing.DefaultButtonModel.setPressed(Unknown Source)    

      at javax.swing.AbstractButton.doClick(Unknown Source)    

      at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(Unknown Source)    

      at java.awt.Component.processMouseEvent(Unknown Source)    

      at java.awt.Component.processEvent(Unknown Source)    

      at java.awt.Container.processEvent(Unknown Source)    

      at java.awt.Component.dispatchEventImpl(Unknown Source)    

      at java.awt.Container.dispatchEventImpl(Unknown Source)    

      at java.awt.Component.dispatchEvent(Unknown Source)    

      at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)    

      at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)    

      at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)    

      at java.awt.Container.dispatchEventImpl(Unknown Source)    

      at java.awt.Window.dispatchEventImpl(Unknown Source)    

      at java.awt.Component.dispatchEvent(Unknown Source)    

      at java.awt.EventQueue.dispatchEvent(Unknown Source)    

      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)    

      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)    

      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)    

      at java.awt.EventDispatchThread.run(Unknown Source)

      Frank Kalinoski

      Sr. Programmer/Analyst

      Sharp Healthcare, ISD

      858-499-5194

      francis.kalinoski@sharp.com

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • November 18, 2005 at 7:23 pm #57666
        Francis Kalinoski
        Participant

          This issue was submitted to QDX Support.  R&D responded that this is a known issue that will be corrected in version 5.4.  If a user-1 is in an Integrator IDE site NWMonitor and another user-2 enters the same Integrator IDE site NWMonitor and breaks the user-1 lock, the next user to enter this Integrator IDE site NWMonitor will get a Java NullPointer Exception – Error connecting to Monitor Daemon.  The IDE Monitor Daemon indicator is RED and all or the threads in the NWMonitor display as ‘dead’.  A check of the site’s monitor daemon will show the pid still active.  Apparently there is a lock file retained in the /integrator/qdx5.3/integrator/site/lock directory that causes the problem.  Deleting the lock file does not help.  Only cycling the Host Server seems to restore the offending NWMonitor to functionality.

        • November 21, 2005 at 3:45 pm #57667
          Rich Durkee
          Participant

            I wonder how long they (Quovadx) have known about this issue. I installed 5.3.3 last week on AIX and was not informed about a potentially serious problem. This is irresponsible on the part of Quovadx. Notification should be sent to all known users when a serious bug like this is included in a rev.  – as soon as it is found.

            Quovadx will probably respond that it not practical to inform all customers. Well how about creating a forum that lists known bugs in revs. Why keep that information hidden. As a customer I want to know everything about everything. I will decide what information to disregard.

            Rich Durkee

          • October 29, 2007 at 8:49 am #57668
            David Teh
            Participant

              Hi folks,

              Has this bug been fixed with Rev 3, or is it still outstanding…to be fixed in QDX 5.4?

              TIA!

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.