JMSDestinationManager cannot be cast to java.lang.String

[matt.drees]

Hi,

I installed embedded jopr 1.1 last week on our jboss 4.2.3 instances.

I regularly see the an exception (below) in the logs. It doesn't appear to affect anything, but it seems like the sort of thing that should be reported.

Want me to submit a jira report?


Thanks for building this tool, by the way; it's pretty cool.

-Matt

2009-02-23 10:36:33,832 403228658 INFO InventoryManager.discovery-1 [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] () Running runtime discovery scan rooted at platform...
2009-02-23 10:36:33,926 403228752 WARN InventoryManager.discovery-1 [org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor] () Failed to execute runtime discovery for Resources of type ResourceType[id=0, category=Service, name=JBossMQ, plugin=JBossAS]
java.lang.ClassCastException: org.jboss.mq.server.JMSDestinationManager cannot be cast to java.lang.String
 at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.getVersionFromSource(AbstractMessagingDiscoveryComponent.java:107)
 at org.rhq.plugins.jbossas.AbstractMessagingDiscoveryComponent.discoverResources(AbstractMessagingDiscoveryComponent.java:72)
 at org.rhq.plugins.jbossas.JBossMQDiscoveryComponent.discoverResources(JBossMQDiscoveryComponent.java:44)
 at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.executeComponentDiscovery(RuntimeDiscoveryExecutor.java:246)
 at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.discoverForResource(RuntimeDiscoveryExecutor.java:218)
 at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.runtimeDiscover(RuntimeDiscoveryExecutor.java:136)
 at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:97)
 at org.rhq.core.pc.inventory.RuntimeDiscoveryExecutor.call(RuntimeDiscoveryExecutor.java:54)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98)
 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:207)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:619)

[ccrouch]

This looks like it could be related to

https://jira.jboss.org/jira/browse/JOPR-40

Embedded Jopr 1.1 was built with Jopr r129, so the last commit for JOPR-40 won't be in it.

Can you try using a more recent version of the JBAS4 console built from /trunk and see if its fixed?

http://hudson.jboss.org/hudson/job/embjopr/

Cheers

[matt.drees]

So far so good. I'll let you know if anything comes up.
Thanks Charles!

[chen-yi-chen]

Hi,

I installed embedded-jopr-1.2.0.CR-JBAS4 this afternoon on my jboss 4.2.3 instance.

I always see the following exception (attachment) in the logs, and the exception led to the Runtime shutdown hook.

java.lang.RuntimeException: exception invoking: init javax.faces.el.EvaluationException: java.lang.RuntimeException: exception invoking: init at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)

Thanks for building this tool, by the way; it's pretty cool.

Chen Yi Chen

[chen-yi-chen]

Hi,

I have tried to installed jopr-embedded-core-1.4.1-SNAPSHOT.war (downloaded from https://hudson.jboss.org/jenkins/job/embjopr/lastSuccessfulBuild/artifact/core/target/jopr-embedded-core-1.4.1-SNAPSHOT.war) and admin-console.war (downloaded from https://hudson.jboss.org/jenkins/job/embjopr/lastSuccessfulBuild/artifact/jbas6/target/admin-console.war) this morning on my jboss 4.2.3 instance.

I always see the following exception (attachment) in the logs, and the exception led to an incompletely deployed package, admin-console.war.

Exception starting filter Seam Filter java.lang.ClassCastException: org.jboss.on.embedded.LazyStartupFilter cannot be cast to javax.servlet.Filter

Thanks for building this tool, by the way; it's pretty cool.

Chen Yi Chen

[chen-yi-chen]

Dear Sir,

After increasing my JVM memory settings in run.sh/conf/bat to at least the following variable (via the JAVA_OPTS environment variable), I can access the Embedded Jopr Core after logging in the Embedded Jopr administrative interface although I still have encounter the warning shown as the first post.

-Xms200M -Xmx200M -XX:PermSize=200M -XX:MaxPermSize=200M

Thanks for building this tool, by the way; it's pretty cool.

Chen Yi Chen