PI52262: WHEN ENABLING COMPTATIBLE FEATURES TOGETHER IN LIBERTY PROFILE, THE SERVER MAY START WITH WWKF0033E ERROR.

APAR status

• Closed as suggestion for future release.

Error description

• When certain features are enabled together, they may result
  in
  WWKF0033E error IllegalArgumentException even though they
  should
  be compatible.
  
  Example:
  server.xml contains:
  
  
  servlet-3.1
  localConnector-1.0
  batch-1.0
  batchManagement-1.0
  appSecurity-2.0
  zosLocalAdapters-1.0
  
  
  When server is restarted, the following errors are issued:
  
  CWWKF0033E: The singleton features
  com.ibm.websphere.appserver.transaction-1.2 and
  com.ibm.websphere.appserver.transaction-1.1 cannot be loaded
  at
  the same time.  The configured features batch-1.0 and
  zosLocalAdapters-1.0 include one or more features that cause
  the
  conflict. Your configuration is not supported; update
  server.xml to remove incompatible features.
  
  FFDC log:
  java.lang.IllegalArgumentException: Unable to load
  conflicting
  versions of features
  "com.ibm.websphere.appserver.transaction-1.2" and
  "com.ibm.websphere.appserver.transaction-1.1".  The feature
  dependency chains that led to the conflict are:
  com.ibm.websphere.appserver.batch-1.0 ->
  com.ibm.websphere.appserver.transaction-1.2 and
  com.ibm.websphere.appserver.zosLocalAdapters-1.0 ->
  com.ibm.websphere.appserver.ejbLite-3.1 ->
  com.ibm.websphere.appserver.transaction-1.1
  at
  com.ibm.ws.kernel.feature.internal.FeatureManager.reportErro
  r
  s(FeatureManager.java:1506)
  at
  com.ibm.ws.kernel.feature.internal.FeatureManager.updateFeat
  u
  res(FeatureManager.java:1109)
  at
  com.ibm.ws.kernel.feature.internal.FeatureManager.update(Fea
  t
  ureManager.java:658)
  at
  com.ibm.ws.kernel.feature.internal.FeatureManager.processFea
  t
  ureChanges(FeatureManager.java:764)
  at
  com.ibm.ws.kernel.feature.internal.FeatureManager$1.run(Feat
  u
  reManager.java:556)
  at
  java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
  E
  xecutor.java:1121)
  at
  java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
  l
  Executor.java:614)
  at java.lang.Thread.run(Thread.java:777)
  
  The problem is with installUtility since it installed a non-
  working configuration for a server which is wrong, if you
  install a server you should get sufficient features
  installed
  for a working configuration.  The underlying resolver that
  installUtility uses treats each feature independently, so it
  doesn't try to find a solution for both together.
  

Local fix

• Contact IBM Support for a workaround.  It will depend on what
  type of features are enabled together.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is being closed as a suggestion and will be considered
  for inclusion in a possible future level.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels