[
https://issues.apache.org/jira/browse/AMQCPP-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Leung updated AMQCPP-534:
Description:
This happen in random; and will cause core dump under Solaris 10.
{panel:title=Core d
[
https://issues.apache.org/jira/browse/AMQCPP-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeremy Leung updated AMQCPP-534:
Description:
This happen in random; and will cause core dump under Solaris 10.
{panel:title=Core d
Jeremy Leung created AMQCPP-534:
---
Summary: Closing connection with setTransportListener to NULL may
cause core dump
Key: AMQCPP-534
URL: https://issues.apache.org/jira/browse/AMQCPP-534
Project: ActiveM
It looks like the broker side reader threads are hung or stopped b/c the
tcp buffers are backing up.
Can you post a broker thread dump?
Also can you use tcp in place of nio in the transport connector to
eliminate nio.
If you can reproduce with a 5.10-SNAPSHOT please raise a jira issue with
your t
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQCPP-533.
-
Resolution: Fixed
Patch applied on trunk and the 3.8.x patch branch
> Memory leak in StompWireFo
[
https://issues.apache.org/jira/browse/AMQ-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5066.
---
Resolution: Fixed
Patch applied
> Duplicate MQTT Subscription with a different QoS for the same Topic
[
https://issues.apache.org/jira/browse/AMQ-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-5065.
---
Resolution: Fixed
Patch applied.
> MQTT Retained message QoS must be set to a maximum of Subscription
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vince Hurrell updated AMQCPP-533:
-
Attachment: stomp_wire_format_leak_fix.patch
This patch fixes a memory leak when marshalling bina
[
https://issues.apache.org/jira/browse/AMQ-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhiraj Bokde updated AMQ-5066:
--
Attachment: AMQ-5066.patch
Patch for duplicate subscriptions, apply after patch for AMQ-5065
> Duplicate
[
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905743#comment-13905743
]
Les Hazlewood commented on AMQ-3621:
Sounds good [~ceposta], I totally understand. Plea
Dhiraj Bokde created AMQ-5066:
-
Summary: Duplicate MQTT Subscription with a different QoS for the
same Topic MUST remove the older Subscription
Key: AMQ-5066
URL: https://issues.apache.org/jira/browse/AMQ-5066
[
https://issues.apache.org/jira/browse/AMQ-5065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhiraj Bokde updated AMQ-5065:
--
Attachment: AMQ-5065.patch
Attached patch to set Retained message QoS to maximum of Subscription QoS
> M
Dhiraj Bokde created AMQ-5065:
-
Summary: MQTT Retained message QoS must be set to a maximum of
Subscription's QoS
Key: AMQ-5065
URL: https://issues.apache.org/jira/browse/AMQ-5065
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dhiraj Bokde closed AMQ-5061.
-
Resolution: Not A Problem
The assumption about leading '/' for MQTT topic levels was incorrect. I am
closi
[
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905628#comment-13905628
]
Christian Posta commented on AMQ-3621:
--
Les, so far what I'm seeing looks great.
I am g
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQCPP-533:
Description:
Here is the afflicted code:
{code}
try {
Pointer bytesMessage =
message.
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905604#comment-13905604
]
Vince Hurrell commented on AMQCPP-533:
--
I'm creating a patch right now. I'll attach
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905601#comment-13905601
]
Timothy Bish commented on AMQCPP-533:
-
We happily accept patches.
> Memory leak in
[
https://issues.apache.org/jira/browse/AMQCPP-533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQCPP-533:
Fix Version/s: 3.9.0
3.8.3
> Memory leak in StompWireFormat.cpp
> --
Vince Hurrell created AMQCPP-533:
Summary: Memory leak in StompWireFormat.cpp
Key: AMQCPP-533
URL: https://issues.apache.org/jira/browse/AMQCPP-533
Project: ActiveMQ C++ Client
Issue Type: Bu
Torsten Mielke
All the limits are under control
Store percent used = 3
Memory percent used = 0
Temp percent used = 1
Currently all the 100 queues are empty. All the messages are dequeued.
Producer flow control is turned on. I have had the same result when
producer flow control is turned off a
Hi All,
after some tests, I moved from JBoss Fuse ActiveMQ to activeMQ standard
(5.8.0).
I'm able to POST and GET a message, but now if I:
1. POST a message
POST http://localhost:8161/api/message/mynewqueue?type=queue&body=hello
HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/jso
[
https://issues.apache.org/jira/browse/AMQ-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13905338#comment-13905338
]
Dejan Bosanac commented on AMQ-2040:
No, this is a general JMS browsing issue. We improv
Is your producer getting flow controlled?
Does your broker reach any of its configured systemUsage limits?
Broker JMX stats should tell you. Particularly check MemoryPercentUsage,
StorePercentUsage and TempPercentUsage of the broker MBean.
Regards,
Torsten Mielke
tmielke.blogspot.com
On 19
Repeated the test with refactored project with 100 producers sharing same jms
template which is configured to use cached connection factory. After several
1,000,000s of messages in 60+ minutes, the producers hang with following
exception.
Name: producerTaskExecutor-27
State: RUNNABLE
Total block
25 matches
Mail list logo
