-
1. Re: Arquillian with a remote JBossAS 7
aslak Sep 3, 2011 4:49 AM (in response to sewatech)managementAddress is used to connect to the management API, from there the rest is suppose to be resolved automatically.
It will lookup the interface where jmx is bound, which by default is "public" and mapped to 127.0.0.1
It would seem you have only exposed the management API on a remote ip, not the jmx/http interfaces ?
-
2. Re: Arquillian with a remote JBossAS 7
sewatech Sep 3, 2011 8:22 AM (in response to aslak)Thanks for you answer, Aslak.
You're right, I had a 127.0.0.1 inet-address for my interface. I've changed it, but it does not work... My JBoss is on a separate LAN (on a EC2 instance) and I have to deal with NAT. I'll try to fix my JBoss config first and try arquillian again after that.
One more question : how does it work if I have an <any-address> interface ?
-
-
4. Re: Arquillian with a remote JBossAS 7
sewatech Sep 3, 2011 7:30 PM (in response to aslak)Thanks Aslak.
It works in my LAN. I still have problems with JMX and the firewall ; I have opened a new thread on that.
I hope that I will find a workaround as it would have been a nice demo for my prez on arquillian at the soft shake conference (http://www.soft-shake.ch/).
-
5. Re: Arquillian with a remote JBossAS 7
sewatech Dec 19, 2011 10:08 AM (in response to sewatech)1 of 1 people found this helpfulI finally made it work with a JBoss 7.1.0.Beta1 deployed on a EC2 instance.
The main issue was at the JMX level, which I fixed with a SOCKS proxy, as briefly described in that thread.
I've implemented the solution in a demo project.