AnsweredAssumed Answered

Why does the wrong JDBC Virtual Service match on the same agent

Question asked by Hyper10n on May 5, 2016
Latest reply on Feb 13, 2017 by fulri02

I have 2 JDBC agent based virtual services:

Both the VSM's have 2 differnent JDBC protocol url_pattern values:

jdbc:oracle:thin:@\(DESCRIPTION=\(ADDRESS=\(PROTOCOL=TCP\)\(PORT=1526\)\(HOST=lneaid01\)\)\(CONNECT_DATA=\(SID=WMESBTS2\)\)\);user=MONITOR_OWN

jdbc:oracle:thin:@\(DESCRIPTION=\(ADDRESS=\(PROTOCOL=TCP\)\(PORT=1521\)\(HOST=172\.22\.25\.105\)\)\(CONNECT_DATA=\(SID=DOMSRPST\)\)\);user=eai_pof_interface

 

Yes, they both are making use of the same agent deployed on the same webmethods integration sever.

 

For some reason, when I deploy both these VSM's, only the Virtual Service that I deployed last gets matched on.

This means that for the tests that rely on Virtual Service Number 1 do not work because the Virtual Service simply returns NO_MATCH.

 

My understanding was that agent based matching relies on a match for the url_pattern, especially:

HOST

PORT

DB SID

user

 

Does anybody have any idea about this?

 

Thanks

Outcomes