aspose file tools
The moose likes BEA/Weblogic and the fly likes ADMIN , NODE MANAGED SERVER ERROR Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Head First Android this week in the Android forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark "ADMIN , NODE MANAGED SERVER ERROR" Watch "ADMIN , NODE MANAGED SERVER ERROR" New topic
Author

ADMIN , NODE MANAGED SERVER ERROR

vidyaraj sarma
Greenhorn

Joined: Aug 23, 2006
Posts: 4
We are having two servers and in each server nodemanaged server is running. Both servers are controlled by one admin server. When admin server is running
we are getting following errors in each of the nodemanaged logs, if any one knows please update us , what is the reason to display the following error message every 5 minutes


[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:27: The markup in the document preceding the root element must be well-formed.
[Fatal Error] :1:23: The markup in the document preceding the root element must be well-formed.
[Fatal Error] :1:32: XML document structures must start and end within the same entity.
[Fatal Error] :1:72: XML document structures must start and end within the same entity.
[Fatal Error] :-1:-1: Premature end of file.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:23: Content is not allowed in prolog.
[Fatal Error] :1:27: The markup in the document preceding the root element must be well-formed.
[Fatal Error] :1:23: The markup in the document preceding the root element must be well-formed.
[Fatal Error] :1:32: XML document structures must start and end within the same entity.
[Fatal Error] :1:72: XML document structures must start and end within the same entity.
 
jQuery in Action, 3rd edition
 
subject: ADMIN , NODE MANAGED SERVER ERROR
 
jQuery in Action, 3rd edition