This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
thank you!
Operation: RETRIEVE PAGE CONTENT
The client sub-operation was Servlet (ViewPage)
The server sub-operation was XML API (SelectPage)
Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
Error Code: 5003
Message: Socket connect failed. Please wait before retrying your request.
Resolution:
Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
Function: processResponse(...)
Did you stop and restart the iServer without restarting Maximo?
If you can, shut down both of them, restart Actuate (the iServer) and then Maximo. There were issues in the past with "remembered" connections from Maximo to Actuate that caused similar issues (if I remember correctly)
R/
Will
512-547-6070 - office
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of bob_blakely
Sent: Thursday, December 01, 2011 11:06 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Actuate 5003 Socket error
Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
thank you!
Operation: RETRIEVE PAGE CONTENT
The client sub-operation was Servlet (ViewPage)
The server sub-operation was XML API (SelectPage)
Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
Error Code: 5003
Message: Socket connect failed. Please wait before retrying your request.
Resolution:
Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
Function: processResponse(...)
ok. I'll give it a try. Thanks! This happened a while back as well but I probably did the same thing (restart the services) to fix it. I did not know if there was some parameter I needed to check to keep this from happening...
-bob
--- In MAXIMO@yahoogroups.com, Will Hampton <will.hampton@...> wrote:
>
> Did you stop and restart the iServer without restarting Maximo?
>
> If you can, shut down both of them, restart Actuate (the iServer) and then Maximo. There were issues in the past with "remembered" connections from Maximo to Actuate that caused similar issues (if I remember correctly)
>
> R/
> Will
> 512-547-6070 - office
>
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of bob_blakely
> Sent: Thursday, December 01, 2011 11:06 AM
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Actuate 5003 Socket error
>
>
>
> Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
>
> It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
>
> thank you!
>
> Operation: RETRIEVE PAGE CONTENT
> The client sub-operation was Servlet (ViewPage)
> The server sub-operation was XML API (SelectPage)
> Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
> Error Code: 5003
> Message: Socket connect failed. Please wait before retrying your request.
> Resolution:
> Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
> Function: processResponse(...)
>
>
>
>
>
I checked Actuate for any jobs running or pending or just plain stuck. Nothing that I could see.
I rebuild the ears (just to have clean ones).
I stopped the Maximo Service, then Actuate.
I cleaned out the logs in the Weblogic folders.
I started Actuate, then Maximo service.
Users say all is well. ( until next time! :-) )
-bob
--- In MAXIMO@yahoogroups.com, "bob_blakely" <bob.blakely@...> wrote:
>
> ok. I'll give it a try. Thanks! This happened a while back as well but I probably did the same thing (restart the services) to fix it. I did not know if there was some parameter I needed to check to keep this from happening...
>
> -bob
>
>
>
> --- In MAXIMO@yahoogroups.com, Will Hampton <will.hampton@> wrote:
> >
> > Did you stop and restart the iServer without restarting Maximo?
> >
> > If you can, shut down both of them, restart Actuate (the iServer) and then Maximo. There were issues in the past with "remembered" connections from Maximo to Actuate that caused similar issues (if I remember correctly)
> >
> > R/
> > Will
> > 512-547-6070 - office
> >
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of bob_blakely
> > Sent: Thursday, December 01, 2011 11:06 AM
> > To: MAXIMO@yahoogroups.com
> > Subject: [MAXIMO List] Actuate 5003 Socket error
> >
> >
> >
> > Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
> >
> > It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
> >
> > thank you!
> >
> > Operation: RETRIEVE PAGE CONTENT
> > The client sub-operation was Servlet (ViewPage)
> > The server sub-operation was XML API (SelectPage)
> > Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
> > Error Code: 5003
> > Message: Socket connect failed. Please wait before retrying your request.
> > Resolution:
> > Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
> > Function: processResponse(...)
> >
> >
> >
> >
> >
>
About the only thing I remember causing it is if the Actuate iServer is "restarted" for any reason and Maximo isn't...
R/
Will
will.hampton@exxtremeconsulting.com
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of bob_blakely
Sent: Thursday, December 01, 2011 12:42 PM
To: MAXIMO@yahoogroups.com
Subject: Re: [MAXIMO List] Actuate 5003 Socket error - results
I checked Actuate for any jobs running or pending or just plain stuck. Nothing that I could see.
I rebuild the ears (just to have clean ones).
I stopped the Maximo Service, then Actuate.
I cleaned out the logs in the Weblogic folders.
I started Actuate, then Maximo service.
Users say all is well. ( until next time! :-) )
-bob
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, "bob_blakely" <bob.blakely@...<mailto:bob.blakely@...>> wrote:
>
> ok. I'll give it a try. Thanks! This happened a while back as well but I probably did the same thing (restart the services) to fix it. I did not know if there was some parameter I needed to check to keep this from happening...
>
> -bob
>
>
>
> --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>, Will Hampton <will.hampton@> wrote:
> >
> > Did you stop and restart the iServer without restarting Maximo?
> >
> > If you can, shut down both of them, restart Actuate (the iServer) and then Maximo. There were issues in the past with "remembered" connections from Maximo to Actuate that caused similar issues (if I remember correctly)
> >
> > R/
> > Will
> > 512-547-6070 - office
> >
> >
> > From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of bob_blakely
> > Sent: Thursday, December 01, 2011 11:06 AM
> > To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
> > Subject: [MAXIMO List] Actuate 5003 Socket error
> >
> >
> >
> > Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
> >
> > It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
> >
> > thank you!
> >
> > Operation: RETRIEVE PAGE CONTENT
> > The client sub-operation was Servlet (ViewPage)
> > The server sub-operation was XML API (SelectPage)
> > Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
> > Error Code: 5003
> > Message: Socket connect failed. Please wait before retrying your request.
> > Resolution:
> > Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
> > Function: processResponse(...)
> >
> >
> >
> >
> >
>
Ok. Thanks for the help!
-bob
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Will Hampton
Sent: Thursday, December 01, 2011 10:45 AM
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] Actuate 5003 Socket error - results
About the only thing I remember causing it is if the Actuate iServer is "restarted" for any reason and Maximo isn't...
R/
Will
will.hampton@exxtremeconsulting.com<mailto:will.hampton%40exxtremeconsulting.com>
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of bob_blakely
Sent: Thursday, December 01, 2011 12:42 PM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Subject: Re: [MAXIMO List] Actuate 5003 Socket error - results
I checked Actuate for any jobs running or pending or just plain stuck. Nothing that I could see.
I rebuild the ears (just to have clean ones).
I stopped the Maximo Service, then Actuate.
I cleaned out the logs in the Weblogic folders.
I started Actuate, then Maximo service.
Users say all is well. ( until next time! :-) )
-bob
--- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com><mailto:MAXIMO%40yahoogroups.com>, "bob_blakely" <bob.blakely@...<mailto:bob.blakely@...>> wrote:
>
> ok. I'll give it a try. Thanks! This happened a while back as well but I probably did the same thing (restart the services) to fix it. I did not know if there was some parameter I needed to check to keep this from happening...
>
> -bob
>
>
>
> --- In MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com><mailto:MAXIMO%40yahoogroups.com>, Will Hampton <will.hampton@> wrote:
> >
> > Did you stop and restart the iServer without restarting Maximo?
> >
> > If you can, shut down both of them, restart Actuate (the iServer) and then Maximo. There were issues in the past with "remembered" connections from Maximo to Actuate that caused similar issues (if I remember correctly)
> >
> > R/
> > Will
> > 512-547-6070 - office
> >
> >
> > From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com><mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com><mailto:MAXIMO%40yahoogroups.com>] On Behalf Of bob_blakely
> > Sent: Thursday, December 01, 2011 11:06 AM
> > To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com><mailto:MAXIMO%40yahoogroups.com>
> > Subject: [MAXIMO List] Actuate 5003 Socket error
> >
> >
> >
> > Maximo 5.2 patch 06, Bea Weblogic 7.2 , Actuate 7 sp2 , oracle backend.
> >
> > It's been a while since I have had this type of error. Does anyone remember how to fix an Actuate 5003 socket error? For some reason we have been getting them lately and I do not think we changed anything.
> >
> > thank you!
> >
> > Operation: RETRIEVE PAGE CONTENT
> > The client sub-operation was Servlet (ViewPage)
> > The server sub-operation was XML API (SelectPage)
> > Item: /rpt/WOTRACK/Work.Order.Details.Report.1.40878.3534490741_74.roi
> > Error Code: 5003
> > Message: Socket connect failed. Please wait before retrying your request.
> > Resolution:
> > Details: Class: com.actuate.reportcast.servlets.ViewPageServlet
> > Function: processResponse(...)
> >
> >
> >
> >
> >
>