Service Virtualization

Hello All,

I am facing issue while restarting RegistryService. Upon restarting, it is going to end state automatically. Please find lisa_agent logs below:

[LISA AGENT:BC][INFO][26953][1][main][Aug 8, 2017 11:11:09 AM] Connection to tcp://APPTUVIRTUAL055.machine.test.group:2009?daemon=true established...
[LISA AGENT:BC][INFO][26953][65][ActiveMQ Session Task][Aug 8, 2017 11:11:09 AM] Agent online: [ID: -461794262][NAME: LW:8770767@V6016826.Global.Lloydstsb.Com][IP: 10.17.26.130][MC: com.install4j.runtime.launcher.WinLauncher][PID: 10668]
[LISA AGENT:BC][INFO][26953][78][ActiveMQ Session: ID:apptuvirtual055.machine.test.group-55147-1502187069059-2:3:1][Aug 8, 2017 11:11:10 AM] Agent online: [ID: -1336617753][NAME: Sim:lisa-user@apptuvirtual055.machine.test.group][IP: 10.240.2.51][MC: com.install4j.runtime.launcher.Launcher][PID: 19518]
[LISA AGENT:BC][INFO][26953][78][ActiveMQ Session: ID:apptuvirtual055.machine.test.group-55147-1502187069059-2:3:1][Aug 8, 2017 11:11:10 AM] Agent online: [ID: 1250381846][NAME: VSE:lisa-user@apptuvirtual055.machine.test.group][IP: 10.240.2.51][MC: com.install4j.runtime.launcher.Launcher][PID: 31605]
[LISA AGENT:BC][WARN][26953][54][Agent Info Notifier][Aug 8, 2017 11:11:13 AM] Connection to Agent broker at tcp://APPTUVIRTUAL055.machine.test.group:2009?daemon=true was dropped... (com.itko.jms.IllegalStateException: The Session is closed)

While in RegistryService.vmoption file is given below:

-Dlisa.tmpdir=/opt/lisa/lisatmp_7.5.2
-Dlisa.registryName=tcp://APPTUVIRTUAL055.machine.test.group:2010/Registry
-Dlisa.net.3.port=2010
-Xms1024m
-Xmx2048m

Why it is not coming up any reason? Also I am seeing in lisa_agent logs it is showing 2009 port and vmoption it is 2010. Please help me urgently as it is stopping every activity.

Thanks..

Shivam Garg

Are you saying the Registy is stopping or the Agent is stopping. If the Registry is stopping, you will probably see better information by reviewing the Registry.log file.

-  Stop the DevTest Servers (VSE, Coordinator, Broker, Simulator, VSE, Registry, etc)

-  Remove or rename the Registry.log file located in /opt/lisa/lisatmp_7.5.2.

-  Try starting the Registry server - do not start any other servers.

-  If the Registry stops, open the Registry.log and let us know what you see there.

Unclear what you meant by agent has 2010 in the vmoptions. If you are referring to the value of -Dlisa.registryName.... that is OK. 

Hello Joel,

I have stopped all server and try to start only Registry but again same error. Registry.log file is not generating for today date and logs I am pasting is from lisa_agent log file.

[LISA AGENT:BC][INFO][9869][1][main][Aug 8, 2017 1:52:14 PM] Connection to vm://localhost established...
[LISA AGENT:BC][INFO][9869][55][ActiveMQ Session: ID:apptuvirtual055.machine.test.group-42874-1502196734256-2:2:1][Aug 8, 2017 1:52:14 PM] Agent online: [ID: -1003140348][NAME: Broker:lisa-user@apptuvirtual055.machine.test.group][IP: 10.240.2.51][MC: com.install4j.runtime.launcher.Launcher][PID: 9869]
[LISA AGENT:BC][INFO][9869][55][ActiveMQ Session: ID:apptuvirtual055.machine.test.group-42874-1502196734256-2:2:1][Aug 8, 2017 1:52:14 PM] Checking LISA Agent schema
[LISA AGENT:BC][INFO][9869][55][ActiveMQ Session: ID:apptuvirtual055.machine.test.group-42874-1502196734256-2:2:1][Aug 8, 2017 1:52:14 PM] Schema matches expected version (v2)
[LISA AGENT:BC][INFO][9869][1][main][Aug 8, 2017 1:52:14 PM] Connection to tcp://APPTUVIRTUAL055.machine.test.group:2009?daemon=true established...
[LISA AGENT:BC][WARN][9869][47][Stats Gathering Thread][Aug 8, 2017 1:52:17 PM] Connection to Agent broker at tcp://APPTUVIRTUAL055.machine.test.group:2009?daemon=true was dropped... (com.itko.jm

It is same error we are facing again and again.

please any furthur advise.

Thanks..

The agent logs may not provide the information we need to solve the issue. 

Our first objective is to create a Registry.log file so we can see more detailed information about what is happening to the Registry during start up.

Let's start with the following:

- If possible, can you provide the settings and directives the team is using in the RegistryService.vmoptions file? Or, Registry.vmoptions is not started as a service.

- Ensure that the lisatmp_7.5.2 directory has space available. You may have to ensure that /opt/lisa has available space.

- Ensure the license key has not expired

- In a separate post, you indicate a SQL connection is failing. It is unclear if this issue is linked to Registry starting.

Hello Joel,

In separate post, I have mentioned issue that is linked to different Registry. And for other things, I can check and provide you details. But can you guide me how to check weather licence got expired or not?

Thanks for looking into it.

Shivam Garg

Hello Joel,

Answers to your questions:

- /opt/lisa has 33G space free. Please find stats below. And lisatmp_7.5.2 is mounted on /opt/lisa. So it confirms that we have enough space.

[lisa-user@apptuvirtual055 lisa]$ df -h /opt/lisa
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/datavg-optlisalv
                       59G   24G   33G  42% /opt/lisa

- Setting ins RegisteryService.vmoption file as below. There is not any Registry.vmoption file only RegistryService.vmoption is there.

-Dlisa.tmpdir=/opt/lisa/lisatmp_7.5.2
-Dlisa.registryName=tcp://APPTUVIRTUAL055.machine.test.group:2010/Registry
-Dlisa.net.3.port=2010
-Xms1024m
-Xmx2048m

-Related to license key, I am not sure how to check from server. If you have any idea then let me know steps to check that.

Please check above things and let me know.

Cheers..

Shivam Garg

Hello Joel,

I have checked one more created during when I tried to restart Registry. It is giving some Licence informtion but I am not able to understand it. Addind file for your refrences to understand and let me know, what it says. I have removed confidential info from the tags.

’name>
<password></password>
<type>Server</type>
<licenseOptions>
<option>LEK</option>
<option>cbt</option>
<option>esbTesting</option>
<option>j2eeTesting</option>
<option>swingTesting</option>
<option>virtualService</option>
<option>vseLoad</option>
<option>webTesting</option>
<option>wsTesting</option>
</licenseOptions>
</license>
<license>
<domain>iTKO/LISA/LLoyds</domain>
<username>LLS_CA_ELA.group.Workstation</username>
<password></password>
<type>Server</type>
<licenseOptions>
<option>LEK</option>
<option>esbTesting</option>
<option>j2eeTesting</option>
<option>pathFinder</option>
<option>pathFinderDevConsole</option>
<option>pathFinderPro</option>
<option>pfCreateBaselineAssets</option>
<option>pfCreateDataAssets</option>
<option>pfCreateVSEAssets</option>
<option>pfManageCases</option>
<option>swingTesting</option>
<option>virtualService</option>
<option>vseLoad</option>
<option>webTesting</option>
<option>wsTesting</option>
</licenseOptions>
</license>
<serial></serial>
</LISALicenseGroup>
t<j2eeTesting>true</j2eeTesting>
    <swingTesting>true</swingTesting>
    <simulator>false</simulator>
    <coordinator>false</coordinator>
    <registry>true</registry>
    <cbt>true</cbt>
    <esbTesting>true</esbTesting>
    <LEK>true</LEK>
    <virtualService>false</virtualService>
    <pathFinder>true</pathFinder>
    <cvs>true</cvs>
    <vseLoad>false</vseLoad>
    <pathFinderPro>true</pathFinderPro>
    <pathFinderDevConsole>true</pathFinderDevConsole>
    <pfManageCases>true</pfManageCases>
    <pfCreateBaselineAssets>true</pfCreateBaselineAssets>
    <pfCreateVSEAssets>true</pfCreateVSEAssets>
    <pfCreateDataAssets>true</pfCreateDataAssets>
    <serial></serial>

</LISALicense>

Shivam,

If you are still facing this issue, please go ahead and open a support ticket.

Thank you,

Heloisa

Sure Heloisa. I will raise one and let you know. 

Hi Heloisa,

Please find case id 00812261. Please have look and help me in sorting out this issue.

Cheers..

Hi Shivam,

As we found out, this was due to a corrupt cvs monitor job mar file.

Following is the text from the closure notice of the case raised:-

Problem Description:
******************************
You were unable to successfully start your registry.

Environment:
******************************
• You are using LISA on release 7.5.2
• The environment is distributed running on Linux


Diagnostic Findings:
******************************
1. Running ./RegistryService start-launchd indicated a corrupted mar file. The registry access mar files when running CVS jobs

Resolution:
*****************************
A directory named "monitors" as created in the installation directory, and the contents of the cvsMonitors directory moved to the new directory.

The registry could then be started.

Since one or more of the monitor files are known corrupt, it is recommended that the cvs monitors be re-deployed from source.

Thank you so much Dav. I am very happy.