On Wed, Apr 17, 2013 at 4:43 PM, George Christman
wrote:
> Cezary, I would agree with your response if it didn't work perfectly fine
> in my test page using the same proxy settings. Anyhow, I removed the proxy
> all together and the behavior remains the same. Do you have any suggestions
> in regar
Cezary, I would agree with your response if it didn't work perfectly fine
in my test page using the same proxy settings. Anyhow, I removed the proxy
all together and the behavior remains the same. Do you have any suggestions
in regards to debugging this issue?
I also agree this should be put on it
Hi George,
you answered your own question. Your proxy waits for response and after
some time it fails the request and issues new one. It is a typical
behaviour of the proxy, and it is designed to recover from failures or
temporary unresponsive servers. Check documentation of your proxy to see
I'd like to also note I'm using Jetty locally.
On Tue, Apr 16, 2013 at 4:06 PM, George Christman
wrote:
> Hi Josh,
>
> I'm running localhost version 5.3.6. The only thing sitting in front of my
> app is Charles Proxy, but I have ruled that out do to the fact there
> doesn't seem to be an issue w
Hi Josh,
I'm running localhost version 5.3.6. The only thing sitting in front of my
app is Charles Proxy, but I have ruled that out do to the fact there
doesn't seem to be an issue with it running in my test page. Charles Proxy
is how I was able to determine the cancel request at 30.0 secs.
I don
Hi George.
Probably need to know more about how your system is set up.
Did you run the test in the exact same environment as you are seeing the
problem? (same codebase different page?)
Are you seeing the problem only in a production environment?
Are you running apache mod_proxy, or something else
I ended up setting up a test app to learn that the issue was on my end
and that the test app worked as intended. I setup Charlies Proxy and
discovered after 30.0 seconds exact, it fails the request and creates
a new request. I've disabled all my JS, css and can not figure out the
underlying issue.
Are you sure that the second request is not generated by e.g. a reverse
proxy?
On Mon, Apr 15, 2013 at 7:59 PM, George Christman
wrote:
> Hello, I have a long running process in my onSuccess method. I'm
> noticing my onActivate and onValidate methods are being called
> multiple times before the
Hmm... I can't reproduce. I assume you're running in a test environment
with controlled requests.
I could imagine extra GET requests caused by broken CSS, but that shouldn't
trigger a onValidate, unless maybe you've rigged something up to process
the form from a GET?
public class About {
@In
Hello, I have a long running process in my onSuccess method. I'm
noticing my onActivate and onValidate methods are being called
multiple times before the onSuccess method has actually completed. I
was able to successfully reproduce this using Thread.sleep in the
following example. Does anybody know
10 matches
Mail list logo
