4 Replies Latest reply on Dec 1, 2008 7:36 AM by Heiko Rupp

    JBoss AS plugin packages not retreived

    Thorbjørn Blixen-Finecke Newbie

      When using the jopr JBoss AS plugin the following exception is reported:

      2008-11-27 20:23:03,086 WARN [ConfigurationManager.threadpool-1] (rhq.core.pc.configuration.ConfigurationCheckExecutor)- Unable to check for updated configuration
      java.lang.NullPointerException
      at org.rhq.plugins.jbossas.AbstractMessagingComponent.loadResourceConfiguration(AbstractMessagingComponent.java:130)
      at sun.reflect.GeneratedMethodAccessor59.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:450)
      at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
      at java.util.concurrent.FutureTask.run(FutureTask.java:123)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
      at java.lang.Thread.run(Thread.java:595)

      It seems that the failing line is this:

      String version = jf.getManifest().getMainAttributes().getValue(Attributes.Name.IMPLEMENTATION_VERSION);

      The result is that no packages are retrieved for the JBoss AS instance being monitored.

      Surrounding the block of code that attempts to retrieve the manifest solves this issue.

      I haven't debugged the issue further but it might seem like jars without a manifest cant be handled by the plugin?