Status code 503--Service Unavailable

[Former Member]

Hi everyone.

A little time ago I 've faced status code 503 -- service unavailable on XI 3.0, so I found Sap Note 803145 and applied it.

The note says to change the PollAttempts parameter from 60 to 100 and that's supposed to solve the problem.

Actually it seems that problem is solved, but occasionally it keeps apearing the same error (status code 503 -- service unavailable).

I've checked all PollAttempts parameters and they are in 100 like the note says.

Before the Note application the error was appearing in some messages that use SOAP and JDBC Adapters, but now this error is only appearing in JDBC adapter.

Not all messages that use JDBC adapter are erroneous, the tricky thing here is that some messages that appear with this error can be restarted and processed succesfully but others can not be restarted.

Can someone give me some light in this??

Thanks in advanced.

Emmanuel Rebolledo

[JoelTrinidade · Accepted solution]

Hi Emmanuel,

The "pollIntervall" and "pollAttempts" properties define how often and in what

interval the messaging system tries to access the Listener Beans

during startup (using JNDI Lookup). In the default system, this is a maximum

of 10 attempts every 60 seconds. This is necessary because the Messaging

System (MS) is implemented as a J2EE service, whereas EJBs are part of a

J2EE application. During server startup, applications are always in a second

phase after the services; therefore they are unavailable during the MS

initialization. If your system starts very slowly (if it takes more than 10

minutes), you may therefore need to increase "pollIntervall" and

"pollAttempts".

Default: pollInterval=60000 [ms], pollAttempts=10

Regards

joel