Discussion:
Content is not allowed in prolog
Patrick Coleman
2010-06-02 18:34:44 UTC
Permalink
Actually after looking at instance log I see that this error comes at the
same time as the first one below.

2010-06-02 19:32:51,472 WARN NSLog appendln
- <WOWorkerThread id=11
socket=Socket[addr=/86.43.39.31,port=49321,localport=2001]> Exception
occurred while responding to client:
com.webobjects.foundation.NSForwardException
[java.lang.IllegalStateException] Assertion failed (POST): expected
non-empty String, got null:
<com.webobjects.appserver._private.WODirectActionRequestHandler>: Exception
while trying to generate an error response: java.lang.IllegalStateException:
Assertion failed (POST): expected non-empty String, got null


Pat.
Hi,
I get the following error in my system.log file about once a minute.
Content is not allowed in prolog.
Jun 2 18:49:30 sr71 com.webobjects.wotaskd[2708]: [2010-6-2 18:49:30 IST]
<WorkerThread6> Wotaskd getStatisticsForInstanceArray: Error parsing: An
Internal Server Error Has Occurred. from instancename
Anyone have any idea what is causing this.
Thanks.
Pat.
--
View this message in context: http://old.nabble.com/Content-is-not-allowed-in-prolog-tp28757835p28758344.html
Sent from the WebObjects-Dev mailing list archive at Nabble.com.
Loading...