Petals Distribution

ESB 4.1+Java7 : Install a service-unit --> SAX2 driver class org.apache.xerces.parsers.SAXParser not found

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 4.1.0
  • Fix Version/s: 5.0.0-M1
  • Component/s: Components
  • Security Level: Public
  • Description:
    Hide

    I have just installes Petals ESB 4.1 on several servers. Topology is master-slave, with the same topology.xml on all the servers. I have installed SOAP-BC on the ESB servers, and everything runs fine. Now, I try to install a service unit generated with Petals Studio 1.3.3 ( I did this operation quite a few times in the past, without any problem) the SU is not installed, and I see this in the petals.log : Error to read default parent => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found What could be the cause ?

    see full discussion on http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-td4025515.html

    Proposed Workaround:
    It seems the problem is solved removing the JAR xercesImpl-2.8.1 from the BC SOAP. With OpenJDK7 and Java7 (that is based on OpenJDK7), Xerces is found as SAX parser from the BC SOAP classloader but the JDK is not able to load the class. I don't known why.

    As Petals ESB can use the SAX2 parser provided by the JVM, it is sufficient to remove the JAR xercesImpl-2.8.1 from the BC SOAP. In the zip file, rename the JAR xercesImpl-2.8.1, and update the JBI descriptor removing the two entries associated to xercesImpl-2.8.1.jar

    Show
    I have just installes Petals ESB 4.1 on several servers. Topology is master-slave, with the same topology.xml on all the servers. I have installed SOAP-BC on the ESB servers, and everything runs fine. Now, I try to install a service unit generated with Petals Studio 1.3.3 ( I did this operation quite a few times in the past, without any problem) the SU is not installed, and I see this in the petals.log : Error to read default parent => SchemaException: Can not get schema: : org.xml.sax.SAXException: SAX2 driver class org.apache.xerces.parsers.SAXParser not found What could be the cause ? see full discussion on http://forum.petalslink.com/Petals-4-1-BC-SOAP-SAX-driver-error-td4025515.html Proposed Workaround: It seems the problem is solved removing the JAR xercesImpl-2.8.1 from the BC SOAP. With OpenJDK7 and Java7 (that is based on OpenJDK7), Xerces is found as SAX parser from the BC SOAP classloader but the JDK is not able to load the class. I don't known why. As Petals ESB can use the SAX2 parser provided by the JVM, it is sufficient to remove the JAR xercesImpl-2.8.1 from the BC SOAP. In the zip file, rename the JAR xercesImpl-2.8.1, and update the JBI descriptor removing the two entries associated to xercesImpl-2.8.1.jar
  • Environment:
    Petals 4.1 ; Java 7

Issue Links

Activity

Christophe DENEUX made changes - Thu, 19 Jun 2014 - 14:56:56 +0200
Field Original Value New Value
Link This issue depends on PETALSBCSOAP-140 [ PETALSBCSOAP-140 ]
Christophe DENEUX made changes - Thu, 19 Jun 2014 - 16:20:54 +0200
Status New [ 10000 ] Open [ 10002 ]
Priority Critical [ 2 ]
Component/s Components [ 10270 ]
Christophe DENEUX made changes - Thu, 19 Jun 2014 - 16:20:57 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Hide
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 16:21:25 +0200

Set to "Resolved" because PETALSBCSOAP-140 is resolved

Show
Christophe DENEUX added a comment - Thu, 19 Jun 2014 - 16:21:25 +0200 Set to "Resolved" because PETALSBCSOAP-140 is resolved
Christophe DENEUX made changes - Thu, 19 Jun 2014 - 16:21:25 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Resolution Fixed [ 1 ]
Christophe DENEUX made changes - Thu, 19 Jun 2014 - 16:21:35 +0200
Fix Version/s 4.3.0 [ 10412 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Open Open
301d 3h 32m
1
Christophe DENEUX
Thu, 19 Jun 2014 - 16:20:54 +0200
Open Open In Progress In Progress
3s
1
Christophe DENEUX
Thu, 19 Jun 2014 - 16:20:57 +0200
In Progress In Progress Resolved Resolved
28s
1
Christophe DENEUX
Thu, 19 Jun 2014 - 16:21:25 +0200



People

Dates

  • Created:
    Thu, 22 Aug 2013 - 12:48:15 +0200
    Updated:
    Thu, 19 Jun 2014 - 16:21:35 +0200
    Resolved:
    Thu, 19 Jun 2014 - 16:21:25 +0200