AnsweredAssumed Answered

Virtual Service Details Cached

Question asked by JimCallaghan4454180 on May 15, 2014
Latest reply on Aug 1, 2014 by JimCallaghan4454180

Like • Show 0 Likes0
Comment • 4

Hi,

When I deploy a virtual service that has a Virtual Java Listener step with a JDBC protocol, I find that the changes that I make to the model are not picked up unless I deploy a new VS (i.e. one that has a different name).

This occurs even when I remove the VS from the environment (i.e. the folder in which the VS was deployed in the 'lads' folder is removed).

Can someone tell me whether the VS details are cached somewhere?

If so, is there a way to clear the cached values so that my changes are picked up without having to create a new VS?

BTW, we are using LISA 7.5 and the JDBC VS was created using the Pathfinder agent.

Regards, Jim

chaja22

May 20, 2014 10:05 PM

Correct Answer

jimcallaghan4454180:

Hi,

When I deploy a virtual service that has a Virtual Java Listener step with a JDBC protocol, I find that the changes that I make to the model are not picked up unless I deploy a new VS (i.e. one that has a different name).

This occurs even when I remove the VS from the environment (i.e. the folder in which the VS was deployed in the 'lads' folder is removed).

Can someone tell me whether the VS details are cached somewhere?

If so, is there a way to clear the cached values so that my changes are picked up without having to create a new VS?

BTW, we are using LISA 7.5 and the JDBC VS was created using the Pathfinder agent.

Regards, Jim

Hi Jim,

Do you get the same behavior when you right click on the .vsm and choose "Re-deploy to VSE..."? This should effectively update the virtual service to the latest version.

Could you clarify what you are doing when you remove the virtual service from the environment? I'm not sure what you are referring to with the lads folder.

Normally when I want to remove a VS from the VSE, I go into the VSE console through the web browser, right click on the VS in question, and select "Remove from the environment".

My final comment would be that when you virtualize JDBC using the agent, the agent is sent instructions on what to virtualize. So it might be possible that the agent is not receiving the updated virtual service. If it's not getting updates, then that should be filed as a support case (as the methods I described above should work).

Best,

-James

See the reply in context

No one else had this question

Outcomes

chaja22

May 20, 2014 10:05 PM

jimcallaghan4454180:

Hi,

When I deploy a virtual service that has a Virtual Java Listener step with a JDBC protocol, I find that the changes that I make to the model are not picked up unless I deploy a new VS (i.e. one that has a different name).

This occurs even when I remove the VS from the environment (i.e. the folder in which the VS was deployed in the 'lads' folder is removed).

Can someone tell me whether the VS details are cached somewhere?

If so, is there a way to clear the cached values so that my changes are picked up without having to create a new VS?

BTW, we are using LISA 7.5 and the JDBC VS was created using the Pathfinder agent.

Regards, Jim

Hi Jim,

Do you get the same behavior when you right click on the .vsm and choose "Re-deploy to VSE..."? This should effectively update the virtual service to the latest version.

Could you clarify what you are doing when you remove the virtual service from the environment? I'm not sure what you are referring to with the lads folder.

Normally when I want to remove a VS from the VSE, I go into the VSE console through the web browser, right click on the VS in question, and select "Remove from the environment".

Best,

-James

1 person found this helpful

Actions

JimCallaghan4454180 @ chaja22 on Jul 1, 2014 6:19 AM

Hi James,

Thank you for your reply and sorry that it has taken me such a long time to respond.

Firstly, let me clarify what I meant by "changes that I make to the model". This is the adding or removal of agents to the Virtual Java Listener step.

Secondly, here are my answers to your questions.

a) Yes I get the same behaviour when I redeploy the VS (.vsm)

b) When you deploy a VS, a copy of the relevant LISA artefacts are copied (as a mini LISA project) to the 'lads' folder on the server in which the VSE is running.

You can tell what subfolder it is deployed in by selecting the VS in the VSE Console and observing the value of the 'Config Name' at the bottom of the screen.

c) I "remove the virtual service from the environment" via the VSE console - the same as how you described it - "right click on the VS ..."

Thirdly, it does seem that the agent that have been added or removed are not getting the updated virtual service. So, I will raise a support case.

Finally, does anyone else see the same behaviour?

Note, that changes to my virtual service image do get picked up when I re-deploy the virtual service!

Regards,

Jim

Actions

chaja22

@ JimCallaghan4454180 on Jul 1, 2014 3:43 PM

Hi Jim,

Thanks for the clarification.

I haven't personally seen this behavior in the past, but it certainly smells like it's something our support team should look into.

Once you open a case with them, they should be able to assist you in getting the issue resolved.

Best,

-James

Actions

JimCallaghan4454180 @ chaja22 on Aug 1, 2014 4:12 AM

Hi Everyone,

This is just to confirm that it was in fact an issue for which I had to receive a patch.

The support case number is 21856275 that can be used to see the release in which the fix is included.

Regards,

Jim

Actions

4 Replies

chaja22 May 20, 2014 10:05 PM
Unmark Correct
Correct Answer

jimcallaghan4454180:

Hi,

When I deploy a virtual service that has a Virtual Java Listener step with a JDBC protocol, I find that the changes that I make to the model are not picked up unless I deploy a new VS (i.e. one that has a different name).

This occurs even when I remove the VS from the environment (i.e. the folder in which the VS was deployed in the 'lads' folder is removed).

Can someone tell me whether the VS details are cached somewhere?

If so, is there a way to clear the cached values so that my changes are picked up without having to create a new VS?

BTW, we are using LISA 7.5 and the JDBC VS was created using the Pathfinder agent.

Regards, Jim

Hi Jim,

Do you get the same behavior when you right click on the .vsm and choose "Re-deploy to VSE..."? This should effectively update the virtual service to the latest version.

Could you clarify what you are doing when you remove the virtual service from the environment? I'm not sure what you are referring to with the lads folder.

Normally when I want to remove a VS from the VSE, I go into the VSE console through the web browser, right click on the VS in question, and select "Remove from the environment".

My final comment would be that when you virtualize JDBC using the agent, the agent is sent instructions on what to virtualize. So it might be possible that the agent is not receiving the updated virtual service. If it's not getting updates, then that should be filed as a support case (as the methods I described above should work).

Best,

-James
1 person found this helpful
Like • Show 1 Like1
Actions
- JimCallaghan4454180 @ chaja22 on Jul 1, 2014 6:19 AM
  Mark Correct
  Correct Answer
  Hi James,
  Thank you for your reply and sorry that it has taken me such a long time to respond.
  
  Firstly, let me clarify what I meant by "changes that I make to the model". This is the adding or removal of agents to the Virtual Java Listener step.
  
  Secondly, here are my answers to your questions.
  a) Yes I get the same behaviour when I redeploy the VS (.vsm)
  
  b) When you deploy a VS, a copy of the relevant LISA artefacts are copied (as a mini LISA project) to the 'lads' folder on the server in which the VSE is running.
  You can tell what subfolder it is deployed in by selecting the VS in the VSE Console and observing the value of the 'Config Name' at the bottom of the screen.
  
  c) I "remove the virtual service from the environment" via the VSE console - the same as how you described it - "right click on the VS ..."
  
  Thirdly, it does seem that the agent that have been added or removed are not getting the updated virtual service. So, I will raise a support case.
  
  Finally, does anyone else see the same behaviour?
  
  Note, that changes to my virtual service image do get picked up when I re-deploy the virtual service!
  
  Regards,
  Jim
  Like • Show 0 Likes0
  Actions
  - chaja22 @ JimCallaghan4454180 on Jul 1, 2014 3:43 PM
    Mark Correct
    Correct Answer
    Hi Jim,
    
    Thanks for the clarification.
    
    I haven't personally seen this behavior in the past, but it certainly smells like it's something our support team should look into.
    
    Once you open a case with them, they should be able to assist you in getting the issue resolved.
    
    Best,
    -James
    Like • Show 0 Likes0
    Actions
    - JimCallaghan4454180 @ chaja22 on Aug 1, 2014 4:12 AM
      Mark Correct
      Correct Answer
      Hi Everyone,
      
      This is just to confirm that it was in fact an issue for which I had to receive a patch.
      The support case number is 21856275 that can be used to see the release in which the fix is included.
      
      Regards,
      Jim
      Like • Show 2 Likes2
      Actions

Virtual Service Details Cached

Outcomes

Related Content

Recommended Content