Small ECO w/ Weblogic Timeout Exception

I was wondering if anyone’s ran into this before.  We’re experiencing an increasing number of ECOs and MCOs that can’t release.  They run up against our 900 second weblogic timer. 
Oracle website just says to not put so many affected items but in our case we’re talking about a fraction of what we’ve seen Agile do with other ECOs and MCOs.  If anyone knows what’s causing this issue or if increasing the weblogic timer will work, please let me know.  I’ve seen this even going as small as an MCO with a few affected items being unable to be released.  

The specific APIException is:

java.rmi.RemoteException: EJB Exception:; nested exception is:
java.rmi.RemoteException: EJB Exception: ; nested exception is:
com.agile.util.exception.CMDebugException: Transaction BEA1-2157941ABC2E325E73A5 not active anymore. tx status = Rolled back. [Reason=weblogic.transaction.internal.TimedOutException: Transaction timed out after 899 seconds
BEA1-2157941ABC2E325E73A5]

Agile Angel Asked on January 24, 2018 in IT and Networking.

The specific stack trace, if anyone’s interested and knows what might help:

{com.agile.api.pc.APIObject.createError(APIObject.java:131), com.agile.api.pc.RouteObject$ChangeStatus932Action.doSdkAction(RouteObject.java:2536), com.agile.api.common.SDKAction.run(SDKAction.java:23), com.agile.api.common.Security.doAs(Security.java:59), com.agile.api.common.Security.doAs(Security.java:109), com.agile.api.pc.RouteObject.doChangeStatus932(RouteObject.java:976), com.agile.api.pc.RouteObject.changeStatus(RouteObject.java:960), sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method), sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:606), org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:86), groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:230), groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:912), groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:756), org.codehaus.groovy.runtime.InvokerHelper.invokePojoMethod(InvokerHelper.java:766), org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:754), org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:170), Mass Update – Change Objects.invokeScript(Mass Update – Change Objects:21), sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method), sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57), sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43), java.lang.reflect.Method.invoke(Method.java:606), org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:86), groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:230), groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:912), groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:756), groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:672), groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:44), groovy.lang.Script.invokeMethod(Script.java:78), com.agile.agileDSL.ScriptMgr.ScriptMgr.executeMethod(ScriptMgr.java:127), com.agile.agileDSL.ScriptMgr.ScriptMgr.execute(ScriptMgr.java:33), com.agile.agileDSL.ScriptMgr.AgileDSLMgrSessionBean.invokePostAction(AgileDSLMgrSessionBean.java:64), com.agile.agileDSL.ScriptMgr.AgileDSLMgrSessionBean_3nrrgd_EOImpl.__WL_invoke(Unknown Source), weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:32), com.agile.agileDSL.ScriptMgr.AgileDSLMgrSessionBean_3nrrgd_EOImpl.invokePostAction(Unknown Source), com.agile.soa.event.handler.ScriptInitiator.invoke(ScriptInitiator.java:94), com.agile.soa.event.listener.PXListener$1.run(PXListener.java:106), weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321), weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120), weblogic.security.Security.runAs(Security.java:41), com.agile.admin.vendor.weblogic.WeblogicServerAdapter.doAs(WeblogicServerAdapter.java:267), com.agile.soa.event.listener.PXListener.onMessage(PXListener.java:144), weblogic.ejb.container.internal.MDListener.execute(MDListener.java:585), weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:488), weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:385), weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4659), weblogic.jms.client.JMSSession.execute(JMSSession.java:4345), weblog…

on January 24, 2018.
Add Comment
4 Answer(s)

You can try increasing the timeout of change session bean in weblogic-ejb-jar.xml inside application.ear/pc.jar/META-INF

RE: Small ECO w/ Weblogic Timeout Exception

Agile Professional Answered on June 1, 2018.

Thank you Swagoto,
Yes, I was tempted to go do that but knowing that we were pointlessly using BOMs with as many as 80 levels(!),  we decided to fix that problem instead.

on June 1, 2018.

hi @Swagoto,

Can you please provide steps that how can we update application.ear file.

As per now I reached to agiledomain\applications directory where application.ear file available but i dont able to transfer this file to my local machine.

So how could i extract and update required file  and again repack Ear file.

Please help

 

Thanks

Priyanka

 

on June 27, 2019.
Add Comment

Hi,
Is there any custom JAva or Groovy PX that runs during the release of the ECO/MCO? I see in the stacktrace this kind of “Mass Update – Change Objects” that seems not to be an Agile one.
In case please share the code or have a look at it in order to check if there is any issue.

Agile Angel Answered on January 25, 2018.
Add Comment
Agile Angel Answered on January 25, 2018.
Add Comment

We did figure out, just for anyone’s knowledge, that when Agile goes through the ECO/MCO release process, it conducts a BOM Explosion report (use Oracle SQL) to update the BOM object numbers (i.e., BOM serial number entries).  We were releasing MCOs and ECOs with 20+ BOM levels.  Because this took over 15 minute for us, weblogic failed.

Agile Angel Answered on February 8, 2018.
Add Comment

Your Answer

By posting your answer, you agree to the privacy policy and terms of service.