Service Virtualization

HI,

Every time when i am accesing CA DevTest, it connects for sometime and then hangs for a while and again ask to re-connect the registry

when looked to the registry server, it show's java.lang.outOfMemoryError (java heap space). & some singleton Error.

Could anyone please help me in understanding the issue and the solution for same.

PFB screenshot:

How much memory does the machine the Registry is running on have?

What other components are also running on this machine?

Do you have any Java options specified in the Registry.vmoptions or RegistryService.vmoptions files?

My Machine Ram is 8GB
Along with registry server, we are also running Dashboard server and VSE server
Sry, your third question didn't understood..

Sabir,

In the link below, you will find how you can increase the heap size with the Registry.

Memory Settings - DevTest Solutions - 10.1 - CA Technologies Documentation 

As Marcy mentioned above, if you have memory available, you can increase the Registry heap size to 1G by adding the following line to the Registry.vmoptions or RegistryService.vmoptions file:

-Xmx1G

The vmoptions file you want to change needs to have the same name of the executable file you are using to start the Registry.

Hope it helps,

Heloisa

Thanks guys for your valauable suggestion, but still i am facing the issue

Now i am unable to access DevTest, registry tries to connect and show's timeOut error
But now, when looking to logs. its not showing memory error, its showing "Singleton "

PFB:

This screen shot is showing the Registry is up.  The last message is info only.

Now Start your Portal Service.

Once the Portal is up, start Broker (If using CAI), Coordinator, Simulator and VSE is needed.

Then try to connect with your Workstation to the Registry.

I will surely try this, but could you please elaborate why we need to start our portal service, coordinator and simulator as of now I am only dealing with virtual services which I already had deployed in VSE.

As per my knowledge, please correct me if am wrong, if we want to work with virtual services then we only need to start our dashboard service or server, registry service and VSE service.

Thanks for your time marcy.. 

No need to start Broker, if not using CAI, no need to start Coordinator and Simulator if not running anything from Application Test.  The Portal needs to be started if you want to view any of the Virtual Services deployed to the VSE.

Ok...noted

I will try this

Actually what we used to do this

After connecting to Devtest workstation, we click on server console then it redirects to VSE manager where we can see our running VS and do further modifications in VS through VSM AND VSI editor and again redeploy it and test.

But now since long i am facing connecting to registry issue, we are fail to modify any of our VS.

Please suggest some better option.

Thanks

Questions:

1. Are you going to an external database?  If so, what database and version?  Is it in the same data center as your DevTest components?

2. How much disk space is free on the machine where your DevTest Server components are running?

3. Is your Workstation running in the same machine as your Server?  If not, what is the RTT between the Workstation and Registry, do a ping to the Registry from your Workstation.

Answers-

1) No, as of now we are working on SOAP based webservices...No external database

2) Around 4 GB

3) No, I am having a dedicated machine (RDP)where all Devtest components are running and I am connecting this machine from another machine using its IP.

Actually, just now I have renewed the licence

Previously it was all working smoothly.

I think it might be because of my licence.

Thanks Marcy,

Its all working smoothly,

i was wrongly increasing the size in vmoptions.

Thanks for your help