Re: problem of connecting to jconsole to remote on activemq using jmx with centos 6
thank you my friend i found the problem i have to change createConnector=true instead of createConnector=false when i changed i traced activemq log i found line that i can connect to jmx:rmi://... managementContext managementContext connectorPort=1099 createConnector=true/ /managementContext thanks alot for helping dear friend -- View this message in context: http://activemq.2283324.n4.nabble.com/problem-of-connecting-to-jconsole-to-remote-on-activemq-using-jmx-with-centos-6-tp4671710p4671804.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
problem of losing messages
i have a problem when i sent about 13 message i found in activemq localhost:8161 all 13 message was dequeued and in my database i found from 8 to 11 message only that's mean i am losing some messages i need to track these messages what's happend to losing messages why i lost these messages and how can i fix this issue can any one help me please really i need help -- View this message in context: http://activemq.2283324.n4.nabble.com/problem-of-losing-messages-tp4671803.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] [Commented] (AMQNET-418) Recovery File Logger does not support multiple concurrent transactions
[ https://issues.apache.org/jira/browse/AMQNET-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777466#comment-13777466 ] Daniel Marbach commented on AMQNET-418: --- Tom, nobody seems to care about the patches we provided. Recovery File Logger does not support multiple concurrent transactions -- Key: AMQNET-418 URL: https://issues.apache.org/jira/browse/AMQNET-418 Project: ActiveMQ .Net Issue Type: New Feature Components: ActiveMQ Reporter: Remo Gloor Assignee: Jim Gomes Priority: Minor Attachments: allDTCImprovments.patch, RecoveryLoggerDoesNotSupportMultipleTransactions.patch Currently it is not possible to use more than one session if you use DTC Transactions. This is because the RecoveryFileLogger can not handle more than one transaction simultanously. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-422) Added support for transactions for Asyncronous Listeners
[
https://issues.apache.org/jira/browse/AMQNET-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777462#comment-13777462
]
Daniel Marbach commented on AMQNET-422:
---
Tom, nobody seems to care about the patches we provided.
Added support for transactions for Asyncronous Listeners
Key: AMQNET-422
URL: https://issues.apache.org/jira/browse/AMQNET-422
Project: ActiveMQ .Net
Issue Type: New Feature
Components: ActiveMQ
Reporter: Remo Gloor
Assignee: Jim Gomes
Priority: Minor
Attachments:
AddedSupportForAmbientTransactionForAsyncConsumers.patch,
allDTCImprovments.patch
Asyncronous Listeners do not support transactions properly. I suggest to add
the option to register a callback that can be used to create a transaction
for each message received by the asyncronous listener.
e.g.
((MessageConsumer)consumer).CreateTransactionScopeForAsyncMessage =
this.CreateScope;
private TransactionScope CreateScope()
{
return new TransactionScope(TransactionScopeOption.RequiresNew);
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: problem of losing messages
this question goes on the user mailing list us...@activemq.apache.org you should probably take a look here before posting: http://activemq.apache.org/tips-for-getting-help.html On Tue, Sep 24, 2013 at 12:39 PM, ossama wagdy ossamawa...@hotmail.comwrote: i have a problem when i sent about 13 message i found in activemq localhost:8161 all 13 message was dequeued and in my database i found from 8 to 11 message only that's mean i am losing some messages i need to track these messages what's happend to losing messages why i lost these messages and how can i fix this issue can any one help me please really i need help -- View this message in context: http://activemq.2283324.n4.nabble.com/problem-of-losing-messages-tp4671803.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
[jira] [Updated] (AMQ-4740) heart-beat is disabled when connecting to web socket
[ https://issues.apache.org/jira/browse/AMQ-4740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeff Mesnil updated AMQ-4740: - Summary: heart-beat is disabled when connecting to web socket (was: heart-beat is disable when connecting to web socket) heart-beat is disabled when connecting to web socket Key: AMQ-4740 URL: https://issues.apache.org/jira/browse/AMQ-4740 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.8.0 Environment: Google Chrome29.0.1547.76 (Official Build 223446) Reporter: Jeff Mesnil If I use the stomp.js library to connect to ActiveMQ over its WebSocket url (ws://localhost:61614), the CONNECTED frame returns with disabled heart-beat: CONNECTED heart-beat:0,0 session:ID:retsina.local-63633-1380117269290-2:1 server:ActiveMQ/5.8.0 version:1.1 If I connect to its TCP socket (localhost:61613), the CONNECT frame will have heart-beat: CONNECTED heart-beat:1,1 session:ID:retsina.local-63384-1380115729700-2:12 server:ActiveMQ/5.8.0 version:1.1 In both case, the stomp.js send the same CONNECT frame with heart-beat: CONNECT login:user passcode:password accept-version:1.1,1.0 heart-beat:1,1 Is heart-beat disabled on purpose for Web Socket? Please note that the stomp.js does support heart-beat (using window.setInterval in a Web browser) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4740) heart-beat is disable when connecting to web socket
Jeff Mesnil created AMQ-4740: Summary: heart-beat is disable when connecting to web socket Key: AMQ-4740 URL: https://issues.apache.org/jira/browse/AMQ-4740 Project: ActiveMQ Issue Type: Bug Affects Versions: 5.8.0 Environment: Google Chrome 29.0.1547.76 (Official Build 223446) Reporter: Jeff Mesnil If I use the stomp.js library to connect to ActiveMQ over its WebSocket url (ws://localhost:61614), the CONNECTED frame returns with disabled heart-beat: CONNECTED heart-beat:0,0 session:ID:retsina.local-63633-1380117269290-2:1 server:ActiveMQ/5.8.0 version:1.1 If I connect to its TCP socket (localhost:61613), the CONNECT frame will have heart-beat: CONNECTED heart-beat:1,1 session:ID:retsina.local-63384-1380115729700-2:12 server:ActiveMQ/5.8.0 version:1.1 In both case, the stomp.js send the same CONNECT frame with heart-beat: CONNECT login:user passcode:password accept-version:1.1,1.0 heart-beat:1,1 Is heart-beat disabled on purpose for Web Socket? Please note that the stomp.js does support heart-beat (using window.setInterval in a Web browser) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
