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]

No Files Were Attached
Matt Paulhus Agile Professional 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
3 Answer(s)

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.

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

Good question – it’s just a PX that attempts to release the ECO/MCO.  The code is simple and has worked on other changes.  Essentially it gets a change number as a scheduled event, defines next status as “released” and attempts to change status using the normal API (change.changeStatus()).  There’s a try block that’s catching the API Root Cause and stack trace as I’ve posted above.  
That’s why I ruled out the script itself having any issues. I’ve eliminated it down to where it’s not this script or any other script as I’ve disabled the one other one running against this event.  

The “Mass Update – Change Objects” is just a temp script at the moment running to try and release the troubling ECO/MCOs as a scheduled event.

<br /><p>IChange change = session.getObject(IChange.OBJECT_TYPE, "MCO06662")</p><p>IStatus released = (IStatus) change.getWorkflow().getStates(StatusConstants.TYPE_RELEASED)[0]</p><p>change.changeStatus(released, false, "Pushing to complete using automatic script", false, false, null, null, null, null, false)</p><br />

 

Is there anything else in the stack trace that seems unusual?  

I believe the error message when attempting as a web client user was “action did not complete within the stipulated time” (or something like that).

Matt Paulhus Agile Professional 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.

Matt Paulhus Agile Professional Answered on February 8, 2018.
Add Comment

Your Answer

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