java.rmi.RemoteException on method getLifetimeTransactionCount exception when a new VSE service is added to a Registy.
search cancel

java.rmi.RemoteException on method getLifetimeTransactionCount exception when a new VSE service is added to a Registy.

book

Article ID: 372777

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

When trying to add a second VSE to a Registry running on another server, Portal does not display any of the Virtual Service Environments. 

we are getting the below error..
- Caused by: java.rmi.RemoteException: Timeout (60,000 ms, actual wait 60,000 ms) on server object ssl://hostname:2013/VSE_01 on method getLifetimeTransactionCount
2024-06-24T21:52:15,041Z (14:52) [qtp1789256070-230] ERROR System.err                     -     at com.itko.lisa.net.Transactor.transact(Transactor.java:109)
2024-06-24T21:52:15,041Z (14:52) [qtp1789256070-230] ERROR System.err                     -     at com.itko.lisa.net.ClientBase.transact(ClientBase.java:353)

Caused by: org.grails.web.converters.exceptions.ConverterException: Error converting Bean with class com.ca.sv.buildersession.VseServerHalResource
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:1.8.0_411]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:1.8.0_411]
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:1.8.0_411]

Environment

DevTest 10.7.2 and up 

 

Cause

The DB connection made from VSE to get LifeTime Tx count failed as the VSE server was not allowed to access the DB Server

Resolution

Work with your network Admins to have the firewall opened up for DB access on the VS environment. Once this is done, the VSE will appear on Portal without any issues.