Re: [xmlblaster] GPRS / Different IP

[Póka Balázs]

Hi!

Sorry for the short addition, but I tested whether messages are passed
normally after reconnection with _no_ IP change, and they do not.
This might be a serious regression (since it had worked a few revisions
back) or I am not familiar with some very recent API changes. :)



The problem is that messages (all are private and transient) are not going
through anymore when the connection is reestabilished. Sending them is not
throwing any exception, either (oneway or not). The connection callback does
not receive anything.

Am I correct to assume that I may use the "old" (pre-IP-change)
XmlBlasterAccess_I instance (I have not connected or disconnected)? What
might be the problem?



regards,
Balázs Póka

Re: [xmlblaster] GPRS / Different IP

[Póka Balázs]

Hi!

Ok, this is now fixed in the current svn,


thanks for your patience

Marcel



I've made a simple manual test consisting of:
- connecting to the XmlBlaster server with a given IP
- reconnect ADSL line so that dynamic IP gets refreshed
- test if everything works

The reconnection does work, but:

Server's log
---
Connecting for the first time:
Jan 24, 2007 3:22:12 AM  INFO
17-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.protocol.socket.HandleClient handleMessage: Client connected,
coming from host=/somenet.216.127 port=4114
Jan 24, 2007 3:22:12 AM  INFO
17-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.util.dispatch.DispatchConnection handleTransition: Connection
'SOCKET' transition UNDEF -> ALIVE: Success,
DispatchConnection-callback:/node/krumpli/client/poka/-3  connected.

Then comes the ping timeout:
... Connection transition ALIVE -> POLLING: socket://192.168.0.10:4114 is
unaccessible ...
(Actually, this callback IP is a private one (NAT) of course, but since the
socket protocol does not need a callback, it doen't matter.)

The reconnection seems ok (notice client different IP):
Jan 24, 2007 3:26:58 AM  INFO
19-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.protocol.socket.HandleClient handleMessage: Client connected,
coming from host=/somenet.216.140 port=4135
Jan 24, 2007 3:26:58 AM  INFO
19-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.authentication.Authenticate connect: Using secretSessionId
'sessionId:192.168.0.252-null-1169605332591-1367373573-4' from ConnectQos
Jan 24, 2007 3:26:58 AM  INFO
19-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.authentication.SessionInfo updateConnectQos:
-3-client/poka/-3: Successfully reconfigured callback address with new
settings, other reconfigurations are not yet implemented
Jan 24, 2007 3:26:58 AM  INFO
19-XmlBlaster.SSLSOCKET.SSL.tcpListener-pokaRL10
org.xmlBlaster.authentication.Authenticate connect: Reconnected with given
secretSessionId.

The problem is that messages (all are private and transient) are not going
through anymore when the connection is reestabilished. Sending them is not
throwing any exception, either (oneway or not). The connection callback does
not receive anything.

Am I correct to assume that I may use the "old" (pre-IP-change)
XmlBlasterAccess_I instance (I have not connected or disconnected)? What
might be the problem?

thanks,
Balázs Póka

Re: [xmlblaster] OSX Testing Errors

[Rizwan Kassim]

Thanks Marcel. We're getting an OSX Server box out to the net soon
that you'll be able to ssh into =). I'll email you directly when it's
up.

-Rizwan

On 1/23/07, Marcel Ruff <[EMAIL PROTECTED]> wrote:

Hi Rizwan,

if you can give me access to your OSX via ssh i can
try to resolve the issue,

regards
Marcel

Rizwan Kassim wrote:
> I'm sorry, I don't fully understand.
>
> I can't do the compilation because of the number of missing symbols -
> when I try to compile directly with
>
> [EMAIL PROTECTED] /opt/xmlBlaster/build.tmp/src/c]$ sudo gcc -Wall
> -pedantic -Wno-long-long -D_REENTRANT  -c -g
> -DXMLBLASTER_PERSISTENT_QUEUE=1 -DXMLBLASTER_ZLIB=1 .
> /opt/xmlblaster/demo/c/socket/Publisher.c
> or with
> [EMAIL PROTECTED] /opt/xmlBlaster]$ sudo gcc -Wall -pedantic
> -Wno-long-long -D_REENTRANT  -c -g -DXMLBLASTER_PERSISTENT_QUEUE=1
> -DXMLBLASTER_ZLIB=1 build.tmp/src/c demo/c/socket/Publisher.c
>
> I get [1].
>
> Even if it did compile fine, I wouldn't know the next steps to
> continue with to finish Build RunTests.
>
> Thoughts?
>
> Thanks,
> Rizwan
>
>
> [1]
> /opt/xmlblaster/demo/c/socket/Publisher.c:15:38: error:
> XmlBlasterAccessUnparsed.h: No such file or directory
> /opt/xmlblaster/demo/c/socket/Publisher.c: In function 'main':
> /opt/xmlblaster/demo/c/socket/Publisher.c:28: error:
> 'XmlBlasterException' undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:28: error: (Each undeclared
> identifier is reported only once
> /opt/xmlblaster/demo/c/socket/Publisher.c:28: error: for each function
> it appears in.)
> /opt/xmlblaster/demo/c/socket/Publisher.c:28: error: parse error
> before 'xmlBlasterException'
> /opt/xmlblaster/demo/c/socket/Publisher.c:29: error:
> 'XmlBlasterAccessUnparsed' undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:29: error: 'xa' undeclared
> (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:30: error: 'bool' undeclared
> (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:30: error: parse error
> before 'disconnect'
> /opt/xmlblaster/demo/c/socket/Publisher.c:35: warning: implicit
> declaration of function 'getXmlBlasterVersion'
> /opt/xmlblaster/demo/c/socket/Publisher.c:35: warning: format '%s'
> expects type 'char *', but argument 2 has type 'int'
> /opt/xmlblaster/demo/c/socket/Publisher.c:39: error:
> 'XMLBLASTER_MAX_USAGE_LEN' undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: implicit
> declaration of function 'xmlBlasterAccessUnparsedUsage'
> /opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: format '%s'
> expects type 'char *', but argument 2 has type 'int'
> /opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: format '%s'
> expects type 'char *', but argument 3 has type 'int'
> /opt/xmlblaster/demo/c/socket/Publisher.c:39: warning: unused variable
> 'usage'
> /opt/xmlblaster/demo/c/socket/Publisher.c:50: warning: implicit
> declaration of function 'getXmlBlasterAccessUnparsed'
> /opt/xmlblaster/demo/c/socket/Publisher.c:51: error:
> 'xmlBlasterException' undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:51: error: 'false'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:54: warning: implicit
> declaration of function 'freeXmlBlasterAccessUnparsed'
> /opt/xmlblaster/demo/c/socket/Publisher.c:58: error: 'disconnect'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:59: error: 'erase'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:65: warning: ISO C forbids
> nested functions
> /opt/xmlblaster/demo/c/socket/Publisher.c:65: error: syntax error
> before 'persistent'
> /opt/xmlblaster/demo/c/socket/Publisher.c:86: error: 'persistent'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:95: warning: implicit
> declaration of function 'xmlBlasterFree'
> /opt/xmlblaster/demo/c/socket/Publisher.c:105: error: parse error
> before 'interactive'
> /opt/xmlblaster/demo/c/socket/Publisher.c:110: error: parse error
> before 'oneway'
> /opt/xmlblaster/demo/c/socket/Publisher.c:116: error: parse error
> before 'persistentPublish'
> /opt/xmlblaster/demo/c/socket/Publisher.c:118: error: parse error
> before 'verbose'
> /opt/xmlblaster/demo/c/socket/Publisher.c:123: error: parse error
> before 'createDomEntry'
> /opt/xmlblaster/demo/c/socket/Publisher.c:126: error: parse error
> before 'forceQueuing'
> /opt/xmlblaster/demo/c/socket/Publisher.c:143: error: 'readonly'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:145: error: 'createDomEntry'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:151: error: 'forceQueuing'
> undeclared (first use in this function)
> /opt/xmlblaster/demo/c/socket/Publisher.c:158: error: 'MsgUnit'
> undeclared (first use in this function)
> /opt/xmlblaster

Re: [xmlblaster] Annoying Warning about recv failed

[chris lau]

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: 
>> 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 sin

Re: [xmlblaster] OSX Testing Errors

[Marcel Ruff]

Hi Rizwan,

if you can give me access to your OSX via ssh i can
try to resolve the issue,

regards
Marcel

Rizwan Kassim wrote:

I'm sorry, I don't fully understand.

I can't do the compilation because of the number of missing symbols -
when I try to compile directly with

[EMAIL PROTECTED] /opt/xmlBlaster/build.tmp/src/c]$ sudo gcc -Wall
-pedantic -Wno-long-long -D_REENTRANT  -c -g
-DXMLBLASTER_PERSISTENT_QUEUE=1 -DXMLBLASTER_ZLIB=1 .
/opt/xmlblaster/demo/c/socket/Publisher.c
or with
[EMAIL PROTECTED] /opt/xmlBlaster]$ sudo gcc -Wall -pedantic
-Wno-long-long -D_REENTRANT  -c -g -DXMLBLASTER_PERSISTENT_QUEUE=1
-DXMLBLASTER_ZLIB=1 build.tmp/src/c demo/c/socket/Publisher.c

I get [1].

Even if it did compile fine, I wouldn't know the next steps to
continue with to finish Build RunTests.

Thoughts?

Thanks,
Rizwan


[1]
/opt/xmlblaster/demo/c/socket/Publisher.c:15:38: error:
XmlBlasterAccessUnparsed.h: No such file or directory
/opt/xmlblaster/demo/c/socket/Publisher.c: In function 'main':
/opt/xmlblaster/demo/c/socket/Publisher.c:28: error:
'XmlBlasterException' undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:28: error: (Each undeclared
identifier is reported only once
/opt/xmlblaster/demo/c/socket/Publisher.c:28: error: for each function
it appears in.)
/opt/xmlblaster/demo/c/socket/Publisher.c:28: error: parse error
before 'xmlBlasterException'
/opt/xmlblaster/demo/c/socket/Publisher.c:29: error:
'XmlBlasterAccessUnparsed' undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:29: error: 'xa' undeclared
(first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:30: error: 'bool' undeclared
(first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:30: error: parse error
before 'disconnect'
/opt/xmlblaster/demo/c/socket/Publisher.c:35: warning: implicit
declaration of function 'getXmlBlasterVersion'
/opt/xmlblaster/demo/c/socket/Publisher.c:35: warning: format '%s'
expects type 'char *', but argument 2 has type 'int'
/opt/xmlblaster/demo/c/socket/Publisher.c:39: error:
'XMLBLASTER_MAX_USAGE_LEN' undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: implicit
declaration of function 'xmlBlasterAccessUnparsedUsage'
/opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: format '%s'
expects type 'char *', but argument 2 has type 'int'
/opt/xmlblaster/demo/c/socket/Publisher.c:45: warning: format '%s'
expects type 'char *', but argument 3 has type 'int'
/opt/xmlblaster/demo/c/socket/Publisher.c:39: warning: unused variable 
'usage'

/opt/xmlblaster/demo/c/socket/Publisher.c:50: warning: implicit
declaration of function 'getXmlBlasterAccessUnparsed'
/opt/xmlblaster/demo/c/socket/Publisher.c:51: error:
'xmlBlasterException' undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:51: error: 'false'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:54: warning: implicit
declaration of function 'freeXmlBlasterAccessUnparsed'
/opt/xmlblaster/demo/c/socket/Publisher.c:58: error: 'disconnect'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:59: error: 'erase'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:65: warning: ISO C forbids
nested functions
/opt/xmlblaster/demo/c/socket/Publisher.c:65: error: syntax error
before 'persistent'
/opt/xmlblaster/demo/c/socket/Publisher.c:86: error: 'persistent'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:95: warning: implicit
declaration of function 'xmlBlasterFree'
/opt/xmlblaster/demo/c/socket/Publisher.c:105: error: parse error
before 'interactive'
/opt/xmlblaster/demo/c/socket/Publisher.c:110: error: parse error
before 'oneway'
/opt/xmlblaster/demo/c/socket/Publisher.c:116: error: parse error
before 'persistentPublish'
/opt/xmlblaster/demo/c/socket/Publisher.c:118: error: parse error
before 'verbose'
/opt/xmlblaster/demo/c/socket/Publisher.c:123: error: parse error
before 'createDomEntry'
/opt/xmlblaster/demo/c/socket/Publisher.c:126: error: parse error
before 'forceQueuing'
/opt/xmlblaster/demo/c/socket/Publisher.c:143: error: 'readonly'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:145: error: 'createDomEntry'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:151: error: 'forceQueuing'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:158: error: 'MsgUnit'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:158: error: parse error
before 'msgUnit'
/opt/xmlblaster/demo/c/socket/Publisher.c:159: error: 'msgUnit'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:161: error: 'interactive'
undeclared (first use in this function)
/opt/xmlblaster/demo/c/socket/Publisher.c:169: warning: implicit
declaration of function 'sleepMillis'
/opt/xmlb

Re: [xmlblaster] GPRS / Different IP

[Marcel Ruff]

Ok, this is now fixed in the current svn,

thanks for your patience

Marcel

Marcel Ruff wrote:

Ok,

thanks for the details!

I will try the case of changing client side IP address with a java client
as soon as i find time for it and come back to this issue,

thanks for reporting,
Marcel


Matthew Monson wrote:

Hi Marcel,

On 11/28/06, *Marcel Ruff* <[EMAIL PROTECTED] 
> wrote:


Hi,

Matthew Monson wrote:
> Hello,
>
> I'm using xmlBlaster for a GPRS receipting solution
> which provides the end user with the ability to issue
> prepaid electricity tokens to a consumer.
> The message server is running at the local municipality
> and so is the server providing the token numbers.
>
> My problem is that every now and again the GPRS connection
> drops and the client needs to redial the GSM modem and
> establish a connection back to VodacomISP, whereby getting
> a brand new IP address. Unfortunately the client cannot
> reconnect to the message server unless I exit the application
> and go back in, basically killing the old connection and
> creating a new one. The connection does change ALIVE -> POLLING,
> but can never connect to the server after redial and there's
> nothing happening in the log file on the server.
>
> I'm assuming its the IP address because the software works
> perfectly on a LAN?
The IP address of the server (xmlBlaster) is not changing,
so you think it is the client side IP address?


Yes the client is allocated a different IP address every time
it dials up and it's connects to the xmlBlaster server which
has a public IP address.

Is your client a java software?
On which OS?
Which xmlBlaster version do you use?


Yes it's a java 1.6 app running on Windows XP at the moment.
And the server is xmlBlaster 1.2 running on Suse Linux Enterprise 9.

>
> This solution is ptp so I managed to kind of
> get a workaround by just connecting using a different
> session name eg. machine2/2, and setting the old sessions
> to expire after 10min, but I'm sure there must be a better way.
Yes, this is a hack...
>
> I'm using the RAW SOCKET and SSL protocols and passing the message
> server the same client session name everytime, my question is,
> what in your opinion should the settings be firstly
> on the message server and secondly on the client to
> enable a client with a different IP address to reconnect
> to an existing session.
Could you please try if it runs fine without SSL ?


First thing I tried, unfortunately still doesn't reconnect.
I also had zlib full stream compression on, but also made
no difference.

>
> A very simple example of the xmlBlaster.properties and
> the client arguments would be appreciated as I'm still quite
> new to xmlBlaster and java.
This is a fail save client:

java javaclients.HelloWorldSubscribe - session.name
 client/joe/session/1
-dispatch/callback/retries -1

if the server disappears or the network disappears it will
automatically
reconnect,


I also tried this example but the same behaviour occurs. It just 
doesn't ever

reconnect to the server and the server never shows anything in the logs.

I've coded the app to retry the connection 5 times and then
first disconnect and reconnect again, the server then shows a
reconnect coming from a different IP address and port.

This should be fine for now but I'm still gonna try using
a GPRS router which will have a static IP address
and port, maybe it'll make a difference.

Thanks,
Matthew

regards
Marcel

>
> Thanks,
>
> Matthew
>

Re: [xmlblaster] Annoying Warning about recv failed

[Marcel Ruff]

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

[chris lau]

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

[Marcel Ruff]

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