How patch JBoss AS 5.1 with JBoss Classloader 2.0.6.SP1 - Fi
timlambertmf Aug 24, 2009 11:02 PMI've been trying to install the patch associated with:
https://jira.jboss.org/jira/browse/JBCL-109
It fixes a hang in the classloader that I think we are hitting because we see all the HTTP threads blocked on a thread that look exactly like the stack in:
https://jira.jboss.org/jira/browse/JBAS-6327
I tried using the -Djboss.patch.url method, but classes in the old jars seem to be getting loaded instead of the new ones.
I tried replacing the jars in jboss_home/lib with the JBCL 2.0.6.SP1 version:
http://repository.jboss.com/maven2/org/jboss/cl/jboss-cl-dist/2.0.6.SP1/
When I did the latter, JBoss AS 5.1 threw the following error at boot time trying to parse classloader.xml.
18:37:51,343 DEBUG [JBossEntityResolver] Cannot resolve [publicID=urn:jboss:classloader:1.0,systemID=null]
18:37:51,345 DEBUG [JBossEntityResolver] Cannot resolve [publicID=null,systemID=urn:jboss:classloader:1.0]
18:37:51,382 DEBUG [ServerImpl] Failed to start
org.jboss.xb.binding.JBossXBException: Failed to parse source: file:/usr/local/jboss-5.1.0.GA/server/default/conf/bootstrap/classloader.xml@27,121
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:177)
at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:147)
at org.jboss.bootstrap.microcontainer.TempBasicXMLDeployer.deploy(TempBasicXMLDeployer.java:150)
at org.jboss.bootstrap.microcontainer.ServerImpl.doStart(ServerImpl.java:138)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:450)
at org.jboss.Main.boot(Main.java:221)
at org.jboss.Main$1.run(Main.java:556)
at java.lang.Thread.run(Thread.java:619)
Caused by: org.jboss.xb.binding.JBossXBRuntimeException: {urn:jboss:classloader:1.0}classloader cannot appear in this position. Expected content of {urn:jboss:bean-deployer:2.0}deployment is unordered_sequence: {urn:jboss:bean-deployer:2.0}stop? {urn:jboss:bean-deployer:2.0}destroy? {urn:jboss:bean-deployer:2.0}annotation* {urn:jboss:bean-deployer:2.0}alias* {urn:jboss:bean-deployer:2.0}start? {urn:jboss:bean-deployer:2.0}classloader? {urn:jboss:bean-deployer:2.0}create? {choice}* {sequence}*
at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:449)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:173)
... 7 more
Any ideas? What should the process be for installing such a patch?