My Oracle Support Banner

Configurator Developer Create Rule Entities Loading Failed With Error: Failure of Web Server Bridge (Doc ID 3015477.1)

Last updated on APRIL 12, 2024

Applies to:

Oracle Configurator Developer - Version 12.2.12 and later
Information in this document applies to any platform.

Symptoms

In the Configurator Developer, if a model and Control Assembly rules is focused and while in process of creating for example a 'Statement Rule' rules entity, other users can not access the same page to also create Statement Rules. For other users, the screen is loading upon clicking Continue on screen 'Create Rule Entities: Select Type', until the first person either clicks Cancel or Apply in the screen 'Create Rule Entities: Define Statement Rule'.

In the database, the session of the first user has event 'SQL*Net message from client' and is blocking the sessions from other users.

If the first user is in the screen 'Create Rule Entities: Define Statement Rule' and closes his browser, then his session still exists with event 'SQL*Net message from client', blocking the rest of the users. The other users eventually receive an error:


A workaround is to let one person do the rule updates in the configurator developer.

The issue can be reproduced at will with the following steps:
1. Configurator Administrator Responsibility, log in as A user. Open a model and go to Rules tab. Create a new rule with entity type = Statement Rule. Click Continue.
2. In another browser session log in as B user into Configurator Administrator responsibility. Since this model was locked by A user, tried to unlock this model by clicking Unlock button. The system waits and finally errors out: Failure of Web Server bridge: No backend server available for connection: timed out after 10 seconds or idempotent set to OFF or method not idempotent.
3. Meanwhile checked the records in v$session after every step. After second step (mentioned above) a new record was created with below values:

client_identified=MFG,
module=e:CZ:fwk:cz.developer.repository.main.server.Rep
action=CZ/CZ_ADMIN
event=enq: TX - row lock contention
state=WAITING
status=ACTIVE

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.