webMethods 9.10 MWS startup issues !MESSAGE FrameworkEvent ERROR

Lea_SEMENGUE · August 26, 2016, 3:28pm

Hi There,

I’m new in webMethods world ! I hope somebody could help me

We are using webMethods 9.10 on Windows 2008 R2 server. We installed this fix “IS_9.10_Core_Fix2” and since then MWS doesn’t start. We use Windows services to start and stop MWS.

In MWS server log, we only have got the shutdown logs.

The only thing I had noticed is there are those errors on the wrapper log every time I try to start MWS :

!ENTRY INFO | jvm 1 | 2016/08/12 15:04:00 INFO | jvm 1 | 2016/08/12 15:04:00 INFO | jvm 1 | 2016/08/12 15:04:00 INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | INFO | jvm 1 | 2016/08/12 15:04:00 | com.softwareag.bam.ui 4 0 2016-08-12 15:04:00.586
| !MESSAGE FrameworkEvent ERROR
| !STACK 0
| org.osgi.framework.BundleException: Could not resolve module: com.softwareag.bam.ui [43]
Unresolved requirement: Import-Package: com.webMethods.portal.bizPolicy.biz.dir; version=“[0.0.0,1.0.0)”
→ Export-Package: com.webMethods.portal.bizPolicy.biz.dir; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”; version=“0.0.0”
com.webMethods.caf.server [6823]
Unresolved requirement: Import-Package: jespa.http; resolution:=“optional”
Unresolved requirement: Import-Package: jespa.security; resolution:=“optional”
Unresolved requirement: Import-Package: junit.framework; resolution:=“optional”
Unresolved requirement: Import-Package: junit.runner; resolution:=“optional”
Unresolved requirement: Import-Package: jespa.ntlm; resolution:=“optional”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.jsf.test; bundle-version=“[9.0.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.portalclient.test; bundle-version=“[9.0.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.ui.unittesting; bundle-version=“[9.0.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.rules.test; bundle-version=“[9.0.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.wsclient.test; bundle-version=“[9.0.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Import-Package: org.eclipse.jetty.osgi.boot; version=“[9.2.0,10.0.0)”
→ Export-Package: org.eclipse.jetty.osgi.boot; bundle-symbolic-name=“com.softwareag.web.caf.jetty.osgi.boot”; bundle-version=“9.10.0.0000-0237”; version=“9.2.9”
com.softwareag.web.caf.jetty.osgi.boot [205]
Unresolved requirement: Import-Package: org.eclipse.jetty.nested; version=“[9.2.0,10.0.0)”; resolution:=“optional”
Unresolved requirement: Import-Package: com.webMethods.portal.webapp.jetty7
→ Export-Package: com.webMethods.portal.webapp.jetty7; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”; version=“0.0.0”
Unresolved requirement: Require-Bundle: com.webMethods.caf.shared.wsclient; bundle-version=“[9.0.0,10.0.0)”
→ Bundle-SymbolicName: com.webMethods.caf.shared.wsclient; bundle-version=“9.10.0.0000-0237”
com.webMethods.caf.shared.wsclient [273]
No resolution report for the bundle. Unresolved requirement: Import-Package: com.webMethods.sc.directory; version=“[9.5.0,10.0.0)”
→ Export-Package: com.webMethods.sc.directory; bundle-symbolic-name=“com.softwareag.web.caf.mws.directory”; bundle-version=“9.10.0.0000-0237”; version=“9.5.1”
com.softwareag.web.caf.mws.directory [209]
Unresolved requirement: Import-Package: com.webMethods.portal.bizPolicy.biz; version=“[0.0.0,1.0.0)”
→ Export-Package: com.webMethods.portal.bizPolicy.biz; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”; version=“0.0.0”
Unresolved requirement: Import-Package: com.webMethods.portal.bizPolicy.biz.dir; version=“[0.0.0,1.0.0)”
→ Export-Package: com.webMethods.portal.bizPolicy.biz.dir; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”; version=“0.0.0”
Unresolved requirement: Import-Package: com.webMethods.portal.service.meta2; version=“[0.0.0,1.0.0)”
→ Export-Package: com.webMethods.portal.service.meta2; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”; version=“0.0.0”
Unresolved requirement: Import-Package: com.webMethods.portal.service.dir.impl; version=“[0.0.0,1.0.0)”
→ Export-Package: com.webMethods.portal.service.dir.impl; bundle-symbolic-name=“com.webMethods.caf.server”; bundle-version=“9.10.0.0001-0029”;

The full wrapper logs and MWS server log are attached on this post.

Thank you for your help !
MWS_logs.zip (273 KB)

Holger_von_Thomsen · August 26, 2016, 5:56pm

Hi Lea,

can you please explain what you were exactly doing as this occured?

Has the MWS been stopped before updating it?

Was this the only fix you wanted to apply?

Please have a look the UpdateManager logs as there might have been an issue during the installation of the Fix(es).

Regards,
Holger

Pierre_LE_CORRE1 · August 30, 2016, 2:46pm

Hello,

Meanwhile, I’ve opened a Support Incident 5249607 with few files attached.

Yes, because it’s requested by install process

No, we installed many of thems on 12th august and then on 30th august (see Support Incident 5249607)

see attached files

UpdateManager_error.zip (1.19 KB)

Pierre_LE_CORRE1 · August 31, 2016, 4:57pm

SAG support has requested to re-create OSGi.
That’s solved the issue (MWS start again).

Holger_von_Thomsen · August 31, 2016, 6:12pm

Hi Pierre,

please check if the fixes have been applied correctly after that.

Eventually they need to be reapplied (overinstalled).
This applies especially to fixes which have a “Bundles”-Portion, i.e. OSGi, Messaging APIs, DataDirect, WebService-Stack.

Regards,
Holger