THe weird thing is that the JMX agent works fine on my JBoss 7.1.1 running
on Windows Vista 32bit, but it fails to load on my colleague's computer
where it has a Windows 7 64bit (even when I copied my whole jboss folder to
his machine).
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Fr
Hi
I assume you want JMX at runtime, as else you can disable it on Camel.
For what is worth it, you can plugin a custom JMX management agent in Camel
http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/ManagementAgent.html
In case you need to do some extra leg-work to g
Trust me, it's the same JBoss all-files-and-folders-and-configurations
(jboss-as-7.1.1-Final) ziped and copied from one machine to the other one.
*Bruno Borges*
(21) 7672-7099
*www.brunoborges.com*
On Thu, Jun 21, 2012 at 12:41 PM, Babak Vahdat
wrote:
> No I don't think that it has something to
No I don't think that it has something to do with network interfaces and
whatnot. The exception is thrown by JBoss intentionally, by the release
7.1.0.CR1b it's here:
http://grepcode.com/file/repo1.maven.org/maven2/org.jboss.as/jboss-as-naming/7.1.0.CR1b/org/jboss/as/naming/WritableServiceBasedNam
What I find most interesting is that it runs fine on my Windows Vista 32bit.
But when I run the same code and JBoss instance on a Windows 7 64bit, this
problem occurs.
Do you think this is something related to network interfaces or something
else? I double checked Windows firewall and it is disab
Hi
I would recommend you to take a look at:
https://community.jboss.org/message/644991
https://issues.jboss.org/browse/AS7-2755
As per se it's a JBoss issue/behaviour and not Camel. And I didn't face
this problem while using JBoss 5.1. And usePlatformMBeanServer flag
defaults to true so you can
