I've been running with this for a day or so and it seems to work fine
now (no mo' stack overflows).
Thanks, David, for the quick fix!
--
Paul O'Rorke
http://ororke.com/paul/blog
http://linkedin.com/in/paulororke
On Feb 16, 2009, at 8:42 AM PST, David Pollak wrote:
Folks,
The problem was
In wireshark you'll be looking to use a normal HTTP rule as the JSON
will just be passed as entity body in the request. Doing a filter for
HTTP port 80 should be sufficient.
Cheers
Tim
--~--~-~--~~~---~--~~
You received this message because you are subscribed
Okay... I've issolated the problem. Lots of GC items being sent. This is
causing a stack overflow. I've got a test for it and I'll fix the problem
today.
On Mon, Feb 16, 2009 at 1:33 AM, Tim Perrett he...@timperrett.com wrote:
In wireshark you'll be looking to use a normal HTTP rule as the
Hi, David:
I'm not using JSON directly myself and when I do a search on json it
only shows up on one line in the default.html page:
script id=json src=/classpath/json.js type=text/javascript/
Perhaps it is JSON that is being used under the hood? I am using
CRUDIFY and the menu items for
Paul,
Something is calling JSONParser with a parameter that's causing the stack
overflow.
You can use Firebug to see what the browser is sending to the server.
That's a way to capture the JSON.
Wireshark is a way of intercepting the HTTP traffic and you can see what the
client is sending to the
