You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Sami Korhonen (JIRA)" <ji...@apache.org> on 2018/01/17 14:10:00 UTC

[jira] [Created] (ARTEMIS-1614) Resource adapter installation on WebSphere Application Server fails

Sami Korhonen created ARTEMIS-1614:
--------------------------------------

             Summary: Resource adapter installation on WebSphere Application Server fails
                 Key: ARTEMIS-1614
                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1614
             Project: ActiveMQ Artemis
          Issue Type: Bug
    Affects Versions: 2.4.0, 2.3.0
            Reporter: Sami Korhonen


WebSphere Application Server (classic) does a class scan (for properties) during resource adapter installation. The scan causes artemis resource adapter classes to initialize, which in turn causes a NPE at ActiveMQRALogger (artemis-ra).

The issue is that during the scan WebSphere seems to use a classloader, which does not support Class.getPackage() properly.

A quick fix: In order to support WebSphere, getPackage().getName() should be replaced with a static string.

Proper fix: Resolving NPE at ActiveMQRALogger leads to another NPE in logging. Similar fix would be required for jboss-logging (LoggerProviders). I believe that changing static initializer to lazy initalizer or initializing the logger at resource adapter startup would resolve both issues. I have yet to verify this fix.

If you are familiar with WebSphere, you can find instructions on how to compile and install adapter here ( [https://github.com/skorhone/websphere-artemis] )



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)