Using the "Generate Steps..." in Web Switching Causes Web Workspace to Appear to Disconnect From NMS (Doc ID 2870048.1)

Last updated on JUNE 04, 2024

Applies to:

Symptoms

On : 2.5.0.1.0 version, Web Switching

Using the generate tag steps seems to cause NMS to go offline for a second.

When attempting to train several users, they used the "generate tag steps" functionality and it seemed to knock the user offline for a second.
They said the command fails and they go offline and then back online right away.

This set of exceptions appeared in the client log:

2022-04-12 10:58:48,562 [AWT-EventQueue-0] INFO com.splwg.oms.client.util.ClientThreadPool: Soft limit for thread pool reached: 26 0
2022-04-12 10:58:59,416 [Timer-1] WARN com.splwg.oms.client.util.proxy.ProxyInvocationHandler: invoke: ISession.getTroubleEvents elapsed: 932 ms. req: 7335 bytes, resp: 15167105 bytes
2022-04-12 10:58:59,678 [AWT-EventQueue-0] WARN com.splwg.oms.client.util.proxy.ProxyInvocationHandler: invoke: ISession.getConditions elapsed: 1184 ms. req: 236 bytes, resp: 12709124 bytes
2022-04-12 10:59:50,425 [AWT-EventQueue-0] ERROR com.splwg.oms.client.BaseEnvironmentManager: We have lost our connection
com.splwg.oms.framework.exception.OmsServiceException: EJB Exception:
at weblogic.utils.StackTraceDisabled.unknownMethod() ~[?:?]
Caused by: javax.ejb.EJBTransactionRolledbackException: EJB Exception:
... 1 more
Caused by: javax.ejb.EJBAccessException
... 1 more
2022-04-12 10:59:50,425 [AWT-EventQueue-0] ERROR SHEET: Exception generating isolate steps
com.splwg.oms.framework.exception.OmsServiceException: EJB Exception:
at weblogic.utils.StackTraceDisabled.unknownMethod() ~[?:?]
Caused by: javax.ejb.EJBTransactionRolledbackException: EJB Exception:
... 1 more
Caused by: javax.ejb.EJBAccessException
... 1 more

2022-04-12 10:59:50,426 [AWT-EventQueue-0] ERROR com.splwg.oms.jbot.adapter.JBotAdapter: java.lang.RuntimeException: com.splwg.oms.framework.exception.OmsClientException: TAG_STEPS_FAILED
java.lang.RuntimeException: com.splwg.oms.framework.exception.OmsClientException: TAG_STEPS_FAILED
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:616) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processCommand(CommandProcessor.java:163) ~[nms_client.jar:?]
at com.splwg.oms.jbot.CommandProcessor.processPackage(CommandProcessor.java:297) ~[nms_client.jar:?]
...
Caused by: com.splwg.oms.framework.exception.OmsClientException: TAG_STEPS_FAILED
at com.splwg.oms.client.control.GenerateTagStepsCommand.execute(GenerateTagStepsCommand.java:172) ~[nms_client.jar:?]
at com.splwg.oms.jbot.JBotCommand.executeCommand(JBotCommand.java:610) ~[nms_client.jar:?]
... 25 more

2022-04-12 10:59:51,696 [Thread-11] WARN com.splwg.oms.client.BaseEnvironmentManager: Connection to app server was reset.

The issue can be reproduced at will with the following steps:
- Need an environment that is not in Training Mode.
- Need a user that does not have access to Configuration Assistant.

1. Create a switching sheet and turn on step recording.
2. Navigate to a conductor in the model.
3. Bring up the Control Tool and select the "Generate Steps..." option followed by each of the submenu options.

Depending on the user's permissions and the environment, it was possible for an exception to be thrown.

Changes

Cause

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