Saving an object causes AWI to freeze up

book

Article ID: 140425

calendar_today

Updated On:

Products

CA Continuous Delivery Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

When saving an object in AWI, the following error pops up:

Error during XRequest com.uc4.communication.requests.SaveObject
Hide Details(Stacktrace)
Error during XRequest com.uc4.communication.requests.SaveObjectcom.uc4.ecc.backends.exceptions.AutomationEngineAPIException
(No Message)java.nio.BufferOverflowException
java.nio.HeapByteBuffer.put(HeapByteBuffer.java:206)
com.uc4.communication.Connection.sendToCP(Connection.java:1347)
com.uc4.communication.Connection.send(Connection.java:1318)
com.uc4.communication.Connection.send(Connection.java:1176)
com.uc4.communication.Connection.sendRequestAndWait(Connection.java:1443)
com.uc4.webui.api.connection.AEConnectionAdapter.sendRequestAndWait(AEConnectionAdapter.java:53)
com.uc4.ecc.backends.util.APICallHelper.sendRequestAndWait(APICallHelper.java:46)
com.uc4.ecc.backends.impl.dataservice.request.RequestService.lambda$sendAndWait$56(RequestService.java:65)
com.uc4.ecc.framework.core.async.VaadinSessionLockUtil.reportLock(VaadinSessionLockUtil.java:89)
com.uc4.ecc.backends.impl.dataservice.request.RequestService.sendAndWait(RequestService.java:65)
com.uc4.ecc.backends.impl.dataservice.request.RequestService.sendAndWait(RequestService.java:85)
com.uc4.ecc.backends.dataservice.request.IRequestService$pbryglu.sendAndWait(Unknown Source)
com.uc4.ecc.backends.impl.dataservice.object.save.Save.saveObject(Save.java:18)
com.uc4.ecc.backends.impl.dataservice.object.save.Save.trySaveObject(Save.java:31)
com.uc4.ecc.backends.impl.dataservice.object.ObjectService.trySaveObject(ObjectService.java:715)
com.uc4.ecc.backends.dataservice.object.IObjectService$pbryglu.trySaveObject(Unknown Source)
com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.save(UC4ObjectPresenter.java:707)
com.uc4.ecc.ae.commons.content.uc4objectview.UC4ObjectPresenter.lambda$initSavingRequestCoordinator$202(UC4ObjectPresenter.java:783)
com.uc4.ecc.framework.core.async.BaseRequestCoordinator$1$1.call(BaseRequestCoordinator.java:226)
com.uc4.ecc.framework.core.pool.ContextAwareExecutorService$CallableImplementation.call(ContextAwareExecutorService.java:72)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)

Cause

Corrupted object

Environment

Release : 12.2

Component : AUTOMATION ENGINE

Resolution

Please delete the object and re-create it from scratch. Most likely, the object is corrupted.

If after the object is re-created, the issue is still present, create a case with support and do the following:

1. After creating a job from scratch, set up the following trace (after thinking about it, I really want to see the Tomcat trace since the error is very specific to AWI – saving with them. That will require Tomcat restart)

            1.) Modify your uc4config.xml for AE Client Trace:

            -- Located at <Apache Tomcat Installation>/webapps/<ECC Name>/config/uc4config.xml

            Change the line reading:

            <trace count="10" xml="0"></trace>

            to

            <trace count="10" xml="3"></trace>   

            2.) Modify your logback.xml for Tomcat Trace:

            -- Located at <Apache Tomcat Installation>/webapps/<ECC Name>/config/logback.xml

             Change the line reading:

            <root level="INFO">

            to

            <root level="TRACE">

            3.) Backup your current Tomcat log directory (<Apache Tomcat Installation>/logs) in case the error is not easily reproducible.

            4.) Remove contents of log directory.

            5.) Restart the Tomcat Server.

            6.) Enable trace on WP and CPs (each individual CP) with TCP/IP=2, DB=4 via the UI System Overview.

            7.)  OPTIONAL step, only is ARA workflow if involved. 

             Set up the trace on ARA:

            Enabling debug for ARA log

            Navigate to where your ARA is installed, and go to the "Config" folder

            C:\inetpub\wwwroot\WEBUI\config    (please note your WEBUI folder/path can varies depending on where you installed it on your system)

            Open a file call "log4net.config" and search for this following section: 

                <root>

                    <!-- Set this to "WARN" for productive use -->

                    <!--[CHECK]-->

                    <priority value="WARN" />

                    <appender-ref ref="standardAppender" />

                    <appender-ref ref="trace" />

                    <level value="WARN" />

                    <appender-ref ref="XMLAppender" />

                </root>

             

            Change the:

            <priority value="WARN" />

            <level value="WARN" />

             

            TO

            <priority value="DEBUG" />

            <level value="DEBUG" />

             

            The logs will generated at:        

            C:\inetpub\wwwroot\WebUI\logs             

            Current log for today will be call:

            - log.txt

            old log file are call:  log.txt.timestamp

 -Another ARA tracing that tracks every XML sent to AE (WebUI > customer.config):

            a. <CustomerAppSettings>

                        <!--TraceLevel: 9: debug; 0: production-->

                        <add key="AutomationEngine.TraceLevel" value="0" />

            >>You can set it to TraceLevel=10.

            >>You don't need to restart IIS.

8.) Replicate the issue.

 9.) Stop the Tomcat Server.

 10 .) Change the values back to original settings in steps 1, 2, and 6 and 7

 11.) Zip the contents of the log directory, WP, CP logs, WP, CP trace files, ARA logs, XML export of the workflow with references and specify the name of task within the workflow you are having issues with, and send to Automic Support.