[Owasp-webscarab] WebScarab Freezes on Ubuntu 9.10

[Rogan Dawes]

On 2010/03/07 9:18 AM, Mathew Brown wrote:
> Hi Rogan,
> 
>   Thank you for your email.  I tried running kill -QUIT <pid> but it
>   wouldn't kill the process.  However, I was able to run jstack.  Below
>   is the output.  Thanks.
> 

Kill -QUIT isn't strictly supposed to make the process exit, but rather
to make the JRE dump the stack trace. Anyway, you got it, so . . .

It looks to me as though you are viewing an HTML response, in some
fashion, based on:

> "AWT-EventQueue-1" prio=10 tid=0x095bac00 nid=0x1bac in Object.wait()
> [0x8fb2b000]
>    java.lang.Thread.State: WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	- waiting on <0x952318e0> (a javax.swing.text.PlainDocument)
> 	at java.lang.Object.wait(Object.java:485)
> 	at
> 	javax.swing.text.AbstractDocument.readLock(AbstractDocument.java:1372)

and the following entries. That seems to be waiting on:

> "Listener-127.0.0.1:8008-60" daemon prio=10 tid=0x095b3400 nid=0x1cb7 in
> Object.wait() [0x8e1c9000]
>    java.lang.Thread.State: WAITING (on object monitor)
> 	at java.lang.Object.wait(Native Method)
> 	- waiting on <0x952318e0> (a javax.swing.text.PlainDocument)
> 	at java.lang.Object.wait(Object.java:485)
> 	at
> 	javax.swing.text.AbstractDocument.writeLock(AbstractDocument.java:1329)
> 	- locked <0x952318e0> (a javax.swing.text.PlainDocument)
> 	at
> 	javax.swing.text.AbstractDocument.remove(AbstractDocument.java:570)
> 	at
>
org.owasp.webscarab.util.swing.DocumentHandler.makeSpace(DocumentHandler.java:118)
> 	at
>
org.owasp.webscarab.util.swing.DocumentHandler.publish(DocumentHandler.java:93)
> 	at java.util.logging.Logger.log(Logger.java:458)
> 	at java.util.logging.Logger.doLog(Logger.java:480)
> 	at java.util.logging.Logger.log(Logger.java:503)
> 	at java.util.logging.Logger.info(Logger.java:1022)
> 	at
>
org.owasp.webscarab.httpclient.URLFetcher.fetchResponse(URLFetcher.java:313)

Which is trying to write a log entry into the "Messages" tab.

For this to be a big problem (i.e. for messages to be logged at such a
rate), my first guess is that your upstream proxy settings are pointing
back at WebScarab. That said, you are only on the 60th request handled
by that Listener ("Listener-127.0.0.1:8008-60"), so that doesn't really
make sense.

Have you been able to pass traffic through WebScarab successfully, or is
this the first time you are trying to use it?

Rogan