You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using jbossas-remote-4.2 and configuring a remote host (with jnpProvider and a host / port combination), I encountered exceptions by the JMX deployer inside the JBoss 4.2.3 server, which stated that it could not deploy the deployment. The deployment which is build in @deployment and enriched on the arquillian side is at the end of all processing in /tmp/mydeployment.ear at the local side. This path is given to JMX deployment bean at the server side, which look at this path from the server part, and does not find it at the server's /tmp directory.
I don't think there's much to do about it in Arquillian, because the missing "upload" should be in JBoss 4.2.3 and nobody ever is going to implement that.
But it would be good if this would be part of the documentation, since it took me some time to figure this out.
Hello,
When using jbossas-remote-4.2 and configuring a remote host (with jnpProvider and a host / port combination), I encountered exceptions by the JMX deployer inside the JBoss 4.2.3 server, which stated that it could not deploy the deployment. The deployment which is build in @deployment and enriched on the arquillian side is at the end of all processing in /tmp/mydeployment.ear at the local side. This path is given to JMX deployment bean at the server side, which look at this path from the server part, and does not find it at the server's /tmp directory.
I don't think there's much to do about it in Arquillian, because the missing "upload" should be in JBoss 4.2.3 and nobody ever is going to implement that.
But it would be good if this would be part of the documentation, since it took me some time to figure this out.
For the interested (or those in need for a solution): https://github.com/kifj/arquillian-container-jbossas/tree/1and1-additions/jbossas-remote-4.2 contains a hack which uses scp to copy the deployment to the server, which probably only works in our environment but may give you hints where to intercept the call chain.
The text was updated successfully, but these errors were encountered: