ssing 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
>
: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
.
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
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
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
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
>
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
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
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
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
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
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
12 matches
Mail list logo
