tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Schultz <ch...@christopherschultz.net>
Subject Re: REST call failure on newer tomcat version/update
Date Wed, 24 Dec 2014 00:57:34 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Sean,

On 12/23/14 5:08 PM, Sean Dawson wrote:
> On Tue, Dec 23, 2014 at 4:59 PM, Christopher Schultz < 
> chris@christopherschultz.net> wrote:
> 
>> Are you worried about spamming the list or giving out too much 
>> information?
> 
> Mostly the former, but a tiny bit the latter.
> 
> 
>> somewhere in between the GWT client and theGWT server -- btw why
>> are you doing that?)
> 
> Is there another/better way to get gwt apps to send REST requests
> to a server located on a different machine?

So the web server (serving the HTML) is on one machine and the
application server (responding to the REST requests the GWT client
initiates) are on different machines? So the problem is with
Javascript not being able to make a connection to a server that wasn't
the source of the page?

>> Does the test-case require a GWT client?
> 
> Yes, I suppose I might be able to remove that part - it's taken up
> a lot of time already though.

If it's mission-critical, then it's worth spending time on it, right? ;)

>> Good. You might want to implement some heavy (disable-able)
>> logging in the proxy to see what information is passing back and
>> forth, there.
>> 
> 
> Thanks, done.
> 
> 
>> Unfortunately, there are a lot of moving parts, here.
>> 
> 
> True - which is why it took some time to reduce.
> 
> 
>> Can you operate without this proxy, just to see if the GWT client
>> and GWT server can talk to each other without a problem, even in
>> newer versions of Tomcat?
>> 
> 
> I don't think so - unless you're talking RPC/RF, or something else
> I'm not aware of.

I just meant having the client make direct requests to the GWT server.
Why can't they talk directly? (See above question)

>> If you get the example "working" with 53, doesn't that mean you
>> will have solved your problem?
>> 
> 
> I'd like to make sure we're doing all the right practices - we're a
> bit low on resources at the moment so we're doing our best.

Understood.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJUmg9+AAoJEBzwKT+lPKRY6ToP/2o0ieXwOrBz5Xus/Z65JNTs
/ZqNI3zQlnpwyeB27Ft6Bl76O6rnK7L9vKR8EMbDN/AxqsesCihI0gTc9S+KftiC
ONiUv3hTUAYsbjVywhiiDsTeyCG18i3s0ejp6uQ+tEjM9SS6r1+iwfcywSRCZcEc
4pZB5M6J7+N40OcokJhhTH3R9e1AVWc3HQlaUhWGZRFBvWKG7bQk2lf/hAz0eOkd
VkRdzC0tlDgWXmET04AjauCw+SRdoAR5Ont+Ci0NP6cyXCr5CTjjmhlaCCjX+mv8
y0mI2f12Di3NPjmkZlzq+qQ9fgDcLIt8NETR2UuumtuD8ZnqFfVLDym/mkqUkR6N
sidD1Ff9Qdu1P3tJ1xmSYosyWUge40BBi7amXkkmcfwRelL/Rpec8qTyNCMpIDqf
q46IjITEkD8DX5RPGixs1gyu0FZu4cUGNylAcocl7nchRWvGKQvdExGYIAql/09d
+L+LM9rvIFeA3g3Z3fFJRIBWJzuNPzEvH4IZEOaIkUBQCp5xUjoO1dw1/2FVOqwK
h8kCPxMx+xURtzduR8OC+LE3Q8PYSHmGHYaG52gJEv9iCQE3sbGl+WTIOmI1DbTB
D78YWbm/si2TCVSniWZc6Ky2aIfvzRlI++wpzPqjs2llKLTC2Dahb0Z+DCQUM/lo
BH0Bju288/rAp6sdUQnV
=rNGY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message