[orca-list] orca sticks when I try to read the attached e-mail

[José Vilmar Estácio de Souza <vilmar informal com br>]

Hi all.
Using the latest orca compiled from git, I can not read the attached 
e-mail using the arrows.

To reproduce try the following:
1. Launch thunderbird and open the file that is attached to this message.
2. Press ctrl+home.
3. Press down arrow until you here something like:
Am 11.01.2013 um 15:00 schrieb Aaron Long <longwa gmail com>:
4. Press down arro again many times.
Orca stays mute although there is more text in the message.
5. Press the up arrow.
Orca reads something like:
Am 11.01.2013 um 15:00 schrieb Aaron Long <longwa gmail com>:

This doesn't happen with orca 3.8.2.
Should I file a bug?
Thanks.



--
{}S José Vilmar Estácio de Souza

--- Begin Message ---

• From: Robert Oschwald <robertoschwald googlemail com>
• To: user grails codehaus org
• Subject: Re: [grails-user] events-push/atmosphere eating all the Tomcat threads
• Date: Wed, 4 Sep 2013 10:29:22 +0200

Are you using Apache HTTPD in front of Tomcat connected by mod_jk?

if yes, check the threads using tomcat manager.

If the threads are in keepalive state, you might need to set keepaliveTimeout oin the AJP 1.3 Tomcat connector to get rid of old threads.

Am 11.01.2013 um 15:00 schrieb Aaron Long <longwa gmail com>:

We are testing with the push plugin and keep having a problem where all of the Tomcat threads end up in this state:

"http-bio-8080-exec-244" daemon prio=10 tid=0x00007f5d180a4000 nid=0x1ef6 waiting on condition [0x00007f5cd81dc000]
     java.lang.Thread.State: WAITING (parking)
     at sun.misc.Unsafe.park(Native Method)
     - parking to wait for <0x00000005a3883ec8> (a java.util.concurrent.CountDownLatch$Sync)
     at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
     at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
     at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:236)
     at org.atmosphere.container.BlockingIOCometSupport.suspend(BlockingIOCometSupport.java:152)
     at org.atmosphere.container.BlockingIOCometSupport.service(BlockingIOCometSupport.java:103)
     at org.atmosphere.container.Tomcat7BIOSupportWithWebSocket.doService(Tomcat7BIOSupportWithWebSocket.java:61)
     at org.atmosphere.container.TomcatWebSocketUtil.doService(TomcatWebSocketUtil.java:82)
     at org.atmosphere.container.Tomcat7BIOSupportWithWebSocket.service(Tomcat7BIOSupportWithWebSocket.java:57)
     at org.atmosphere.cpr.AtmosphereFramework.doCometSupport(AtmosphereFramework.java:1293)
     at org.atmosphere.cpr.AtmosphereServlet.doPost(AtmosphereServlet.java:293)
     at org.atmosphere.cpr.AtmosphereServlet.doGet(AtmosphereServlet.java:279)

Eventually this makes Tomcat completely unresponsive. The plugin works fine but I notice that in Firefox and IE, they complain about it not disconnecting. I'm not sure how, or if, you are supposed to do some cleanup when the user switches pages but maybe they are related.

Anyone using atmosphere and having issues like this?

-Aaron

--- End Message ---