hi steve, here i have another snippet of the log:
[DEBUG ] (app.Client1): creating new channel with id: 0 [DEBUG ] (app.net4j.Channel.lifecycle): incarnation [DEBUG ] (app.net4j.Channel.lifecycle): instantiating component with a null constructor DEFAULT CHANNEL CONSTRUCTION: 198cb3d [DEBUG ] (app.net4j.Channel.lifecycle): applying logger [DEBUG ] (app.net4j.Channel.lifecycle): applying service manager [DEBUG ] (app.net4j.Channel.lifecycle): resolved bufferPool: [EMAIL PROTECTED] [DEBUG ] (app.net4j.Channel.lifecycle): resolved multiplexer: [EMAIL PROTECTED] [DEBUG ] (app.net4j.Channel.lifecycle): resolved dispatcher: [EMAIL PROTECTED] [DEBUG ] (app.net4j.Channel.lifecycle): applying initialization [DEBUG ] (app.net4j.Channel.lifecycle): incarnation complete [DEBUG ] (app.net4j.Channel): ====================================================198cb3d [DEBUG ] (app.net4j.Channel): received id: 0 [DEBUG ] (app.net4j.Channel): received connector: CLIENT-0 ... [DEBUG ] (app.Client1): creating new channel with id: 1 [DEBUG ] (app.net4j.Channel): ====================================================198cb3d [DEBUG ] (app.net4j.Channel): received id: 1 [DEBUG ] (app.net4j.Channel): received connector: CLIENT-0 i've logged the hashcode of the channel in the constructor and in setId(). as you can see, when the Client1 creates the second Channel, the constructor is not called. setId() logs the hashcode of the first Channel!!! also this behavious is not predicatble. it occurs every third or fourth run. do you need more infos? /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
