Re: Upgrade Wicket to 1.5-RC5.1 -> 'Page expired'
yes, It happens in
org.apache.wicket.request.handler.PageProvider.getPageInstance() ,
but not for the WelcomePage, but the redirection page (RedirectPage).
the CASPageAuthorizationStrategy as we are not authentified a
org.apache.wicket.RestartResponseAtInterceptPageException with in
parameter an instance of RedirectPage.
On the second call of PageProvider.getPageInstance, the pageId is of 0,
an all other parameters are nulls.
The run seems quite different on 1.5-RC4.2 version - There is only one
call of the method PageProvider.getPageInstance() and it come after the
CASPageAuthorizationStrategy.isPageAuthorized
Le 27/06/2011 11:24, Martin Grigorov a écrit :
Put a breakpoint in
org.apache.wicket.request.handler.PageProvider.getPageInstance() and
see what happens.
It seems the test tries to retrieve a page from the page store by id
but there is no such.
On Mon, Jun 27, 2011 at 12:20 PM, Thomas Franconville
wrote:
Hi,
Upgrading wicket from 1.5-RC4.2 to 1.5-RC5.1 make my Junit Test down with
the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
public void setUp()
{
tester = new WicketTester(new MyApplication());
}
@Test
public void homepageRendersSuccessfully()
{
//start and render the test page
tester.startPage(WelcomePage.class);
//assert rendered page class
tester.assertRenderedPage(RedirectPage.class);
}
}
My application use a CASPageAuthorizationStrategy inspired of
http://www.lunikon.net/2009/11/24/integrating-cas-and-wicket/
Kind Regards
Thomas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Upgrade Wicket to 1.5-RC5.1 -> 'Page expired'
Hi,
Upgrading wicket from 1.5-RC4.2 to 1.5-RC5.1 make my Junit Test down
with the error 'Page expired'
/**
* Simple test using the WicketTester
*/
public class TestHomePage
{
private WicketTester tester;
@Before
public void setUp()
{
tester = new WicketTester(new MyApplication());
}
@Test
public void homepageRendersSuccessfully()
{
//start and render the test page
tester.startPage(WelcomePage.class);
//assert rendered page class
tester.assertRenderedPage(RedirectPage.class);
}
}
My application use a CASPageAuthorizationStrategy inspired of
http://www.lunikon.net/2009/11/24/integrating-cas-and-wicket/
Kind Regards
Thomas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Re: Deploiment problem of wicket application with Jboss 5.1
To put in hard, into the vfs.xml file the directory where my ear file is generated is not satisfying as when I really want to redeploy, calling the maven command, jboss doesn't deploy the last ear. Then, I try to configure my application on integration mode instead development mode, and it works very well. So, there is a conflict between wicket in development mode and deploiment with jmx on jboss 5.1 The solution is sufficient for me. Many thanks all for your help. Thomas Le 17/06/2011 10:26, Thomas Franconville a écrit : Hi Avraham, Thank you for your experience return. Have you deployed your application with maven with JMX jboss services ? If you have made hard deployment (copy into deploy directory), it is normal that you have no problem as the directory deploy is defined into the vfs.xml file. But, I don't like this mecanism as you need to parametrized maven on all machine to say where is jboss. Isn't it ? Thanks Thomas Le 17/06/2011 07:16, Avraham Rosenzweig a écrit : We have an application based on Wicket 1.4.17 that we have deployed on JBoss 5.10 using JDK 1.6 in both clustered (using farm) and single node environments, on both Windows and Linux environments in hundreds of machines and we never experienced such an issue. I guess you need to take it to a JBoss forum. Thanks, Avraham On Thu, Jun 16, 2011 at 12:45 AM, Thomas Franconville< tfranconvi...@tetraedge.com> wrote: Yes, before deploying and using the wicket application, I have had 4Go space left on my disk. After, 0 octet is left as the [Jboss_home]/default/tmp/vfs-nested.tmp directory growing as non sense with with jar and war contained into the ear were duplicated as space left. It is "as" wicket find that the ear change and force to redeploy and then jboss find that the ear change and redeploy and so on until that no more space left. It appends on my windows machine, but also on our linux machine were we integrate the application. Le 15/06/2011 20:10, Peter Ertl a écrit : Google Translate tells me: 'Espace insuffisant sur le disque' -> 'Not enough space on disk' So did you check your free disk space? Am 15.06.2011 um 15:32 schrieb Thomas Franconville: Hi all, I am deploying my wicket application as an EAR with maven using JMX deploiment of JBoss. When I use the web application, the directory [Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the hardrive (several gigabytes !), duplicating all the jar and war in the ear. When the disk is saturated, I have this stack 2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task) ERROR - Task - Unhandled exception thrown by user code in task ModificationWatcher java.lang.RuntimeException: Failed to read zip file: org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de - D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165) at org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107) at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) at org.apache.wicket.util.io.Connections.close(Connections.java:127) at org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87) at org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233) at org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149) at org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153) at org.apache.wicket.util.thread.Task$1.run(Task.java:115) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Espace insuffisant sur le disque at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutput
Re: Deploiment problem of wicket application with Jboss 5.1
Hi Avraham, Thank you for your experience return. Have you deployed your application with maven with JMX jboss services ? If you have made hard deployment (copy into deploy directory), it is normal that you have no problem as the directory deploy is defined into the vfs.xml file. But, I don't like this mecanism as you need to parametrized maven on all machine to say where is jboss. Isn't it ? Thanks Thomas Le 17/06/2011 07:16, Avraham Rosenzweig a écrit : We have an application based on Wicket 1.4.17 that we have deployed on JBoss 5.10 using JDK 1.6 in both clustered (using farm) and single node environments, on both Windows and Linux environments in hundreds of machines and we never experienced such an issue. I guess you need to take it to a JBoss forum. Thanks, Avraham On Thu, Jun 16, 2011 at 12:45 AM, Thomas Franconville< tfranconvi...@tetraedge.com> wrote: Yes, before deploying and using the wicket application, I have had 4Go space left on my disk. After, 0 octet is left as the [Jboss_home]/default/tmp/vfs-nested.tmp directory growing as non sense with with jar and war contained into the ear were duplicated as space left. It is "as" wicket find that the ear change and force to redeploy and then jboss find that the ear change and redeploy and so on until that no more space left. It appends on my windows machine, but also on our linux machine were we integrate the application. Le 15/06/2011 20:10, Peter Ertl a écrit : Google Translate tells me: 'Espace insuffisant sur le disque' -> 'Not enough space on disk' So did you check your free disk space? Am 15.06.2011 um 15:32 schrieb Thomas Franconville: Hi all, I am deploying my wicket application as an EAR with maven using JMX deploiment of JBoss. When I use the web application, the directory [Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the hardrive (several gigabytes !), duplicating all the jar and war in the ear. When the disk is saturated, I have this stack 2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task) ERROR - Task - Unhandled exception thrown by user code in task ModificationWatcher java.lang.RuntimeException: Failed to read zip file: org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de - D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165) at org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107) at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) at org.apache.wicket.util.io.Connections.close(Connections.java:127) at org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87) at org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233) at org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149) at org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153) at org.apache.wicket.util.thread.Task$1.run(Task.java:115) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Espace insuffisant sur le disque at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) at org.jboss.virtual.VFSUtils.copyStream(VFSUtils.java:941) at org.jboss.virtual.VFSUtils.copyStreamAndClose(VFSUtils.java:901) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:562) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:619) ... 17 more My environnement is: JBoss 5.1 Wicket 1.5-RC4.2 Jdk 1.6 I am still in development mode. When I am working with the war with Jetty, I have no problem. Is somebody can explain me what happen an
Re: Deploiment problem of wicket application with Jboss 5.1
Yes, before deploying and using the wicket application, I have had 4Go space left on my disk. After, 0 octet is left as the [Jboss_home]/default/tmp/vfs-nested.tmp directory growing as non sense with with jar and war contained into the ear were duplicated as space left. It is "as" wicket find that the ear change and force to redeploy and then jboss find that the ear change and redeploy and so on until that no more space left. It appends on my windows machine, but also on our linux machine were we integrate the application. Le 15/06/2011 20:10, Peter Ertl a écrit : Google Translate tells me: 'Espace insuffisant sur le disque' -> 'Not enough space on disk' So did you check your free disk space? Am 15.06.2011 um 15:32 schrieb Thomas Franconville: Hi all, I am deploying my wicket application as an EAR with maven using JMX deploiment of JBoss. When I use the web application, the directory [Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the hardrive (several gigabytes !), duplicating all the jar and war in the ear. When the disk is saturated, I have this stack 2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task) ERROR - Task - Unhandled exception thrown by user code in task ModificationWatcher java.lang.RuntimeException: Failed to read zip file: org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de - D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165) at org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107) at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) at org.apache.wicket.util.io.Connections.close(Connections.java:127) at org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87) at org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233) at org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149) at org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153) at org.apache.wicket.util.thread.Task$1.run(Task.java:115) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Espace insuffisant sur le disque at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) at org.jboss.virtual.VFSUtils.copyStream(VFSUtils.java:941) at org.jboss.virtual.VFSUtils.copyStreamAndClose(VFSUtils.java:901) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:562) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:619) ... 17 more My environnement is: JBoss 5.1 Wicket 1.5-RC4.2 Jdk 1.6 I am still in development mode. When I am working with the war with Jetty, I have no problem. Is somebody can explain me what happen and give me any clue to go forward. Thanks Thomas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Deploiment problem of wicket application with Jboss 5.1
The workaround is not so far.
I try to put the target directory as a key of the vfs.xml file and it
works. It duplicates only once files so no more problem of space.
BUT it is not so good for me as each developer has directory different,
and when we work with remote server, the directory is where wagon is
copying file. JMX lets file where they are.
I go back with my question about wicket, because of, with any other ear
without wicket, there is no problem.
What is doing wicket to give jboss a such problem ?
Le 15/06/2011 17:29, Thomas Franconville a écrit :
I have added as specified the entry
${jboss.server.home.url}farm
*
into the file server\default\conf\bootstrap\vfs.xml
But it changes nothing.
They wrote about farm. I am in default configuration, so farm is not
activated. I am not sure it is exactely the problem.
What mecanism is there into wicket of refresh ? Why it is scanning the
ear ?
NB: I have had already seen this note but as it was specified on all
configuration, I have already test this in the file
**server\all\conf\bootstrap\vfs.xml, but it chanded nothing too.*
Le 15/06/2011 15:42, Avraham Rosenzweig a écrit :
It's a known JBoss issue with a workaround:
http://community.jboss.org/message/8053
On Wed, Jun 15, 2011 at 4:32 PM, Thomas Franconville<
tfranconvi...@tetraedge.com> wrote:
Hi all,
I am deploying my wicket application as an EAR with maven using JMX
deploiment of JBoss.
When I use the web application, the directory
[Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the
hardrive (several gigabytes !), duplicating all the jar and war in
the ear.
When the disk is saturated, I have this stack
2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task)
ERROR -
Task - Unhandled exception thrown by user code
in task
ModificationWatcher
java.lang.RuntimeException: Failed to read zip file:
org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de -
D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817)
at
org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191)
at
org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684)
at
org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165)
at
org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107)
at
org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93)
at
org.apache.wicket.util.io.Connections.close(Connections.java:127)
at
org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87)
at
org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233)
at
org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149)
at
org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153)
at org.apache.wicket.util.thread.Task$1.run(Task.java:115)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: Espace insuffisant sur le disque
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)
at
java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.jboss.virtual.VFSUtils.copyStream(VFSUtils.java:941)
at
org.jboss.virtual.VFSUtils.copyStreamAndClose(VFSUtils.java:901)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:562)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:619)
... 17 more
My environnement is:
JBoss 5.1
Wicket 1.5-RC4.2
Jdk 1.6
I am still in development mode.
When I am working with the war with Jetty, I have no problem.
Is somebody can explain me what happen and give me any clue to go
forward.
Thanks
Thomas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket
Re: Deploiment problem of wicket application with Jboss 5.1
I have added as specified the entry
${jboss.server.home.url}farm
*
into the file server\default\conf\bootstrap\vfs.xml
But it changes nothing.
They wrote about farm. I am in default configuration, so farm is not
activated. I am not sure it is exactely the problem.
What mecanism is there into wicket of refresh ? Why it is scanning the ear ?
NB: I have had already seen this note but as it was specified on all
configuration, I have already test this in the file
**server\all\conf\bootstrap\vfs.xml, but it chanded nothing too.*
Le 15/06/2011 15:42, Avraham Rosenzweig a écrit :
It's a known JBoss issue with a workaround:
http://community.jboss.org/message/8053
On Wed, Jun 15, 2011 at 4:32 PM, Thomas Franconville<
tfranconvi...@tetraedge.com> wrote:
Hi all,
I am deploying my wicket application as an EAR with maven using JMX
deploiment of JBoss.
When I use the web application, the directory
[Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the
hardrive (several gigabytes !), duplicating all the jar and war in the ear.
When the disk is saturated, I have this stack
2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task) ERROR -
Task - Unhandled exception thrown by user code in task
ModificationWatcher
java.lang.RuntimeException: Failed to read zip file:
org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de -
D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817)
at
org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191)
at
org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684)
at
org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165)
at
org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107)
at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118)
at
org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93)
at org.apache.wicket.util.io.Connections.close(Connections.java:127)
at
org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87)
at
org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233)
at
org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149)
at
org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153)
at org.apache.wicket.util.thread.Task$1.run(Task.java:115)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: Espace insuffisant sur le disque
at java.io.FileOutputStream.writeBytes(Native Method)
at java.io.FileOutputStream.write(FileOutputStream.java:260)
at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105)
at org.jboss.virtual.VFSUtils.copyStream(VFSUtils.java:941)
at org.jboss.virtual.VFSUtils.copyStreamAndClose(VFSUtils.java:901)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:562)
at
org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:619)
... 17 more
My environnement is:
JBoss 5.1
Wicket 1.5-RC4.2
Jdk 1.6
I am still in development mode.
When I am working with the war with Jetty, I have no problem.
Is somebody can explain me what happen and give me any clue to go forward.
Thanks
Thomas
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
Deploiment problem of wicket application with Jboss 5.1
Hi all, I am deploying my wicket application as an EAR with maven using JMX deploiment of JBoss. When I use the web application, the directory [Jboss_home]/default/tmp/vfs-nested.tmp is growing until saturated the hardrive (several gigabytes !), duplicating all the jar and war in the ear. When the disk is saturated, I have this stack 2011-06-15 11:06:41,220 INFO [STDOUT] (ModificationWatcher Task) ERROR - Task - Unhandled exception thrown by user code in task ModificationWatcher java.lang.RuntimeException: Failed to read zip file: org.jboss.virtual.plugins.context.zip.ZipFileWrapper@1d295de - D:\Workspaces\UbiAnt\HemisEAR\target\Hemis.ear at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:628) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.checkIfModified(ZipEntryContext.java:773) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.getChild(ZipEntryContext.java:817) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.createChildHandler(ZipEntryHandler.java:191) at org.jboss.virtual.plugins.context.AbstractVirtualFileHandler.structuredFindChild(AbstractVirtualFileHandler.java:684) at org.jboss.virtual.plugins.context.zip.ZipEntryHandler.getChild(ZipEntryHandler.java:165) at org.jboss.virtual.plugins.context.DelegatingHandler.getChild(DelegatingHandler.java:107) at org.jboss.virtual.VirtualFile.findChild(VirtualFile.java:457) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.resolveVirtualFile(VirtualFileURLConnection.java:106) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getVirtualFile(VirtualFileURLConnection.java:118) at org.jboss.virtual.plugins.vfs.VirtualFileURLConnection.getInputStream(VirtualFileURLConnection.java:93) at org.apache.wicket.util.io.Connections.close(Connections.java:127) at org.apache.wicket.util.io.Connections.getLastModified(Connections.java:87) at org.apache.wicket.util.resource.UrlResourceStream.lastModifiedTime(UrlResourceStream.java:233) at org.apache.wicket.markup.MarkupResourceStream.lastModifiedTime(MarkupResourceStream.java:149) at org.apache.wicket.util.watch.ModificationWatcher$1.run(ModificationWatcher.java:153) at org.apache.wicket.util.thread.Task$1.run(Task.java:115) at java.lang.Thread.run(Thread.java:662) Caused by: java.io.IOException: Espace insuffisant sur le disque at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:260) at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) at org.jboss.virtual.VFSUtils.copyStream(VFSUtils.java:941) at org.jboss.virtual.VFSUtils.copyStreamAndClose(VFSUtils.java:901) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.initEntries(ZipEntryContext.java:562) at org.jboss.virtual.plugins.context.zip.ZipEntryContext.ensureEntries(ZipEntryContext.java:619) ... 17 more My environnement is: JBoss 5.1 Wicket 1.5-RC4.2 Jdk 1.6 I am still in development mode. When I am working with the war with Jetty, I have no problem. Is somebody can explain me what happen and give me any clue to go forward. Thanks Thomas - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
