Bug 1334638 - [QA] (6.2.z) SOAP does not work on WebSphere AS
Summary: [QA] (6.2.z) SOAP does not work on WebSphere AS
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Business Central
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Shelly McGowan
QA Contact: Lukáš Petrovický
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-10 08:27 UTC by Tomas Livora
Modified: 2020-03-27 19:39 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:39:07 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
WebSphere server log (9.36 MB, text/plain)
2016-05-10 08:27 UTC, Tomas Livora
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1322171 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1333277 0 unspecified CLOSED Upgrade of xstream library causing exceptions during project navigation 2021-02-22 00:41:40 UTC

Internal Links: 1322171 1333277

Description Tomas Livora 2016-05-10 08:27:41 UTC
Created attachment 1155616 [details]
WebSphere server log

Description of problem:
SOAP does not work when Business Central is deployed on WebSphere AS.

Version-Release number of selected component (if applicable):
6.2.3 CR1

Steps to Reproduce:
1. Run Business Central on WAS
2. Try to access http://SERVER_ADDRESS:9080/business-central/ws/CommandService?wsdl

Actual results:
404 Not Found

Expected results:
SOAP working without any problems

Additional info:
It seems that the problem is caused by XStream library. This can be seen in the attached server log:

WSWS7011E: The configuration for the business-central.war application module cannot load correctly. 
The following error occurred:  com.ibm.ws.metadata.annotations.AnnotationException: Annotation processing failed for class:  com/thoughtworks/xstream/mapper/LambdaMapper.class

Comment 2 Marco Rietveld 2016-05-11 06:39:52 UTC
Which version fo WAS is this?

Comment 3 Tomas Livora 2016-05-11 07:11:58 UTC
It is WebSphere 8.5.5.7.

Comment 4 Marco Rietveld 2016-05-17 12:00:20 UTC
The com.thoughtworks.xstream.mapper.LambdaMapper class in XStream 1.4.9 can only be compiled using Java 8. 

https://github.com/x-stream/xstream/blob/master/xstream/src/java/com/thoughtworks/xstream/mapper/LambdaMapper.java#L45

The java.lang.reflect.Method.isDefault() method only exists in JDK 8: 

https://docs.oracle.com/javase/8/docs/api/java/lang/reflect/Method.html#isDefault--

https://docs.oracle.com/javase/7/docs/api/java/lang/reflect/Method.html

--

Websphere is failing because the ASM framework can not read the class -- and my very strong suspicion is that this is happened because the ASM framework being used doesn't expect a version 52/JDK 8 class. 


Caused by: java.lang.IllegalArgumentException
	at org.objectweb.asm.ClassReader.<init>(Unknown Source)
	at org.objectweb.asm.ClassReader.<init>(Unknown Source)
	at org.objectweb.asm.ClassReader.<init>(Unknown Source)
	at com.ibm.ws.metadata.annotations.AnnotationConfigReader.getAnnotationData(AnnotationConfigReader.java:836)

Comment 5 Marco Rietveld 2016-05-17 12:15:08 UTC
All further comments and status updates will happen here: 

https://issues.jboss.org/browse/RHBPMS-137

Comment 6 Michael 2016-09-07 14:35:40 UTC
Verified with WAS 8.5.5.10.
The deployed war hat the xstream 1.4.9.
With JAVA 1.8  the WAS could be started and accessed http://SERVER_ADDRESS:PORT/business-central/ws/CommandService?wsdl, a XML was displayed.
The WAS was stopped, the JAVA versions set to 1.6 and the WAS restarted.
Also, when accessing http://SERVER_ADDRESS:PORT/business-central/ws/CommandService?wsdl a XML the same XML was dispalyed.
This bug couldn't be reproduced with WAS 8.5.5.10.


Note You need to log in before you can comment on or make changes to this bug.