Hi, any updates on this issue? I believe this problem is also apparent in
JBoss AS 4.2 and JBoss 5.
khudalla wrote:
>
> Okay, I have implemented the changes based on the SVN trunk and have
> posted a patch in JIRA for issue AMQ-765. I have been successfully testing
> the RA now on glassfish v2
Hi All,
Any updates on this issue, that is, is it already incorporated on any
release of ActiveMQ?
I am currently using ActiveMQ 5.3.0 and set up ActiveMQ with JBoss 5 using
JCA RA. Reading through this email thread, I think I have encountered the
same issue with ActiveMQ and JBoss. I also encoun
Okay, I have implemented the changes based on the SVN trunk and have posted a
patch in JIRA for issue AMQ-765. I have been successfully testing the RA now
on glassfish v2 and v2 UR1. Could someone please check whether this also
works on Geronimo?
Regards,
Kai
rajdavies wrote:
>
> sounds good
Okay Raj(?),
how should I proceed on this matter? Do we need consent of any other players
in this area? The JIRA issue is not assigned to anyone yet. If I create a
patch and post it on JIRA, who will take notice of it and incorporate it
into the trunk (and/or previous branches)? Are there any cod
sounds good to me!
On Jan 7, 2008, at 8:36 AM, khudalla wrote:
Ok then!
From my point of view the main problem is the fact that the factory
property
of the ActiveMQConnectionFactory class is transient. Thus, if the
ActiveMQConnectionFactory gets serialized/deserialized in the
process of
Ok then!
>From my point of view the main problem is the fact that the factory property
of the ActiveMQConnectionFactory class is transient. Thus, if the
ActiveMQConnectionFactory gets serialized/deserialized in the process of
binding/retrieving from/to JNDI (which glassfish obviously does), its
r
please discuss it on the list kai
On Jan 6, 2008, at 9:26 PM, khudalla wrote:
Hi, Chris, James!
I have put some time into this issue and already have commented on
it in
JIRA. I think I have found the problem and already have hacked up a
solution
which I would like to elaborate on. However
Hi, Chris, James!
I have put some time into this issue and already have commented on it in
JIRA. I think I have found the problem and already have hacked up a solution
which I would like to elaborate on. However, James, in JIRA the issue is not
assigned to anyone and I would like to discuss some
