Weblogic 12c Deployment Fails With SIP Exceptions (Doc ID 1543695.1)

Last updated on AUGUST 09, 2017

Applies to:

Oracle WebLogic Server - Version 12.1.1.0 and later
Information in this document applies to any platform.

Symptoms

Customer report a problem deploying an ear application in WebLogic 12c when the SIP container is enabled for the domain. In config.xml you can see the SIP components:

<custom-resource>
<name>sipserver</name>
<target>AdminServer</target>
<descriptor-file-name>custom/sipserver.xml</descriptor-file-name>
<resource-class>com.bea.wcp.sip.management.descriptor.resource.SipServerResource</resource-class>
<descriptor-bean-class>com.bea.wcp.sip.management.descriptor.beans.SipServerBean</descriptor-bean-class>
</custom-resource>

When trying to deploy through console, we cannot deploy the application on top of 12c. The deploy fails after clicking next in the admin GUI with:

Messages
Message icon - Error Unable to access the selected application.
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error Unable to resolve deadlock in factory claims
Message icon - Error Unable to resolve deadlock in factory claims

In server logs, we can see as below:

####<Apr 4, 2013 9:34:15 AM BST> <Info> <Health> <v445-tvp540-b> <AdminServer> <weblogic.GCMonitor> <<WLS Kernel>> <> <> <1365064455562> <BEA-310002> <52% of the total memory in the server is free.>
<Apr 4, 2013 9:35:10 AM BST> <Error> <J2EE> <BEA-160233> <Unable to identify module type>
<Apr 4, 2013 9:35:10 AM BST> <Error> <J2EE> <BEA-160228> <AppMerge failed to merge your application. Merge again with the -verbose option for more details. See the error message(s) below.>
####<Apr 4, 2013 9:35:10 AM BST> <Error> <J2EE> <v445-tvp540-b> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1365064510472> <BEA-160233> <Unable to identify module type>
####<Apr 4, 2013 9:35:10 AM BST> <Error> <J2EE> <v445-tvp540-b> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1365064510481> <BEA-160228> <AppMerge failed to merge your application. Merge again with the -verbose option for more details. See the error message(s) below.>

<Apr 4, 2013 9:36:39 AM BST> <Error> <J2EE> <BEA-160233> <Unable to identify module type>
<Apr 4, 2013 9:36:39 AM BST> <Error> <J2EE> <BEA-160228> <AppMerge failed to merge your application. Merge again with the -verbose option for more details. See the error message(s) below.>
####<Apr 4, 2013 9:36:39 AM BST> <Error> <J2EE> <v445-tvp540-b> <AdminServer> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1365064599149> <BEA-160233> <Unable to identify module type>
####<Apr 4, 2013 9:36:39 AM BST> <Error> <J2EE> <v445-tvp540-b> <AdminServer> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1365064599235> <BEA-160228> <AppMerge failed to merge your application. Merge again with the -verbose option for more details. See the error message(s) below.>

To reproduce you only need to create a new domain with "Basic WebLogic SIP Server Domain - 12.1.1.0 [wlserver_12.1] [2] x" selected during the installation.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms