Remote deployment broken in IDEA 6.0.x ?

Hi,
I'm trying to deploy a simple webapp to a JBoss remote server.
I can connect to the server and everything is fine ( Idea connects to the remote JBoss instance), except...that the created war is never deployed. The JBoss instance looks for the war using my local war generation path. See the attached screenshots for my config.
Tested and not working with IDEA 6.0, 6.0.1 & 6.0.2. Am I missing something obvious here?

+Connected to server
Module test: Module is being deployed, please wait...
org.jboss.deployment.DeploymentException: url file:/Users/milmber/Documents/IdeaProjects/test/test.war could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.]]>(DeploymentInfo.java:214)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:781)
at sun.reflect.GeneratedMethodAccessor54.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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:585)
at org.jboss.jmx.connector.invoker.InvokerAdaptorService.invoke(InvokerAdaptorService.java:266)
at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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 org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:179)
at sun.reflect.GeneratedMethodAccessor78.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
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:819)
at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:420)
at sun.reflect.GeneratedMethodAccessor77.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
at sun.rmi.transport.Transport$1.run(Transport.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
at java.lang.Thread.run(Thread.java:595)
Module test: Error during module deployment. See server log for details.+



Attachment(s):
Picture 3.png
Picture 2.png
Picture 1.png
4 comments

In the first place you have to blame JBoss for not being able to handle this case automatically. When invoking the JBoss deployer remotely and instructing it to deploy your webapp, only the archive file's URL is sent to the server instead of the whole file.

So the solution we're heading for is to transfer the file onto the target machine prior to deploying it. But this work isn't finished yet and there are still some errors in IDEA core which are preventing it from being finished.

Please vote for http://www.jetbrains.net/jira/browse/IDEA-10173 if you want to speed up things.

0

Hi Martin,
Thanks for clearing that up. I will add my vote.

0

Hi, Martin!

The bug description in JIRA doesn't look related to JBoss. Are you sure, that it's the right one?

Also, the solution could be to tell IDEA and respectively JBoss what URL to use on the remote machine. In that case we could copy the file to the remote server and initiate the deployment with "remote" URL.

Andrey

0

The bug description in JIRA doesn't look related to
JBoss. Are you sure, that it's the right one?


Well, yes, I'm very sure. It's not directly related to JBoss, but it's the location where the JBoss plugin will be hooked in.

Also, the solution could be to tell IDEA and
respectively JBoss what URL to use on the remote
machine. In that case we could copy the file to the
remote server and initiate the deployment with
"remote" URL.


If you are willing to interrupt the make/deploy cycle by manually copying the file, then you can as well copy it directly into the deploy folder and let JBoss deploy it automatically. I don't see any added value in using IDEA's remote deployment mechanism if you have to copy the file manually first.

0

Please sign in to leave a comment.