Uploaded image for project: 'CloverETL'
  1. CloverETL
  2. CLO-2013

Clover.war deployment failed on Oracle WebLogic Server 11g in production model for 64-bit jvm

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: rel-3-4-1
    • Fix Version/s: rel-3-4-3
    • Component/s: Server
    • Security Level: Users (General product issues)
    • Labels:
    • Environment:

      OS: Windows 64-bit
      WLS version: "Oracle WebLogic Server 11gR1 (10.3.6) + Coherence - Package Installer" wls1036_generic.jar for 64-bit JVM

    • QA Testing:
      UNDECIDED
    • OTRS_Ticket_ID:
      2013090910000031

      Description

      I deployed the clover server 3.4.1 on the 64-bit WLS in production model, when I started the application, it failed. After I restart the WLS, the status of clover server will be active in the WLS console and it also works correctly, but it still cause another exception in the admin.log.
      After I checked the log and did some test on it, I found the root cause.
      The reason is that the weblogic server would deploy a internal war "wls-wsat.war". There is a jar conflict between clover.war and wls-wsat.war. The conflicted jars are saaj-impl.jar and saaj-api.jar in clover. After I removed them before deployment, it will be ok.
      We hope Javlin can give us a better way to solve this problem, such as provide us a new war without the conflict with the WLS.

        Attachments

          Activity

            People

            • Assignee:
              michalicaj Jano Michalica
              Reporter:
              oracle-endeca Oracle Endeca (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: