Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.lang.NumberFormatException: For input string: "901 "

111 views
Skip to first unread message

Miloš Hurdálek

unread,
Mar 19, 2007, 11:13:41 AM3/19/07
to
Hello,
in my HR connector to TIM i call SOAP (via HTTPClient) to get current HR
data.
This AL is scheduled by Timer eventhandler to 1:00 a.m. it works, but
sometimes it throws java.lang.NumberFormatException.

Could you please help me.
Thank you.
Milos Hurdalek


Full log:
2007-03-19 14:38:18,529 INFO [AssemblyLine.1readSOAP-405492782] -
AssemblyLine AssemblyLines/1readSOAP started
2007-03-19 14:38:18,873 INFO [AssemblyLine.1readSOAP-405492782] - BEGIN
Iteration
2007-03-19 14:39:29,607 ERROR [AssemblyLine.1readSOAP-405492782] -
[1SOAPrequest] Get
java.lang.NumberFormatException: For input string: "901 "
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:63)
at java.lang.Integer.parseInt(Integer.java:501)
at java.lang.Integer.parseInt(Integer.java:542)
at com.ibm.di.parser.HTTPParser.parseBody(Unknown Source)
at com.ibm.di.parser.HTTPParser.readEntry(Unknown Source)
at com.ibm.di.connector.HTTPClientConnector.readResponse(Unknown Source)
at com.ibm.di.connector.HTTPClientConnector.getNextEntry(Unknown Source)
at com.ibm.di.server.AssemblyLineComponent.getnext(Unknown Source)
at com.ibm.di.server.AssemblyLine.msGetNextIteratorEntry(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainStep(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainLoop(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeMainLoop(Unknown Source)
at com.ibm.di.server.AssemblyLine.executeAL(Unknown Source)
at com.ibm.di.server.AssemblyLine.run(Unknown Source)
2007-03-19 14:39:29,607 ERROR [AssemblyLine.1readSOAP-405492782] - Error in:
NextIteratorEntry: java.lang.NumberFormatException: For input string: "901
"
2007-03-19 14:39:29,623 INFO [AssemblyLine.1readSOAP-405492782] - BEGIN
Connector Statistics
2007-03-19 14:39:29,623 INFO [AssemblyLine.1readSOAP-405492782] -
[1SOAPrequest] Errors:1
2007-03-19 14:39:29,623 INFO [AssemblyLine.1readSOAP-405492782] - Total:
Errors:2
2007-03-19 14:39:29,623 INFO [AssemblyLine.1readSOAP-405492782] - END
Connector Statistics
2007-03-19 14:39:29,623 ERROR [AssemblyLine.1readSOAP-405492782] - failed
with error: For input string: "901 "


Jamais

unread,
Mar 19, 2007, 11:46:08 AM3/19/07
to
Perhaps the trailing chars that you see after "901 aren't blanks, try if you
can to right trim the input string


"Miloš Hurdálek" <milos.h...@seznam.cz> ha scritto nel messaggio
news:etm9bd$49o5i$1...@news.boulder.ibm.com...

Christian Chateauvieux

unread,
Mar 22, 2007, 3:27:52 PM3/22/07
to
Milos,

First, you seem to be using an HTTP client connector to invoke a SOAP
Service. Sure, this can be done... but why not use the WebServices
Function Components? Do you not care about the SOAP result?

The 'failed.log' log file shows an HTTP Timeout error (HTTP/1.0 500
Timeout). Seems your SAP server has problems responding in a timely manner.

Anyways, I still consider this as a connector bug. I would have expected
the connector to bail into its error hooks with some sort of Timeout or
communication exception. Can you please open a PMR to IBM support?

Thanks,

Christian

Miloą Hurdálek wrote:

> Hello,
> i have tried detailed log to get more info about communication between ITDI
> and SOAP(SAP) and it seems like problem on the SAP's side, because it
> returns wrong size of file to be transferred.
>
> Am I correct? Could you please check it in two attached files (the first one
> is fragment of successful communication and second one is for failed comm.)
>
> Thank You
> M.H.
>
>
>
> "Jamais" <jam...@yahoo.it> píąe v diskusním příspěvku
> news:etmb5u$3oc6a$1...@news.boulder.ibm.com...


>
>>Perhaps the trailing chars that you see after "901 aren't blanks, try if
>>you
>>can to right trim the input string
>>
>>

>>"Miloą Hurdálek" <milos.h...@seznam.cz> ha scritto nel messaggio

Milos Hurdálek

unread,
Mar 30, 2007, 2:21:31 AM3/30/07
to
Hello Christian,

we solved it by some optimalizations on SAP's side and now it works
correctly.
For next I would use WebServices Function Components, there are more usefull
for calling SOAP.

Thanks for help,

Milos


"Christian Chateauvieux" <christian.c...@fr.ibm.com> píse v
diskusním príspevku news:etulbm$3hk3o$1...@news.boulder.ibm.com...

0 new messages