Default VSE error

[John Sebastian]

Hi,

 

VSE service stopped and I try to start I'm getting this error.

 

 

P.S. I have multiple VSE set up on the machine, all looks good except the default one...

 

 

Thanks,

John

[Mike_Gavaghan]

Hi John,

 

We'd need to see the log file to find the root cause.

 

Thanks.

 

--Mike

[John Sebastian]

Thanks Mike, for your quick response. How do I attach log file here?

 

Thanks,

John

[John Sebastian]

Thanks Mike, for your quick response. I'm attaching the latest vse.log.

 

Thanks,

 

John Sebastian | Service Virtualization, Testing Centre of Excellence | Sun Life Financial<http://www.sunlife.com/>

Direct: 416-753-4468 | Extn: 333-4468 | 2255 Sheppard Ave E, Suite A135, North York, ON M2J 4Y1

Life's brighter under the sun

Attachment(s)

vse.log.zip   129 KB 1 version

[Mike_Gavaghan]

I see

 

Timed out trying to connect to test registry tcp://CL11106:2010/Registry

 

Is that the correct Registry URL?

 

--Mike

[John Sebastian]

Hi Mike, thats because, the Registry service is also being stopped during the time....

[Mike_Gavaghan]

Hi John,

 

That's your problem, then.  If the Registry is down, VSE will try repeatedly (about once per second) to reconnect.  After a awhile, it gives up and shuts down.  It's indicated in your log file by repeated connection failures followed by:

 

ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Cannot register with the DevTest Registry [Timed out trying to connect to test registry tcp://CL11106:2010/Registry]

 

--Mike

[Marcy Nunns]

Are you just using the defaults for the vseName, Port, and log name?

 

Can you verify all your other VSEs are starting with unique names, ports and log fie names?

 

Try this:

Bring up a command prompt.

cd to your DEVTEST_HOME/bin folder

run VirtualServiceEnvironment.exe

screenshot what it shows and post here. 

[John Sebastian]

Hi Marcy,

 

All the VSE parameters are unique. I have added a new one today (the last one), I'm not sure if that has caused the issue.

Registry and VSE services are stopping alternatively.

 

Is there any limitations on creating multiple VSE's ?

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:2013/VSE
-Dlisa.net.8.port=2013
-DLISA_LOG=vse.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20131/VSE_GnCAS
-Dlisa.net.8.port=20131
-DLISA_LOG=vse01.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20132/VSE_IIDAS
-Dlisa.net.8.port=20132
-DLISA_LOG=vse02.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20133/VSE_Scorpion
-Dlisa.net.8.port=20133
-DLISA_LOG=vse03.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20134/VSE_TCoE_Automation
-Dlisa.net.8.port=20134
-DLISA_LOG=vse04.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20135/VSE_DHS-Web
-Dlisa.net.8.port=20135
-DLISA_LOG=vse05.log

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:20136/VSE_MCoE
-Dlisa.net.8.port=20136
-DLISA_LOG=vse06.log

 

Thanks,

John

[Marcy Nunns]

John,

 

As long as your machine has the bandwidth, we have no limit on the number is VSEs on the same machine.

 

Just for grins, for the new VSE you added put this in the VirtualServiceEnvironmentService.vmoptions file:

 

-Dlisa.vseName=tcp://cl11106.sunlifecorp.com:2013/VSE_NEW
-Dlisa.net.8.port=2013
-DLISA_LOG=vse_new.log

 

Try to start and let me know the results.

 

~Marcy