Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jbossas-remote-4.2 does not work with remote hosts #10

Open
kifj opened this issue May 12, 2014 · 0 comments
Open

jbossas-remote-4.2 does not work with remote hosts #10

kifj opened this issue May 12, 2014 · 0 comments

Comments

@kifj
Copy link

kifj commented May 12, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant