my clients are not disconnecting frequently bcoz one client will connect only once and stay connected for 10 mins without any disconnection. Similarly all 1000s clients will connect only once and stay connected for 10mins. So there is no chance of clients diconnecting and reconnecting frequently.Even i also checked the same thing by extending the client disconnection time from 10 mins to 30 mins and i didn't find a single trace of Client disconnection. If i will give a delay of 1000 ms (1 sec) between two clients to send data then activemq will never fail and never disconnect which was happenging since last two years. Now i have a requirement where all the 1000 clients will connect and send data at one time means all 1000 data will reach ActiveMQ at same time.
Below is my design pattern i m maintaining only one JMSConnection for all the 1000s clients. When a client connection reached my server application after accetping that client i create a new Thread to handle that particular client including Connection, Data, Acknowledgment and disconnection in that particular Thread only. So for 1000s clients i am creating 1000s Thread and manage their interaction and all 1000s client's data go to ActiveMQ through only one JMS Connection and one Producer. Here only ActiveMQ fails. If i give delay in sending the data then ActiveMQ find enough time to send the data to Queue and go for next client's data. Here all 1000s client's data comes at same time bcoz of which ActiveMQ or Producer is not finding time to put the data in Queue and go for next client's data. And only One JMSCOnnection is maintained through the application life cycle and when JMSBroker connection fails it reconnect to the JMSBroker and after that only application send the data. Here one JMS Connection and One Producer is maintained. And i am not maintaining the fail over yet. Will that help me and make sure that Activemq is not diconnecting?? And how to enable the log ? -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-not-able-to-handle-message-load-tp4703928p4704077.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.