Re: Mid tier on one, AR Server on another
Hi Mike, We never identified the parameter. This issue delayed our MT upgrade for well over a month and by the time we found a solution, by starting with fresh config, we did not have much interest in finding the specific parameter that was causing the problem. We have updated mid tiers to every SP version since our issue with 9.1 SP4 and have not experienced this exact issue. However recently with 19.02 MTs against 9.1.02 AR Servers, we are seeing an issue with forms hanging on the loading spinner and needing to hit refresh to load the form. Similar to what you are seeing, it comes after the MTs have been up for while and after a form had been loaded successfully days prior. Not sure if it is an off-shoot of what I experienced with 9.1.04 or not. It is currently open with BMC Support. Jason On Fri, May 31, 2019 at 7:07 AM Mike Galat wrote: > Hi Dave/Jason – > > > > We have been running 18.08.01 MT (just the standard install, not a WAR > deployment,) first against our 8.1.02 AR Server, and then against 18.08.00 > – since about 4/7. One thing we noticed is we would have certain menus > items/buttons, etc. not show up if they were to be hidden/displayed by > permissions. When we were on 8.1.02, we were told, the workaround is to > run with Preload on the midtiers, which we did, of course that makes > flushing excruciatingly slow. We were told that once we upgrade the back > end, we could go back to not having preload enabled. We tried this in our > lab environment, and still found that with 18.08.01 MT, and 18.08.00 ARS we > would still loose elements if preload was not enabled. We would really > like to get away from preload. Although you may want to enable it, do a > hard flush, and see if your missing elements magically reappear. > > > > Jason – Is this parameter getting pulled from central config still an > issue with 18.08.01? What was the parameter? > > > > Thanks, > > > > MIke > > > > > > *From:* ARSList *On Behalf Of *Jason Miller > *Sent:* Friday, March 08, 2019 10:55 > *To:* ARSList > *Subject:* Re: Mid tier on one, AR Server on another > > > > Yes, I have used 9.1.03, 9.1.04 and 18.08 against our non-prod 9.1.02 AR > servers. The only issue we saw was with 9.1.04 and dreadful performance. > There was some parameter in config.properties that would get pulled from > central config (so it affected a fresh .war deployment) that would make > form load times excruciating, even after pre-loading. Once we figured this > out, we created a new Cluster ID right after getting a fresh MT up and > running, which prevented the old configuration from being pull from the DB. > Worked great once we manually re-configured. > > > > Jason > > > > On Fri, Mar 8, 2019 at 5:24 AM Dave Barber wrote: > > Shortly after messaging, I experienced similar - 9.1.04 p002 was supposed > to fix these problems. > > > > We have a mixture of in-house applications and lightly modified OOTB, and > it is normally the work detail tab that disappears, along with a few fields > and buttons of our own. > > > > Has anyone ever tried the 18.05 or 18.08 mid tiers against a 9.1.02 AR > Server? (I'm grasping at straws, our mid tiers are a continual pain during > migrations, but the amount of pain varies randomly) > > > > On Wed, 6 Mar 2019 at 16:45, Jason Miller wrote: > > I should not have said anything. Right after I sent this, one of our Mid > Tiers had corrupt cache and I had to stop TC and delete files. The telltale > sign usually is that the Work Detail table on the Incident form does not > show up. If the Work Detail panel is blank we know it is time to do the > cache dance with that MT server. > > > > Jason > > > > On Wed, Mar 6, 2019 at 9:53 AM Dave Barber wrote: > > We have been finding different behaviours across servers; we have 5 or 6 > forms/areas to check, and we can find that each server seems to randomly > miss elements - doesn't matter if we have made any changes to that form on > a deployment, the mid tiers just misbehave. Random selection of > sync/flush/restart and after an hour or two things tend to be working. > > > > I'll try that method of installation on one of our pre-prod servers, does > sound very easy. > > > > On Wed, 6 Mar 2019 at 15:12, Jason Miller wrote: > > We too have issues with 9.1 SP2 and cache. Basically sync cache and flush > cache features are not usable. Anytime our cache becomes corrupt or a major > change needs to be picked up, we need to shut down the Mid Tiers and > manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade > to (originally SP4 but now 18.08) keeps getting delayed for production. > > > > On Wed, Ma
Re: Mid tier on one, AR Server on another
We have been running preload in production with a 86400 check interval, chache persistence enabled, lifespan enabled, and connection lifespan 15 minutes. We haven't had any major issues with this. Sometimes if we manually flush the cache IE users need to remove their temporary internet files to see the changes. Firefox and Chrome have worked fine. We're on the latest release. However, we've had this configuration since upgrading to 9.x a couple years ago. Hope that helps. Brian From: ARSList on behalf of Mike Galat Sent: Friday, May 31, 2019 8:03 AM To: ARSList Subject: RE: Mid tier on one, AR Server on another Hi Dave/Jason – We have been running 18.08.01 MT (just the standard install, not a WAR deployment,) first against our 8.1.02 AR Server, and then against 18.08.00 – since about 4/7. One thing we noticed is we would have certain menus items/buttons, etc. not show up if they were to be hidden/displayed by permissions. When we were on 8.1.02, we were told, the workaround is to run with Preload on the midtiers, which we did, of course that makes flushing excruciatingly slow. We were told that once we upgrade the back end, we could go back to not having preload enabled. We tried this in our lab environment, and still found that with 18.08.01 MT, and 18.08.00 ARS we would still loose elements if preload was not enabled. We would really like to get away from preload. Although you may want to enable it, do a hard flush, and see if your missing elements magically reappear. Jason – Is this parameter getting pulled from central config still an issue with 18.08.01? What was the parameter? Thanks, MIke From: ARSList On Behalf Of Jason Miller Sent: Friday, March 08, 2019 10:55 To: ARSList Subject: Re: Mid tier on one, AR Server on another Yes, I have used 9.1.03, 9.1.04 and 18.08 against our non-prod 9.1.02 AR servers. The only issue we saw was with 9.1.04 and dreadful performance. There was some parameter in config.properties that would get pulled from central config (so it affected a fresh .war deployment) that would make form load times excruciating, even after pre-loading. Once we figured this out, we created a new Cluster ID right after getting a fresh MT up and running, which prevented the old configuration from being pull from the DB. Worked great once we manually re-configured. Jason On Fri, Mar 8, 2019 at 5:24 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: Shortly after messaging, I experienced similar - 9.1.04 p002 was supposed to fix these problems. We have a mixture of in-house applications and lightly modified OOTB, and it is normally the work detail tab that disappears, along with a few fields and buttons of our own. Has anyone ever tried the 18.05 or 18.08 mid tiers against a 9.1.02 AR Server? (I'm grasping at straws, our mid tiers are a continual pain during migrations, but the amount of pain varies randomly) On Wed, 6 Mar 2019 at 16:45, Jason Miller mailto:jason.mil...@gmail.com>> wrote: I should not have said anything. Right after I sent this, one of our Mid Tiers had corrupt cache and I had to stop TC and delete files. The telltale sign usually is that the Work Detail table on the Incident form does not show up. If the Work Detail panel is blank we know it is time to do the cache dance with that MT server. Jason On Wed, Mar 6, 2019 at 9:53 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: We have been finding different behaviours across servers; we have 5 or 6 forms/areas to check, and we can find that each server seems to randomly miss elements - doesn't matter if we have made any changes to that form on a deployment, the mid tiers just misbehave. Random selection of sync/flush/restart and after an hour or two things tend to be working. I'll try that method of installation on one of our pre-prod servers, does sound very easy. On Wed, 6 Mar 2019 at 15:12, Jason Miller mailto:jason.mil...@gmail.com>> wrote: We too have issues with 9.1 SP2 and cache. Basically sync cache and flush cache features are not usable. Anytime our cache becomes corrupt or a major change needs to be picked up, we need to shut down the Mid Tiers and manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade to (originally SP4 but now 18.08) keeps getting delayed for production. On Wed, Mar 6, 2019 at 7:52 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: All, Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. There are some really weird caching issues that appear to have been fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to 9.1.04 patch 002. (If anyone is interested, there are massive inconsistencies in the mid tier handling of changes - whenever we make a change, we find the mid tiers either not reflecting the change, needing several restarts to pic
RE: Mid tier on one, AR Server on another
Hi Dave/Jason – We have been running 18.08.01 MT (just the standard install, not a WAR deployment,) first against our 8.1.02 AR Server, and then against 18.08.00 – since about 4/7. One thing we noticed is we would have certain menus items/buttons, etc. not show up if they were to be hidden/displayed by permissions. When we were on 8.1.02, we were told, the workaround is to run with Preload on the midtiers, which we did, of course that makes flushing excruciatingly slow. We were told that once we upgrade the back end, we could go back to not having preload enabled. We tried this in our lab environment, and still found that with 18.08.01 MT, and 18.08.00 ARS we would still loose elements if preload was not enabled. We would really like to get away from preload. Although you may want to enable it, do a hard flush, and see if your missing elements magically reappear. Jason – Is this parameter getting pulled from central config still an issue with 18.08.01? What was the parameter? Thanks, MIke From: ARSList On Behalf Of Jason Miller Sent: Friday, March 08, 2019 10:55 To: ARSList Subject: Re: Mid tier on one, AR Server on another Yes, I have used 9.1.03, 9.1.04 and 18.08 against our non-prod 9.1.02 AR servers. The only issue we saw was with 9.1.04 and dreadful performance. There was some parameter in config.properties that would get pulled from central config (so it affected a fresh .war deployment) that would make form load times excruciating, even after pre-loading. Once we figured this out, we created a new Cluster ID right after getting a fresh MT up and running, which prevented the old configuration from being pull from the DB. Worked great once we manually re-configured. Jason On Fri, Mar 8, 2019 at 5:24 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: Shortly after messaging, I experienced similar - 9.1.04 p002 was supposed to fix these problems. We have a mixture of in-house applications and lightly modified OOTB, and it is normally the work detail tab that disappears, along with a few fields and buttons of our own. Has anyone ever tried the 18.05 or 18.08 mid tiers against a 9.1.02 AR Server? (I'm grasping at straws, our mid tiers are a continual pain during migrations, but the amount of pain varies randomly) On Wed, 6 Mar 2019 at 16:45, Jason Miller mailto:jason.mil...@gmail.com>> wrote: I should not have said anything. Right after I sent this, one of our Mid Tiers had corrupt cache and I had to stop TC and delete files. The telltale sign usually is that the Work Detail table on the Incident form does not show up. If the Work Detail panel is blank we know it is time to do the cache dance with that MT server. Jason On Wed, Mar 6, 2019 at 9:53 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: We have been finding different behaviours across servers; we have 5 or 6 forms/areas to check, and we can find that each server seems to randomly miss elements - doesn't matter if we have made any changes to that form on a deployment, the mid tiers just misbehave. Random selection of sync/flush/restart and after an hour or two things tend to be working. I'll try that method of installation on one of our pre-prod servers, does sound very easy. On Wed, 6 Mar 2019 at 15:12, Jason Miller mailto:jason.mil...@gmail.com>> wrote: We too have issues with 9.1 SP2 and cache. Basically sync cache and flush cache features are not usable. Anytime our cache becomes corrupt or a major change needs to be picked up, we need to shut down the Mid Tiers and manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade to (originally SP4 but now 18.08) keeps getting delayed for production. On Wed, Mar 6, 2019 at 7:52 AM Dave Barber mailto:daddy.bar...@gmail.com>> wrote: All, Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. There are some really weird caching issues that appear to have been fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to 9.1.04 patch 002. (If anyone is interested, there are massive inconsistencies in the mid tier handling of changes - whenever we make a change, we find the mid tiers either not reflecting the change, needing several restarts to pick up the change, random parts of forms stop rendering properly - CHG:Infrastructure Change Work Info table being one that disappears). 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not appear to work - can't even import the 9.1.04 patch 002 deployment package into the deployment console, as it seems to require the 9.1.04 updates to the deployment console. Has anyone manually updated a 9.1.04 mid tier without using the deployment management console? Regards Dave -- ARSList mailing list ARSList@arslist.org<mailto:ARSList@arslist.org> https://mailman.rrr.se/cgi/listinfo/arslist -- ARSList mailing list ARSList@arslist.org<mailto:ARSList@arslist.org> https://mail
Re: Mid tier on one, AR Server on another
Yes, I have used 9.1.03, 9.1.04 and 18.08 against our non-prod 9.1.02 AR servers. The only issue we saw was with 9.1.04 and dreadful performance. There was some parameter in config.properties that would get pulled from central config (so it affected a fresh .war deployment) that would make form load times excruciating, even after pre-loading. Once we figured this out, we created a new Cluster ID right after getting a fresh MT up and running, which prevented the old configuration from being pull from the DB. Worked great once we manually re-configured. Jason On Fri, Mar 8, 2019 at 5:24 AM Dave Barber wrote: > Shortly after messaging, I experienced similar - 9.1.04 p002 was supposed > to fix these problems. > > We have a mixture of in-house applications and lightly modified OOTB, and > it is normally the work detail tab that disappears, along with a few fields > and buttons of our own. > > Has anyone ever tried the 18.05 or 18.08 mid tiers against a 9.1.02 AR > Server? (I'm grasping at straws, our mid tiers are a continual pain during > migrations, but the amount of pain varies randomly) > > On Wed, 6 Mar 2019 at 16:45, Jason Miller wrote: > >> I should not have said anything. Right after I sent this, one of our Mid >> Tiers had corrupt cache and I had to stop TC and delete files. The telltale >> sign usually is that the Work Detail table on the Incident form does not >> show up. If the Work Detail panel is blank we know it is time to do the >> cache dance with that MT server. >> >> Jason >> >> On Wed, Mar 6, 2019 at 9:53 AM Dave Barber >> wrote: >> >>> We have been finding different behaviours across servers; we have 5 or 6 >>> forms/areas to check, and we can find that each server seems to randomly >>> miss elements - doesn't matter if we have made any changes to that form on >>> a deployment, the mid tiers just misbehave. Random selection of >>> sync/flush/restart and after an hour or two things tend to be working. >>> >>> I'll try that method of installation on one of our pre-prod servers, >>> does sound very easy. >>> >>> On Wed, 6 Mar 2019 at 15:12, Jason Miller >>> wrote: >>> We too have issues with 9.1 SP2 and cache. Basically sync cache and flush cache features are not usable. Anytime our cache becomes corrupt or a major change needs to be picked up, we need to shut down the Mid Tiers and manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade to (originally SP4 but now 18.08) keeps getting delayed for production. On Wed, Mar 6, 2019 at 7:52 AM Dave Barber wrote: > All, > > Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. > > There are some really weird caching issues that appear to have been > fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid > tier to 9.1.04 patch 002. (If anyone is interested, there are massive > inconsistencies in the mid tier handling of changes - whenever we make a > change, we find the mid tiers either not reflecting the change, needing > several restarts to pick up the change, random parts of forms stop > rendering properly - CHG:Infrastructure Change Work Info table being one > that disappears). > > 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not > appear to work - can't even import the 9.1.04 patch 002 deployment package > into the deployment console, as it seems to require the 9.1.04 updates to > the deployment console. > > Has anyone manually updated a 9.1.04 mid tier without using the > deployment management console? > > Regards > > Dave > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
Shortly after messaging, I experienced similar - 9.1.04 p002 was supposed to fix these problems. We have a mixture of in-house applications and lightly modified OOTB, and it is normally the work detail tab that disappears, along with a few fields and buttons of our own. Has anyone ever tried the 18.05 or 18.08 mid tiers against a 9.1.02 AR Server? (I'm grasping at straws, our mid tiers are a continual pain during migrations, but the amount of pain varies randomly) On Wed, 6 Mar 2019 at 16:45, Jason Miller wrote: > I should not have said anything. Right after I sent this, one of our Mid > Tiers had corrupt cache and I had to stop TC and delete files. The telltale > sign usually is that the Work Detail table on the Incident form does not > show up. If the Work Detail panel is blank we know it is time to do the > cache dance with that MT server. > > Jason > > On Wed, Mar 6, 2019 at 9:53 AM Dave Barber wrote: > >> We have been finding different behaviours across servers; we have 5 or 6 >> forms/areas to check, and we can find that each server seems to randomly >> miss elements - doesn't matter if we have made any changes to that form on >> a deployment, the mid tiers just misbehave. Random selection of >> sync/flush/restart and after an hour or two things tend to be working. >> >> I'll try that method of installation on one of our pre-prod servers, does >> sound very easy. >> >> On Wed, 6 Mar 2019 at 15:12, Jason Miller wrote: >> >>> We too have issues with 9.1 SP2 and cache. Basically sync cache and >>> flush cache features are not usable. Anytime our cache becomes corrupt or a >>> major change needs to be picked up, we need to shut down the Mid Tiers and >>> manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade >>> to (originally SP4 but now 18.08) keeps getting delayed for production. >>> >>> On Wed, Mar 6, 2019 at 7:52 AM Dave Barber >>> wrote: >>> All, Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. There are some really weird caching issues that appear to have been fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to 9.1.04 patch 002. (If anyone is interested, there are massive inconsistencies in the mid tier handling of changes - whenever we make a change, we find the mid tiers either not reflecting the change, needing several restarts to pick up the change, random parts of forms stop rendering properly - CHG:Infrastructure Change Work Info table being one that disappears). 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not appear to work - can't even import the 9.1.04 patch 002 deployment package into the deployment console, as it seems to require the 9.1.04 updates to the deployment console. Has anyone manually updated a 9.1.04 mid tier without using the deployment management console? Regards Dave -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
Murphy's law .. On Wed, 6 Mar 2019, 17:46 Jason Miller, wrote: > I should not have said anything. Right after I sent this, one of our Mid > Tiers had corrupt cache and I had to stop TC and delete files. The telltale > sign usually is that the Work Detail table on the Incident form does not > show up. If the Work Detail panel is blank we know it is time to do the > cache dance with that MT server. > > Jason > > On Wed, Mar 6, 2019 at 9:53 AM Dave Barber wrote: > >> We have been finding different behaviours across servers; we have 5 or 6 >> forms/areas to check, and we can find that each server seems to randomly >> miss elements - doesn't matter if we have made any changes to that form on >> a deployment, the mid tiers just misbehave. Random selection of >> sync/flush/restart and after an hour or two things tend to be working. >> >> I'll try that method of installation on one of our pre-prod servers, does >> sound very easy. >> >> On Wed, 6 Mar 2019 at 15:12, Jason Miller wrote: >> >>> We too have issues with 9.1 SP2 and cache. Basically sync cache and >>> flush cache features are not usable. Anytime our cache becomes corrupt or a >>> major change needs to be picked up, we need to shut down the Mid Tiers and >>> manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade >>> to (originally SP4 but now 18.08) keeps getting delayed for production. >>> >>> On Wed, Mar 6, 2019 at 7:52 AM Dave Barber >>> wrote: >>> All, Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. There are some really weird caching issues that appear to have been fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to 9.1.04 patch 002. (If anyone is interested, there are massive inconsistencies in the mid tier handling of changes - whenever we make a change, we find the mid tiers either not reflecting the change, needing several restarts to pick up the change, random parts of forms stop rendering properly - CHG:Infrastructure Change Work Info table being one that disappears). 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not appear to work - can't even import the 9.1.04 patch 002 deployment package into the deployment console, as it seems to require the 9.1.04 updates to the deployment console. Has anyone manually updated a 9.1.04 mid tier without using the deployment management console? Regards Dave -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
I should not have said anything. Right after I sent this, one of our Mid Tiers had corrupt cache and I had to stop TC and delete files. The telltale sign usually is that the Work Detail table on the Incident form does not show up. If the Work Detail panel is blank we know it is time to do the cache dance with that MT server. Jason On Wed, Mar 6, 2019 at 9:53 AM Dave Barber wrote: > We have been finding different behaviours across servers; we have 5 or 6 > forms/areas to check, and we can find that each server seems to randomly > miss elements - doesn't matter if we have made any changes to that form on > a deployment, the mid tiers just misbehave. Random selection of > sync/flush/restart and after an hour or two things tend to be working. > > I'll try that method of installation on one of our pre-prod servers, does > sound very easy. > > On Wed, 6 Mar 2019 at 15:12, Jason Miller wrote: > >> We too have issues with 9.1 SP2 and cache. Basically sync cache and flush >> cache features are not usable. Anytime our cache becomes corrupt or a major >> change needs to be picked up, we need to shut down the Mid Tiers and >> manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade >> to (originally SP4 but now 18.08) keeps getting delayed for production. >> >> On Wed, Mar 6, 2019 at 7:52 AM Dave Barber >> wrote: >> >>> All, >>> >>> Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. >>> >>> There are some really weird caching issues that appear to have been >>> fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid >>> tier to 9.1.04 patch 002. (If anyone is interested, there are massive >>> inconsistencies in the mid tier handling of changes - whenever we make a >>> change, we find the mid tiers either not reflecting the change, needing >>> several restarts to pick up the change, random parts of forms stop >>> rendering properly - CHG:Infrastructure Change Work Info table being one >>> that disappears). >>> >>> 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not >>> appear to work - can't even import the 9.1.04 patch 002 deployment package >>> into the deployment console, as it seems to require the 9.1.04 updates to >>> the deployment console. >>> >>> Has anyone manually updated a 9.1.04 mid tier without using the >>> deployment management console? >>> >>> Regards >>> >>> Dave >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
We have been finding different behaviours across servers; we have 5 or 6 forms/areas to check, and we can find that each server seems to randomly miss elements - doesn't matter if we have made any changes to that form on a deployment, the mid tiers just misbehave. Random selection of sync/flush/restart and after an hour or two things tend to be working. I'll try that method of installation on one of our pre-prod servers, does sound very easy. On Wed, 6 Mar 2019 at 15:12, Jason Miller wrote: > We too have issues with 9.1 SP2 and cache. Basically sync cache and flush > cache features are not usable. Anytime our cache becomes corrupt or a major > change needs to be picked up, we need to shut down the Mid Tiers and > manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade > to (originally SP4 but now 18.08) keeps getting delayed for production. > > On Wed, Mar 6, 2019 at 7:52 AM Dave Barber wrote: > >> All, >> >> Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. >> >> There are some really weird caching issues that appear to have been fixed >> on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to >> 9.1.04 patch 002. (If anyone is interested, there are massive >> inconsistencies in the mid tier handling of changes - whenever we make a >> change, we find the mid tiers either not reflecting the change, needing >> several restarts to pick up the change, random parts of forms stop >> rendering properly - CHG:Infrastructure Change Work Info table being one >> that disappears). >> >> 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not >> appear to work - can't even import the 9.1.04 patch 002 deployment package >> into the deployment console, as it seems to require the 9.1.04 updates to >> the deployment console. >> >> Has anyone manually updated a 9.1.04 mid tier without using the >> deployment management console? >> >> Regards >> >> Dave >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
It is awesome! I like to rename the existing /.midtier directory (e.g. midtier_9102001) and then unzip the war next to it. That way I can simply revert to the old MT by simply shutting down Tomcat and renaming directories. I have have done this a lot when bouncing back and forth between SP2 and SP4/18.05/18.08 in our non prod environments. On Wed, Mar 6, 2019 at 9:08 AM Dave Barber wrote: > I have never tried that method; have just gone through the rather dubious > file replacement process from the various zip files - the mid tier seems to > think it is running 9.1.04 patch 002. > > I'll have a look at the WAR method, many thanks! > > On Wed, 6 Mar 2019 at 14:00, LJ LongWing wrote: > >> You can still use the WAR rollout method without issue. >> >> On Wed, Mar 6, 2019 at 6:54 AM Dave Barber >> wrote: >> >>> All, >>> >>> Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. >>> >>> There are some really weird caching issues that appear to have been >>> fixed on 9.1.04 patch 002 - so I have been looking into upgrading the mid >>> tier to 9.1.04 patch 002. (If anyone is interested, there are massive >>> inconsistencies in the mid tier handling of changes - whenever we make a >>> change, we find the mid tiers either not reflecting the change, needing >>> several restarts to pick up the change, random parts of forms stop >>> rendering properly - CHG:Infrastructure Change Work Info table being one >>> that disappears). >>> >>> 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not >>> appear to work - can't even import the 9.1.04 patch 002 deployment package >>> into the deployment console, as it seems to require the 9.1.04 updates to >>> the deployment console. >>> >>> Has anyone manually updated a 9.1.04 mid tier without using the >>> deployment management console? >>> >>> Regards >>> >>> Dave >>> -- >>> ARSList mailing list >>> ARSList@arslist.org >>> https://mailman.rrr.se/cgi/listinfo/arslist >>> >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
We too have issues with 9.1 SP2 and cache. Basically sync cache and flush cache features are not usable. Anytime our cache becomes corrupt or a major change needs to be picked up, we need to shut down the Mid Tiers and manually delete files in ./midtier and ./tomcat. Unfortunately our upgrade to (originally SP4 but now 18.08) keeps getting delayed for production. On Wed, Mar 6, 2019 at 7:52 AM Dave Barber wrote: > All, > > Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. > > There are some really weird caching issues that appear to have been fixed > on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to > 9.1.04 patch 002. (If anyone is interested, there are massive > inconsistencies in the mid tier handling of changes - whenever we make a > change, we find the mid tiers either not reflecting the change, needing > several restarts to pick up the change, random parts of forms stop > rendering properly - CHG:Infrastructure Change Work Info table being one > that disappears). > > 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not > appear to work - can't even import the 9.1.04 patch 002 deployment package > into the deployment console, as it seems to require the 9.1.04 updates to > the deployment console. > > Has anyone manually updated a 9.1.04 mid tier without using the deployment > management console? > > Regards > > Dave > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
I have never tried that method; have just gone through the rather dubious file replacement process from the various zip files - the mid tier seems to think it is running 9.1.04 patch 002. I'll have a look at the WAR method, many thanks! On Wed, 6 Mar 2019 at 14:00, LJ LongWing wrote: > You can still use the WAR rollout method without issue. > > On Wed, Mar 6, 2019 at 6:54 AM Dave Barber wrote: > >> All, >> >> Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. >> >> There are some really weird caching issues that appear to have been fixed >> on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to >> 9.1.04 patch 002. (If anyone is interested, there are massive >> inconsistencies in the mid tier handling of changes - whenever we make a >> change, we find the mid tiers either not reflecting the change, needing >> several restarts to pick up the change, random parts of forms stop >> rendering properly - CHG:Infrastructure Change Work Info table being one >> that disappears). >> >> 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not >> appear to work - can't even import the 9.1.04 patch 002 deployment package >> into the deployment console, as it seems to require the 9.1.04 updates to >> the deployment console. >> >> Has anyone manually updated a 9.1.04 mid tier without using the >> deployment management console? >> >> Regards >> >> Dave >> -- >> ARSList mailing list >> ARSList@arslist.org >> https://mailman.rrr.se/cgi/listinfo/arslist >> > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
Re: Mid tier on one, AR Server on another
You can still use the WAR rollout method without issue. On Wed, Mar 6, 2019 at 6:54 AM Dave Barber wrote: > All, > > Our live AR Servers are on 9.1.02. Our mid tiers are on 9.1.03. > > There are some really weird caching issues that appear to have been fixed > on 9.1.04 patch 002 - so I have been looking into upgrading the mid tier to > 9.1.04 patch 002. (If anyone is interested, there are massive > inconsistencies in the mid tier handling of changes - whenever we make a > change, we find the mid tiers either not reflecting the change, needing > several restarts to pick up the change, random parts of forms stop > rendering properly - CHG:Infrastructure Change Work Info table being one > that disappears). > > 9.1.04 itself is fine, but the patching to 9.1.04 patch 002 does not > appear to work - can't even import the 9.1.04 patch 002 deployment package > into the deployment console, as it seems to require the 9.1.04 updates to > the deployment console. > > Has anyone manually updated a 9.1.04 mid tier without using the deployment > management console? > > Regards > > Dave > -- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist > -- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist
