activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Hudalla (JIRA)" <>
Subject [jira] Commented: (AMQ-765) ActiveMQ RA serialization issue on Glassfish
Date Mon, 14 Jan 2008 15:49:45 GMT


Kai Hudalla commented on AMQ-765:


I have spent some time fixing the Resource Adapter's serialization issue in order to make
it work in glassfish v2. Therefore I made some changes to ActiveMQConnectionFactory, ActiveMQManagedConnectionFactory
and ActiveMQResourceAdapter. I have also created additional test cases and updated the existing
ones to reflect my changes. I have successfully tested it in my local environment using glassfish
v2 and v2 UR1 on JDK 1.5.0_14. I have also attached a patch for the 5.1 SNAPSHOT code in SVN.
Could someone test it against Geronimo in order to see if it's still working there?


> ActiveMQ RA serialization issue on Glassfish
> --------------------------------------------
>                 Key: AMQ-765
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 4.0, 4.0.1
>         Environment: Glassfish
>            Reporter: Chris Conrad
>             Fix For: 5.2.0
>         Attachments: finest-log.txt, log.txt
> I've been trying to work through an issue with a NullPointerException run using the JCA
1.5 resource adapter on Glassfish.  In the course of debugging, Siva from the Glassfish team
provided this information:
> "Thanks for trying out GlassFish. Since I have only the trace snippet above, I tried
to debug this problem by going through ActiveMQ RA's source available at
> This is what I understand happens. Please correct me if there are errors. When ActiveMQConnectionFactory
is created at the createConnectionFactory method of,
the ConnectionManager is initialized to a *transient* variable "manager". Since ConnectionFactory
instances can be serialized/deserialized while publishing to JNDI (as is the case in Project
GlassFish), the connectionManager reference is lost and hence the NPE. The fix ideally should
be in the ActiveMQRA's code. You could copy me [sivakumart AT sun DOT com] while you are discussing
this with ActiveMQ, if you wish. If you still have any issues, please provide a copy of your
domain.xml [connector connection pool, resource configuratin information] and the entire trace
in server.log." 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message