Jboss 5.1

Greenhorn

I am using OData4j for my RESTful service (deployed in JBoss AS 5.1.0). When i send PUT (i.e. Update request) and DELETE (i.e. Delete request) requests from my client, I am getting this error: HTTP Status 405 - Status report. The specified HTTP method is not allowed for the requested resource. JBoss Web/2.1.3.GA. GET and POST are working fine. Running on Jboss 5.1: Date: Fri, 16 Oct 2009 14:28:33 GMT: Hello, Do you have any instructions on running Continuum on Jboss 5.1? I tried to deploy the war but got.

posted 9 years ago

Optional 'thank-you' note:

Hi,
I'm trying to deploy my ejb3 application which was developed in JBoss 4.3 to JBoss 5.1. After resolving all the build issues, I'm getting the below error everytime I start the deployment in JBoss 5.1. I have checked all my manifest files and everything looks good. Is this error related to any EJB3 annotations? Any help on this would be appreciated.

14:48:14,836 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/C:/jboss/jboss-5.1/server/default/deploy/myejbproj.ear/ state=ClassLoader mode=Manual requiredState=PostClassLoader org.jboss.deployers.spi.DeploymentException: Cannot process metadata at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:210) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:122) at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70) at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53) at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403) at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:778) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:543) at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308) at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256) at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461) at org.jboss.Main.boot(Main.java:221) at org.jboss.Main$1.run(Main.java:556) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: invalid header field at java.util.jar.Attributes.read(Attributes.java:389) at java.util.jar.Manifest.read(Manifest.java:182) at java.util.jar.Manifest.<init>(Manifest.java:52) at org.jboss.virtual.VFSUtils.readManifest(VFSUtils.java:283) at org.jboss.deployment.AnnotationMetaDataDeployer.getMainClassName(AnnotationMetaDataDeployer.java:359) at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:80) at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:206) ... 31 more

Thanks

Sheriff

posted 9 years ago

Optional 'thank-you' note:

What's the contents of your MANIFEST.MF file(s) of the jar/ear?
P.S: If you are thinking of migrating to a new JBoss AS version then I would recommend JBoss AS 7.1.x instead of JBoss AS 5.x

Greenhorn

posted 9 years ago

Optional 'thank-you' note:

I was able to resolve this issue after I deleted everything from my ear manifest file. There was a manual entry for a custom framework like FrameX_Version: 3.4, which was giving this error. Hope this helps someone.

Greenhorn

posted 9 years ago

Optional 'thank-you' note:

Jboss 5.1.0 Ga

Jboss 5.1 Tls 1.2

After a closer look, I saw that the colon( was missing the custom framework line and a space was missing at the end of the manifest file after the 'Class-Path'. After I made these changes, I'm able to deploy to JBoss 5.1 successfully.