-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Community JBoss 5.1.0-GA
RHEL 5.3 JBoss 5.0.0-GA
5.1.0-GA uses:
<groupId>org.jboss</groupId>
<artifactId>jboss-vfs</artifactId>
<packaging>jar</packaging>
<version>2.1.2.GA</version>
RH 5.0.0-GA uses:
<groupId>org.jboss</groupId>
<artifactId>jboss-vfs</artifactId>
<packaging>jar</packaging>
<version>2.1.3.SP1</version>
This causes an error at line 117 below in:
hudson.remoting.Which
110 if(resURL.startsWith("vfszip:")) {
111 // JBoss5
112 InputStream is = res.openStream();
113 try
catch (NoSuchFieldException e)
{ 122 // something must have changed in JBoss5. fall through 123 LOGGER.log(Level.FINE, "Failed to resolve vfszip into a jar location",e); 124 }catch (IllegalAccessException e)
{ 125 // something must have changed in JBoss5. fall through 126 LOGGER.log(Level.FINE, "Failed to resolve vfszip into a jar location",e); 127 }finally
{ 128 is.close(); 129 }The second time into Which hudson is looking for the jar containing:
vfszip:/usr/local/jboss-apps/node00/webapps/hudson.war/WEB-INF/lib/remoting-1.349.jar/hudson/remoting/Launcher.class
In vfs-2.1.2-GA the InputStream is a:
org.jboss.virtual.plugins.context.zip.ZipEntryInputStream
And everything is grand, but in vfs-2.1.3-SP1 the InputStream returns:
org.jboss.virtual.plugins.context.zip.CertificateReaderInputStream
Which wraps the ZipEntryInputStream not returning you access to the parent that you intended.
- is related to
-
JENKINS-5722 Hudson fails to execute
- Resolved