0 Votes

Troubleshooting

Last modified by Jeff McDonald on 2021/09/26 19:53

This is a running log of issues with WSC...

Default Application Not Found

After installing the latest patches, I got this error when starting 'engine1'.

[WscSipApplicationRouter] : Wsc SipApplicationRouter initialized
<Feb 16, 2020 9:49:58 AM CST> <Error> <WLSS.Engine> <BEA-330112> <Application Router throws exception
com.bea.wcp.sip.engine.server.ar.oam.AppRouterConfigException: default application [oracle.wsc] is not found.
at com.bea.wcp.sip.engine.server.CanaryServerImpl.onDefaultApplicationNameChange(CanaryServerImpl.java:1308)
at com.bea.wcp.sip.engine.server.CanaryServerImpl.prepareToAcceptClientTraffic(CanaryServerImpl.java:1137)
at com.bea.wcp.sip.engine.server.CanaryServerImpl.propertyChange(CanaryServerImpl.java:1250)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:335)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:327)
Truncated. see log file for complete stacktrace
>

Need to verify what's going on.

This appears to be a problem with the 'wsc' not starting on a physical host serving both the AdminServer and engine1. Why?

Looking in the 'engine1' logs, I found this:

####<Feb 16, 2020 9:49:56 AM CST> <Error> <Deployer> <mothra> <engine1> <[ACTIVE] ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1581868196501> <BEA-149231> <Unable to set the activation state to true for the application "wsc".
weblogic.application.ModuleException: java.lang.IllegalArgumentException: Cluster address must be set when clustering is enabled.
at weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)

That could explain it... Let's set the "cluster address" to "mothra:7001" and restart engine1. (Hostname & port number of both AdminServer and engine1.)

That did the trick!