dcsimg
Bridge Swiftlet dies with Sybase EAServer.
1 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   Nathan_Phelps
Posted On:   Wednesday, March 20, 2002 08:20 AM

When I try and use the bridge swiftlet with Sybase EAServer 4.1 it works great if I'm doing a remote_to_local bridging, however, if I try and do a local_to_remote it simply crashes the bridge whenever I send a message. Here is the section of the log file that details the error: 2002-03-20 10:14:13.284/xt$bridge/INFORMATION/destroy server 'easerver' 2002-03-20 10:14:27.685/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: Socket[addr=localhost/127.0.0.1,port=2545,localport=4001] 2002-03-20 10:14:28.356/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: Socket[addr=65.163.49.25/65.163.49.25,port=2546,localport=4001] 2002-03   More>>

When I try and use the bridge swiftlet with Sybase EAServer 4.1 it works great if I'm doing a remote_to_local bridging, however, if I try and do a local_to_remote it simply crashes the bridge whenever I send a message. Here is the section of the log file that details the error:


2002-03-20 10:14:13.284/xt$bridge/INFORMATION/destroy server 'easerver'

2002-03-20 10:14:27.685/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: Socket[addr=localhost/127.0.0.1,port=2545,localport=4001]

2002-03-20 10:14:28.356/[BlockingTCPListener, swiftlet=sys$jms, port=4001]/Listener/INFORMATION/connection accepted: Socket[addr=65.163.49.25/65.163.49.25,port=2546,localport=4001]

2002-03-20 10:14:28.486/65.163.49.25:2546/BlockingHandler/INFORMATION/Exception, EXITING: java.io.EOFException

2002-03-20 10:14:28.586/localhost:2545/BlockingHandler/INFORMATION/Exception, EXITING: java.net.SocketException: Connection reset by peer: JVM_recv in socket input stream read

   <<Less

Re: Bridge Swiftlet dies with Sybase EAServer.

Posted By:   Andreas_Mueller  
Posted On:   Wednesday, March 20, 2002 02:07 PM

If local_to_remote is the problem then there is probably a problem converting a SwiftMQ message to a Sybase message. Switch the 'swiftlet' trace space on and look what it says.
About | Sitemap | Contact