Siebel Business Process & Functionality (MOSC)

MOSC Banner

Siebel WebServer Error Failed to connect to pipe

edited Dec 16, 2014 3:37PM in Siebel Business Process & Functionality (MOSC) 1 commentAnswered ✓

Hi Siebel Community Experts

At our SCBroker log we were continusly getting error like "Failed to connect to pipe (SEBL_33_<PID>) on process <PID>. Its having impacting on our Siebel Web Server Requests processing. So ,

We analyzed after refering some Oracle Docs and got some help from Oracle Support Engineers and identified this issue in below manner.

*****
1. Under certain scenarios, an AOM process can be in a hanging state and is not able to acknowledge connection requests from the SC Broker anymore. If this hanging AOM process happens to have the least number of running tasks, SCB will attempt to route new session requests to this AOM process repeatedly. This results in blockage of all new login requests on that Siebel Server. And the SC Broker log is continuously logging the following error message:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center