sailfin
  1. sailfin
  2. SAILFIN-1863

[regression] could not access application after upgrade

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: milestone 1
    • Component/s: Tools
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Sun

    • Issuezilla Id:
      1,863

      Description

      Sidebyside upgrade for cluster support between sailfin 1.0 to sailfin 2.0 b23

      After upgrade, could not access application onlinebank on machine 1 at
      http://<machine 1>:38080. On machine 2, application works fine.

      1. broker_instance1.txt
        5 kB
        1xpert
      2. instance.log
        79 kB
        naman_mehta
      3. instance1.log
        41 kB
        1xpert
      4. nodeagent.log
        28 kB
        1xpert

        Activity

        1xpert created issue -
        Hide
        1xpert added a comment -

        Created an attachment (id=1044)
        instance log

        Show
        1xpert added a comment - Created an attachment (id=1044) instance log
        Hide
        1xpert added a comment -

        Created an attachment (id=1045)
        nodeagent log

        Show
        1xpert added a comment - Created an attachment (id=1045) nodeagent log
        Hide
        naman_mehta added a comment -

        Created an attachment (id=1048)
        Adding instance log for JMS error.

        Show
        naman_mehta added a comment - Created an attachment (id=1048) Adding instance log for JMS error.
        Hide
        naman_mehta added a comment -

        This is failing due to JMS is not starting up after upgrade from 1.5 to 2.0.
        Assigning this to satish for further investigation.

        Show
        naman_mehta added a comment - This is failing due to JMS is not starting up after upgrade from 1.5 to 2.0. Assigning this to satish for further investigation.
        Hide
        naman_mehta added a comment -

        Assigned it to wrong userid. Now Assigning to Satish (sats).

        Show
        naman_mehta added a comment - Assigned it to wrong userid. Now Assigning to Satish (sats).
        Hide
        Nigel Deakin added a comment -

        The local broker is not starting for an unknown reason. before we explore
        further I'd like to check whether you're hitting an issue caused by the wrong
        version of Microsoft's C++ libraries being installed on your Windows machine.

        The quick way to test this is whether you are able to use the
        imq\bin\imqbrokerd.exe to start a standalone broker or not. If your C++
        libraries are incorrect this will fail. (Simply make sure there is no broker or
        Glassfish instance running on your machine and then execute that program).

        Please see Glassfish issue 8711 for more information.
        (https://glassfish.dev.java.net/issues/show_bug.cgi?id=8771)

        Show
        Nigel Deakin added a comment - The local broker is not starting for an unknown reason. before we explore further I'd like to check whether you're hitting an issue caused by the wrong version of Microsoft's C++ libraries being installed on your Windows machine. The quick way to test this is whether you are able to use the imq\bin\imqbrokerd.exe to start a standalone broker or not. If your C++ libraries are incorrect this will fail. (Simply make sure there is no broker or Glassfish instance running on your machine and then execute that program). Please see Glassfish issue 8711 for more information. ( https://glassfish.dev.java.net/issues/show_bug.cgi?id=8771 )
        Hide
        Nigel Deakin added a comment -

        Mrs/Miss/Mr 1xpert: My previous response related to Naman's attenmpt to
        reproduce the issue. As for your issue, can you please supply broker logs for
        the local broker used by instance1? This didn't seem to start for some reason.

        Show
        Nigel Deakin added a comment - Mrs/Miss/Mr 1xpert: My previous response related to Naman's attenmpt to reproduce the issue. As for your issue, can you please supply broker logs for the local broker used by instance1? This didn't seem to start for some reason.
        Hide
        1xpert added a comment -

        Created an attachment (id=1054)
        imq broker log on machine1

        Show
        1xpert added a comment - Created an attachment (id=1054) imq broker log on machine1
        Hide
        Nigel Deakin added a comment -

        Thanks. I'm trying to see if there's anything in the broker log corresponding to
        the point in the Glassfish instance that started the broker. This is the part of
        the Glassfish server log I was interested in:

        glassfish-comms-server1.5|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=11;_ThreadName=main;|MQJMSRA_LB1101:
        Looking for Broker Running at:localhost:37676|#]

        [#|2009-07-20T13:23:45.903-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;|[C4003]:
        Error occurred on connection creation [localhost:37676]. - cause:
        java.net.ConnectException: Connection refused|#]

        [#|2009-07-20T13:23:46.981-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;|[C4003]:
        Error occurred on connection creation [localhost:37676]. - cause:
        java.net.ConnectException: Connection refused|#]

        [#|2009-07-20T13:23:47.991-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;|[C4003]:
        Error occurred on connection creation [localhost:37676]. - cause:
        java.net.ConnectException: Connection refused|#]

        [#|2009-07-20T13:23:50.468-0700|INFO|sun-glassfish-comms-server1.5|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=11;_ThreadName=main;|MQJMSRA_RA1101:
        SJSMQ JMSRA Started:LOCAL|#]

        The MQ broker log you supplied began at 13:36:16, which was later. This suggests
        the broker never even started.

        I notice you started the broker several times subsequent to that. The first two
        times it seemed to fail; the third time it ran for a few seconds and then shut
        down. Can you say what you were doing to trigger this? Did you start the
        Glassfish instance again? If so, can you supply its server log?

        Show
        Nigel Deakin added a comment - Thanks. I'm trying to see if there's anything in the broker log corresponding to the point in the Glassfish instance that started the broker. This is the part of the Glassfish server log I was interested in: glassfish-comms-server1.5|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=11;_ThreadName=main;|MQJMSRA_LB1101: Looking for Broker Running at:localhost:37676|#] [#|2009-07-20T13:23:45.903-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;| [C4003] : Error occurred on connection creation [localhost:37676] . - cause: java.net.ConnectException: Connection refused|#] [#|2009-07-20T13:23:46.981-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;| [C4003] : Error occurred on connection creation [localhost:37676] . - cause: java.net.ConnectException: Connection refused|#] [#|2009-07-20T13:23:47.991-0700|WARNING|sun-glassfish-comms-server1.5|javax.jms|_ThreadID=11;_ThreadName=main;_RequestID=6a4a8948-c3eb-46a0-998f-5082b1053123;| [C4003] : Error occurred on connection creation [localhost:37676] . - cause: java.net.ConnectException: Connection refused|#] [#|2009-07-20T13:23:50.468-0700|INFO|sun-glassfish-comms-server1.5|javax.resourceadapter.mqjmsra.lifecycle|_ThreadID=11;_ThreadName=main;|MQJMSRA_RA1101: SJSMQ JMSRA Started:LOCAL|#] The MQ broker log you supplied began at 13:36:16, which was later. This suggests the broker never even started. I notice you started the broker several times subsequent to that. The first two times it seemed to fail; the third time it ran for a few seconds and then shut down. Can you say what you were doing to trigger this? Did you start the Glassfish instance again? If so, can you supply its server log?
        Hide
        naman_mehta added a comment -

        hi 1xpert,

        I tested side by side upgrade on Linux machine. I couldn't able to reproduce
        this error.

        Have you tried same on Linux?
        On which OS are you getting this error? Is it spar/x86 machine?

        Naman.

        Show
        naman_mehta added a comment - hi 1xpert, I tested side by side upgrade on Linux machine. I couldn't able to reproduce this error. Have you tried same on Linux? On which OS are you getting this error? Is it spar/x86 machine? Naman.
        Hide
        1xpert added a comment -

        Tried starting nodeagent with syncinstances option on machine1 and was able to
        access application after upgrade.

        Show
        1xpert added a comment - Tried starting nodeagent with syncinstances option on machine1 and was able to access application after upgrade.
        Hide
        1xpert added a comment -

        reassign

        Show
        1xpert added a comment - reassign
        Hide
        naman_mehta added a comment -

        Closing this issue as it works with syncinstances=true option on both machines.

        Show
        naman_mehta added a comment - Closing this issue as it works with syncinstances=true option on both machines.
        kenaiadmin made changes -
        Field Original Value New Value
        issue.field.bugzillaimportkey 1863 19115

          People

          • Assignee:
            Satish Kumar
            Reporter:
            1xpert
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: