Re: 5.4 Upload / Long Response Issue?

2014-09-04 Thread Michael Gentry 
FWIW,

I just tested in Tomcat and it works fine.  I'm going to assume it is
something with the Maven Jetty plugin and not a Tapestry 5.4 issue.

Thanks!

mrg



On Fri, Aug 29, 2014 at 8:40 AM, Michael Gentry mgen...@masslight.net
wrote:

 H Lance,

 There were no exceptions and I was using VisualVM to monitor the
 heap/GCs/etc and there was plenty of memory available, even when processing
 both threads.  (About 150-200MB used out of 1GB allocated.)

 mrg



 On Fri, Aug 29, 2014 at 3:17 AM, Lance Java lance.j...@googlemail.com
 wrote:

 Put a
 try {...} catch (Throwable t)
 Around the processing of this large file. Perhaps maven isn't giving jetty
 enough memory and it's throwing OutOfMemoryError or something?

Re: 5.4 Upload / Long Response Issue?

2014-08-29 Thread Lance Java 
Put a
try {...} catch (Throwable t)
Around the processing of this large file. Perhaps maven isn't giving jetty
enough memory and it's throwing OutOfMemoryError or something?

Re: 5.4 Upload / Long Response Issue?

2014-08-29 Thread Michael Gentry 
H Lance,

There were no exceptions and I was using VisualVM to monitor the
heap/GCs/etc and there was plenty of memory available, even when processing
both threads.  (About 150-200MB used out of 1GB allocated.)

mrg



On Fri, Aug 29, 2014 at 3:17 AM, Lance Java lance.j...@googlemail.com
wrote:

 Put a
 try {...} catch (Throwable t)
 Around the processing of this large file. Perhaps maven isn't giving jetty
 enough memory and it's throwing OutOfMemoryError or something?

5.4 Upload / Long Response Issue?

2014-08-28 Thread Michael Gentry 
Hi everyone,

I'm currently using 5.4B6 and we are doing uploads of XML data (using the
standard Tapestry Upload/UploadFile mechanism -- no multi-file AJAX/etc
extensions).

When we upload a small file, it processes just fine, but on a larger file
(which takes several minutes to process), multiple threads are created
along with multiple onValidate/onSuccess calls (and no, we weren't
double-clicking the submit button).  The second thread
and onValidate/onSuccess get created/called 30 seconds after the original
invocation.  This can cause duplicate inserts into the database or other
shenanigans.

Another oddity:

Chrome: Always 2 threads.
Firefox: Always 2 threads.
Safari: Always 2+ threads (we'd just kill the app instead of letting it run
for hours)

Has anyone else experienced this before?  Is it an issue with 5.4 (we don't
seem to have the issue in 5.3)?  Another possibility is Jetty is kicking
off the additional threads when a response isn't generated in time, but it
seems odd that many more threads get kicked off when connecting via Safari
instead of Chrome/Firefox.

Thanks,

mrg

PS. We worked around the issue by creating an upload status page and doing
the processing in the background with an AJAX update, so no hurry for a
resolution, just wanted to ask about a possible 5.4 issue.

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Lance Java 
Strange? Can you open up the network traffic in your browser's dev tools
and see the httptraffic?

If there's 2 requests, can you copy / paste the request headers?

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Michael Gentry 
Hi Lance,

All 3 browsers issue a single request.  The second thread and
onValidate/onSuccess occur 30 seconds after the original upload using all 3
browsers (and repost/redeliver the original payload it seems, since the
complete XML file is available to the new thread(s)).

Thanks,

mrg



On Thu, Aug 28, 2014 at 11:20 AM, Lance Java lance.j...@googlemail.com
wrote:

 Strange? Can you open up the network traffic in your browser's dev tools
 and see the httptraffic?

 If there's 2 requests, can you copy / paste the request headers?

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Lance Java 
1.Is your app sitting behind a proxy? (eg apache?).

2. Are there any other servlet filters we should know about? (eg spring?)

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Norman Franke 
While not the same problem, I’ve had issues uploading even small files to 
Tapestry on Tomcat when behind a load balancer. Eliminating the load balancer 
solved the problem. Not really a Tapestry problem, I’d suspect, but possibly 
related.

Norman Franke
Answering Service for Directors, Inc.
www.myasd.com



On Aug 28, 2014, at 2:05 PM, Lance Java lance.j...@googlemail.com wrote:

 1.Is your app sitting behind a proxy? (eg apache?).
 
 2. Are there any other servlet filters we should know about? (eg spring?)

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Michael Gentry 
Hi again Lance,

1) No proxy.  Directly connecting to Jetty @ http://localhost:6789/

2) No other filters.  I'm using Tapestry's IOC for services and trying to
keep things lean.

FWIW, when I dropped the file in as a unit test, it would import just fine
using the T5 service without spawning extra threads, so I don't think it is
related to the T5 service itself (which make's sense, since the
onValidate/onSuccess events are being triggered more than once).

Thanks,

mrg



On Thu, Aug 28, 2014 at 2:05 PM, Lance Java lance.j...@googlemail.com
wrote:

 1.Is your app sitting behind a proxy? (eg apache?).

 2. Are there any other servlet filters we should know about? (eg spring?)

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Lance Java 
Totally weird, can you try deploying to tomcat? It's worth a try to see if
an issue with jetty.
 On 28 Aug 2014 19:36, Michael Gentry mgen...@masslight.net wrote:

 Hi again Lance,

 1) No proxy.  Directly connecting to Jetty @ http://localhost:6789/

 2) No other filters.  I'm using Tapestry's IOC for services and trying to
 keep things lean.

 FWIW, when I dropped the file in as a unit test, it would import just fine
 using the T5 service without spawning extra threads, so I don't think it is
 related to the T5 service itself (which make's sense, since the
 onValidate/onSuccess events are being triggered more than once).

 Thanks,

 mrg



 On Thu, Aug 28, 2014 at 2:05 PM, Lance Java lance.j...@googlemail.com
 wrote:

  1.Is your app sitting behind a proxy? (eg apache?).
 
  2. Are there any other servlet filters we should know about? (eg spring?)

Re: 5.4 Upload / Long Response Issue?

2014-08-28 Thread Michael Gentry 
More information:

When running from Terminal with mvn jetty:run or from within Eclipse
using the M2E plugin (Run or Debug mode), it will create extra threads.
 When running from within Eclipse using RunJettyRun (Run or Debug mode), no
extra threads are created and it works perfectly.

Could be the Maven plugin, perhaps.



On Thu, Aug 28, 2014 at 4:17 PM, Michael Gentry mgen...@masslight.net
wrote:

 I can try Tomcat, but i'll be a day or two or so before I can get to that.

 mrg



 On Thu, Aug 28, 2014 at 3:35 PM, Lance Java lance.j...@googlemail.com
 wrote:

 Totally weird, can you try deploying to tomcat? It's worth a try to see if
 an issue with jetty.
  On 28 Aug 2014 19:36, Michael Gentry mgen...@masslight.net wrote:

  Hi again Lance,
 
  1) No proxy.  Directly connecting to Jetty @ http://localhost:6789/
 
  2) No other filters.  I'm using Tapestry's IOC for services and trying
 to
  keep things lean.
 
  FWIW, when I dropped the file in as a unit test, it would import just
 fine
  using the T5 service without spawning extra threads, so I don't think
 it is
  related to the T5 service itself (which make's sense, since the
  onValidate/onSuccess events are being triggered more than once).
 
  Thanks,
 
  mrg
 
 
 
  On Thu, Aug 28, 2014 at 2:05 PM, Lance Java lance.j...@googlemail.com
  wrote:
 
   1.Is your app sitting behind a proxy? (eg apache?).
  
   2. Are there any other servlet filters we should know about? (eg
 spring?)