Lisa Invoke API SuiteCoordinatorClient cannot be cast to com.itko.lisa.testing.StagedSuite Error

[Saikiran Garapati]

Hi Team,

We have suite which consists of 148 Test Cases, we are executing that suite through lisa-invoke API, when we trigger gitlab job which will trigger the lisa invoke URL, Entire suite is not executing in between suite execution is aborting. So created MARI file for the same suite and tried to execute the same from post man but getting the below error.

Could any body help on this issue. 

Divided the Test Suite in to 7 parts and ran a suite it is working fine but we want to entire suite to be execute in one run. Please let us know any solution we have.

Is there any limitation of Test cases for the suite?

https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxx.org:xxxx/lisa-invoke/runMar?marOrMariPath=/xxxx/xxxx/xxxxx/xxxxx/xxxxxxx/Tests/Suites/xxxxx.mari

<?xml version="1.0" encoding="UTF-8"?>
<invokeResult>
<method name="RunMar">
<params>
<param name="marOrMariPath" value="/xxxx/xxxx/xxxxx/xxxxx/xxxxxxx/Tests/Suites/xxxxx.mari" />
<param name="callbackKey" value="AE2A04C7FEBB11EAAC1000505687F03E" />
</params>
</method>
<status>ERROR</status>
<result>
<status>RUNNING</status>
<message>An error occured in 'runMar'. Message: com.itko.lisa.net.SuiteCoordinatorClient cannot be cast to com.itko.lisa.testing.StagedSuite
Stack: java.lang.ClassCastException: com.itko.lisa.net.SuiteCoordinatorClient cannot be cast to com.itko.lisa.testing.StagedSuite
at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runMarNewSchool(LaunchLisaTestHelper.java:1028)
at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.runMar(LaunchLisaTestHelper.java:959)
at com.itko.lisa.invoke.webapp.LaunchLisaTestHelper.invokeLisaMar(LaunchLisaTestHelper.java:925)
at com.itko.lisa.invoke.webapp.InvokeLisaMarServlet.service(InvokeLisaMarServlet.java:98)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:668)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:845)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1689)
at com.ca.devtest.http.XSSFilter.doFilter(XSSFilter.java:55)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1668)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:581)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1180)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1112)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
at org.eclipse.jetty.server.Server.handle(Server.java:524)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:253)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:202)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:745)</message>
</result>
</invokeResult>


------------------------------
Thanks & Regards,
Saikiran Garapati.

------------------------------

[Vaibhav Jain]

Hi Saikiran,

In your test suite, Are you executing the testcases in sequential or parallel manner?

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Saikiran Garapati]

Hi Vaibhav,
Thanks for the reply. We have to run in parallel only as we have more Test cases and if we mentioned serial, Suite execution is taking more than two hours So we are running in Parallel Run Mode only.

[Vaibhav Jain]

Hi Saikiran,

You can try to add more simulators and test once, as may be existing simulator may not be able to create multiple threads as per your expectations.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Saikiran Garapati]

okay Thank you Vaibhav. I will  try this option and let you know. 

[Saikiran Garapati]

Hi Vaibhav,

Created 8 Simulators but still purpose is not served. Suite is aborting or coming out of the execution.

For First 20 or 30 TCs it is executing and after wards it is coming out giving count as <pass count="11" />
<fail count="134" />
<abort count="3" />

Tried different options in Staging document with Percent distribution to each simulator and round robin also but no luck

Could you please advise what are all other options we have to make this big suite to run in single shot?


In coordinator i am able to see following logs:

[Number of polling threads: 561] ERROR com.itko.lisa.net.Transporter - We will attempt to resend the message one more time (and only one more time)
2020-10-01 05:59:31,587Z (22:59) [Number of polling threads: 588] ERROR com.itko.lisa.net.Transporter - Encountered an Exception sending the message RemoteExecBase [target=ssl://xxxxxxxxxxxxxxxxx.unix.gsm1900.org:2015/Sim_B4922EA603A811EBAEAE00505687F03E, code=getStats, arguments=null, ret=null, async=false] to ssl://xxxxxxxxxxxxxxxxxx.unix.gsm1900.org:2015
com.itko.jms.IllegalStateException: The Session is closed
at com.itko.activemq.ActiveMQSession.checkClosed(ActiveMQSession.java:722)
at com.itko.activemq.ActiveMQSession.configureMessage(ActiveMQSession.java:710)
at com.itko.activemq.ActiveMQSession.createObjectMessage(Acti

[Vaibhav Jain]

Have you created 8 simulators on same machine or on 8 different machines ?

For such bulky executions, it is recommended to have separate machines for coordinator and simulator instances.

Other option is to create modular suites for your test cases and execute them in sequential manner.

Thanks

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------

[Saikiran Garapati]

Hi Vaibhav,

I have configured 8 simulators in single system as we have some limitations. As you suggested we are Dividing the suites and executing.
Thank you very much for your suggestions.

Thanks & Regards,
Saikiran Garapati.

[Vaibhav Jain]

Thanks for the update.

------------------------------
Regards,
Vaibhav Jain
Capgemini
------------------------------