Hi,
We were also plagued by these EOF errors since upgrade to Wicket 6 from
1.4. In the old Wicket the errors (which are not errors - it's an expected
behavior when a user cancels navigation) were not reported in such
aggressive manner, with long stack traces.
How is it possible to hide these
You can extend your logging library and check for this specific exception
and convert it to one line... (too much work, imo).
You can also add custom IRequestCycleListener and catch the error in
#onException() and do something else.
Martin Grigorov
Wicket Training and Consulting
On Sat, Jan
Hi,
On Sat, Jan 4, 2014 at 1:06 AM, eaglei22 jchojnack...@gmail.com wrote:
Here is the errors I get:
Jan 03 17:04:20 WARN RequestCycleExtra-
Jan 03 17:04:20 WARN RequestCycleExtra-Handling the following exception
org.eclipse.jetty.io.RuntimeIOException:
I seem to be able to avoid this by limiting the amount of rows I print to the
screen from the ListView. I turned it into a PageableListView and put a max
of 200 per page, and the problem went away.
--
View this message in context:
As per the API:
Exception invoked when when stale link has been clicked. The page should
then be rerendered with an explanatory error message.
Read more about the Sateless Links
http://wicket.apache.org/guide/guide/chapter9.html#chapter9_5
And about Page Versions:
Here is the errors I get:
Jan 03 17:04:20 WARN RequestCycleExtra-
Jan 03 17:04:20 WARN RequestCycleExtra-Handling the following exception
org.eclipse.jetty.io.RuntimeIOException: org.eclipse.jetty.io.EofException
at
Looks like your Jetty is calling the Wicket filter that in turn crashes
because of an EOF Exception.
How about a quick start?
On Fri, Jan 3, 2014 at 6:06 PM, eaglei22 jchojnack...@gmail.com wrote:
Here is the errors I get:
Jan 03 17:04:20 WARN
Following the example for multi-threading, I still randomly get:
SSAID: Access6
count: 1213
SSAID: Access6
java.io.IOException: Read error
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:220)
at
I have temporarily fixed it by first loading the lines into a string
ArrayList and just read from that list..
I don't really see any latency issues, so maybe this can be considered a
good alternative?
--
View this message in context:
I don't think that's a good idea since ArrayList is not thread-safe :)
http://docs.oracle.com/javase/7/docs/api/java/util/ArrayList.html
*Note that this implementation is not synchronized.* If multiple threads
access an ArrayList instance concurrently, and at least one of the threads
modifies
Great catch Paul. I have made the changes reccommended. However, I read the
file into the arrayList using the main thread, and then use the worker
thread for processing. I don't think the ArrayList is being modified during
this time, but just incase something is happening beyond my knowledge under
Your main thread must be the request cycle's worker thread that wicket
has for your syncronized on the page.
If something takes more than 1 sec as you would expect ti to, it must mean
that whatever you're doing on the page is running your CPU high keeping it
bussy long enough for the 10 secs.
In
And for your curiosity, the THREAD_POOL is nothing but an ExecutorService
inside the WebApplication:
/**
* Cashed thread pool used for background tasks that are outside of the
Quartz scheduler.
* TODO: We might be better off using a spring service
*/
public static final
Thanks Paul I really appreciate your time and efforts to assist me in this
issue.
I have implemented your reccommendations and I was still getting the same
issues (This seems to only be with the larger file as well) and I thought it
was the AjaxSelfUpdatingTimer but instead it looks like the page
Awesome resources to look over. Thanks Paul!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/MultiThreading-issues-with-Wicket-tp4663325p4663355.html
Sent from the Users forum mailing list archive at Nabble.com.
Wicket sometimes makes things easier for us that we forget what's under the
hood :)
Remember that most of your implementation is already thread safe and synced on
the Page.
Read more about the request cycle in the free guide at:
http://wicket.apache.org/guide/guide/chapter8.html
So you want to
16 matches
Mail list logo
