ws-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Wade Chandler <hwadechandler-apa...@yahoo.com>
Subject Re: AIX 5.2 Java 1.4 WebServer Garbage in the stream?
Date Thu, 29 Dec 2005 21:00:59 GMT
--- John Southerland <john@southerland-consulting.com>
wrote:

> Wade knocked out my ssl issue in short order, thanks
> again, but I still have
> a connection problem on AIX using http.
> 
> I enabled debug for XmlRpc and tried once again to
> send a message the first
> test, a simple telnet to the port and "GET /
> HTTP/1.0"  returned nothing,
> but printed on the remote in all it's accurate
> glory, however the actually
> xmlrpc request did something more interesting.  I
> didn't capture the raw
> request but it was generated from a linux box
> running jvm 1.5 against the
> remote AIX 5.2 server with a 1.5 jvm as well.
> 
> To make a long setup short, here is the resulting
> output on the server:
> 
>  b9  /32
> 
> java.util.NoSuchElementException
> 
> java.util.NoSuchElementException
> 
>             at
>
java.util.StringTokenizer.nextToken(StringTokenizer.java:347)
> 
>             at
>
org.apache.xmlrpc.WebServer$Connection.run(WebServer.java)
> 
>             at
>
org.apache.xmlrpc.WebServer$Runner.run(WebServer.java)
> 
>             at java.lang.Thread.run(Thread.java:788)
> 
>  
> 
> Anyone seen this before?  Is it network byte order
> versus host byte order
> conversion error or something?
> 
> Once again the same code runs brilliantly on Linux
> and Solaris, fun fun
> 
> Thanks, John
> 
>  
> 
> John Buren Southerland
Should not an issue with the byte order (only matters
for floats and doubles and numbers not character
formatted data), but what appears to be happening (I
haven't looked at the source for WebServer.java, but
it is not checking hasMoreTokens in StringTokenizer
before calling nextToken...I'm not sure exactly what
it is parsing, but if there should be another value
then what really needs to happen is an exception needs
to be thrown stating there should be more elements and
what the real issue is and explain that something
isn't formatted correctly instead of a blind nextToken
read which is what is happening (unless there is no
blind nextToken and hasMoreTokens is checking before
calling nextToken and it is a bug in the IBM jvm).

Wade

Mime
View raw message