[
https://issues.apache.org/jira/browse/AMQ-4909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846184#comment-13846184
]
Richard Kettelerij commented on AMQ-4909:
-
This is definitely a step in the right
Sophia Wright created AMQ-4932:
--
Summary: Large tx-*.tmp file in the kahadb directory
Key: AMQ-4932
URL: https://issues.apache.org/jira/browse/AMQ-4932
Project: ActiveMQ
Issue Type: Bug
Steven has a point...
A message is not send to the broker untill commit occurs, SO how does this
tx-..tmp file gets created before commit ?
Please explain this issue.. What is the root cause for this file creation...
Thanks,
Sophia
--
View this message in context:
On 12/12/2013 05:32 AM, Sophia Wright wrote:
Steven has a point...
A message is not send to the broker untill commit occurs, SO how does this
tx-..tmp file gets created before commit ?
Please explain this issue.. What is the root cause for this file creation...
Thanks,
Sophia
--
View this
[
https://issues.apache.org/jira/browse/AMQ-4932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-4932.
-
Resolution: Invalid
This is a support question which is best discussed on the Users list.
Large
Henrik Karlsson created AMQ-4933:
Summary: Migration of database fails
Key: AMQ-4933
URL: https://issues.apache.org/jira/browse/AMQ-4933
Project: ActiveMQ
Issue Type: Bug
Affects
So basically this file is getting created, because Producer is using
transactions and has sent messages more than maxTransactionSize before
commit occurs.
and this file will only be created when I am using transactions ?
Please correct me if I am wrong.
Thanks
--
View this message in
Dejan Bosanac created AMQ-4934:
--
Summary: JDBCPersistenceAdapter: queue messages trapped in store
when DB connection is lost and restored
Key: AMQ-4934
URL: https://issues.apache.org/jira/browse/AMQ-4934
[
https://issues.apache.org/jira/browse/AMQ-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-4934.
Resolution: Fixed
The problem can happen when JDBC driver throw SQLEcxeption after it stores a
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846385#comment-13846385
]
Timothy Bish commented on AMQCPP-527:
-
Best to retest with v3.8.2 which was recently
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846380#comment-13846380
]
Christian Mamen edited comment on AMQCPP-527 at 12/12/13 4:00 PM:
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846394#comment-13846394
]
Christian Mamen edited comment on AMQCPP-527 at 12/12/13 4:08 PM:
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846394#comment-13846394
]
Christian Mamen edited comment on AMQCPP-527 at 12/12/13 4:08 PM:
Michael Yara created AMQ-4935:
-
Summary: Deadlock caused by Re-entrant lock with no locking thread
Key: AMQ-4935
URL: https://issues.apache.org/jira/browse/AMQ-4935
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846394#comment-13846394
]
Christian Mamen edited comment on AMQCPP-527 at 12/12/13 7:55 PM:
[
https://issues.apache.org/jira/browse/AMQCPP-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846702#comment-13846702
]
Timothy Bish commented on AMQCPP-527:
-
Since the iterators are working with a snapshot
[
https://issues.apache.org/jira/browse/AMQ-4925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Lumpkin updated AMQ-4925:
Description:
The 'JMXConnectorFactory(url, null).connect() ' request returns as if it is
[
https://issues.apache.org/jira/browse/AMQ-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Yara updated AMQ-4935:
--
Component/s: (was: activemq-pool)
Broker
Deadlock caused by Re-entrant lock with
[
https://issues.apache.org/jira/browse/AMQ-4888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-4888.
-
Resolution: Not A Problem
These are configuration related warnings that are resolved by properly
[
https://issues.apache.org/jira/browse/AMQ-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846756#comment-13846756
]
Timothy Bish commented on AMQ-4819:
---
Any progress on a patch for this?
Reducing memory
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846794#comment-13846794
]
Tom M. commented on AMQ-4914:
-
Can anyone please clarify this issue? Is this a productive
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-4914:
--
Fix Version/s: 5.10.0
AMQP consumer hangs when receiving large messages
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846801#comment-13846801
]
Timothy Bish commented on AMQ-4914:
---
This occurs in our test against the QPid JMS client:
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQ-4914:
--
Affects Version/s: 5.9.0
AMQP consumer hangs when receiving large messages
[
https://issues.apache.org/jira/browse/AMQNET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846806#comment-13846806
]
Timothy Bish commented on AMQNET-454:
-
Added the vendor tree to the NMS svn repo.
[
https://issues.apache.org/jira/browse/AMQ-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846875#comment-13846875
]
Michael Yara commented on AMQ-4935:
---
I have discovered that the issue also occurs when
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846924#comment-13846924
]
Tom M. edited comment on AMQ-4914 at 12/12/13 11:47 PM:
Hi Timothy,
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846924#comment-13846924
]
Tom M. commented on AMQ-4914:
-
Hi Timothy,
thanks for your explanation and updates for this
[
https://issues.apache.org/jira/browse/AMQ-4914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13846930#comment-13846930
]
Timothy Bish commented on AMQ-4914:
---
First we'd need to figure out if its a broker or
I am new to the field of message queues.
My question might be high level. I have a client that has IBM Websphere MQ
and want us to integrate with them via message queues. They have indicated
that we will have to send/receive to their IBM QueueManager.
We want to have our own internal Message
Yes, via a bridge or camel.
Sent from my pressure cooker.
On Dec 12, 2013, at 21:43, Adam Atawneh aataw...@anzgcis.com wrote:
I am new to the field of message queues.
My question might be high level. I have a client that has IBM Websphere MQ
and want us to integrate with them via message
By Bridge do you mean having an application connecting to both queues and
transferring between them?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Integrating-ActveMQ-with-IBM-Queue-Manager-tp4675509p4675511.html
Sent from the ActiveMQ - Dev mailing list archive at
32 matches
Mail list logo
