Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:Solaris 10
-
Number of attachments :
Description
We've found that if we build our application on Solaris, everything looks good until the deploy. Ears built on windows that are copied to the UNIX deploy servers work.
Unzipping comparing the ears generated show differences only in Manifest files.
The error we receive is:
weblogic.Deployer invoked with options: -adminurl t3://lamprey.sdc.vzwcorp.com:8999 -user system -name mybiz-commerce -targets COMM_B2B_Clus -deploy /app/comptt/10.1/drop/mybiz-commerce.ear Task 903 initiated: [Deployer:149026]deploy application mybiz-commerce on COMM_B2B_Clus. Task 903 failed: [Deployer:149026]deploy application mybiz-commerce on COMM_B2B_Clus. Target state: deploy failed on Cluster COMM_B2B_Clus java.lang.NoSuchMethodError: org.springframework.jms.listener.AbstractJmsListeningContainer.createConnection()Ljavax/jms/Connection;
From the same company, using same process for a different application we have a slightly different result:
1. Build on Windows and deploy to Solaris, app works fine.
2. Build on Linux/Unix and deploy to Solaris, JSTL tags fail because this line: 'context.equals("/")' does not return true as expected. If you take this same ear built on Linux/Unix and unzip on Solaris, zip, then re-deploy, this issue disappears.