FMW Control Does Not Report WLS Required Restart Before/after Failing OSB Changes (Doc ID 2274487.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle Service Bus - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms


FMW Control does not report WLS Required Restart before/after failing OSB changes

While performing different activation using FMW Control, changes are not applied, there is no message regarding the failure status of applying those changes.

In the logs there is the following error which reports that the activation was not successful due to "Server(s) require restart before session can be activated."

FMW Control must report that the WLS require a restart before activate the session and applying the changes.


ERROR
-----------------------

com.bea.wli.config.deployment.server.ServerRestartRequiredException: Server(s) require restart before session can be activated.
at com.bea.wli.config.deployment.server.ServerDeploymentReceiver$1.run(ServerDeploymentReceiver.java:232)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:259)
at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:61)
at oracle.security.jps.internal.jaas.AbstractSubjectSecurity$ActionExecutorWrapper.execute(AbstractSubjectSecurity.java:230)
at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedAction.run(CascadeActionExecutor.java:67)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.security.Security.runAs(Security.java:41)
at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:46)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Browse to OSBCOnsole /sbconsole and Create a new Session
2. Create a "TEST_PS" Proxy Service under "Default" project and a "TEST_BS" Business Service.
3. Activate Session in OSBConsole.
4. Access to WLS Admin Console and save a change which needs a server restart to take effect, for instance, modify the ListenAddress. DO NOT RESTART THE WLS SERVER.
5. Browse now to the FMW Conttrol /em.
6. Under SOA > service-bus(AdminServer) > Default > Operations Tab, you should see the previous TEST_PS and TEST_BS services.
7. For one of them, check the Monitoring checkbox to activate that feature and click APPLY.
8. The change is not applied, and if you check the logs, the error reported by the customer appears:

[2017-03-29T09:12:48.983+00:00] [AdminServer] [ERROR] [] [oracle.osb.mgmt.model.operations.OperationalSettingsModel] [tid: [ACTIVE].ExecuteThread: '41' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: weblogic] [ecid: 2e602634-f54a-4d7d-a275-3bd1a5945768-000002d5,0] [APP: em] [DSID: 0000LgPKoG2Fw000jzwkno1OqrNk000003] [[
com.bea.wli.config.deployment.server.ServerRestartRequiredException: Server(s) require restart before session can be activated.

9. If you click in another folder and you return to the Operations Tab, the change is not applied. However no notification is reported to the user.



Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms