Service Virtualization

Hi, 

I have a test suite with 6 test cases and have marked 1 test case as "Startup Test" which is basically a shell script test case that loads data into DB. If my Startup test fails I will not execute the others. When I added my shell script test case as Startup it fails as "There was a problem while connecting to {{host}}:22". Same test case works if I don't add to Startup Test. What could be the reason.

What error are you seeing in the Simulator logs? please send the entire stack trace.  

Issue is when I trigger the job from Jenkins. If I stage locally it works fine. DevTest Registry is on docker container. This is what I see on Docker Simulator

2017-06-08T15:02:11.656643810Z Jun 08, 2017 3:02:11 PM com.itko.activemq.ActiveMQMessageConsumer$4 run
2017-06-08T15:02:11.656668369Z SEVERE: ID:3456c1360dc0-43175-1495478225427-5:771448:1:1 failed to delivered acknowledgements
2017-06-08T15:02:11.656672717Z com.itko.jms.JMSException: Channel was inactive for too long: 
2017-06-08T15:02:11.656676242Z at com.itko.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:62)
2017-06-08T15:02:11.656679700Z at com.itko.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1278)
2017-06-08T15:02:11.656682989Z at com.itko.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:1270)
2017-06-08T15:02:11.656686116Z at com.itko.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1863)
2017-06-08T15:02:11.656689349Z at com.itko.activemq.ActiveMQSession.sendAck(ActiveMQSession.java:2029)
2017-06-08T15:02:11.656698396Z at com.itko.activemq.ActiveMQMessageConsumer$4.run(ActiveMQMessageConsumer.java:722)
2017-06-08T15:02:11.656701954Z at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2017-06-08T15:02:11.656705690Z at java.util.concurrent.FutureTask.run(FutureTask.java:266)
2017-06-08T15:02:11.656724825Z at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2017-06-08T15:02:11.656734420Z at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
2017-06-08T15:02:11.656737500Z at java.lang.Thread.run(Thread.java:745)
2017-06-08T15:02:11.656740607Z Caused by: com.itko.activemq.transport.InactivityIOException: Channel was inactive for too long: 
2017-06-08T15:02:11.656743571Z at com.itko.activemq.transport.InactivityMonitor.oneway(InactivityMonitor.java:247)
2017-06-08T15:02:11.656746435Z at com.itko.activemq.transport.TransportFilter.oneway(TransportFilter.java:85)
2017-06-08T15:02:11.656749206Z at com.itko.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:104)
2017-06-08T15:02:11.656752038Z at com.itko.activemq.transport.MutexTransport.oneway(MutexTransport.java:40)
2017-06-08T15:02:11.656754823Z at com.itko.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
2017-06-08T15:02:11.656757718Z at com.itko.activemq.ActiveMQConnection.doAsyncSendPacket(ActiveMQConnection.java:1276)
2017-06-08T15:02:11.656760931Z ... 9 more
2017-06-08T15:02:11.656763654Z

This is what I see on Registry: When I removed the Startup it worked fine from Jenkins. All test cases ran in serial:

Thu Jun 08 03:54:23 UTC 2017 : Execution failed because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error Code Value = 3. Plaintext connection attempt from an SSL enabled client?
org.apache.derby.impl.drda.DRDAProtocolException: Execution failed because of a Distributed Protocol Error: DRDA_Proto_SYNTAXRM; CODPNT arg = 0; Error Code Value = 3. Plaintext connection attempt from an SSL enabled client?
at org.apache.derby.impl.drda.DRDAConnThread.throwSyntaxrm(Unknown Source)
at org.apache.derby.impl.drda.DDMReader.readDssHeader(Unknown Source)
at org.apache.derby.impl.drda.DRDAConnThread.exchangeServerAttributes(Unknown Source)
at org.apache.derby.impl.drda.DRDAConnThread.sessionInitialState(Unknown Source)
at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)

Jagadish,  is it possible for you to open a Support ticket.?  We could resolve this issue in a webex.  

Thanks

Shiney. 

Resolved in Support ticket  00766700