Re: GWT RPC Serialization on web and app server

[Snehalkumar Rangnenwar]

Yes they do match.

On Friday, June 5, 2020 at 9:47:18 PM UTC+5:30, Michael Joyner wrote:
>
> Does your servlet context path exactly match the request path as sent by 
> the browser?
>
> On 6/5/20 3:23 AM, Snehalkumar Rangnenwar wrote:
>
> Hey Entlog ,  
>  what was the solution you applied in jmeter to fix the incompatibility 
> issue ? please let us know as well.
>
> Thank in advance, 
> skay
>
>
> On Wednesday, January 15, 2014 at 7:10:34 PM UTC+5:30, Benoit GUILLOTIN 
> wrote: 
>>
>> HI Entlog,
>>
>> How did U fix ur problem on Jmeter with the .gwt.rpc file ? 
>> Im still looking for fixing this IncompatibleRemoteServiceException.
>>
>> Thanks for ur answer.
>> Benoit
>>
>> Le jeudi 23 mai 2013 12:30:21 UTC+2, Entlog a écrit : 
>>>
>>> Awesome!! Thanks. I was having problems with a jmeter test and I saw 
>>> your solution...it's really that! The jmeter captured request had the 
>>> reference to the hash for another deployed environment and when trying to 
>>> test against another deployed war it was throwing the serializable error. 
>>> Now I know how to fix it :)...
>>>
>>> El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió: 

 Make sure that your app server can still find the .rpc file. 
 Thats your GWT-RPC serialization policy file that the server must know in 
 order to serialize anything that implements Serializable. If it does not 
 find this file it falls back to the old IsSerializable mechanism and if 
 you 
 do not have implemented that interface serialization will fail.  

 Normally you should see a warning in the app server log on the first 
 RPC request when GWT's RemoteServiceServlet tries to load the 
 serialization 
 policy file but can not find it.

 For example I often have to change the lookup of that file because my 
 deployment does not conform to GWT's standard assumptions.

 -- J.

>>> -- 
> You received this message because you are subscribed to the Google Groups 
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit+unsubscr...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit/5c9d5947-af97-4b68-892c-b98f52de3033o%40googlegroups.com
>  
> 
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/f6d3dcb9-3350-4823-8c9e-dea51f95851do%40googlegroups.com.

Re: GWT RPC Serialization on web and app server

[Michael Conrad]

Does your servlet context path exactly match the request path as sent by 
the browser?


On 6/5/20 3:23 AM, Snehalkumar Rangnenwar wrote:

Hey Entlog ,
 what was the solution you applied in jmeter to fix the 
incompatibility issue ? please let us know as well.


Thank in advance,
skay


On Wednesday, January 15, 2014 at 7:10:34 PM UTC+5:30, Benoit 
GUILLOTIN wrote:


HI Entlog,

How did U fix ur problem on Jmeter with the .gwt.rpc file ?
Im still looking for fixing this IncompatibleRemoteServiceException.

Thanks for ur answer.
Benoit

Le jeudi 23 mai 2013 12:30:21 UTC+2, Entlog a écrit :

Awesome!! Thanks. I was having problems with a jmeter test and
I saw your solution...it's really that! The jmeter captured
request had the reference to the hash for another deployed
environment and when trying to test against another deployed
war it was throwing the serializable error. Now I know how to
fix it :)...

El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:

Make sure that your app server can still find the
.rpc file. Thats your GWT-RPC serialization policy
file that the server must know in order to serialize
anything that implements Serializable. If it does not find
this file it falls back to the old IsSerializable
mechanism and if you do not have implemented that
interface serialization will fail.

Normally you should see a warning in the app server log on
the first RPC request when GWT's RemoteServiceServlet
tries to load the serialization policy file but can not
find it.

For example I often have to change the lookup of that file
because my deployment does not conform to GWT's standard
assumptions.

-- J.

--
You received this message because you are subscribed to the Google 
Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to google-web-toolkit+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5c9d5947-af97-4b68-892c-b98f52de3033o%40googlegroups.com 
.


--
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d50a6861-a180-1e49-4fe0-e5f9d2e2803e%40newsrx.com.

Re: GWT RPC Serialization on web and app server

[Snehalkumar Rangnenwar]

Hey Entlog , 
 what was the solution you applied in jmeter to fix the incompatibility 
issue ? please let us know as well.

Thank in advance, 
skay


On Wednesday, January 15, 2014 at 7:10:34 PM UTC+5:30, Benoit GUILLOTIN 
wrote:
>
> HI Entlog,
>
> How did U fix ur problem on Jmeter with the .gwt.rpc file ? 
> Im still looking for fixing this IncompatibleRemoteServiceException.
>
> Thanks for ur answer.
> Benoit
>
> Le jeudi 23 mai 2013 12:30:21 UTC+2, Entlog a écrit :
>>
>> Awesome!! Thanks. I was having problems with a jmeter test and I saw your 
>> solution...it's really that! The jmeter captured request had the reference 
>> to the hash for another deployed environment and when trying to test 
>> against another deployed war it was throwing the serializable error. Now I 
>> know how to fix it :)...
>>
>> El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:
>>>
>>> Make sure that your app server can still find the .rpc file. Thats 
>>> your GWT-RPC serialization policy file that the server must know in order 
>>> to serialize anything that implements Serializable. If it does not find 
>>> this file it falls back to the old IsSerializable mechanism and if you do 
>>> not have implemented that interface serialization will fail. 
>>>
>>> Normally you should see a warning in the app server log on the first RPC 
>>> request when GWT's RemoteServiceServlet tries to load the serialization 
>>> policy file but can not find it.
>>>
>>> For example I often have to change the lookup of that file because my 
>>> deployment does not conform to GWT's standard assumptions.
>>>
>>> -- J.
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/5c9d5947-af97-4b68-892c-b98f52de3033o%40googlegroups.com.

Re: GWT RPC Serialization on web and app server

[Benoit GUILLOTIN]

HI Entlog,

How did U fix ur problem on Jmeter with the HASH.gwt.rpc file ? 
Im still looking for fixing this IncompatibleRemoteServiceException.

Thanks for ur answer.
Benoit

Le jeudi 23 mai 2013 12:30:21 UTC+2, Entlog a écrit :

 Awesome!! Thanks. I was having problems with a jmeter test and I saw your 
 solution...it's really that! The jmeter captured request had the reference 
 to the hash for another deployed environment and when trying to test 
 against another deployed war it was throwing the serializable error. Now I 
 know how to fix it :)...

 El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:

 Make sure that your app server can still find the HASH.rpc file. Thats 
 your GWT-RPC serialization policy file that the server must know in order 
 to serialize anything that implements Serializable. If it does not find 
 this file it falls back to the old IsSerializable mechanism and if you do 
 not have implemented that interface serialization will fail. 

 Normally you should see a warning in the app server log on the first RPC 
 request when GWT's RemoteServiceServlet tries to load the serialization 
 policy file but can not find it.

 For example I often have to change the lookup of that file because my 
 deployment does not conform to GWT's standard assumptions.

 -- J.



-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT RPC Serialization on web and app server

[Entlog]

Awesome!! Thanks. I was having problems with a jmeter test and I saw your 
solution...it's really that! The jmeter captured request had the reference 
to the hash for another deployed environment and when trying to test 
against another deployed war it was throwing the serializable error. Now I 
know how to fix it :)...

El jueves, 1 de noviembre de 2012 10:27:54 UTC+1, Jens escribió:

 Make sure that your app server can still find the HASH.rpc file. Thats 
 your GWT-RPC serialization policy file that the server must know in order 
 to serialize anything that implements Serializable. If it does not find 
 this file it falls back to the old IsSerializable mechanism and if you do 
 not have implemented that interface serialization will fail. 

 Normally you should see a warning in the app server log on the first RPC 
 request when GWT's RemoteServiceServlet tries to load the serialization 
 policy file but can not find it.

 For example I often have to change the lookup of that file because my 
 deployment does not conform to GWT's standard assumptions.

 -- J.


-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Re: GWT RPC Serialization on web and app server

[Jens]

Make sure that your app server can still find the HASH.rpc file. Thats 
your GWT-RPC serialization policy file that the server must know in order 
to serialize anything that implements Serializable. If it does not find 
this file it falls back to the old IsSerializable mechanism and if you do 
not have implemented that interface serialization will fail. 

Normally you should see a warning in the app server log on the first RPC 
request when GWT's RemoteServiceServlet tries to load the serialization 
policy file but can not find it.

For example I often have to change the lookup of that file because my 
deployment does not conform to GWT's standard assumptions.

-- J.

-- 
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/google-web-toolkit/-/yM2c4-jVl4gJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en.