# DWR 3.0.2 Upgrade - "Incomplete reply from server"

**URL:** <https://discourse.dojo.io/t/dwr-3-0-2-upgrade-incomplete-reply-from-server/563>\
**Category:** DWR users\
**Created:** [August 13, 2021, 7:29am UTC](https://discourse.dojo.io/t/dwr-3-0-2-upgrade-incomplete-reply-from-server/563 "2021-08-13T07:29:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![agabel](https://avatars.discourse-cdn.com/v4/letter/a/b4bc9f/32.png) [@agabel](https://discourse.dojo.io/u/agabel)\
**Post date:** [August 13, 2021, 7:29am UTC](https://discourse.dojo.io/t/dwr-3-0-2-upgrade-incomplete-reply-from-server/563/1 "2021-08-13T07:29:56Z")

</div>

Hi all,

Our setup: DWR 3.0.2, Java 1.8, Spring 2.5.6, Websphere

We have upgraded from DWR 2.0.3 to DWR 3.0.2.  
It works fine running locally, but not in a test environment. Both have the setup mentioned above.

In the test environment we get the same error in both the application and in the debugging tool (/dwr/index.html).

In the console we get an LogEvent with the following message:  
“Incomplete reply from server”

In the network tab we see a request to “hostname:9080/dwr/call/plaincall/\_\_System.generateId.dwr”.  
With the following Request Payload:  
 ![image](https://canada1.discourse-cdn.com/flex031/uploads/dojo/original/1X/0f16cea7c55f5c23f24c2cb6acc559a8485a8ca7.png)

With the following Response:  
//#DWR-REPLY  
//#DWR-START#  
(function(){  
if(!window.dwr)return;  
var dwr=window.dwr.\_[0];  
dwr.engine.remote.handleCallback({bytes:’/dwr/download/FZX4!kmKXGmvVn59VsApgwxXr2BALtLc!In-2’,empty:{}},{bytes:’/dwr/download/fY5UoiwB5T0C~Inb4RM4whyIkOAVLtLc!In-3’,empty:{}},{bytes:’/dwr/download/6exJBVjct0OBQsDZ8bNmsBp9vy4UMtLc!In’,empty:{}});  
})();  
//#DWR-END#

Which is also significantly different than the response locally:  
//#DWR-REPLY  
//#DWR-START#  
(function(){  
if(!window.dwr)return;  
var dwr=window.dwr.\_[0];  
dwr.engine.remote.handleCallback(“0”,“0”,“9dVqWXBwXaZZS~gyK!2cuRsQncu8yMwp!In”);  
})();  
//#DWR-END#

No other requests are made in the test environment. Caused by the weird arguments to the handleCallback function in the first response, it seems.  
We don’t see anything in the logs - even using the DWR accessLogLevel.

Hope you can help us out.