Skip to main content

Bug in TLS messenger?

2 replies [Last post]
vonazor
Offline
Joined: 2007-09-10

Hi.
I'm trying to play round with JXTA 2.5 RC3
My configuration as follows:
Peer A: RDV
Peer B: EDGE
Peer A opens secure input pipe ( InputPipe or JxtaBiDiPipe - doesn't matter)
Peer B connects to A's pipe and send messages.
But once peer A goes down and wakes up, B can not send it no more messages. If B opens non secured pipe, everything is ok - no matter how many times A restarts, B still can send it messages.

On A's side I get following warnings (don't pay attention to log format - it's Log4J wrapper around Java Logging):

2007-09-25 15:22:47,097 WARN [Executor - 3]
- (net.jxta.impl.endpoint.tls.TlsManager:processIncomingMessage) net.jxta.endpoint.Message@16685777(9){151} is not start of handshake (seqn#11) for uuid-5C3AB7653E5B4BF289629254F258FDDD1DA32436403C4F93B4A4E1C07EA6A90903
2007-09-25 15:22:47,107 WARN [Executor - 1]
- (net.jxta.impl.endpoint.tls.TlsManager:processIncomingMessage) net.jxta.endpoint.Message@5691087(9){153} is not start of handshake (seqn#13) for uuid-5C3AB7653E5B4BF289629254F258FDDD1DA32436403C4F93B4A4E1C07EA6A90903

Can it be, that TLS messenger on B side does not detect that it does not have a partner on the other side? I also tried to recreate the output pipe for every message, but the result stays the same - it seems that messanger is cached somewhere?
If it is a bug, where do I report it?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
vonazor
Offline
Joined: 2007-09-10

Response anyone? At least where can I report an issue?

Message was edited by: vonazor

hamada
Offline
Joined: 2003-06-12

It appears to be a bug. You can file an issue under http://jxta-jxse.dev.java.net