-
1. Re: Production Data from mod_cluster 1.1.10
rhusar May 20, 2011 6:14 PM (in response to joaocunhalopes)I have never seen that, looks like Microsoft Forefront striking back again? Maybe look at your events console in Windows (I dont remember what is it called). It would be really helpful if you can describe steps to reproduce so I can try it locally (I have Windows Server 2008 R2 (64 bit) to test with). Are the JBoss instances running on that Windows version too?
-
2. Production Data from mod_cluster 1.1.10
joaocunhalopes May 21, 2011 2:48 AM (in response to rhusar)Hello Radoslav,
thank you for your reply
We have completely removed Microsoft Forefront from all our production servers. Any problems we may still have cannot be tracked to MS Forefront anymore.
As for the 2 remaining problems:
Problem 1:
[Fri May 20 14:08:44 2011] [error] proxy: CLUSTER: (balancer://ApacheHttpdBalancer). All workers are in error state for route (jvm55_3)
and
Problem 2:
[Fri May 20 15:38:06 2011] [error] ajp_cping_cpong: awaited CPONG, received 41 42 00 04 03
[Fri May 20 15:38:08 2011] [error] ajp_check_msg_header() got bad signature 00
[Fri May 20 15:38:08 2011] [error] ajp_ilink_receive() received bad header
The logs also show that this problems can occur at very low traffic hours (at dawn),
Both problems are refered on this thread:
http://community.jboss.org/thread/162578?tstart=8
We are using Apache 2.2.17 and TC 6.0.32. Spring is used extensibely on our apps. Everything is running on MS Windows Server 2008 R2.
I'll try to create an app that reproduces the error and, if I succedd, I'll post it here.
-
3. Production Data from mod_cluster 1.1.10
rhusar May 23, 2011 5:38 AM (in response to joaocunhalopes)I'll try to create an app that reproduces the error and, if I succedd, I'll post it here.
That would be great!
BTW unless I am mistanken, your problem #1 is caused by problem #2 because the cping fails and the node is marked as in error state.