I found another post from 5/2011 that discussed activation groups and how Valence handles them but that was for version 2.2. I'd like some clarification on the same topic but as it applies to 3.2, in case it's different.
Here's my problem:
I have an application running in a Valence instance but outside of the portal. Same concept as your "No Security" example. As with all of my Valence RPG programs, it runs in the VALENCE activation group. In my RPG, a call is made to a CL that runs a third party software command which then spawns off into it's own activation group. I can't access the third party source so I have no way of preventing this. The problem is that sometimes the third party program bombs and from what I can see in the joblog, it's because the CLEANUP procedure in VVCALL is deleting the third party activation group.
It baffles me as to why it only happens sometimes - I can't duplicate it on demand. I suspect it has to do with the nature of the CGI jobs that run in the Apache instance but I'm not well versed in that area and am only speculating.
Based on a conversation I had with Richard a few weeks ago regarding an unrelated challenge, I don't believe changing the Valence activation group reclaim behavior in the "Server Instance Options" settings will make a difference since the program is not running inside of the portal. Not to mention, even if that would work, I wouldn't want a change like that to be a global setting anyway as the problem only applies to this particular app.
Any suggestions as to how I can resolve my dilemma?
Here's my problem:
I have an application running in a Valence instance but outside of the portal. Same concept as your "No Security" example. As with all of my Valence RPG programs, it runs in the VALENCE activation group. In my RPG, a call is made to a CL that runs a third party software command which then spawns off into it's own activation group. I can't access the third party source so I have no way of preventing this. The problem is that sometimes the third party program bombs and from what I can see in the joblog, it's because the CLEANUP procedure in VVCALL is deleting the third party activation group.
It baffles me as to why it only happens sometimes - I can't duplicate it on demand. I suspect it has to do with the nature of the CGI jobs that run in the Apache instance but I'm not well versed in that area and am only speculating.
Based on a conversation I had with Richard a few weeks ago regarding an unrelated challenge, I don't believe changing the Valence activation group reclaim behavior in the "Server Instance Options" settings will make a difference since the program is not running inside of the portal. Not to mention, even if that would work, I wouldn't want a change like that to be a global setting anyway as the problem only applies to this particular app.
Any suggestions as to how I can resolve my dilemma?
Comment