Hi, We have two load balanced front end web servers (IIS) that have been working

David Williams over 9 years ago

Hi, We have two load balanced front end web servers (IIS) that have been working perfectly well for the past 9 months since upgrading. Earlier this week we launched our first "heavy duty" Tempo based processes where user activity was purely focussed in Tempo.

As is the norm, we have been making some fixes where necessary and releasing, but have encountered a slight problem.

When a change is deployed, the majority of the time, only certain users can see the change. Even logging out, refreshing the cache, closing windows etc doesnt solve the problem until perhaps a day later.

Is this an IIS or jBoss caching issue? Just curious as to whether anyone has encountered these problems before?

Thanks, David.

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 9 years ago

What type of changes? Is it rule definitions what doesn't get updated right away?
What Appian version? (please attach <APPIAN_HOME>\\ear\\suite.ear\\conf\\build.info)
How do you end up fixing this problem?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 David Williams over 9 years ago

It's interfaces we have noticed it most with. I will get hold of the build file and get back to you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 tomr384 over 9 years ago

Hi, I have attached our build.info file.
build.info
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

1. How do you end up fixing this problem?
2. The build.info indicates you're on 7.8, is that correct?
3. Do you have two application servers?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 David Williams over 9 years ago

Fixed by either rebooting one of the application servers ... The one we know where the change hasn't taken effect on.

Yes that's right we are in 7.8 at the moment with 2 application servers with IIS and load balancer.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Can you review your standalone.xml and see if this line is the same on both standalone.xml files?

<socket-binding name="messaging-group" port="0" multicast-address="${jboss.messaging.group.address:233.252.134.135}" multicast-port="${jboss.messaging.group.port:9876}"/>

Then review the same file and line for your OTHER environments and make sure the address is different for every environment

Finally review clustering is enabled in the problematic environment.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel