[JBoss JIRA] Created: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
10:14 a.m.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http
resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: VFS
Affects Versions: 6.0.0.M3, JBossAS-5.1.0.GA, JBossAS-5.0.1.GA, JBossAS-5.0.0.GA
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and
even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in
JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No
context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:14 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Attachment: stacktrace-jboss-5.txt
stacktrace-jboss-6.txt
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M3
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in
JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No
context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:34 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Affects Version/s: 6.0.0.M4
(was: 6.0.0.M3)
Environment:
JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
was:
JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M3 (jboss-vfs 3.0.0 CR5)
Description:
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and
even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
was:
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x, and
even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5 and JBoss 6; in
JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws: java.io.IOException: No
context factory for http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.0.GA, JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:36 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Affects Version/s: (was: JBossAS-5.0.0.GA)
Environment:
Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
was:
JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:43 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Steps to Reproduce:
Call the JBoss deployer with a remote URL, for example:
http://localhost:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&n...
was:Call the JBoss deployer with a remote URL
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:32 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Alexandre GASNE commented on JBAS-8319:
---------------------------------------
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/bss-ear-business.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/bss-ear-business.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/bss-ear-business.ear -> org.jboss.deployers.spi.DeploymentException:
Error during deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Alexandre GASNE edited comment on JBAS-8319 at 8/11/10 1:33 PM:
----------------------------------------------------------------
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://localhost/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/my-ear.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
was (Author: agasne):
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/my-ear.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Alexandre GASNE edited comment on JBAS-8319 at 8/11/10 1:33 PM:
----------------------------------------------------------------
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/bss-ear-business.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
was (Author: agasne):
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/bss-ear-business.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/bss-ear-business.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/bss-ear-business.ear -> org.jboss.deployers.spi.DeploymentException:
Error during deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Alexandre GASNE edited comment on JBAS-8319 at 8/11/10 1:33 PM:
----------------------------------------------------------------
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/my-ear.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
was (Author: agasne):
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://192.168.110.8/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/bss-ear-business.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:42 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Alexandre GASNE edited comment on JBAS-8319 at 8/11/10 1:41 PM:
----------------------------------------------------------------
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console :
org.jboss.system.tools.DeploymentScanner ->
addURL("http://localhost/deploy/my-ear.ear")
and I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://localhost/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/my-ear.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
was (Author: agasne):
Trying to deploy an EAR on jboss6-M3 or M4 via an URL in JMX console, I get this :
********************
19:27:20,195 INFO [org.jboss.deployment.MainDeployer] deploy,
url=http://localhost/deploy/my-ear.ear
19:27:20,198 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error
installing to Parse: name=vfs:///deploy/my-ear.ear state=PreParse mode=Manual
requiredState=Parse: org.jboss.deployers.spi.DeploymentException: Error during deploy:
vfs:///deploy/my-ear.ear
[...]
Caused by: java.lang.NullPointerException
at org.jboss.deployment.EARContentsDeployer.deploy(EARContentsDeployer.java:149)
[:6.0.0.20100429-M3]
19:27:20,216 WARN [org.jboss.deployment.MainDeployer] Failed to deploy:
http://localhost/deploy/my-ear.ear:
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete
deployments (SEE PREVIOUS ERRORS FOR DETAILS):
*** DEPLOYMENTS MISSING DEPLOYERS: Name
vfs:///deploy/my-ear.ear
*** DEPLOYMENTS IN ERROR: Name -> Error
vfs:///deploy/my-ear.ear -> org.jboss.deployers.spi.DeploymentException: Error during
deploy: vfs:///deploy/my-ear.ear
*********************
the EAR is exposed via Apache (working) and is 'deployable' (it works when
deployed in "/server/.../deploy")
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:34 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Attachment: stacktrace-jboss6-m5.txt
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:36 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Fix Version/s: 6.0.0.CR1
Affects Version/s: 6.0.0.M5
This is still broken with the latest JBoss 6.0.0 M5.
It would be great to have it fixed for JBoss 6.0.0 CR1.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:38 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Component/s: Deployers
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers, VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:06 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
David Lloyd commented on JBAS-8319:
-----------------------------------
Just to make sure this is clear to all, this is not a VFS function. VFS is not meant to
support resource types of any kind outside of VFS. The issue is at the deployer layer,
which is apparently ignoring the URL scheme and assuming it's a local filesystem
deployment.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers, VFS
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:49 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Component/s: (was: VFS)
Thank you for your comment, David
Changing the component do "deployers".
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen updated JBAS-8319:
-----------------------------------
Labels: remote deployer deployment (was: vfs remote)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:22 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan reassigned JBAS-8319:
------------------------------------
Assignee: Ales Justin
Have you seen this before?
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Ales Justin
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] Assigned: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Ales Justin reassigned JBAS-8319:
---------------------------------
Assignee: Emanuel Muckenhuber (was: Ales Justin)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:01 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Ales Justin commented on JBAS-8319:
-----------------------------------
Like David said, this has nothing to do with VFS.
Could be PS and/or JMX connector should support this.
Dunno how was this handled in pre-AS5?
Assigning it to Emanuel who works/worked on PS.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Ales Justin
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Ales Justin commented on JBAS-8319:
-----------------------------------
Ah, OK, we established that this is not a VFS issue.
Nor is deployers, since deployers only understand what VFS tells them to do.
Potentially there could be "remote" impl of Deployment,
but my guess is, like I already mentioned, that this should be handled by PS.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:10 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Ales Justin updated JBAS-8319:
------------------------------
Component/s: ProfileService
(was: Deployers)
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:50 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Shelly McGowan commented on JBAS-8319:
--------------------------------------
Emanuel, is there work planned for CR1 ?
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:15 a.m.
New subject: [JBoss JIRA] Resolved: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Emanuel Muckenhuber resolved JBAS-8319.
---------------------------------------
Resolution: Done
This should be working in CR1. However MainDeployer is a deprecated service, which is
going to be removed in the next major release of AS.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:33 a.m.
New subject: [JBoss JIRA] Closed: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.sy...
]
Savas Ali Tokmen closed JBAS-8319.
----------------------------------
The fix has been verified opn JBoss AS 6.0.0 CR1.
Thank you for your continuing efforts.
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://jira.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Labels: deployer, deployment, remote
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:06 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-8319) [Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't support fetching http resources
[
https://issues.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin....
]
Ondrej Zizka commented on JBAS-8319:
------------------------------------
Will this be backported to AS/EAP 5?
[Regression in JBoss 5.x and 6.x compared to 4.x] VFS doesn't
support fetching http resources
---------------------------------------------------------------------------------------------
Key: JBAS-8319
URL: https://issues.jboss.org/browse/JBAS-8319
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: z - Legacy - ProfileService
Affects Versions: JBossAS-5.0.1.GA, JBossAS-5.1.0.GA, 6.0.0.M4, 6.0.0.M5
Environment: Bug has been observed on all three versions:
* JBoss 5.0.1 GA (jboss-vfs 2.1.2 GA)
* JBoss 5.1.0 GA (jboss-vfs 2.1.0 GA)
* JBoss 6.0.0 M4 (jboss-vfs 3.0.0 CR5)
Reporter: Savas Ali Tokmen
Assignee: Emanuel Muckenhuber
Labels: deployer, deployment, remote
Fix For: 6.0.0.CR1
Attachments: stacktrace-jboss-5.txt, stacktrace-jboss-6.txt,
stacktrace-jboss6-m5.txt
I'm currently working on the porting of our JBoss 4.2 infrastructure to JBoss 5.x,
and even maybe 6.x.
Since JBoss doesn't allow automated remote deployment (i.e., via JMX for example -a
manual access to the JBoss console is necessary) of applications (WAR, EJBs, EARs, etc.),
we used to call the JBoss MainDeployer's deploy method with a URL pointing to an HTTP
URL which contains all our deployable artifacts.
As of JBoss 5.x, this broke. I'm attaching stack traces for JBoss 5.1.0 and JBoss
6.0.0 M3:
* In JBoss 5 we clearly see that org.jboss.virtual.VFS.getVFS throws:
java.io.IOException: No context factory for
http://192.168.0.12:58407/simple-war-1.0.3-SNAPSHOT.war
* In JBoss 6 the exception is even more interesting: Invalid or unreadable WAR file :
/simple-war-1.0.3-SNAPSHOT.war
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4932
days inactive
5172
days old
24 comments
7 participants
participants (7)
-
Ales Justin (JIRA) -
Alexandre GASNE (JIRA)
-
David Lloyd (JIRA)
-
Emanuel Muckenhuber (JIRA)
-
Ondrej Zizka (JIRA)
-
Savas Ali Tokmen (JIRA)
-
Shelly McGowan (JIRA)