You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Adrian Co (JIRA)" <ji...@apache.org> on 2006/11/23 00:26:02 UTC
[jira] Commented: (AMQ-1060) Unable to connect to AMQ 4.x queue
with MDB
[ https://issues.apache.org/activemq/browse/AMQ-1060?page=comments#action_37527 ]
Adrian Co commented on AMQ-1060:
--------------------------------
Kindly attach the broker and client logs with debug turned on and whatever configuration you used for the broker and client. I don't have Websphere, but maybe someone will see something. :)
> Unable to connect to AMQ 4.x queue with MDB
> -------------------------------------------
>
> Key: AMQ-1060
> URL: https://issues.apache.org/activemq/browse/AMQ-1060
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0.1, 4.0.2
> Environment: OS Windows 2003 Server, AMQ 4.0.2, Websphere 5.1.11
> Reporter: Stephen Murray
> Fix For: 3.2.2
>
>
> Can you please raise a JIRA for a bug introduced in Version 4.x of ActiveMQ ?
> I'm unable to connect to an ActiveMQ queue with an MDB when the ActiveMQ queue I'm connecting to has a queue depth.
> This works in ActiveMQ 3.2.2, but doesn't in 4.0.1 or 4.0.2.
> Environment :
> AMQ 4.0.1 or 4.0.2 deployed standalone on a Windows 2003 server.
> Basic (Hello World) MDB deployed within IBM Websphere 5.1 (Patch 11).
> Intructions to recreate :
> Start AMQ, load a message onto the MDBs Queue, start Websphere and MDB won't connect to the ActiveMQ queue.
> If there is any further information you require to assist in the resolution of this problem, please let us know. We can provide details of the code or the WAS/AMQ config.
> Whilst stating this doesn't work for a Hello World MDB, this is for simplicity and ease of testing this issue, in reality we are using the MDB and AMQ as part of a full blown integration solution at 2 major Utility companies and seriously need some assistance with this. Testing onsite of the solution at each of these companies has revealed this issue, this is therefore preventing the move of the solution into production.
> We cannot revert to the use of the version 3.2.2 of AMQ as there are some memory limitations with this version (that have been addressed in 4.x) that mean that it will not cope with the volumes of messages that are required to be handled.
> Thanks,
> Stephen Murray
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira