Re: Duplex and network fault.

2010-07-22 Thread Eric-AWL
: (DUPLEX back) Link from >>>>>>> SIBBusModule >>>>>>> TestDeCharge(Client) to SIBBusSupervisor port 61601, broken >>>>>>> 2010-07-19 14:00:23,733 [isor-td0sib01s]] INFO >>>>>>> DemandForwardingBridge >>>

Re: Duplex and network fault.

2010-07-21 Thread Eric-AWL
SIBBusSupervisor >>>>>> port >>>>>> 61601 >>>>>> 2010-07-19 14:00:55,920 [0.29.12.1:33840] INFO TransportConnection >>>>>> >>>>>> - Created Duplex Bridge back to SIBBusModule-TestDeCharge-td0sib01

Re: Duplex and network fault.

2010-07-21 Thread Rob Davies
n between vm://SIBBusSupervisor-td0sib01s#22 and >>>>> tcp:///10.29.12.1:33840(SIBBusModule-TestDeCharge-td0sib01v) has been >>>>> established. >>>>> >>>>> STOP Old DUPLEX back Connection >>>>> >>>>> Lin

Re: Duplex and network fault.

2010-07-21 Thread Eric-AWL
own due to a remote error: >>>> org.apache.activemq.transport.InactivityIOException: Channel was >>>> inactive >>>> for too long: /10.29.12.1:36485 >>>> 2010-07-19 14:00:58,945 [0.29.12.1:36485] INFO DemandForwardingBridge >>>>

Re: Duplex and network fault.

2010-07-21 Thread Eric-AWL
dule-TestDeCharge-td0sib01v >>> stopped >>> >>> >>> It seems that bridge on Link 1 is finally broken ??? >>> >>> Eric-AWL >>> >>> >>> Eric-AWL wrote: >>>> >>>> Hi >>>> >&

Re: Duplex and network fault.

2010-07-21 Thread Rob Davies
wn() call on this latch at the end of the stop() method >>> - correctly managing an exception to alert the discovery connector that >>> the bridge was disposed during the start call. >>> >>> Now, I think that I have a problem on the other side with this >>> configuration. >>> T0 - A duplex connection is correctly >>> established >>> T0+X minutes- the network is down, the duplex bridge >>> back is stopped, but the corresponding transport (back) connection seems >>> not to be closed >>> T0+X minutes + x ms - the networl is up : a new transport >>> connection want to be established and is established >>> T0+X minutes + y seconds - the transport inactivity thread closes the >>> old transport connection >>> >>> (y seconds >> x milliseconds) >>> >>> All seems Ok, but no message are exchanged with this bridge. >>> >>> Eric-AWL >>> >> >> > > -- > View this message in context: > http://old.nabble.com/Duplex-and-network-fault.-tp29205793p29223448.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >

Re: Duplex and network fault.

2010-07-21 Thread Eric-AWL
> back is stopped, but the corresponding transport (back) connection seems >> not to be closed >> T0+X minutes + x ms - the networl is up : a new transport >> connection want to be established and is established >> T0+X minutes + y seconds - the transport inactivity thread closes the >> old transport connection >> >> (y seconds >> x milliseconds) >> >> All seems Ok, but no message are exchanged with this bridge. >> >> Eric-AWL >> > > -- View this message in context: http://old.nabble.com/Duplex-and-network-fault.-tp29205793p29223448.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Duplex and network fault.

2010-07-20 Thread Eric-AWL
0+X minutes + y seconds - the transport inactivity thread closes the > old transport connection > > (y seconds >> x milliseconds) > > All seems Ok, but no message are exchanged with this bridge. > > Eric-AWL > -- View this message in context: http://old

Duplex and network fault.

2010-07-19 Thread Eric-AWL
minutes + y seconds - the transport inactivity thread closes the old transport connection (y seconds >> x milliseconds) All seems Ok, but no message are exchanged with this bridge. Eric-AWL -- View this message in context: http://old.nabble.com/Duplex-and-network-fault.-tp29205793p2