Re: [xmlblaster] Annoying Warning about recv failed
Okay, thanks. It's no big deal if no messages are lost. The server is pretty slow since it is a PII 266mhz 192mb of RAM (test server) so I'm not surprised. - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Sunday, January 28, 2007 5:01:20 AM Subject: Re: [xmlblaster] Annoying Warning about recv failed The warning an 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from '/192.168.1.102:4178', check if client and server have identical compression or SSL settings: java.net.socketException: Software caused connection abort: recv failed is emitted when the socket handle throws an exception. It could happen when the client closes the socket very quickly before the server has processed a disconnect. But it can also be a hint for a misbehaving client. If you want to suppress it try the command line (or xmlBlaster.properties entry) -logging/org.xmlBlaster.protocol.socket.HandleClient SEVERE Marcel chris lau wrote: > okay, I did some testing on my webservice. What I found out is really > bizarre. Basically, I stripped the webservice down to a simple > connect as in the following code: > > I_XmlBlasterAccess con = null; > Global glob = null; > > try { > glob = new Global(); > > con = glob.getXmlBlasterAccess(); > > ConnectQos qos = new ConnectQos(glob); > qos.setSessionName(new SessionName(glob, "test_publisher")); > > System.out.println ("Connecting"); > con.connect(qos, null); > > } catch (XmlBlasterException e) { > } finally { > System.out.println ("Disconnecting"); > > try { Thread.sleep(1000); } catch (InterruptedException e) {} > > if (con != null) { > if (con.isConnected()) >con.disconnect(new DisconnectQos(glob)); > } > } > > In the finally section, I upped the sleep time to 5000 instead of 1000 so I > could tell when the disconnect would happen and when the recv-failed message > appeared. It looks like the recv-failed message appears on disconnect. So to > confirm this, I commented out the disconnect and the message doesn't appear > after the client quits. I did this a few times to confirm. > > I then added another Thread.sleep command of 5 seconds right after the > disconnect so I could confirm that it was the disconnect command causing this > warning. After looking at the blaster console I was able to count 5 seconds, > then the recv-failed message appears, then counted another 5 seconds, and my > client program resumes from it's call to the webservice. > > Is there anyway I coded the disconnect call wrong? > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
The warning an 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from '/192.168.1.102:4178', check if client and server have identical compression or SSL settings: java.net.socketException: Software caused connection abort: recv failed is emitted when the socket handle throws an exception. It could happen when the client closes the socket very quickly before the server has processed a disconnect. But it can also be a hint for a misbehaving client. If you want to suppress it try the command line (or xmlBlaster.properties entry) -logging/org.xmlBlaster.protocol.socket.HandleClient SEVERE Marcel chris lau wrote: okay, I did some testing on my webservice. What I found out is really bizarre. Basically, I stripped the webservice down to a simple connect as in the following code: I_XmlBlasterAccess con = null; Global glob = null; try { glob = new Global(); con = glob.getXmlBlasterAccess(); ConnectQos qos = new ConnectQos(glob); qos.setSessionName(new SessionName(glob, "test_publisher")); System.out.println ("Connecting"); con.connect(qos, null); } catch (XmlBlasterException e) { } finally { System.out.println ("Disconnecting"); try { Thread.sleep(1000); } catch (InterruptedException e) {} if (con != null) { if (con.isConnected()) con.disconnect(new DisconnectQos(glob)); } } In the finally section, I upped the sleep time to 5000 instead of 1000 so I could tell when the disconnect would happen and when the recv-failed message appeared. It looks like the recv-failed message appears on disconnect. So to confirm this, I commented out the disconnect and the message doesn't appear after the client quits. I did this a few times to confirm. I then added another Thread.sleep command of 5 seconds right after the disconnect so I could confirm that it was the disconnect command causing this warning. After looking at the blaster console I was able to count 5 seconds, then the recv-failed message appears, then counted another 5 seconds, and my client program resumes from it's call to the webservice. Is there anyway I coded the disconnect call wrong? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
okay, I did some testing on my webservice. What I found out is really bizarre. Basically, I stripped the webservice down to a simple connect as in the following code: I_XmlBlasterAccess con = null; Global glob = null; try { glob = new Global(); con = glob.getXmlBlasterAccess(); ConnectQos qos = new ConnectQos(glob); qos.setSessionName(new SessionName(glob, "test_publisher")); System.out.println ("Connecting"); con.connect(qos, null); } catch (XmlBlasterException e) { } finally { System.out.println ("Disconnecting"); try { Thread.sleep(1000); } catch (InterruptedException e) {} if (con != null) { if (con.isConnected()) con.disconnect(new DisconnectQos(glob)); } } In the finally section, I upped the sleep time to 5000 instead of 1000 so I could tell when the disconnect would happen and when the recv-failed message appeared. It looks like the recv-failed message appears on disconnect. So to confirm this, I commented out the disconnect and the message doesn't appear after the client quits. I did this a few times to confirm. I then added another Thread.sleep command of 5 seconds right after the disconnect so I could confirm that it was the disconnect command causing this warning. After looking at the blaster console I was able to count 5 seconds, then the recv-failed message appears, then counted another 5 seconds, and my client program resumes from it's call to the webservice. Is there anyway I coded the disconnect call wrong? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
Hi Marcel, I originally started out trying to port the java applet to c#, but I ran into some problems and abandoned it.. (my programming skills are limited.. ha ha). Anyway, the webservice is a good option for me because the client (written in any language) does not need to know anything about the underlying messaging system just the appropriate calls to the webservice. Hence, I could use Java and C# together and not care about including the proper xmlblaster libraries. Also, the c# client has callback capabilities. It is basically a fire-and-forget type of call to the webservice. When the result is returned, a method is called on the c# client program that passes the data from the webservice (similar to the xmlblaster update method). I did some testing and found that my work computer (a p4 3ghz with 1gb ram) doesn't throw these recv failed warnings as much (about once every 20 or so messages) as my test server. My test server is an antiquated p2 266mhz with 192mb of ram and a 4 gig hard drive :-) The only difference between these two machines (besides the hardware) is the test server is running java 1.5 update 10 and my work computer is running java 1.5 update 6. All other software is the same. - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Wednesday, January 24, 2007 8:28:03 AM Subject: Re: [xmlblaster] Annoying Warning about recv failed Hi Chris, i couldn't follow all of it :-) I can offer our native C# wrapper (calling the C client lib) which connects over the SOCKET protocol and tunnels callbacks back (compressed with zlib:stream) in real time. It works very well on Windows, Windows CE (Smartphone/PocketPC/Mobile) and on Linux/mono. If it is only the port which counts you can put the xmlBlaster server on port 80, but if it must be http traffic this wont help. Further you can use some of our servlets and look at the (tiny) applet code how to talk to them. Then implement the same client code in C#. Finally your approach sounds nice as well, but as you don't have a callback possibility you need to poll from C# (which is not too problematic on low traffic). Marcel __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
Hi Chris, i couldn't follow all of it :-) I can offer our native C# wrapper (calling the C client lib) which connects over the SOCKET protocol and tunnels callbacks back (compressed with zlib:stream) in real time. It works very well on Windows, Windows CE (Smartphone/PocketPC/Mobile) and on Linux/mono. If it is only the port which counts you can put the xmlBlaster server on port 80, but if it must be http traffic this wont help. Further you can use some of our servlets and look at the (tiny) applet code how to talk to them. Then implement the same client code in C#. Finally your approach sounds nice as well, but as you don't have a callback possibility you need to poll from C# (which is not too problematic on low traffic). Marcel chris lau wrote: Yes, I think that is it. Basically, my webservice, which started out simple, turned out to be a nightmare simply because the webservice is oblivious to the client state (crashed, disconnected, connected). It just happily waits for a message to arrive and return it back to a client that may not be there. Hence, my solution was for the webservice to spawn a new thread at startup that publishes status messages to the queue every minute or so. These status message get returned to the client and when this happens, it reconnects to the webservice and the process starts all over again. So basically, there are 2 threads, one subscribed and the other publishing status messages. You may be thinking that there is a possibility of lost messages when the client crashes in between status messages and a real message arrives in the queue. Well, the webservice only passes the real message back to the client when instructed to do so. When the webservice gets a real message, it will consume it, inspect it for certain conditions, and republish it back to the same queue. It will then return a status back to the client indicating that a message has arrived. The client, if it is there, will call the webservice again to get the message. If the client has crashed, well, the message is still in the queue and when the client comes back online, the first thing it does is get any outstanding messages. It is complicated, but it works. If you have any suggestions on how to get around this with a C# frontend and a java back end that communicates strictly through port 80 or 443, then please let me know!!! Anyway, I believe it is the thread that publishes the status messages that is causing the problem because I'm connecting with the same client name as the other thread that is subscribed to the queue. I will have to confirm this when I get the chance later on tonight. I will let you know. - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Tuesday, January 23, 2007 1:36:09 PM Subject: Re: [xmlblaster] Annoying Warning about recv failed If you use a positive session id like "client/joe/session/1" (or "joe/1") you MUST assure that only such client exists, if by mistake two of them get alive they will throw each other out of the server ... Could it be such a behaviour? regards Marcel chris lau wrote: hmm... your points have me thinking Marcel. The chain is correct. The client only sends data to the web service. The data determines what the webservice does. It is the webservice that connects, publishes, retrieves and returns data to the client. Messages are published in PTP mode. 1. I have will have to test. 2. It is only the webservice that talks to the blaster server. Nobody else. 3. This has me thinking that I forgot to close the connection to the server before exiting? - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Tuesday, January 23, 2007 3:18:42 AM Subject: Re: [xmlblaster] Annoying Warning about recv failed Hi Chris, i assume this chain: Client C# SOAP/SSL> servlet : java xmlBlaster client -SOCKET---> xmlBlaster server Your problem is that the java client looses connection to the server. The exception tells me that the SOCKET connection will be shutdown. As your publish arrives there must be a reconnect behind the scene. I'm quite sure that your java xmlBlaster client has some coding problem or it is another client showing the behaviour. 1. Try to test you client 'standalone' outside of tomcat 2. Who does the reconnect after your lost connection? 3. Can you switch on detailed logging inside tomcat showing the xmlBlaster client lifecycle? thanks Marcel chris lau wrote: Hi, Recently, I moved from a pure Java client to a C# .Net 1.1 client. This meant that I had to stop using the xmlblasterappletlib.jar servlet and write my own webservice. Everything is working fine except that I get these annoying java.net.socketexception warnings in the xmlBlaster server console. I don't know why I'm getting these warni
Re: [xmlblaster] Annoying Warning about recv failed
Yes, I think that is it. Basically, my webservice, which started out simple, turned out to be a nightmare simply because the webservice is oblivious to the client state (crashed, disconnected, connected). It just happily waits for a message to arrive and return it back to a client that may not be there. Hence, my solution was for the webservice to spawn a new thread at startup that publishes status messages to the queue every minute or so. These status message get returned to the client and when this happens, it reconnects to the webservice and the process starts all over again. So basically, there are 2 threads, one subscribed and the other publishing status messages. You may be thinking that there is a possibility of lost messages when the client crashes in between status messages and a real message arrives in the queue. Well, the webservice only passes the real message back to the client when instructed to do so. When the webservice gets a real message, it will consume it, inspect it for certain conditions, and republish it back to the same queue. It will then return a status back to the client indicating that a message has arrived. The client, if it is there, will call the webservice again to get the message. If the client has crashed, well, the message is still in the queue and when the client comes back online, the first thing it does is get any outstanding messages. It is complicated, but it works. If you have any suggestions on how to get around this with a C# frontend and a java back end that communicates strictly through port 80 or 443, then please let me know!!! Anyway, I believe it is the thread that publishes the status messages that is causing the problem because I'm connecting with the same client name as the other thread that is subscribed to the queue. I will have to confirm this when I get the chance later on tonight. I will let you know. - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Tuesday, January 23, 2007 1:36:09 PM Subject: Re: [xmlblaster] Annoying Warning about recv failed If you use a positive session id like "client/joe/session/1" (or "joe/1") you MUST assure that only such client exists, if by mistake two of them get alive they will throw each other out of the server ... Could it be such a behaviour? regards Marcel chris lau wrote: > hmm... your points have me thinking Marcel. > > The chain is correct. The client only sends data to the web service. The data > determines what the webservice does. > It is the webservice that connects, publishes, retrieves and returns data to > the client. Messages are published in PTP mode. > > 1. I have will have to test. > 2. It is only the webservice that talks to the blaster server. Nobody else. > 3. This has me thinking that I forgot to close the connection to the server > before exiting? > > > - Original Message > From: Marcel Ruff <[EMAIL PROTECTED]> > To: xmlblaster@server.xmlBlaster.org > Sent: Tuesday, January 23, 2007 3:18:42 AM > Subject: Re: [xmlblaster] Annoying Warning about recv failed > > Hi Chris, > > i assume this chain: > > Client C# SOAP/SSL> servlet : java xmlBlaster client > -SOCKET---> xmlBlaster server > > Your problem is that the java client looses connection to the > server. > > The exception tells me that the SOCKET connection will be shutdown. > As your publish arrives there must be a reconnect behind the scene. > > I'm quite sure that your java xmlBlaster client has some coding problem > or it is another client showing the behaviour. > > 1. Try to test you client 'standalone' outside of tomcat > 2. Who does the reconnect after your lost connection? > 3. Can you switch on detailed logging inside tomcat showing the > xmlBlaster client lifecycle? > > thanks > Marcel > > > chris lau wrote: > >> Hi, >> >> Recently, I moved from a pure Java client to a C# .Net 1.1 client. This >> meant that I had to stop using the xmlblasterappletlib.jar servlet and write >> my own webservice. Everything is working fine except that I get these >> annoying java.net.socketexception warnings in the xmlBlaster server console. >> I don't know why I'm getting these warnings because it doesn't really effect >> the operation of the client or server (ie. no messages lost or anything). >> >> The message is: >> Jan 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 >> org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from >> '/192.168.1.102:4178', check if client and server have identical compression >> or SSL settings: java.net.socketException: Software caused connection abort: >> re
Re: [xmlblaster] Annoying Warning about recv failed
If you use a positive session id like "client/joe/session/1" (or "joe/1") you MUST assure that only such client exists, if by mistake two of them get alive they will throw each other out of the server ... Could it be such a behaviour? regards Marcel chris lau wrote: hmm... your points have me thinking Marcel. The chain is correct. The client only sends data to the web service. The data determines what the webservice does. It is the webservice that connects, publishes, retrieves and returns data to the client. Messages are published in PTP mode. 1. I have will have to test. 2. It is only the webservice that talks to the blaster server. Nobody else. 3. This has me thinking that I forgot to close the connection to the server before exiting? - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Tuesday, January 23, 2007 3:18:42 AM Subject: Re: [xmlblaster] Annoying Warning about recv failed Hi Chris, i assume this chain: Client C# SOAP/SSL> servlet : java xmlBlaster client -SOCKET---> xmlBlaster server Your problem is that the java client looses connection to the server. The exception tells me that the SOCKET connection will be shutdown. As your publish arrives there must be a reconnect behind the scene. I'm quite sure that your java xmlBlaster client has some coding problem or it is another client showing the behaviour. 1. Try to test you client 'standalone' outside of tomcat 2. Who does the reconnect after your lost connection? 3. Can you switch on detailed logging inside tomcat showing the xmlBlaster client lifecycle? thanks Marcel chris lau wrote: Hi, Recently, I moved from a pure Java client to a C# .Net 1.1 client. This meant that I had to stop using the xmlblasterappletlib.jar servlet and write my own webservice. Everything is working fine except that I get these annoying java.net.socketexception warnings in the xmlBlaster server console. I don't know why I'm getting these warnings because it doesn't really effect the operation of the client or server (ie. no messages lost or anything). The message is: Jan 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from '/192.168.1.102:4178', check if client and server have identical compression or SSL settings: java.net.socketException: Software caused connection abort: recv failed So everytime the client publishes a message to the server, I get the above warning on the console. The message reaches it's destination without any problems. Some other relevant details are: 1. Server machine is running Windows XP SP2. 2. Running Apache Tomcat 5.5.15 with a single webservice developed on Netbeans 5.5 3. xmlBlaster 1.4 release. (no cvs versions). 4. webservice and xmlBlaster are on the same machine. 5. Client connects to webservice via SSL, but communication between webservice and xmlBlaster is not using SSL. Actually, I turned of the SSL between the client and webservice and I still get the same message. I don't know. I'm lost. Is it some property that I didn't configure properly or is it something in my code that I didn't do right? Or is it something to do with Tomcat? Any help would be appreciated. Chris. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
hmm... your points have me thinking Marcel. The chain is correct. The client only sends data to the web service. The data determines what the webservice does. It is the webservice that connects, publishes, retrieves and returns data to the client. Messages are published in PTP mode. 1. I have will have to test. 2. It is only the webservice that talks to the blaster server. Nobody else. 3. This has me thinking that I forgot to close the connection to the server before exiting? - Original Message From: Marcel Ruff <[EMAIL PROTECTED]> To: xmlblaster@server.xmlBlaster.org Sent: Tuesday, January 23, 2007 3:18:42 AM Subject: Re: [xmlblaster] Annoying Warning about recv failed Hi Chris, i assume this chain: Client C# SOAP/SSL> servlet : java xmlBlaster client -SOCKET---> xmlBlaster server Your problem is that the java client looses connection to the server. The exception tells me that the SOCKET connection will be shutdown. As your publish arrives there must be a reconnect behind the scene. I'm quite sure that your java xmlBlaster client has some coding problem or it is another client showing the behaviour. 1. Try to test you client 'standalone' outside of tomcat 2. Who does the reconnect after your lost connection? 3. Can you switch on detailed logging inside tomcat showing the xmlBlaster client lifecycle? thanks Marcel chris lau wrote: > Hi, > > Recently, I moved from a pure Java client to a C# .Net 1.1 client. This meant > that I had to stop using the xmlblasterappletlib.jar servlet and write my own > webservice. Everything is working fine except that I get these annoying > java.net.socketexception warnings in the xmlBlaster server console. I don't > know why I'm getting these warnings because it doesn't really effect the > operation of the client or server (ie. no messages lost or anything). > > The message is: > Jan 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 > org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from > '/192.168.1.102:4178', check if client and server have identical compression > or SSL settings: java.net.socketException: Software caused connection abort: > recv failed > > So everytime the client publishes a message to the server, I get the above > warning on the console. The message reaches it's destination without any > problems. > > Some other relevant details are: > 1. Server machine is running Windows XP SP2. > 2. Running Apache Tomcat 5.5.15 with a single webservice developed on > Netbeans 5.5 > 3. xmlBlaster 1.4 release. (no cvs versions). > 4. webservice and xmlBlaster are on the same machine. > 5. Client connects to webservice via SSL, but communication between > webservice and xmlBlaster is not using SSL. Actually, I turned of the SSL > between the client and webservice and I still get the same message. > > I don't know. I'm lost. Is it some property that I didn't configure properly > or is it something in my code that I didn't do right? Or is it something to > do with Tomcat? > > Any help would be appreciated. > > Chris. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: [xmlblaster] Annoying Warning about recv failed
Hi Chris, i assume this chain: Client C# SOAP/SSL> servlet : java xmlBlaster client -SOCKET---> xmlBlaster server Your problem is that the java client looses connection to the server. The exception tells me that the SOCKET connection will be shutdown. As your publish arrives there must be a reconnect behind the scene. I'm quite sure that your java xmlBlaster client has some coding problem or it is another client showing the behaviour. 1. Try to test you client 'standalone' outside of tomcat 2. Who does the reconnect after your lost connection? 3. Can you switch on detailed logging inside tomcat showing the xmlBlaster client lifecycle? thanks Marcel chris lau wrote: Hi, Recently, I moved from a pure Java client to a C# .Net 1.1 client. This meant that I had to stop using the xmlblasterappletlib.jar servlet and write my own webservice. Everything is working fine except that I get these annoying java.net.socketexception warnings in the xmlBlaster server console. I don't know why I'm getting these warnings because it doesn't really effect the operation of the client or server (ie. no messages lost or anything). The message is: Jan 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from '/192.168.1.102:4178', check if client and server have identical compression or SSL settings: java.net.socketException: Software caused connection abort: recv failed So everytime the client publishes a message to the server, I get the above warning on the console. The message reaches it's destination without any problems. Some other relevant details are: 1. Server machine is running Windows XP SP2. 2. Running Apache Tomcat 5.5.15 with a single webservice developed on Netbeans 5.5 3. xmlBlaster 1.4 release. (no cvs versions). 4. webservice and xmlBlaster are on the same machine. 5. Client connects to webservice via SSL, but communication between webservice and xmlBlaster is not using SSL. Actually, I turned of the SSL between the client and webservice and I still get the same message. I don't know. I'm lost. Is it some property that I didn't configure properly or is it something in my code that I didn't do right? Or is it something to do with Tomcat? Any help would be appreciated. Chris. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
[xmlblaster] Annoying Warning about recv failed
Hi, Recently, I moved from a pure Java client to a C# .Net 1.1 client. This meant that I had to stop using the xmlblasterappletlib.jar servlet and write my own webservice. Everything is working fine except that I get these annoying java.net.socketexception warnings in the xmlBlaster server console. I don't know why I'm getting these warnings because it doesn't really effect the operation of the client or server (ie. no messages lost or anything). The message is: Jan 21, 2007 4:29:29 PM WARNING 19-XmlBlaster.SOCKET RL10 org.xmlBlaster.protocol.socket.HandleClient run: Error parsing TCP data from '/192.168.1.102:4178', check if client and server have identical compression or SSL settings: java.net.socketException: Software caused connection abort: recv failed So everytime the client publishes a message to the server, I get the above warning on the console. The message reaches it's destination without any problems. Some other relevant details are: 1. Server machine is running Windows XP SP2. 2. Running Apache Tomcat 5.5.15 with a single webservice developed on Netbeans 5.5 3. xmlBlaster 1.4 release. (no cvs versions). 4. webservice and xmlBlaster are on the same machine. 5. Client connects to webservice via SSL, but communication between webservice and xmlBlaster is not using SSL. Actually, I turned of the SSL between the client and webservice and I still get the same message. I don't know. I'm lost. Is it some property that I didn't configure properly or is it something in my code that I didn't do right? Or is it something to do with Tomcat? Any help would be appreciated. Chris. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com