[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-5024) JBoss AS start fails if used configuration is not default one

[Rob Stryker (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-5024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12489879#action_12489879 ] 

Rob Stryker commented on JBIDE-5024:
------------------------------------

This appears to be a bug with the actual jboss 3.2.x runtime and not in the tooling. The actual stacktrace (after checking the root cause) is:

Caused by: java.lang.ClassCastException: java.lang.Boolean
	at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1158)
	at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1375)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:590)
	at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:583)
	at javax.naming.InitialContext.lookup(InitialContext.java:351)
	at org.jboss.ide.eclipse.as.core.extensions.jmx.JMXSafeRunner.run(JMXSafeRunner.java:67)

But the code I'm executing to cause this is:
			InitialContext ic = new InitialContext(p);
			Object obj = ic.lookup("jmx/invoker/RMIAdaptor");

It's worthwhile to note that this only fails while the server is still starting up. If I actually pause the polling thread until the server is up, it doesn't error after that.  So I'm convinced this is a runtime bug and there's really not very much I can do to fix it. 

if you'd like, you can change this request to ask for an "automatic success" poller if you think it would help. 

> JBoss AS start fails if used configuration is not default one
> -------------------------------------------------------------
>
>                 Key: JBIDE-5024
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-5024
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: JBossAS
>    Affects Versions: 3.1.0.M4
>         Environment: Win32
> Java 1.6 U16
> Eclipse Galileo 3.5 SR1 
> JBoss Tools 3.1.0.M3 
> JBoss 3.2.7
>            Reporter: Denis Golovin
>            Assignee: Rob Stryker
>             Fix For: 3.1.0.CR1
>
>
> When starting the 'default' configuration everything is fine, but any other config fails. I've got the following error:
> "Server JBoss 3.2 Runtime Server failed to start.
> An exception stack trace is not available."
> After searching the filesystem for any clues or hints what's going wrong, I found a logfile in the metadir of my workspace @
> ".metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_3.2_Runtime_Server\log" with the following content:
> !ENTRY org.jboss.ide.eclipse.as.core 4 16842752 2009-10-14 10:19:48.580
> !MESSAGE Failure in Poll Thread
> !STACK 0
> org.jboss.ide.eclipse.as.core.server.IServerStatePoller$PollingException: java.lang.Boolean cannot be cast to java.lang.String
> 	at org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.handleException(JMXPoller.java:166)
> 	at org.jboss.ide.eclipse.as.core.extensions.polling.JMXPoller$PollerRunnable.run(JMXPoller.java:106)
> 	at java.lang.Thread.run(Thread.java:619)
> After that I switch the Server Polling method from "JMX Poller" to "Timeout Poller" and the server starts, but the plugin never reached the state "Started" - it remains in the the state "Starting".
> In the default config the JMX Poller works as expected.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira