Unable to Deploy JBoss Applications in EAP 102.216/103.14

Hi

After upgrading from 102.149 I am no longer able to launch my run configuration for JBOSS app successfully.

Instead I am getting the exception shown below.

The application.xml file is of course at the correct location.  If I start up build 102.149 with the same project and choose the same run configuration everything works perfect again.

Have you guys changed anything regarding EAR deployments to JBOSS?

Regards,
Claus

...

08:54:58,587 INFO  [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139)] Started in 1m:4s:730ms
[2011-01-31 08:54:58,595] Artifact myapp exploded: Artifact is being deployed, please wait...
08:55:01,075 INFO  [EARDeployer] Init J2EE application: file:///C:/svn/myproject/out/artifacts/myapp.ear
08:55:01,143 ERROR [MainDeployer] Could not initialise deployment: file:///C:/svn/myproject/out/artifacts/myapp.ear
org.jboss.deployment.DeploymentException: No META-INF/application.xml found
 at org.jboss.deployment.EARDeployer.init(EARDeployer.java:146)
 at org.jboss.deployment.MainDeployer.init(MainDeployer.java:872)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:809)
 at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782)
 at sun.reflect.GeneratedMethodAccessor25.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
 at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142)
 at org.jboss.jmx.connector.invoker.SerializableInterceptor.invoke(SerializableInterceptor.java:74)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
 at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155)
 at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
 at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
 at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
 at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
 at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:818)
 at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:419)
 at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
 at sun.rmi.transport.Transport$1.run(Transport.java:159)
 at java.security.AccessController.doPrivileged(Native Method)
 at sun.rmi.transport.Transport.serviceCall(Transport.java:155)
 at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790)
 at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:619)

5 comments
Comment actions Permalink
Hello,

Yes, thats a bug, thank you for catching, I've submitted http://youtrack.jetbrains.net/issue/IDEA-64863.



The reason is that jmx deployment uses slightly different uris for  deployment of exploded artifacts with ear extensions to Jboss 4.x and 5.x (for  4.0 the uri must end with trailing slash and 5.0 does not require  it).

Until we deliver a fix in next build, the only workaround I can suggest is to migrate to JBoss 5.x.

Sorry for inconvenience,



Regards,
Michael
0
Comment actions Permalink

Thank you Michael,

Jboss 5.x is not an option, so I will look forward to the next EAP :)

Regards,
Claus

0
Comment actions Permalink

Hi again,

IntelliJ IDEA 10.0.2 now has a release candidate release available. Is there any chance that this issue will be solved for the final 10.0.2 (There is no fix version set in youtrack) ?

It kind of makes IDEA for JBoss 4.x users useless.

Thanks,
Claus

0
Comment actions Permalink

Hello,

I strongly believe that the fix had been delivered to the branch where the RC had been built from.
I was going to close the YouTrack shortly, but please feel free to reopen if something is still wrong.

Regards,
Michael

0
Comment actions Permalink

Thanks Michael. Just installed 103.59 and it is indeed solved.

Regards,
Claus

0

Please sign in to leave a comment.