PI70614: Clean up all resources on an application startup failure on cdi-1.0 feature

Fixes are available

APAR status

Closed as program error.

Error description

```
Duplicated bean id found
```

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Contexts and Dependency    *
*                  Injection (CDI)                             *
****************************************************************
* PROBLEM DESCRIPTION: Clean up all resources on an            *
*                      application startup failure on cdi-1.0  *
*                      feature                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When trying to start an application that failed to start the
first time, the following exception might be thrown.

org.apache.webbeans.exception.definition.DuplicateDefinitionExce
ption was found (count = 1):
>Stack Dump =
org.apache.webbeans.exception.definition.DuplicateDefinitionExce
ption: PassivationCapable bean id is not unique:
MANAGER#interface
javax.enterprise.inject.spi.BeanManager#@javax.enterprise.inject
.Any(),@javax.enterprise.inject.Default(), bean:BeanManager,
Name:null, WebBeans Type:MANAGER, API
Types:[javax.enterprise.inject.spi.BeanManager,java.lang.Object]
,
Qualifiers:[javax.enterprise.inject.Any,javax.enterprise.inject.
Default]
>	at
org.apache.webbeans.container.BeanManagerImpl.addPassivationInfo
(BeanManagerImpl.java:394)
>	at
org.apache.webbeans.container.BeanManagerImpl.addInternalBean(Be
anManagerImpl.java:367)
>	at
org.apache.webbeans.config.BeansDeployer.deploy(BeansDeployer.ja
va:157)
>	at
org.apache.webbeans.lifecycle.AbstractLifeCycle.startApplication
(AbstractLifeCycle.java:157)
>	at
org.apache.webbeans.web.lifecycle.WebContainerLifecycle.startApp
lication(WebContainerLifecycle.java:97)
>	at
com.ibm.ws.webbeans.WebBeansInitializer.onStartup(WebBeansInitia
lizer.java:70)
>	at
com.ibm.ws.webcontainer.webapp.WebApp.initializeServletContainer
Initializers(WebApp.java:2488)
>	at
com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:104
0)
>	at
com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:650
7)
>	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.startWebApp(Dyna
micVirtualHost.java:446)
>	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.createRunnableHa
ndler(DynamicVirtualHost.java:248)
>	at
com.ibm.ws.webcontainer.osgi.DynamicVirtualHost.createRunnableHa
ndler(DynamicVirtualHost.java:313)
>	at
com.ibm.ws.http.internal.VirtualHostImpl.discriminate(VirtualHos
tImpl.java:251)
>	at
com.ibm.ws.http.dispatcher.internal.channel.HttpDispatcherLink.r
eady(HttpDispatcherLink.java:300)
>	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleD
iscrimination(HttpInboundLink.java:471)
>	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.handleN
ewRequest(HttpInboundLink.java:405)
>	at
com.ibm.ws.http.channel.internal.inbound.HttpInboundLink.process
Request(HttpInboundLink.java:285)
>	at
com.ibm.ws.http.channel.internal.inbound.HttpICLReadCallback.com
plete(HttpICLReadCallback.java:66)
>	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(
WorkQueueManager.java:504)
>	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQu
eueManager.java:574)
>	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQu
eueManager.java:929)
>	at
com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQ
ueueManager.java:1018)
>	at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExec
utor.java:1177)
>	at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExe
cutor.java:642)
>	at java.lang.Thread.run(Thread.java:795)

Problem conclusion

The first attempt to start an application stored some
information but that was not cleaned up completely if the
startup was not successful.

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.4.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PI70614
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
CD0
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-12
Closed date
2016-11-01
Last modified date
2016-11-01

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

Fix information

Fixed component name
WAS LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

RCD0 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"CD0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI70614: Clean up all resources on an application startup failure on cdi-1.0 feature

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

RCD0 PSY

Document Information

Share your feedback

Need support?