Bug 779610 (SOA-1980)

Summary: SOA-P cannot be executed on IBM JDK out-of-the-box
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Jiri Pechanec <jpechane>
Component: ConfigurationAssignee: Len DiMaggio <ldimaggi>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.0.0 GA   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1980
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
java version "1.6.0" Java(TM) SE Runtime Environment (build pxi3260sr6-20090925_01(SR6)) IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr6-20090923_42924 (JIT enabled, AOT enabled) J9VM - 20090923_042924 JIT - r9_20090902_1330ifx1 GC - 20090817_AA) JCL - 20090924_01
Last Closed: 2010-07-21 16:31:48 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
server.log.gz
none
startup.txt none

Description Jiri Pechanec 2010-03-08 13:29:02 UTC
Date of First Response: 2010-04-13 09:57:49
project_key: SOA

When starting SOA-P on IBM JDK the server generates an exception when it starts ESB deployer

08:20:57,432 ERROR [AbstractKernelController] Error installing to Create: name=EsbPropertyService state=Configured
javax.xml.stream.FactoryConfigurationError: Provider null not found
	at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:136)
	at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
	at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
	at org.jboss.internal.soa.esb.util.XMLHelper.<clinit>(XMLHelper.java:669)
	at java.lang.J9VMInternals.initializeImpl(Native Method)
	at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
	at org.jboss.soa.esb.common.JBossESBPropertyService.createService(JBossESBPropertyService.java:135)

The problem is that IBM JDK comes with its own implementation of StAX API - different from the one coming with SOA-P.

There are multiple workarounds to this problem
1) It is possible to start the server if run.conf contains peoperties necessary to be set to use IBM's implementation.
-Djavax.xml.stream.XMLInputFactory=com.ibm.xml.xlxp.api.stax.XMLInputFactoryImpl
-Djavax.xml.stream.XMLOutputFactory=com.ibm.xml.xlxp.api.stax.XMLOutputFactoryImpl
-Djavax.xml.stream.XMLEventFactory=com.ibm.xml.xlxp.api.stax.XMLEventFactoryImpl

2) Enable properties mention in 1) in file {java.home}/lib/stax.properties

3) Copy jboss-as/lib/endorsed/stax-api.jar to {java.home}/lib/endorsed

We need to confirm that this is not issue related to SOA-P codebase. If it is unrelated we have to decide which of the solutions above is proper and document it.

Comment 1 Jiri Pechanec 2010-03-08 13:30:06 UTC
Attachment: Added: server.log.gz


Comment 2 Len DiMaggio 2010-04-13 13:57:49 UTC
I have not been able to recreate this issue - was it a lab issue?

 java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr7-20091215_02(SR7))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr7-20091214_49398 (JIT enabled, AOT enabled)
J9VM - 20091214_049398
JIT  - r9_20091123_13891
GC   - 20091111_AA)
JCL  - 20091202_01



Comment 3 Len DiMaggio 2010-04-13 13:57:49 UTC
Attachment: Added: startup.txt


Comment 4 Jiri Pechanec 2010-04-19 06:30:18 UTC
It is working now, might be a misconfiguration in the lab

Comment 5 Jiri Pechanec 2010-04-19 06:30:40 UTC
Unable to reproduce