Announcement

Collapse
No announcement yet.

[SOLVED] Duplicated shipment/invoice/voucher generate in Scalability ENV

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • [SOLVED] Duplicated shipment/invoice/voucher generate in Scalability ENV

    We are using OTM 5.5CU5RU6. There are 2 application servers with the salability on in the cluster with name 'DEFAULT'.

    We found that sometimes, one user action might trigger 2 parallel process in the 2 application servers (one in each server) and generate duplicated object. The issues happens when we try to generate the shipment(bulk plan), invoice and voucher.

    Attached you may find the log file extract from the 2 servers for the duplicated shipments.

    Any comments on this? In OTM, can we make use of the application function to limit this function can only processed on one server?

    CK Lam
    Attached Files

  • #2
    Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

    The duplicate object issue definitely shouldn't happen. I'd start by checking out your cluster via the Scalability diagnostic servlets, to ensure that no setup issues are identified. For instance, each should have a unique name and they should (idealy) exist on different hosts. If they're on the same host, then there is some manual configuration necessary.

    However - there is also a way to split functionality up on the cluster, so that certain functions only occur on specific servers. The setup is detailed in the Scalability guide that's on Oracle's site. This is an option, but shouldn't be necessary to resolve the issue you're encountering. A standard cluster should handle that just fine.

    --Chris

    Comment


    • #3
      Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

      CK,

      Do you have a SECONDARY cluster defined with an Application Server? If not then you can try changing the configuration so that the second app server resides in the SECONDARY cluster.

      Comment


      • #4
        Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

        Originally posted by chrisplough View Post
        The duplicate object issue definitely shouldn't happen. I'd start by checking out your cluster via the Scalability diagnostic servlets, to ensure that no setup issues are identified. For instance, each should have a unique name and they should (idealy) exist on different hosts. If they're on the same host, then there is some manual configuration necessary.

        However - there is also a way to split functionality up on the cluster, so that certain functions only occur on specific servers. The setup is detailed in the Scalability guide that's on Oracle's site. This is an option, but shouldn't be necessary to resolve the issue you're encountering. A standard cluster should handle that just fine.

        --Chris
        Chris,

        The application servers are on different hosts and they have unique name. We just followed the administration guide and configured them into the DEFAULT cluster.

        We also suspect that whether there is possiblity 2 duplicated requests had sumbit to the cluster. That is, althought the user only click the action button once, but the IE may submit twice. Or the user click action button twice in short time and 2 requests are submitted to the server.

        Comment


        • #5
          Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

          Originally posted by itnole View Post
          CK,

          Do you have a SECONDARY cluster defined with an Application Server? If not then you can try changing the configuration so that the second app server resides in the SECONDARY cluster.
          Itnole,

          When you mention SECONDARY cluster, you mean that we should seperate the 2 application server in to 2 cluster? Or just create another cluster and put a app server in it?

          Thanks.

          Comment


          • #6
            Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

            Create a Second cluster and add one of the App Servers to the new Cluster. I believe the set up for each Cluster should be Active/Active for High Scalability -- refer to OTM Clustering guide.

            Comment


            • #7
              Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

              We reproduce the issue succefully on a scalable env.
              There are 2 web(05, 06) server and 2 app server(03,04) in our production Env. The primary app server of 05 is 03 and the primary app server of 06 is 04.
              Steps to reproduce the shipment duplicated issue are as below:
              1. Confirm that the different app servers are apply by each webserver.
              2. Log on each web server, run the bulk plan for the same order release:
              3. 4 shipments are generated for the order release although a 2 leg itinerary apply by the order release. HTM2010042600264 is same as HTM2010042600266 which HTM2010042600265 is the same as HTM2010042600267.

              Is it the because of the setting of scalability? How can I fixed this? Thanks.

              CK Lam
              Attached Files

              Comment


              • #8
                Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

                To verify, have you used the Scalability Overview Servlet to ensure that you don't have any basic config issues? (glog.webserver.appserver.AppServerOverviewServlet )

                --Chris

                Comment


                • #9
                  Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

                  Chris,

                  I check the issue with the servlet and found below error message:
                  Source Severity Message
                  Data Error (All Functions,All Domains) is handled by multiple clusters: [DEFAULT, ORACLEQUEUE]
                  gc3-szxhtm03-or Error Appserver property-based URL: t3://szxhtm03-or.huawei.com:7001 for DEFAULT does not match database URL
                  gc3-szxhtm04-or Error Appserver property-based URL: t3://szxhtm04-or.huawei.com:7001 for DEFAULT does not match database URL


                  But I do not get the idea what does it mean by "does not match database URL". Do you have any suggestion on this? Thank you.

                  CK
                  Last edited by CK Lam; May 5, 2010, 11:04.

                  Comment


                  • #10
                    Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

                    This means that the SCA configuration that is setup in your glog.properties files does not match the configuration that's setup within the application (under the DBA.ADMIN login). These need to match up, or the cluster will not work correctly.

                    --Chris

                    Comment


                    • #11
                      Re: Duplicated shipment/invoice/voucher generate in Scalability ENV

                      Hi Chris,

                      Thanks. Our issue had been resolved.

                      The root cause of the issue is we had
                      'glog.scalability.thisMachine=DEFAULT' in all our appserver's glog.properties.
                      As a result, all appservers think they are the DEFAULT server. In addition to picking up each other's locks, each server will maintain JMS communication with itself, causing other odd behavior.

                      We had correct the configuration and it's working fine now.

                      CK Lam

                      Comment

                      Working...
                      X