We have located the problem.
This seems to be a problem in v5r2 and v5r1 and its http server which was
solved by installing a ptf. I can not see that there is any ptf for v5r3 to
solve this issue.


"KS" skrev i melding
news:dcqg49$4mpa$1@news.boulder.ibm.com...
> We are running J2EE Web application on OS400 v5r3 with the application
> server:
> IBM WebSphere Application Server for Network Deployment, 5.1.1.4
> Build Number: cf40515.01
> Build Date: 04/11/2005
>
> The WAS is now jusing 100 % of the CPU of OS400 and at the same time it
> writes the same lines bellow into to the SystemOut.log file over and over
> again.
> SystemOut.log just keeps getting bigger with ten of thousands of the lines
> bellow.
>
> [03.08.05 14:53:39:184 CEST] 5bb71921 RequestUtils E parsePostData: post
> body contains less bytes than specified by content-length
> [03.08.05 14:53:39:190 CEST] 5bb71221 RequestUtils E parsePostData: post
> body contains less bytes than specified by content-length
> [03.08.05 14:53:39:244 CEST] 5bb71921 TraceNLS u No message text
> associated with key
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> h in bundle com.ibm.ejs.resources.seriousMessages
> [03.08.05 14:53:39:248 CEST] 5bb71221 TraceNLS u No message text
> associated with key
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> h in bundle com.ibm.ejs.resources.seriousMessages
> [03.08.05 14:53:39:244 CEST] 5bb71921 RequestUtils E parsePostData: post
> body contains less bytes than specified by content-length
> [03.08.05 14:53:39:259 CEST] 5bb71921 TraceNLS u No message text
> associated with key
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> h in bundle com.ibm.ejs.resources.seriousMessages
> [03.08.05 14:53:39:247 CEST] 5bb71221 RequestUtils E parsePostData: post
> body contains less bytes than specified by content-length
> [03
>
>
> What does the lines above say, and what might be the problem. We have been
> running the Application for a long time without seeing this problem
before.
> Any help would be great since this is killing the application and all the
> people that are jusing it.
>
>
> Thanks
> Kato Strandjord
>
>
>

We have ordered ptf that should fix this problem. It has been a documented
problem from IBM with OS400 v5r1 and v5r2 so why it is a problem in v5r3?
Hopefully the ptf will solve it.

"KS" skrev i melding
news:dcsk6l$7cfu$1@news.boulder.ibm.com...
> We have located the problem.
> This seems to be a problem in v5r2 and v5r1 and its http server which was
> solved by installing a ptf. I can not see that there is any ptf for v5r3
to
> solve this issue.
>
>
> "KS" skrev i melding
> news:dcqg49$4mpa$1@news.boulder.ibm.com...
> > We are running J2EE Web application on OS400 v5r3 with the application
> > server:
> > IBM WebSphere Application Server for Network Deployment, 5.1.1.4
> > Build Number: cf40515.01
> > Build Date: 04/11/2005
> >
> > The WAS is now jusing 100 % of the CPU of OS400 and at the same time it
> > writes the same lines bellow into to the SystemOut.log file over and
over
> > again.
> > SystemOut.log just keeps getting bigger with ten of thousands of the
lines
> > bellow.
> >
> > [03.08.05 14:53:39:184 CEST] 5bb71921 RequestUtils E parsePostData:
post
> > body contains less bytes than specified by content-length
> > [03.08.05 14:53:39:190 CEST] 5bb71221 RequestUtils E parsePostData:
post
> > body contains less bytes than specified by content-length
> > [03.08.05 14:53:39:244 CEST] 5bb71921 TraceNLS u No message text
> > associated with key
> >
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> > h in bundle com.ibm.ejs.resources.seriousMessages
> > [03.08.05 14:53:39:248 CEST] 5bb71221 TraceNLS u No message text
> > associated with key
> >
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> > h in bundle com.ibm.ejs.resources.seriousMessages
> > [03.08.05 14:53:39:244 CEST] 5bb71921 RequestUtils E parsePostData:
post
> > body contains less bytes than specified by content-length
> > [03.08.05 14:53:39:259 CEST] 5bb71921 TraceNLS u No message text
> > associated with key
> >
>
parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
> > h in bundle com.ibm.ejs.resources.seriousMessages
> > [03.08.05 14:53:39:247 CEST] 5bb71221 RequestUtils E parsePostData:
post
> > body contains less bytes than specified by content-length
> > [03
> >
> >
> > What does the lines above say, and what might be the problem. We have
been
> > running the Application for a long time without seeing this problem
> before.
> > Any help would be great since this is killing the application and all
the
> > people that are jusing it.
> >
> >
> > Thanks
> > Kato Strandjord
> >
> >
> >
>
>

Can you please provide to the reference to the documentation regarding
this.Thanks.

Tech

"KS" wrote in message
news:ddcere$11de$1@news.boulder.ibm.com...
> We have ordered ptf that should fix this problem. It has been a
> documented
> problem from IBM with OS400 v5r1 and v5r2 so why it is a problem in v5r3?
> Hopefully the ptf will solve it.
>
> "KS" skrev i melding
> news:dcsk6l$7cfu$1@news.boulder.ibm.com...
>> We have located the problem.
>> This seems to be a problem in v5r2 and v5r1 and its http server which was
>> solved by installing a ptf. I can not see that there is any ptf for v5r3
> to
>> solve this issue.
>>
>>
>> "KS" skrev i melding
>> news:dcqg49$4mpa$1@news.boulder.ibm.com...
>> > We are running J2EE Web application on OS400 v5r3 with the application
>> > server:
>> > IBM WebSphere Application Server for Network Deployment, 5.1.1.4
>> > Build Number: cf40515.01
>> > Build Date: 04/11/2005
>> >
>> > The WAS is now jusing 100 % of the CPU of OS400 and at the same time it
>> > writes the same lines bellow into to the SystemOut.log file over and
> over
>> > again.
>> > SystemOut.log just keeps getting bigger with ten of thousands of the
> lines
>> > bellow.
>> >
>> > [03.08.05 14:53:39:184 CEST] 5bb71921 RequestUtils E parsePostData:
> post
>> > body contains less bytes than specified by content-length
>> > [03.08.05 14:53:39:190 CEST] 5bb71221 RequestUtils E parsePostData:
> post
>> > body contains less bytes than specified by content-length
>> > [03.08.05 14:53:39:244 CEST] 5bb71921 TraceNLS u No message text
>> > associated with key
>> >
>>
> parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
>> > h in bundle com.ibm.ejs.resources.seriousMessages
>> > [03.08.05 14:53:39:248 CEST] 5bb71221 TraceNLS u No message text
>> > associated with key
>> >
>>
> parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
>> > h in bundle com.ibm.ejs.resources.seriousMessages
>> > [03.08.05 14:53:39:244 CEST] 5bb71921 RequestUtils E parsePostData:
> post
>> > body contains less bytes than specified by content-length
>> > [03.08.05 14:53:39:259 CEST] 5bb71921 TraceNLS u No message text
>> > associated with key
>> >
>>
> parsePostData:.post.body.contains.less.bytes.than. specified.by.content-lengt
>> > h in bundle com.ibm.ejs.resources.seriousMessages
>> > [03.08.05 14:53:39:247 CEST] 5bb71221 RequestUtils E parsePostData:
> post
>> > body contains less bytes than specified by content-length
>> > [03
>> >
>> >
>> > What does the lines above say, and what might be the problem. We have
> been
>> > running the Application for a long time without seeing this problem
>> before.
>> > Any help would be great since this is killing the application and all
> the
>> > people that are jusing it.
>> >
>> >
>> > Thanks
>> > Kato Strandjord
>> >
>> >
>> >
>>
>>
>
>