soa-infra not Starting (Changing to Running State) and other Issues after Upgrading SOA Suite 11g to a Later Patch Set
(Doc ID 1330224.1)
Last updated on JANUARY 08, 2024
Applies to:
Oracle SOA Suite - Version 11.1.1.4.0 and laterOracle Service Bus - Version 11.1.1.9.0 to 11.1.1.9.0 [Release 11g]
Information in this document applies to any platform.
Symptoms
This note is relevant for the following cases:
1.- After upgrading from 11.1.1.3 to 11.1.1.4 the soa_infra application won't change into a Running state.
2.- Having a composite deployed on the default partition then undeployed this composite after that deployed the same composite to another partition there is a message that specifies a different target namespace for this task component. This behavior occurs even if the partition was deleted.
3.- Flow trace information for all instances of BPEL processes fail to load from EM, i.e. when attempt to open Instance Information from EM console for any executed BPEL process the below exception is show "Unable to display Flowtrace due to exception while initializing object, Please review logs for detailed information"
4.- Found a similar stacktrace:
<Jun 13, 2011 9:01:29 AM PDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'soa-infra' due to error weblogic.application.ModuleException: Exception preparing module: EJBModule(fabric-ejb.jar)
Unable to deploy EJB: FacadeFinderBean from fabric-ejb.jar:
[EJB:010101]A mismatch exists between the bean code and generated code.FacadeFinderBean(Application: soa-infra, EJBComponent: fabric-ejb.jar) . Please rerun appc on the bean code. The error was java.lang.NoSuchFieldException: md_eo_getApplicationName
at java.lang.Class.getField(Class.java:1520)
at weblogic.ejb.container.deployer.BeanInfoImpl.setObjectMDField(BeanInfoImpl.java:910)
at weblogic.ejb.container.deployer.BeanInfoImpl.setMDField(BeanInfoImpl.java:867)
at weblogic.ejb.container.deployer.BeanInfoImpl.setMethodDescriptor(BeanInfoImpl.java:794)
...
weblogic.application.ModuleException: Exception preparing module: EJBModule(fabric-ejb.jar)
----------
5.- Having issue to access or deploy SOA composite, EM Console seems freeze or just show a blank page, and get a similar stacktrace in the Admin server log:
[WARNING] [ADF_FACES-60099] [oracle.adfinternal.view.faces.renderkit.rich.RegionRenderer] [tid: [ACTIVE].ExecuteThread: '24' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: jkorn] [ecid: 11d1def534ea1be0:-1bc47d44:13be4402b32:-8000-0000000000000462,0] [APP: em] The region component with id: emTemplate:fmwRegion has detected a page fragment with multiple root components. Fragments with more than one root component may not display correctly in a region and may have a negative impact on performance. It is recommended that you restructure the page fragment to have a single root component.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |