After upgrade to DevTest 7.2 virtual services are failing
search cancel

After upgrade to DevTest 7.2 virtual services are failing


Article ID: 245092


Updated On:


Service Virtualization


After upgrade to DevTest 10.7 all virtual services are failing on VSE server.

Will attach logs from vse and registry.

Error from vse logs:

(13:53) [main] ERROR com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl - Could not load virtual service 'DETERMINATION 4'.
com.itko.lisa.test.TestDefException: Could not stage: Problem preparing the test case: Unable to preread service image named //DevTest/lisatmp_10.7.2/lads/D5D83B/DETERMINATION.vsi
 at com.itko.lisa.coordinator.CoordinatorImpl.stageModelArchive( ~[lisa-core-10.7.2.jar:?]
 at com.itko.lisa.coordinator.VirtualServiceCoordinator.<init>( ~[lisa-virtualize-10.7.2.jar:?]
 at com.itko.lisa.coordinator.VirtualServiceImpl.createVSCoordinator( ~[lisa-virtualize-10.7.2.jar:?]
 at com.itko.lisa.coordinator.VirtualServiceImpl.<init>( ~[lisa-virtualize-10.7.2.jar:?]
 at com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.loadInitialServices( [lisa-virtualize-10.7.2.jar:?]
 at com.itko.lisa.coordinator.VirtualServiceEnvironmentImpl.main( [lisa-virtualize-10.7.2.jar:?]
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_232]
 at sun.reflect.NativeMethodAccessorImpl.invoke( ~[?:1.8.0_232]
 at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:1.8.0_232]
 at java.lang.reflect.Method.invoke( ~[?:1.8.0_232]
 at com.exe4j.runtime.LauncherEngine.launch( [i4jruntime.jar:?]
 at com.exe4j.runtime.WinLauncher$ [i4jruntime.jar:?]





Release : 10.7

Component : DevTest Virtual Service


VSM has customer logging Adapters


VSM has customer logging Adapters and code that uses lower versions of log4j.

Dev Suggestion:   

You should exclude Log4j 1.x jars from your custom code and upgrade to log4j 2.x. Based on the implementation, you should consider adding the appropriate logging adapters and API jars.
Please do not add log4j-slf4j-impl 2.x. 
Unfortunately, we won't be able to support or help in upgrading the logging framework for your custom code to work. You should upgrade based on the migration guide provided by Log4j.