VMware Cloud Community
santhoshsd
Contributor
Contributor

Not able to configure JBoss 4.2

I have installed Hyperic server 4.1.2 in one machine and hyperic agent 4.1.2 on Windows machine.

On the windows machine, JBoss 4.2 is running.
The agent did not auto-discover JBoss running on the machine.

I added the new server JBoss 4.2, but when I try to configure it. I get the following error

The configuration has not been set for this resource due to : Invalid configuration: Error contacting resource: Can't connect to MBeanServer [java.naming.provider.url=jnp%3A//localhost%3A1099,java.naming.security.principal=hqadministrator,java.naming.security.credentials=hqadministrator]: javax.naming.NoInitialContextException: Cannot instantiate class: org.jboss.security.jndi.JndiLoginInitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.jboss.security.jndi.JndiLoginInitialContextFactory]

I checked the agent log file .. the following error was being written

2009-05-31 23:10:11,484 INFO [Thread-1] [RuntimeAutodiscoverer] Running runtime autodiscovery for JBoss 4.2
2009-05-31 23:10:11,641 ERROR [Thread-1] [RuntimeAutodiscoverer] Unexpected error running autodiscoverer for plugin: JBoss 4.2: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
org.hyperic.hq.product.PluginException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory
at org.hyperic.hq.plugin.jboss.JBossDetector.discoverJBossServices(JBossDetector.java:614)
at org.hyperic.hq.plugin.jboss.JBossDetector.discoverServices(JBossDetector.java:599)
at org.hyperic.hq.product.ServerDetector.discoverResources(ServerDetector.java:203)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: org.jnp.interfaces.NamingContextFactory [Root exception is java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at org.hyperic.hq.plugin.jboss.JBossUtil.getMBeanServer(JBossUtil.java:138)
at org.hyperic.hq.plugin.jboss.JBossDetector.discoverJBossServices(JBossDetector.java:612)
... 7 more
Caused by: java.lang.ClassNotFoundException: org.jnp.interfaces.NamingContextFactory
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at com.sun.naming.internal.VersionHelper12.loadClass(Unknown Source)


Message was edited by: santhoshsd
Reply
0 Kudos
2 Replies
shippu4u
Contributor
Contributor

did u ever got the solution to this..i am also facing the same problem
Reply
0 Kudos
benjoyner1983
Contributor
Contributor

i had a similar issue, it turned out the firewall had been blocking port 1099 even though jboss was configured to listen on it.