[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-1110) Client incorrectly initiates client-side fail over on high concurrency

Sun Oct 14 00:13:03 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-1110?page=all ]

Ovidiu Feodorov updated JBMESSAGING-1110:
-----------------------------------------

    Priority: Critical  (was: Major)

> Client incorrectly initiates client-side fail over on high concurrency
> ----------------------------------------------------------------------
>
>                 Key: JBMESSAGING-1110
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1110
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Facade
>    Affects Versions: 1.4.0.GA
>            Reporter: Ovidiu Feodorov
>         Assigned To: Tim Fox
>            Priority: Critical
>
> Dump of a faulty test run:
> ofeodorov at yamato$ mess -sessions 50 receive all
> ConnectionFactory: JBossConnectionFactory->ClusteredConnectionFactoryDelegate[SIDs={38,39}]
> Destination: JBossQueue[ovidiu]
> Consumer21 starting to consume ...
> Consumer43 starting to consume ...
> Consumer23 starting to consume ...
> Consumer44 starting to consume ...
> Consumer11 starting to consume ...
> Consumer29 starting to consume ...
> Consumer26 starting to consume ...
> Consumer39 starting to consume ...
> Consumer40 starting to consume ...
> Consumer01 starting to consume ...
> Consumer17 starting to consume ...
> Consumer14 starting to consume ...
> Consumer04 starting to consume ...
> Consumer16 starting to consume ...
> Consumer49 starting to consume ...
> Consumer42 starting to consume ...
> Consumer41 starting to consume ...
> Consumer34 starting to consume ...
> Consumer18 starting to consume ...
> Consumer46 starting to consume ...
> Consumer20 starting to consume ...
> Consumer02 starting to consume ...
> Consumer06 starting to consume ...
> Consumer32 starting to consume ...
> Consumer07 starting to consume ...
> Consumer19 starting to consume ...
> Consumer35 starting to consume ...
> Consumer48 starting to consume ...
> Consumer24 starting to consume ...
> Consumer30 starting to consume ...
> Consumer08 starting to consume ...
> Consumer12 starting to consume ...
> Consumer36 starting to consume ...
> Consumer09 starting to consume ...
> Consumer47 starting to consume ...
> Consumer00 starting to consume ...
> Consumer13 starting to consume ...
> Consumer31 starting to consume ...
> Consumer27 starting to consume ...
> Consumer33 starting to consume ...
> Consumer10 starting to consume ...
> Consumer05 starting to consume ...
> Consumer45 starting to consume ...
> Consumer15 starting to consume ...
> Consumer03 starting to consume ...
> Consumer37 starting to consume ...
> Consumer28 starting to consume ...
> Consumer38 starting to consume ...
> Consumer22 starting to consume ...
> Consumer30 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer33 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer22 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer32 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer31 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer10 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer09 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer34 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer12 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer38 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer24 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer15 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer13 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer29 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer36 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer16 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer41 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer14 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer26 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer19 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer08 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer07 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer23 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer11 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer18 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer00 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer03 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer02 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer27 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer05 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer20 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer04 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer45 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer48 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer06 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer47 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer43 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer46 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer44 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer42 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer17 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer39 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> Consumer49 doesn't get any more messages, exiting after a timeout of 3000 ms ...
> @Consumer25 18:11:31,474 WARN  [ClusteringAspect] Client attempted failover, but no failover attempt has been detected on the server side. We will now try again on the original server in case there was a temporary glitch on the client--server network
> closing connection JBossConnection->ConnectionDelegate[1572973638, ID=yc-2wk3vq7f-1-6ii5qq7f-onm5l5-31184a, SID=39] on exit ...
> @Timer-1 18:16:58,969 WARN  [BisocketServerInvoker] org.jboss.remoting.transport.bisocket.BisocketServerInvoker$ControlMonitorTimerTask at 11dba9f9: detected failure on control connection Thread[control: Socket[addr=/10.152.1.39,port=3309,localport=50826],5,main] (a4812d-tafka6-f7qv26rw-1-f7qv3kvq-o: requesting new control connection

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira