[#DWR-244] "The specified call count is not a number" in cluster environment - DWR

Details

Type: Bug
Status: Open
Priority: Major
Resolution: Unresolved
Affects Version/s: 2.0.3
Fix Version/s: 4.0
Component/s: None

Description:

In WebLogic Cluster + Apache HTTP environment, "The specified call count is not a number" still pop up in v2.0.3.

Issue Links

Dependency

This issue depends on:
DWR-304 Support clustered environments better

This issue is depended on by:
DWR-249 DWR + Spring Security 2.0 => The specified call count is not a number

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Davey Yan added a comment - 04/Apr/08 6:41 AM

The cluster has two or more servers.

If there is only one server, it's OK.

Show

Davey Yan added a comment - 04/Apr/08 6:41 AM The cluster has two or more servers. If there is only one server, it's OK.

Hide

Permalink

Rick Oosterholt added a comment - 21/Oct/08 9:14 AM

We experience the same problem.
We do not have a cluster setup and are using Apache Tomcat.

It seems to appear after a lot of refreshes (we are developing a page with some dwr calls)
The amount of data isn't too much...

Rick -

Show

Rick Oosterholt added a comment - 21/Oct/08 9:14 AM We experience the same problem. We do not have a cluster setup and are using Apache Tomcat. It seems to appear after a lot of refreshes (we are developing a page with some dwr calls) The amount of data isn't too much...

Rick -

Hide

Permalink

Jeff Strike added a comment - 27/Nov/08 3:39 PM

Throwing in a me too...

It only happens once in a great while and we can't consistently reproduce the issue.
Using WebLogic 10.2
We just switched to Apache from IIS, I'm almost positive we never got this with IIS but we had other issues with IIS which is why we're switching to Apache.
Similar circumstances to Rick...we have a name search field and if you keep hammering on it it will sometimes throw the error.
The server is not clustered but we do have a BigIP in front of it for load balancing, right now there's only one server.

Show

Jeff Strike added a comment - 27/Nov/08 3:39 PM Throwing in a me too... It only happens once in a great while and we can't consistently reproduce the issue. Using WebLogic 10.2 We just switched to Apache from IIS, I'm almost positive we never got this with IIS but we had other issues with IIS which is why we're switching to Apache. Similar circumstances to Rick...we have a name search field and if you keep hammering on it it will sometimes throw the error. The server is not clustered but we do have a BigIP in front of it for load balancing, right now there's only one server.

Hide

Permalink

Davey Yan added a comment - 27/Dec/08 2:05 AM

It's OK in WebSphere ND 6.1.0.21, with two servers in two seperated physical servers.

Show

Davey Yan added a comment - 27/Dec/08 2:05 AM It's OK in WebSphere ND 6.1.0.21, with two servers in two seperated physical servers.

Hide

Permalink

RGGJ added a comment - 01/Mar/13 7:05 AM

este problema se soluciona dejando la asincronicidad falsa en la llamada al método java desde la funcion javascript.
ejemplo:
javascript.methodJava(parameters....,{callback:showFunction, async:false});

Show

RGGJ added a comment - 01/Mar/13 7:05 AM este problema se soluciona dejando la asincronicidad falsa en la llamada al método java desde la funcion javascript. ejemplo: javascript.methodJava(parameters....,{callback:showFunction, async:false});

People

Assignee:

David Marginian

Reporter:

Davey Yan
Votes:

4

Watchers:

2

Dates

Created:

03/Apr/08 10:46 AM

Updated:

01/Mar/13 7:05 AM