Multiple IMS Connector installations cause OSGi cache out of sync condition

Technote (troubleshooting)


Problem(Abstract)

Repeated installation of the IBM IP Multimedia Subsystem Connector (IMS Connector) may cause the OSGi cache to get out of sync.

Symptom

Occasionally, users might experience a problem where the Diameter transport channels fail to load during server startup. This problem can happen when the user uninstalls and then reinstalls the IMS Connector or when an IMS Connector fixpack is applied.

The exception in the WebSphere SystemOut.log file looks like the following:

[10/25/07 14:05:06:804 EDT] 0000000a PMIImpl A CWPMI1001I: PMI is enabled
[10/25/07 14:05:07:154 EDT] 0000000a WSChannelFram E CHFW0014E: Could not find channel descriptor to match channel configuration type com.ibm.websphere.models.config.channelservice.channels.impl.GenericInboundChannelImpl.
[10/25/07 14:05:07:162 EDT] 0000000a ChannelFramew E CHFW0017E: Failed to load transport channel: com.ibm.wsspi.channel.framework.exception.ChannelException: Channel descriptor not found for com.ibm.websphere.models.config.channelservice.channels.impl.GenericInboundChannelImpl
at com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl.getChannelType(WSChannelFrameworkImpl.java:419)
at com.ibm.ws.channel.framework.impl.WSChannelFrameworkImpl.addChannel(WSChannelFrameworkImpl.java:362)
at com.ibm.ws.runtime.component.ChannelFrameworkServiceImpl.addChannel(ChannelFrameworkServiceImpl.java:836)
at com.ibm.ws.runtime.component.ChannelFrameworkServiceImpl.initialize(ChannelFrameworkServiceImpl.java:324)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponent(ContainerImpl.java:1338)
at com.ibm.ws.runtime.component.ContainerImpl.initializeComponents(ContainerImpl.java:1136)
at com.ibm.ws.runtime.component.ServerImpl.initialize(ServerImpl.java:356)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:178)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:140)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:461)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:183)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:90)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:72)
at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:336)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:91)

Cause

The Diameter base is included in an OSGi bundle. The act of uninstalling and reinstalling, or of installing a fixpack, can cause the OSGi cache to get out of sync. To resolve, the OSGi cache needs to be cleared and reinitialized.

Resolving the problem

Clear the OSGI cache using the following instructions:

1. Stop WebSphere Application Server if it is running.
2. From the was_profile_root/bin directory run the osgiCfgInit.sh script. For example:
- cd /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/bin
- ./osgiCfgInit.sh
3. Start WebSphere Application Server.

Note: Depending on where WebSphere Application Server is installed, the path may be different from the example above.


Product Alias/Synonym

IMS

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere IP Multimedia Subsystem Connector

Software version:

6.1, 6.2

Operating system(s):

AIX, Linux Red Hat - iSeries, Linux Red Hat - pSeries, Linux SUSE - iSeries, Linux SUSE - pSeries

Reference #:

1296482

Modified date:

2012-02-10

Translate my page

Machine Translation

Content navigation