strange exceptions in log
Hi, our production log is full of strange exceptions like this: http://pastebin.com/Sq7EnV8c Has anybody any idea what is wrong? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: strange exceptions in log
The browser closed the connection and Wicket cannot write the response back. The reasons for this closed connection are many. On Thu, Dec 22, 2011 at 10:54 AM, danisevsky danisev...@gmail.com wrote: Hi, our production log is full of strange exceptions like this: http://pastebin.com/Sq7EnV8c Has anybody any idea what is wrong? Thanks in advance! - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Regarding Stack Overflow exception
Thanks for the reply I was also bothered about this serialization issue in wicket version 1.4.17. Still not sure, the latest version (1.5.3) of wicket will resolve the issue because I haven't find any migration changes statement which states about this serialization fix @ http://svn.apache.org/repos/asf/wicket/trunk/CHANGELOG-1.5 *CHANGELOG* . Please let me know, if you come across particular statement I have already started updating wicket version to 1.5.3 stable version, there seems to be many methods need to be updated. I will let you know the results once I am done with complete upgrade. Meanwhile, if you have any other suggestions...please let me know? - //Maddy -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Regarding-Stack-Overflow-exception-tp4203930p4224818.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Regarding Stack Overflow exception
Try first with 1.4.19 On Thu, Dec 22, 2011 at 12:50 PM, smsmaddy smsd...@gmail.com wrote: Thanks for the reply I was also bothered about this serialization issue in wicket version 1.4.17. Still not sure, the latest version (1.5.3) of wicket will resolve the issue because I haven't find any migration changes statement which states about this serialization fix @ http://svn.apache.org/repos/asf/wicket/trunk/CHANGELOG-1.5 *CHANGELOG* . Please let me know, if you come across particular statement I have already started updating wicket version to 1.5.3 stable version, there seems to be many methods need to be updated. I will let you know the results once I am done with complete upgrade. Meanwhile, if you have any other suggestions...please let me know? - //Maddy -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Regarding-Stack-Overflow-exception-tp4203930p4224818.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Running unit test in parallel
Hi!
We are using wicket-1.4.8.
We have a lot of unit tests and it takes long time to run them. To reduce
running time at multi-core systems we decided to run them parallel in
multiple threads.
I use this
http://mycila.googlecode.com/svn/sandbox/src/main/java/com/mycila/sandbox/junit/runner/ConcurrentSuite.java
class
to run junits concurrently.
First problem I've faced with was some exception from
org.apache.wicket.jmx.Initializer :
*org.apache.wicket.WicketRuntimeException:
javax.management.InstanceAlreadyExistsException:
org.apache.wicket.app.SimpleWicketTester$1:type=Application
at org.apache.wicket.jmx.Initializer.init(Initializer.java:207)
at
org.apache.wicket.Application.callInitializers(Application.java:843)
at
org.apache.wicket.Application.initializeComponents(Application.java:678)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:725)
at
org.apache.wicket.protocol.http.MockWebApplication.init(MockWebApplication.java:168)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:219)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:325)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:308)
at
com.infoblox.platform.test.PlatformWicketTester.init(PlatformWicketTester.java:60)
at
com.infoblox.nios.ui.widget.test.SimpleWicketTester.setUp(SimpleWicketTester.java:54)
*
I've patched the Initializer file, added some synchronization:
*
synchronized (mbeanServer) {
int i = 0;
while (mbeanServer.isRegistered(appBeanName))
{
tempDomain = name + - + i++; //$NON-NLS-1$
appBeanName = new ObjectName(tempDomain + :type=Application);
//$NON-NLS-1$
}
domain = tempDomain;
Application appBean = new Application(application);
register(appBean, appBeanName);
register(new ApplicationSettings(application), new ObjectName(domain +
:type=Application,name=ApplicationSettings)); //$NON-NLS-1$
register(new DebugSettings(application), new ObjectName(domain +
:type=Application,name=DebugSettings)); //$NON-NLS-1$
register(new MarkupSettings(application), new ObjectName(domain +
:type=Application,name=MarkupSettings)); //$NON-NLS-1$
register(new ResourceSettings(application), new ObjectName(domain +
:type=Application,name=ResourceSettings)); //$NON-NLS-1$
register(new PageSettings(application), new ObjectName(domain +
:type=Application,name=PageSettings)); //$NON-NLS-1$
register(new RequestCycleSettings(application), new ObjectName(domain +
:type=Application,name=RequestCycleSettings)); //$NON-NLS-1$
register(new SecuritySettings(application), new ObjectName(domain +
:type=Application,name=SecuritySettings)); //$NON-NLS-1$
register(new SessionSettings(application), new ObjectName(domain +
:type=Application,name=SessionSettings)); //$NON-NLS-1$
register(new CookieValuePersisterSettings(application), new
ObjectName(domain +
:type=Application,name=CookieValuePersisterSettings)); //$NON-NLS-1$
RequestLogger sessionsBean = new RequestLogger(application);
ObjectName sessionsBeanName = new ObjectName(domain +
:type=RequestLogger); //$NON-NLS-1$
register(sessionsBean, sessionsBeanName);
}*
and the problem was gone.
The second problem I found was such mysterious exceptions from different
classes:
*org.apache.wicket.WicketRuntimeException: Exception in rendering
component: [MarkupContainer [Component id = _header_0]]
at org.apache.wicket.Component.renderComponent(Component.java:2658)
at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
at org.apache.wicket.Component.render(Component.java:2450)
at
org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
at
org.apache.wicket.markup.resolver.HtmlHeaderResolver.resolve(HtmlHeaderResolver.java:80)
at
org.apache.wicket.markup.resolver.ComponentResolvers.resolve(ComponentResolvers.java:81)
at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1418)
at
org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1528)
at org.apache.wicket.Page.onRender(Page.java:1565)
at org.apache.wicket.Component.render(Component.java:2450)
at org.apache.wicket.Page.renderPage(Page.java:914)
at
org.apache.wicket.request.target.component.PageRequestTarget.respond(PageRequestTarget.java:63)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.respond(AbstractRequestCycleProcessor.java:105)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1258)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at
Re: Running unit test in parallel
Hi,
Some people ran 1.5.x core tests in parallel with JUnit/Surefire
parallel support and the problems they had were related with setting
current Locale with Locale.setDefault(), i.e. JVM wide. Some tests
expect specific i18n-ized results and due to changed Locale they
failed.
Improvements in this area for 1.4.x wont be done but you can provide
patches for 1.5 if there are no API breaks and for 6.0 with API
changes.
On Thu, Dec 22, 2011 at 5:18 PM, Vervenko Pavel willcode4f...@tut.by wrote:
Hi!
We are using wicket-1.4.8.
We have a lot of unit tests and it takes long time to run them. To reduce
running time at multi-core systems we decided to run them parallel in
multiple threads.
I use this
http://mycila.googlecode.com/svn/sandbox/src/main/java/com/mycila/sandbox/junit/runner/ConcurrentSuite.java
class
to run junits concurrently.
First problem I've faced with was some exception from
org.apache.wicket.jmx.Initializer :
*org.apache.wicket.WicketRuntimeException:
javax.management.InstanceAlreadyExistsException:
org.apache.wicket.app.SimpleWicketTester$1:type=Application
at org.apache.wicket.jmx.Initializer.init(Initializer.java:207)
at
org.apache.wicket.Application.callInitializers(Application.java:843)
at
org.apache.wicket.Application.initializeComponents(Application.java:678)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:725)
at
org.apache.wicket.protocol.http.MockWebApplication.init(MockWebApplication.java:168)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:219)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:325)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:308)
at
com.infoblox.platform.test.PlatformWicketTester.init(PlatformWicketTester.java:60)
at
com.infoblox.nios.ui.widget.test.SimpleWicketTester.setUp(SimpleWicketTester.java:54)
*
I've patched the Initializer file, added some synchronization:
*
synchronized (mbeanServer) {
int i = 0;
while (mbeanServer.isRegistered(appBeanName))
{
tempDomain = name + - + i++; //$NON-NLS-1$
appBeanName = new ObjectName(tempDomain + :type=Application);
//$NON-NLS-1$
}
domain = tempDomain;
Application appBean = new Application(application);
register(appBean, appBeanName);
register(new ApplicationSettings(application), new ObjectName(domain +
:type=Application,name=ApplicationSettings)); //$NON-NLS-1$
register(new DebugSettings(application), new ObjectName(domain +
:type=Application,name=DebugSettings)); //$NON-NLS-1$
register(new MarkupSettings(application), new ObjectName(domain +
:type=Application,name=MarkupSettings)); //$NON-NLS-1$
register(new ResourceSettings(application), new ObjectName(domain +
:type=Application,name=ResourceSettings)); //$NON-NLS-1$
register(new PageSettings(application), new ObjectName(domain +
:type=Application,name=PageSettings)); //$NON-NLS-1$
register(new RequestCycleSettings(application), new ObjectName(domain +
:type=Application,name=RequestCycleSettings)); //$NON-NLS-1$
register(new SecuritySettings(application), new ObjectName(domain +
:type=Application,name=SecuritySettings)); //$NON-NLS-1$
register(new SessionSettings(application), new ObjectName(domain +
:type=Application,name=SessionSettings)); //$NON-NLS-1$
register(new CookieValuePersisterSettings(application), new
ObjectName(domain +
:type=Application,name=CookieValuePersisterSettings)); //$NON-NLS-1$
RequestLogger sessionsBean = new RequestLogger(application);
ObjectName sessionsBeanName = new ObjectName(domain +
:type=RequestLogger); //$NON-NLS-1$
register(sessionsBean, sessionsBeanName);
}*
and the problem was gone.
The second problem I found was such mysterious exceptions from different
classes:
*org.apache.wicket.WicketRuntimeException: Exception in rendering
component: [MarkupContainer [Component id = _header_0]]
at org.apache.wicket.Component.renderComponent(Component.java:2658)
at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
at org.apache.wicket.Component.render(Component.java:2450)
at
org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
at
org.apache.wicket.markup.resolver.HtmlHeaderResolver.resolve(HtmlHeaderResolver.java:80)
at
org.apache.wicket.markup.resolver.ComponentResolvers.resolve(ComponentResolvers.java:81)
at
org.apache.wicket.MarkupContainer.renderNext(MarkupContainer.java:1418)
at
org.apache.wicket.MarkupContainer.renderAll(MarkupContainer.java:1528)
at org.apache.wicket.Page.onRender(Page.java:1565)
at org.apache.wicket.Component.render(Component.java:2450)
at org.apache.wicket.Page.renderPage(Page.java:914)
at
Re: Running unit test in parallel
I didn't mean that I want to run core tests.
I need to run junits for wicket-based web applications in 3-4 parallel
threads. We have a lot of tests based on WicketTester and it takes a lot of
time to run them. Parallel running reduces execution time significantly.
But as far as I can see it's impossible with wicket 1.4. I'm not sure
about 1.5.x but I can't migrate to this version just to check.
22 декабря 2011 г. 18:25 пользователь Martin Grigorov
mgrigo...@apache.orgнаписал:
Hi,
Some people ran 1.5.x core tests in parallel with JUnit/Surefire
parallel support and the problems they had were related with setting
current Locale with Locale.setDefault(), i.e. JVM wide. Some tests
expect specific i18n-ized results and due to changed Locale they
failed.
Improvements in this area for 1.4.x wont be done but you can provide
patches for 1.5 if there are no API breaks and for 6.0 with API
changes.
On Thu, Dec 22, 2011 at 5:18 PM, Vervenko Pavel willcode4f...@tut.by
wrote:
Hi!
We are using wicket-1.4.8.
We have a lot of unit tests and it takes long time to run them. To reduce
running time at multi-core systems we decided to run them parallel in
multiple threads.
I use this
http://mycila.googlecode.com/svn/sandbox/src/main/java/com/mycila/sandbox/junit/runner/ConcurrentSuite.java
class
to run junits concurrently.
First problem I've faced with was some exception from
org.apache.wicket.jmx.Initializer :
*org.apache.wicket.WicketRuntimeException:
javax.management.InstanceAlreadyExistsException:
org.apache.wicket.app.SimpleWicketTester$1:type=Application
at org.apache.wicket.jmx.Initializer.init(Initializer.java:207)
at
org.apache.wicket.Application.callInitializers(Application.java:843)
at
org.apache.wicket.Application.initializeComponents(Application.java:678)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:725)
at
org.apache.wicket.protocol.http.MockWebApplication.init(MockWebApplication.java:168)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:219)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:325)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:308)
at
com.infoblox.platform.test.PlatformWicketTester.init(PlatformWicketTester.java:60)
at
com.infoblox.nios.ui.widget.test.SimpleWicketTester.setUp(SimpleWicketTester.java:54)
*
I've patched the Initializer file, added some synchronization:
*
synchronized (mbeanServer) {
int i = 0;
while (mbeanServer.isRegistered(appBeanName))
{
tempDomain = name + - + i++; //$NON-NLS-1$
appBeanName = new ObjectName(tempDomain + :type=Application);
//$NON-NLS-1$
}
domain = tempDomain;
Application appBean = new Application(application);
register(appBean, appBeanName);
register(new ApplicationSettings(application), new ObjectName(domain +
:type=Application,name=ApplicationSettings)); //$NON-NLS-1$
register(new DebugSettings(application), new ObjectName(domain +
:type=Application,name=DebugSettings)); //$NON-NLS-1$
register(new MarkupSettings(application), new ObjectName(domain +
:type=Application,name=MarkupSettings)); //$NON-NLS-1$
register(new ResourceSettings(application), new ObjectName(domain +
:type=Application,name=ResourceSettings)); //$NON-NLS-1$
register(new PageSettings(application), new ObjectName(domain +
:type=Application,name=PageSettings)); //$NON-NLS-1$
register(new RequestCycleSettings(application), new ObjectName(domain
+
:type=Application,name=RequestCycleSettings)); //$NON-NLS-1$
register(new SecuritySettings(application), new ObjectName(domain +
:type=Application,name=SecuritySettings)); //$NON-NLS-1$
register(new SessionSettings(application), new ObjectName(domain +
:type=Application,name=SessionSettings)); //$NON-NLS-1$
register(new CookieValuePersisterSettings(application), new
ObjectName(domain +
:type=Application,name=CookieValuePersisterSettings)); //$NON-NLS-1$
RequestLogger sessionsBean = new RequestLogger(application);
ObjectName sessionsBeanName = new ObjectName(domain +
:type=RequestLogger); //$NON-NLS-1$
register(sessionsBean, sessionsBeanName);
}*
and the problem was gone.
The second problem I found was such mysterious exceptions from different
classes:
*org.apache.wicket.WicketRuntimeException: Exception in rendering
component: [MarkupContainer [Component id = _header_0]]
at
org.apache.wicket.Component.renderComponent(Component.java:2658)
at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
at org.apache.wicket.Component.render(Component.java:2450)
at
org.apache.wicket.MarkupContainer.autoAdd(MarkupContainer.java:229)
at
Re: Running unit test in parallel
Wicket tests also use WicketTester :-)
You can create simple application to experiment with.
2011/12/22 Vervenko Pavel willcode4f...@tut.by:
I didn't mean that I want to run core tests.
I need to run junits for wicket-based web applications in 3-4 parallel
threads. We have a lot of tests based on WicketTester and it takes a lot of
time to run them. Parallel running reduces execution time significantly.
But as far as I can see it's impossible with wicket 1.4. I'm not sure
about 1.5.x but I can't migrate to this version just to check.
22 декабря 2011 г. 18:25 пользователь Martin Grigorov
mgrigo...@apache.orgнаписал:
Hi,
Some people ran 1.5.x core tests in parallel with JUnit/Surefire
parallel support and the problems they had were related with setting
current Locale with Locale.setDefault(), i.e. JVM wide. Some tests
expect specific i18n-ized results and due to changed Locale they
failed.
Improvements in this area for 1.4.x wont be done but you can provide
patches for 1.5 if there are no API breaks and for 6.0 with API
changes.
On Thu, Dec 22, 2011 at 5:18 PM, Vervenko Pavel willcode4f...@tut.by
wrote:
Hi!
We are using wicket-1.4.8.
We have a lot of unit tests and it takes long time to run them. To reduce
running time at multi-core systems we decided to run them parallel in
multiple threads.
I use this
http://mycila.googlecode.com/svn/sandbox/src/main/java/com/mycila/sandbox/junit/runner/ConcurrentSuite.java
class
to run junits concurrently.
First problem I've faced with was some exception from
org.apache.wicket.jmx.Initializer :
*org.apache.wicket.WicketRuntimeException:
javax.management.InstanceAlreadyExistsException:
org.apache.wicket.app.SimpleWicketTester$1:type=Application
at org.apache.wicket.jmx.Initializer.init(Initializer.java:207)
at
org.apache.wicket.Application.callInitializers(Application.java:843)
at
org.apache.wicket.Application.initializeComponents(Application.java:678)
at
org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:725)
at
org.apache.wicket.protocol.http.MockWebApplication.init(MockWebApplication.java:168)
at
org.apache.wicket.util.tester.BaseWicketTester.init(BaseWicketTester.java:219)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:325)
at
org.apache.wicket.util.tester.WicketTester.init(WicketTester.java:308)
at
com.infoblox.platform.test.PlatformWicketTester.init(PlatformWicketTester.java:60)
at
com.infoblox.nios.ui.widget.test.SimpleWicketTester.setUp(SimpleWicketTester.java:54)
*
I've patched the Initializer file, added some synchronization:
*
synchronized (mbeanServer) {
int i = 0;
while (mbeanServer.isRegistered(appBeanName))
{
tempDomain = name + - + i++; //$NON-NLS-1$
appBeanName = new ObjectName(tempDomain + :type=Application);
//$NON-NLS-1$
}
domain = tempDomain;
Application appBean = new Application(application);
register(appBean, appBeanName);
register(new ApplicationSettings(application), new ObjectName(domain +
:type=Application,name=ApplicationSettings)); //$NON-NLS-1$
register(new DebugSettings(application), new ObjectName(domain +
:type=Application,name=DebugSettings)); //$NON-NLS-1$
register(new MarkupSettings(application), new ObjectName(domain +
:type=Application,name=MarkupSettings)); //$NON-NLS-1$
register(new ResourceSettings(application), new ObjectName(domain +
:type=Application,name=ResourceSettings)); //$NON-NLS-1$
register(new PageSettings(application), new ObjectName(domain +
:type=Application,name=PageSettings)); //$NON-NLS-1$
register(new RequestCycleSettings(application), new ObjectName(domain
+
:type=Application,name=RequestCycleSettings)); //$NON-NLS-1$
register(new SecuritySettings(application), new ObjectName(domain +
:type=Application,name=SecuritySettings)); //$NON-NLS-1$
register(new SessionSettings(application), new ObjectName(domain +
:type=Application,name=SessionSettings)); //$NON-NLS-1$
register(new CookieValuePersisterSettings(application), new
ObjectName(domain +
:type=Application,name=CookieValuePersisterSettings)); //$NON-NLS-1$
RequestLogger sessionsBean = new RequestLogger(application);
ObjectName sessionsBeanName = new ObjectName(domain +
:type=RequestLogger); //$NON-NLS-1$
register(sessionsBean, sessionsBeanName);
}*
and the problem was gone.
The second problem I found was such mysterious exceptions from different
classes:
*org.apache.wicket.WicketRuntimeException: Exception in rendering
component: [MarkupContainer [Component id = _header_0]]
at
org.apache.wicket.Component.renderComponent(Component.java:2658)
at
org.apache.wicket.MarkupContainer.onRender(MarkupContainer.java:1512)
at
Using proxy server
Hi folks, Trying to set up apache2/wicket combo. Wondering if instructions at https://cwiki.apache.org/WICKET/wicket-behind-a-front-end-proxy.html#Wicketbehindafront-endproxy-HowtofixWicketgeneratedlinks are still valid for wicket 1.5. If not does anyone has pointer to new setup of documents? What I want to achieve is something as follows: QA server running apache2 has two tomcat AJP connectors coming from two different server - say test and staging. Want to setup apache2 so that if you go to http://qa/test, results are served using test ajp connector. This works - almost. When wicket sees I need to sign-in or other wicket generated urls, they don't have my apache2 context. I thought fixed above mentioned was solution but that does not seem to be working. May be I am doing something bad. Any help is appreciated. Regards, Niranjan - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
