You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Adam Walczak (JIRA)" <ji...@apache.org> on 2009/11/16 19:05:52 UTC
[jira] Commented: (AMQ-2148) ActiveMQ 5.2.0 time to live > 0
problem
[ https://issues.apache.org/activemq/browse/AMQ-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=55468#action_55468 ]
Adam Walczak commented on AMQ-2148:
-----------------------------------
Thank Dejan Bosanac, your solution worked for me. (ActiveMQ 5.3)
Btw. shouldn't this be enabled by default ?
I don't think it's a normal activity to sync times in all systems interacting with the JMS broker. At least it's impossible in my scenario.
> ActiveMQ 5.2.0 time to live > 0 problem
> ----------------------------------------
>
> Key: AMQ-2148
> URL: https://issues.apache.org/activemq/browse/AMQ-2148
> Project: ActiveMQ
> Issue Type: Bug
> Components: Connector
> Affects Versions: 5.2.0
> Reporter: Dmitry Geurkov
> Priority: Minor
>
> problem on activemq 5.2.0 running on opensolaris server
> message producer is running on the same server publishing messages on topic with time to live set to 30000
> message consumer was running on windows xp client.. not even single message was recieved
> on contrary
> both message producer and consumer running on windows xp with the same settings work just fine..
> I think the problem is in message producer code when it's running on unix type operating system
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.