last message should of read, 4.0.2 version didn't have the problem, not 4.1.0, sorry
pleaseHelpMe:o) wrote: > > Well, now it seems as I increase the load of messages going to the server, > I start to get these errors showing up. > > It seems with a small load I did not see this. Also, anybody know why the > web console will only show topics and memory usage when having 1 broker > open? when I have 2 networked together, it doesn't seem to show anything, > but lists broker1 as active. If I kill broker1 and broker2 takes over, it > starts to show memory usage and Topics.... > > I read a lot of people seeing this message with a load involved, but I > really didn't see any solutions in the forums. > > Just fyi, My app creates java threads that pass messages to the server and > process receive messages from the server. With 4.1.0 I was able to create > many more threads without seeing the following error ever, so it seems > something changed in regards to why I would see this????? > > javax.jms.JMSException: Wire format negotiation timeout: peer did not send > his wire format. > at > org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62) > at > org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1206) > at > org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1289) > at > org.apache.activemq.ActiveMQConnection.createSession(ActiveMQConnection.java:295) > at > org.apache.activemq.ActiveMQConnection.createTopicSession(ActiveMQConnection.java:998) > at com.divas.mts.MTSBase.createSession(MTSBase.java:71) > at > com.divas.imm.CommunicationModuleBase.createSubscriber(CommunicationModuleBase.java:79) > > pleaseHelpMe:o) wrote: >> >> excellent, working now, had to tweak a few more files that had the old >> references in them, thanks all who helped get it going. I also tested >> what I was originally trying to do by killing broker 1 with broker 2 >> setup as a networkConnector, sure enough, worked like a champ. Thanks >> all. >> >> Next thing I need to work on now is finding out how I can improve >> performance if I send a lot of messages, i.e. 100,000 or so within a >> short time, is it just finding enough memory to enable it, or some other >> tricks to increase performance. >> >> I was also originally trying to randomly connect to a particular broker, >> say I have 4 of them in a network, if I auto connect clients to broker1, >> will it limit performance, is there a way to randomly connect to one in >> the network through activeMQ or just need to tweak my client to randomly >> connect to a broker from a list of them. >> >> This forum rocks and I thank all who have helped with this. >> >> JB >> >> rajdavies wrote: >>> >>> No - you shouldn't need to update the code - you're probably pulling >>> in an old version of activemq on the class path >>> >>> On 11 Jun 2008, at 13:19, pleaseHelpMe:o) <[EMAIL PROTECTED]> >>> wrote: >>> >>>> >>>> I upgraded my client libraries, but couldn't get past this error. >>>> Will try >>>> again tonight, maybe i missed something. Shouldn't i really just >>>> need the >>>> library that contains this, and not have to modify old client code? >>>> >>>> JB >>>> >>>> >>>> rajdavies wrote: >>>>> >>>>> ok - looks like a version mismatch - can you upgrade your clients >>>>> too ? >>>>> On 11 Jun 2008, at 02:04, pleaseHelpMe:o) wrote: >>>>> >>>>>> >>>>>> I upgraded to 5.1, now my client reports this and won't connect. >>>>>> Will >>>>>> investigate, but if anybody knows this error, please advise. >>>>>> >>>>>> Exception in thread "ActiveMQ Transport: tcp:///192.168.1.101:61616" >>>>>> java.lang.IllegalArgumentException: Invalid version: 3, could not >>>>>> load >>>>>> org.apache.activemq.openwire.v3.MarshallerFactory >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq.openwire.OpenWireFormat.setVersion(OpenWireFormat.java: >>>>>> 329) >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq >>>>>> .openwire.OpenWireFormat.renegociatWireFormat(OpenWireFormat.java: >>>>>> 569) >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq >>>>>> .transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java: >>>>>> 108) >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq >>>>>> .transport.InactivityMonitor.onCommand(InactivityMonitor.java:122) >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq >>>>>> .transport.TransportSupport.doConsume(TransportSupport.java: >>>>>> 87) >>>>>> at >>>>>> org >>>>>> .apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java: >>>>>> 127) >>>>>> at java.lang.Thread.run(Thread.java:595) >>>>>> Caused by: java.lang.ClassNotFoundException: >>>>>> org.apache.activemq.openwire.v3.MarshallerFactory >>>>>> at >>>>>> org.apache.activemq.util.ClassLoading.loadClass(ClassLoading.java: >>>>>> 104) >>>>>> at >>>>>> org >>>>>> .apache >>>>>> .activemq.openwire.OpenWireFormat.setVersion(OpenWireFormat.java: >>>>>> 327) >>>>>> ... 6 more >>>>>> >>>>>> >>>>>> >>>>>> rajdavies wrote: >>>>>>> >>>>>>> Hi Jason, >>>>>>> >>>>>>> this will work on ActiveMQ 5.x - I suggest you upgrade >>>>>>> >>>>>>> cheers, >>>>>>> >>>>>>> Rob >>>>>>> >>>>>>> On 10 Jun 2008, at 03:58, pleaseHelpMe:o) >>>>>>> <[EMAIL PROTECTED]> >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> I tried this but no luck, is it the way my client connects to >>>>>>>> broker1, then >>>>>>>> if broker1 dies, the client disconnects? >>>>>>>> >>>>>>>> <networkConnector name="jason cluster" >>>>>>>> uri="static://(tcp://localhost:61617,tcp://localhost:61618)" >>>>>>>> failover="true" >>>>>>>> dynamicOnly="true" networkTTL="3"/> >>>>>>>> >>>>>>>> Should this mean that if broker1 dies, broker2 takes over, so if >>>>>>>> the >>>>>>>> client >>>>>>>> is connected to broker1, he auto connects over to broker2, thus >>>>>>>> the >>>>>>>> client >>>>>>>> stays connected? >>>>>>>> >>>>>>>> I have been searching for an example of how to do this, but no >>>>>>>> luck, >>>>>>>> can >>>>>>>> somebody tell me if my logic is good or bad, and where I can >>>>>>>> find an >>>>>>>> example >>>>>>>> of doing what I am trying to do? Surely it can't be this hard to >>>>>>>> setup to >>>>>>>> work properly, so I must have something configured wrong, and >>>>>>>> don't >>>>>>>> know >>>>>>>> what it is? >>>>>>>> >>>>>>>> JB >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> pleaseHelpMe:o) wrote: >>>>>>>>> >>>>>>>>> What is the syntax for that option to configure? >>>>>>>>> >>>>>>>>> JB >>>>>>>>> >>>>>>>>> navneek wrote: >>>>>>>>>> >>>>>>>>>> Hi, >>>>>>>>>> >>>>>>>>>> It seems you missed to configure DynamicallyIncludedDestination >>>>>>>>>> attribute >>>>>>>>>> in your network connector configuration. >>>>>>>>>> Add this attribute and try again. >>>>>>>>>> >>>>>>>>>> regds >>>>>>>>>> Nava. >>>>>>>>>> >>>>>>>>>> pleaseHelpMe:o) wrote: >>>>>>>>>>> >>>>>>>>>>> Here is the setup: >>>>>>>>>>> ActiveMQ 4.0.2 (I know it's old, but need to try to get it >>>>>>>>>>> working >>>>>>>>>>> before upgrading, seems backwards logic, but short on time) >>>>>>>>>>> >>>>>>>>>>> 4 brokers running locally on a Windows machine, Java code >>>>>>>>>>> connecting to >>>>>>>>>>> brokers, i.e. connect to transport with this code from java: >>>>>>>>>>> props.setProperty(Context.PROVIDER_URL,"tcp://localhost: >>>>>>>>>>> 61616"); >>>>>>>>>>> this connection works great and everything is fine, but I >>>>>>>>>>> want to >>>>>>>>>>> provide redundancy if this connection were to fail, so I am >>>>>>>>>>> trying >>>>>>>>>>> this..... >>>>>>>>>>> >>>>>>>>>>> in xml config for brokers, I want to provide a network of >>>>>>>>>>> brokers >>>>>>>>>>> that >>>>>>>>>>> can work as a cluster, or will work if 1 fails. My preference >>>>>>>>>>> would be >>>>>>>>>>> to randomly connect to 1 of the brokers in the network, and >>>>>>>>>>> failover to >>>>>>>>>>> any other 1 if possible. It appears I have hardcoded >>>>>>>>>>> connection >>>>>>>>>>> to this >>>>>>>>>>> 1, so not sure how to randomly connect, unless I modify my java >>>>>>>>>>> code to >>>>>>>>>>> randomly connect (is this the best approach?). >>>>>>>>>>> >>>>>>>>>>> When I do connect to the 61616 port on localhost, I have >>>>>>>>>>> configured >>>>>>>>>>> networkConnector to other ports statically. My log shows this >>>>>>>>>>> when >>>>>>>>>>> starting up brokers. >>>>>>>>>>> ACTIVEMQ_HOME: C:\DIVAS Snapshot\activemq-4.0.2 Broker1\bin\.. >>>>>>>>>>> Loading message broker from: xbean:activemq.xml >>>>>>>>>>> INFO BrokerService - ActiveMQ 4.0.2 JMS >>>>>>>>>>> Message >>>>>>>>>>> Broker >>>>>>>>>>> (broker >>>>>>>>>>> 1) is starting >>>>>>>>>>> INFO BrokerService - For help or more >>>>>>>>>>> information >>>>>>>>>>> please see: >>>>>>>>>>> http://incubator.apache.org/activemq/ >>>>>>>>>>> INFO TransportServerThreadSupport - Listening for >>>>>>>>>>> connections >>>>>>>>>>> at: >>>>>>>>>>> tcp://MAVS0 >>>>>>>>>>> 1:61616?connectionTimeout=0 >>>>>>>>>>> INFO TransportConnector - Connector default >>>>>>>>>>> Started >>>>>>>>>>> INFO NetworkConnector - Establishing network >>>>>>>>>>> connection >>>>>>>>>>> between f >>>>>>>>>>> rom vm://broker1?network=true to >>>>>>>>>>> failover:(tcp://localhost:61617)?maxReconnectDelay >>>>>>>>>>> =1000 >>>>>>>>>>> INFO TransportConnector - Connector vm://broker1 >>>>>>>>>>> Started >>>>>>>>>>> INFO NetworkConnector - Establishing network >>>>>>>>>>> connection >>>>>>>>>>> between f >>>>>>>>>>> rom vm://broker1?network=true to >>>>>>>>>>> failover:(tcp://localhost:61618)?maxReconnectDelay >>>>>>>>>>> =1000 >>>>>>>>>>> INFO NetworkConnector - Establishing network >>>>>>>>>>> connection >>>>>>>>>>> between f >>>>>>>>>>> rom vm://broker1?network=true to >>>>>>>>>>> failover:(tcp://localhost:61619)?maxReconnectDelay >>>>>>>>>>> =1000 >>>>>>>>>>> INFO NetworkConnector - Network Connector host1 >>>>>>>>>>> and host2 >>>>>>>>>>> and hos >>>>>>>>>>> t3 and host4 and host5 and host6 and host7 Started >>>>>>>>>>> INFO BrokerService - ActiveMQ JMS Message >>>>>>>>>>> Broker >>>>>>>>>>> (broker1, ID: >>>>>>>>>>> localhost-3643-1212949248389-0:0) started >>>>>>>>>>> INFO DemandForwardingBridge - Network connection >>>>>>>>>>> between >>>>>>>>>>> vm://broker1#0 >>>>>>>>>>> and tcp://localhost:61617(broker2) has been established. >>>>>>>>>>> INFO DemandForwardingBridge - Network connection >>>>>>>>>>> between >>>>>>>>>>> vm://broker1#4 >>>>>>>>>>> and tcp://localhost:61619(broker4) has been established. >>>>>>>>>>> INFO DemandForwardingBridge - Network connection >>>>>>>>>>> between >>>>>>>>>>> vm://broker1#2 >>>>>>>>>>> and tcp://localhost:61618(Unknown) has been established. >>>>>>>>>>> >>>>>>>>>>> So it appears connections seem good, but....if I kill >>>>>>>>>>> broker1, my >>>>>>>>>>> java >>>>>>>>>>> client reports The session is closed. Below is my config file, >>>>>>>>>>> anything >>>>>>>>>>> I am missing with this logic or implementation? >>>>>>>>>>> >>>>>>>>>>> <transportConnector name="default" >>>>>>>>>>> uri="tcp://localhost:61616?connectionTimeout=0" /> >>>>>>>>>>> >>>>>>>>>>> <networkConnector name="host1 and host2" >>>>>>>>>>> uri="static://(tcp://localhost:61617,tcp://localhost:61618" >>>>>>>>>>> failover="true"/> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Any help would be greatly appreciated, I am trying to run a >>>>>>>>>>> test >>>>>>>>>>> where I >>>>>>>>>>> close broker1, and broker 2 will maintain the connection to the >>>>>>>>>>> client. >>>>>>>>>>> I would also like to understand how to randomly connect to 1 or >>>>>>>>>>> the >>>>>>>>>>> other from my client? Do I do this in client code or is >>>>>>>>>>> there a >>>>>>>>>>> way to >>>>>>>>>>> configure it in ActiveMQ? >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> View this message in context: >>>>>>>> http://www.nabble.com/Networking-help%2C-not-working-for-me....-tp17721624p17746763.html >>>>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://www.nabble.com/Networking-help%2C-not-working-for-me....-tp17721624p17768019.html >>>>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/Networking-help%2C-not-working-for-me....-tp17721624p17776191.html >>>> Sent from the ActiveMQ - User mailing list archive at Nabble.com. >>>> >>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Networking-help%2C-not-working-for-me....-tp17721624p17792217.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
