2362736 - Unable to connect to JMS queue 'JobQueue' after '10' attempts

Symptom

Java scheduler jobs fail after a Support Package upgrade or full system upgrade. The error is:

Error occurred while submitting a job generated for task <id> to the Job Execution Runtime.
Probably this expiration of the task won't be executed
Error details: Uanble to start Job. JMS message could not be sent.

...

Unable to connect to JMS queue 'JobQueue' after '10' attempts. Giving up.
Caused by: javax.naming.NameNotFoundException: [LDAP: error code 32 ...

Environment

SAP NetWeaver Application Server Java 7.1+

Product

SAP NetWeaver 7.3 ; SAP NetWeaver 7.4 ; SAP NetWeaver 7.5 ; SAP NetWeaver Application Server for Java 7.1 ; SAP NetWeaver Application Server for Java 7.2 ; SAP enhancement package 1 for SAP NetWeaver 7.3 ; SAP enhancement package 1 for SAP NetWeaver Application Server for Java 7.1

Keywords

jobs failing jms queue cleanjob clean job LDAP: error code 32 Uanble to start Job, '10' attempts, Unable to connect to JMS queue,UME inconsistency. , KBA , BC-JAS-BTC , NetWeaver Scheduler (Java) , BC-JAS-SEC-UME , User Management Engine , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.