-
1. Re: Problem while connecting to remote HornetQ provider using JMX
clebert.suconic Aug 9, 2011 8:55 PM (in response to m.carbone)connecting to a remote connection is actually a FAQ on Oracle:
http://download.oracle.com/javase/1.5.0/docs/guide/management/faq.html
Regarding the administration, we have been doing some work with the Application Server 7 team. We may do something on standalone soon.
-
2. Re: Problem while connecting to remote HornetQ provider using JMX
m.carbone Aug 10, 2011 5:11 AM (in response to clebert.suconic)Thanks for your answer Clebert, but those FAQs didn't help.
I'm happy about future ennhancements in the standalone architecture, but now I have to fall back to other JMS providers. I'm runnig a complex architecture and I can't deal with this lack of management. pity.
Bye
-
3. Re: Problem while connecting to remote HornetQ provider using JMX
clebert.suconic Aug 10, 2011 1:18 PM (in response to m.carbone)have you really looked at the JMX console and Beans you have on HornetQ?
-
4. Re: Problem while connecting to remote HornetQ provider using JMX
m.carbone Aug 11, 2011 12:13 PM (in response to clebert.suconic)Hi Clebert,
I'm using the default bean in the standalone/non clustered configuration:
...
<!-- MBean server -->
<bean name="MBeanServer" class="javax.management.MBeanServer">
<constructor factoryClass="java.lang.management.ManagementFactory"
factoryMethod="getPlatformMBeanServer"/>
</bean>
...
And it should work, because if I try accessing on the same host but with the remote connection url it works. So I guess it must be a connectivity problem, even if the basic tests and firewall are fine. Definitively, it is not an HornetQ problem, but a specific limitation of JMS remote access.
If u mean other beans/configs, let me know.
Bye
-
5. Re: Problem while connecting to remote HornetQ provider using JMX
m.carbone Aug 11, 2011 12:33 PM (in response to clebert.suconic)Hi Clebert,
I'm using the default bean in the standalone/non clustered configuration:
...
<!-- MBean server -->
<bean name="MBeanServer" class="javax.management.MBeanServer">
<constructor factoryClass="java.lang.management.ManagementFactory"
factoryMethod="getPlatformMBeanServer"/>
</bean>
...
And it should work, because if I try accessing on the same host but with the remote connection url it works. So I guess it must be a connectivity problem, even if the basic tests and firewall are fine. Definitively, it is not an HornetQ problem, but a specific limitation of JMS remote access.
If u mean other beans/configs, let me know.
Bye
-
6. Re: Problem while connecting to remote HornetQ provider using JMX
clebert.suconic Aug 11, 2011 1:07 PM (in response to m.carbone)a remote connection to JMX should work fine.
Anyway, a friend of ours have written some admin console that works on HornetQ. They are selling it commercially I think.
I don't mean to be doing free ad for them here, but maybe that's an option for you?
-
7. Re: Problem while connecting to remote HornetQ provider using JMX
m.carbone Aug 11, 2011 1:46 PM (in response to clebert.suconic)...maybe not an option for my current customer... budget is a critical issue...
But I've just downloaded the trial and will look into it.
Thanks for advice
bye
-
8. Re: Problem while connecting to remote HornetQ provider using JMX
smerzlia Aug 14, 2011 11:42 PM (in response to m.carbone)Michele,
I have released an updated version today (1.0.2), which fixed connectivity issues with hornetq and the install will now allow installations even when it cannot find a JRE or JDK installed.
http://www.rockeyesoftware.com/
Regards,
Serge
-
9. Re: Problem while connecting to remote HornetQ provider using JMX
smerzlia Aug 14, 2011 11:47 PM (in response to m.carbone)Michele,
Something to try - not elegant but it works. Edit your hornetq-beans.xml and hardcode your servers IP address (I have used 10.0.1.11 as an example below):
<!-- JNDI server. Disable this if you don't want JNDI -->
<bean name="JNDIServer" class="org.jnp.server.Main">
<property name="namingInfo">
<inject bean="Naming"/>
</property>
<property name="port">${jnp.port:1099}</property>
<property name="bindAddress">${jnp.host:10.0.1.11}</property>
<property name="rmiPort">${jnp.rmiPort:1098}</property>
<property name="rmiBindAddress">${jnp.host:10.0.1.11}</property>
</bean>