[jboss-jira] [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

Alexandre GASNE (JIRA) jira-events at lists.jboss.org
Wed Aug 11 13:34:49 EDT 2010


    [ https://jira.jboss.org/browse/JBAS-8319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12544349#action_12544349 ] 

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

        


More information about the jboss-jira mailing list