[OT] Configure wicket.configuration outside web.xml in Tomcat 6

2011-07-04 Thread Mike Mander

Hi,

i'm trying to configure my wicket.configuration property without adding 
it to web.xml. I use tomcat 6.
Adding wicket.configuration=deployment in 
CATALINA_HOME/conf/catalina.properties was not working.
App starts in development mode (after tomcat restart / param not present 
in web.xml). Adding the property to command line is only the last option 
for me. Because i'm stupid i bet i will forget it somewhere :-).


Background is: If i add the property to web.xml
a) i have to change it for all production apps on server
b) and i have to deploy all apps twice in production. Firstly with the 
default configured web.xml (development) and then hotdeploy with the 
changed web.xml (deployment).


This leads often to perm gen space which is another problem (I know it 
and it's not part of this problem :-).


Maybe someone has a good plan on this issue.

Thanks
Per

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [OT] Configure wicket.configuration outside web.xml in Tomcat 6

2011-07-04 Thread Bas Gooren

Hi,

As suggested on the mailing list once, what I've been using for a while 
now is having deployment in web.xml, and adding 
-Dwicket.configuration=development to my tomcat command line from Eclipse.


This way you always package a production-ready jar/war/ear and can run 
in development mode locally.


Bas

Op 4-7-2011 9:46, schreef Mike Mander:

Hi,

i'm trying to configure my wicket.configuration property without 
adding it to web.xml. I use tomcat 6.
Adding wicket.configuration=deployment in 
CATALINA_HOME/conf/catalina.properties was not working.
App starts in development mode (after tomcat restart / param not 
present in web.xml). Adding the property to command line is only the 
last option for me. Because i'm stupid i bet i will forget it 
somewhere :-).


Background is: If i add the property to web.xml
a) i have to change it for all production apps on server
b) and i have to deploy all apps twice in production. Firstly with the 
default configured web.xml (development) and then hotdeploy with the 
changed web.xml (deployment).


This leads often to perm gen space which is another problem (I know it 
and it's not part of this problem :-).


Maybe someone has a good plan on this issue.

Thanks
Per

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: [OT] Configure wicket.configuration outside web.xml in Tomcat 6

2011-07-04 Thread Mike Mander

Thanks Bas,

you solved my problem. I don't use tomcat within eclipse. I use the 
standard jetty server with Start class. I wasn't clear at this point.


But you brought me the light. I set deployment as 
configuration-param-value to my web.xml. And in Start class i set the 
system property wicket.configuration to development. And it works.


Thanks and Cheers
Per

Am 04.07.2011 12:56, schrieb Bas Gooren:

Hi,

As suggested on the mailing list once, what I've been using for a 
while now is having deployment in web.xml, and adding 
-Dwicket.configuration=development to my tomcat command line from 
Eclipse.


This way you always package a production-ready jar/war/ear and can run 
in development mode locally.


Bas

Op 4-7-2011 9:46, schreef Mike Mander:

Hi,

i'm trying to configure my wicket.configuration property without 
adding it to web.xml. I use tomcat 6.
Adding wicket.configuration=deployment in 
CATALINA_HOME/conf/catalina.properties was not working.
App starts in development mode (after tomcat restart / param not 
present in web.xml). Adding the property to command line is only the 
last option for me. Because i'm stupid i bet i will forget it 
somewhere :-).


Background is: If i add the property to web.xml
a) i have to change it for all production apps on server
b) and i have to deploy all apps twice in production. Firstly with 
the default configured web.xml (development) and then hotdeploy 
with the changed web.xml (deployment).


This leads often to perm gen space which is another problem (I know 
it and it's not part of this problem :-).


Maybe someone has a good plan on this issue.

Thanks
Per

-
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: tomcat 6

2008-10-22 Thread Nino Saturnino Martinez Vazquez Wael

Argh just saw that I did a typo..

I of course meant start.java :) Everything's setup for you if you use 
wicket archetype, iolite or wickettopia..


Nino Saturnino Martinez Vazquez Wael wrote:

Check you dependencies..

I just use jetty when running from eclipse, much simpler.. Just run 
start jar or debug start jar.. etc..


Leucht, Axel wrote:

Hi,

I'm currently trying to get a HelloWorld application running with 
wicket 1.3.4.


I'm doing all my web development from within the Eclipse IDE (3.4 
Ganymede), so I suspect setup of the project should be easy.
When the server environment is set to tomcat 5.5.27 the 
HelloWorldApplication runs fine but NOT under tomcat 6.0.16!


There is no clue in the logs stating that wicket is started in 
development mode which it is when started under tc 5.5.27. The 
application does run when I start tomcat 6.0.16 in standalone mode 
(outside Eclipse).


Does someone knows what to do to make it run from within Eclipse?

/Axel

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  




--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat 6

2008-10-21 Thread Guðmundur Bjarni

If you decide to go for Jetty, you should try the run-jetty-run[1] plugin
that Eelco wrote. Basically if your project is set up right, i.e. web.xml in
the right place and so on. You can run it like any other Java Application
from Eclipse's run configurations.

regards,
Guðmundur Bjarni


[1] http://code.google.com/p/run-jetty-run/
-- 
View this message in context: 
http://www.nabble.com/tomcat-6-tp20064539p20086138.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat 6

2008-10-21 Thread Timo Rantalaiho
On Tue, 21 Oct 2008, Guðmundur Bjarni wrote:
 If you decide to go for Jetty, you should try the run-jetty-run[1] plugin
 that Eelco wrote. Basically if your project is set up right, i.e. web.xml in
 the right place and so on. You can run it like any other Java Application
 from Eclipse's run configurations.

Jetty can also easily be run like any Java application, 
without any plugin, with about 20 lines of code. Wicket 
quickstart provides a working example.

Best wishes,
Timo

-- 
Timo Rantalaiho   
Reaktor Innovations OyURL: http://www.ri.fi/ 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat 6

2008-10-20 Thread Nino Saturnino Martinez Vazquez Wael

Check you dependencies..

I just use jetty when running from eclipse, much simpler.. Just run 
start jar or debug start jar.. etc..


Leucht, Axel wrote:

Hi,

I'm currently trying to get a HelloWorld application running with wicket 1.3.4.

I'm doing all my web development from within the Eclipse IDE (3.4 Ganymede), so 
I suspect setup of the project should be easy.
When the server environment is set to tomcat 5.5.27 the HelloWorldApplication 
runs fine but NOT under tomcat 6.0.16!

There is no clue in the logs stating that wicket is started in development mode 
which it is when started under tc 5.5.27. The application does run when I start 
tomcat 6.0.16 in standalone mode (outside Eclipse).

Does someone knows what to do to make it run from within Eclipse?

/Axel

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

  


--
-Wicket for love

Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: tomcat 6

2008-10-20 Thread Timm Helbig
Hi,

I use Tomcat 6.0.16/17/18 with the Wicket Example Application out of the box. 
No Problems at all. I suspect Tomcat is not the Problem.

Regards,
Timm

Am Monday 20 October 2008 09:30:32 schrieb Leucht, Axel:
 Hi,

 I'm currently trying to get a HelloWorld application running with wicket
 1.3.4.

 I'm doing all my web development from within the Eclipse IDE (3.4
 Ganymede), so I suspect setup of the project should be easy. When the
 server environment is set to tomcat 5.5.27 the HelloWorldApplication runs
 fine but NOT under tomcat 6.0.16!

 There is no clue in the logs stating that wicket is started in development
 mode which it is when started under tc 5.5.27. The application does run
 when I start tomcat 6.0.16 in standalone mode (outside Eclipse).

 Does someone knows what to do to make it run from within Eclipse?

 /Axel

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Wicket/Seam on Tomcat 6?

2008-09-30 Thread Martijn Lindhout
Hi all,

Has anyone a running setup of Wicket/Seam on Tomcat. No EJB's, just JPA.

I get a string ClassNotFoundException on a class that is present in
WEB-INF/classes

-- 
Martijn Lindhout
JointEffort IT Services
http://www.jointeffort.nl
[EMAIL PROTECTED]
+31 (0)6 18 47 25 29

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Wicket/Seam on Tomcat 6?

2008-09-30 Thread Paolo Di Tommaso
I've successfully run it on Tomcat 5.5 ..

-- Paolo

On Tue, Sep 30, 2008 at 1:49 PM, Martijn Lindhout
[EMAIL PROTECTED]wrote:

 Hi all,

 Has anyone a running setup of Wicket/Seam on Tomcat. No EJB's, just JPA.

 I get a string ClassNotFoundException on a class that is present in
 WEB-INF/classes

 --
 Martijn Lindhout
 JointEffort IT Services
 http://www.jointeffort.nl
 [EMAIL PROTECTED]
 +31 (0)6 18 47 25 29

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Tomcat 6 clustering problem

2008-06-25 Thread Artem D.

Hi all,
I've got wicket 1.4-m2 based application running on two different network
hosts configured as Tomcat 6 Simple TCP cluster.
I try to simulate failover with session replication using the following
schema:
1) Log into the first server, store some info in HTTP session
2) Access mounted page on the first server, i.e.
http://first.server/mounted/page
3) Try to access the same page on the second server, i.e.
http://second.server/mounted/page

I assume that HTTP session should replicate between Tomcat's and I want to
get immediate reply from the second server, but all I get is forwarding me
to the login screen and the following entries in log:

Jun 25, 2008 5:10:39 PM org.apache.catalina.ha.session.DeltaManager
messageReceived
SEVERE: Manager [localhost#/mas]: Unable to receive message through TCP
channel
java.lang.IllegalArgumentException: Unknown object type null
at
org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSerialization(DiskPageStore.java:1211)
at
org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.readObject(SecondLevelCacheSessionStore.java:403)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at
java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at
java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at
java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
org.apache.catalina.ha.session.DeltaRequest$AttributeInfo.readExternal(DeltaRequest.java:361)
at
org.apache.catalina.ha.session.DeltaRequest.readExternal(DeltaRequest.java:255)
at
org.apache.catalina.ha.session.DeltaManager.deserializeDeltaRequest(DeltaManager.java:619)
at
org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaManager.java:1363)
at
org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager.java:1320)
at
org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaManager.java:1083)
at
org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(ClusterSessionListener.java:87)
at
org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:899)
at
org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:880)
at
org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChannel.java:269)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:110)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:241)
at
org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:225)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:188)
at
org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:91)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

Is there a way to resolve this issue?
-- 
View this message in context: 
http://www.nabble.com/Tomcat-6-clustering-problem-tp18112263p18112263.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 6 clustering problem

2008-06-25 Thread Matej Knopp
Any chance you can try it with latest trunk?

-Matej

On Wed, Jun 25, 2008 at 3:18 PM, Artem D. [EMAIL PROTECTED] wrote:

 Hi all,
 I've got wicket 1.4-m2 based application running on two different network
 hosts configured as Tomcat 6 Simple TCP cluster.
 I try to simulate failover with session replication using the following
 schema:
 1) Log into the first server, store some info in HTTP session
 2) Access mounted page on the first server, i.e.
 http://first.server/mounted/page
 3) Try to access the same page on the second server, i.e.
 http://second.server/mounted/page

 I assume that HTTP session should replicate between Tomcat's and I want to
 get immediate reply from the second server, but all I get is forwarding me
 to the login screen and the following entries in log:

 Jun 25, 2008 5:10:39 PM org.apache.catalina.ha.session.DeltaManager
 messageReceived
 SEVERE: Manager [localhost#/mas]: Unable to receive message through TCP
 channel
 java.lang.IllegalArgumentException: Unknown object type null
at
 org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSerialization(DiskPageStore.java:1211)
at
 org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.readObject(SecondLevelCacheSessionStore.java:403)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at
 java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at
 java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
 org.apache.catalina.ha.session.DeltaRequest$AttributeInfo.readExternal(DeltaRequest.java:361)
at
 org.apache.catalina.ha.session.DeltaRequest.readExternal(DeltaRequest.java:255)
at
 org.apache.catalina.ha.session.DeltaManager.deserializeDeltaRequest(DeltaManager.java:619)
at
 org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaManager.java:1363)
at
 org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager.java:1320)
at
 org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaManager.java:1083)
at
 org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(ClusterSessionListener.java:87)
at
 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:899)
at
 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:880)
at
 org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChannel.java:269)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:110)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:241)
at
 org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:225)
at
 org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:188)
at
 org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:91)
at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

 Is there a way to resolve this issue?
 --
 View this message in context: 
 http://www.nabble.com/Tomcat-6-clustering-problem-tp18112263p18112263.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Tomcat 6 clustering problem

2008-06-25 Thread Artem D.

Just tried with 1.4-SNAPSHOT.
Same exception but different line in the DiskPageStore.java
SEVERE: Manager [localhost#/mas]: Unable to receive message through TCP
channel
java.lang.IllegalArgumentException: Unknown object type null
at
org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSerialization(DiskPageStore.java:1215)



Matej Knopp-2 wrote:
 
 Any chance you can try it with latest trunk?
 
 -Matej
 
 On Wed, Jun 25, 2008 at 3:18 PM, Artem D. [EMAIL PROTECTED] wrote:

 Hi all,
 I've got wicket 1.4-m2 based application running on two different network
 hosts configured as Tomcat 6 Simple TCP cluster.
 I try to simulate failover with session replication using the following
 schema:
 1) Log into the first server, store some info in HTTP session
 2) Access mounted page on the first server, i.e.
 http://first.server/mounted/page
 3) Try to access the same page on the second server, i.e.
 http://second.server/mounted/page

 I assume that HTTP session should replicate between Tomcat's and I want
 to
 get immediate reply from the second server, but all I get is forwarding
 me
 to the login screen and the following entries in log:

 Jun 25, 2008 5:10:39 PM org.apache.catalina.ha.session.DeltaManager
 messageReceived
 SEVERE: Manager [localhost#/mas]: Unable to receive message through TCP
 channel
 java.lang.IllegalArgumentException: Unknown object type null
at
 org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSerialization(DiskPageStore.java:1211)
at
 org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevelCachePageMap.readObject(SecondLevelCacheSessionStore.java:403)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
at
 java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
at
 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753)
at
 java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
at
 java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
at
 org.apache.catalina.ha.session.DeltaRequest$AttributeInfo.readExternal(DeltaRequest.java:361)
at
 org.apache.catalina.ha.session.DeltaRequest.readExternal(DeltaRequest.java:255)
at
 org.apache.catalina.ha.session.DeltaManager.deserializeDeltaRequest(DeltaManager.java:619)
at
 org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaManager.java:1363)
at
 org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager.java:1320)
at
 org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaManager.java:1083)
at
 org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(ClusterSessionListener.java:87)
at
 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:899)
at
 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpCluster.java:880)
at
 org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChannel.java:269)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.messageReceived(TcpFailureDetector.java:110)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(ChannelInterceptorBase.java:79)
at
 org.apache.catalina.tribes.group.ChannelCoordinator.messageReceived(ChannelCoordinator.java:241)
at
 org.apache.catalina.tribes.transport.ReceiverBase.messageDataReceived(ReceiverBase.java:225)
at
 org.apache.catalina.tribes.transport.nio.NioReplicationTask.drainChannel(NioReplicationTask.java:188)
at
 org.apache.catalina.tribes.transport.nio.NioReplicationTask.run(NioReplicationTask.java:91)
at
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)

 Is there a way to resolve this issue?
 --
 View this message in context:
 http://www.nabble.com/Tomcat-6-clustering-problem-tp18112263p18112263.html
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED

RE: Tomcat 6 clustering problem

2008-06-25 Thread Zappaterrini, Larry
Well in a production situation there would be one host name used and
failover would just change which server the requests to that host name
get routed to. In that scenario the same cookies would be used so no
problem.

You should be able to use some trickery in your hosts file to mimic
this. Add a host name (clustertest perhaps)  that points to the first
server's IP address, access the site, switch the IP address in the hosts
file to the second server, verify that the second server is indeed hit
and that the behavior is correct.

I'm not sure if you are familiar with working with a hosts file so just
know that on all Unix-like systems I have encountered it is found at
/etc/hosts and on all Windows systems I have encountered it is found at
C:\WINDOWS\system32\drivers\etc\hosts

Larry

-Original Message-
From: Artem D. [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, June 25, 2008 10:05 AM
To: users@wicket.apache.org
Subject: RE: Tomcat 6 clustering problem


Disabling cookies in browser made it work!
Servers are configured with jvmRoutes jvm1 and jvm2, i.e. for the first
server:

Engine name=Catalina defaultHost=localhost jvmRoute=jvm1

jsessionid request parameter while requesting the first server looks
like
jsessionid=3E526DD2214AEA5B5C2DAB9C6713AF26.jvm1

When switching to the second server jvm2 suffix is used.

What's the correct way to make it work with enabled cookies?

-Artem.


lzappaterrini wrote:
 
 Are you sure that the same JSESSIONID cookie is being sent to both
 servers? Cookies only get sent when the host value matches the host in
 the URL. Might that be your issue?  
 
 -Original Message-
 From: Artem D. [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 25, 2008 9:18 AM
 To: users@wicket.apache.org
 Subject: Tomcat 6 clustering problem
 
 
 Hi all,
 I've got wicket 1.4-m2 based application running on two different
 network
 hosts configured as Tomcat 6 Simple TCP cluster.
 I try to simulate failover with session replication using the
following
 schema:
 1) Log into the first server, store some info in HTTP session
 2) Access mounted page on the first server, i.e.
 http://first.server/mounted/page
 3) Try to access the same page on the second server, i.e.
 http://second.server/mounted/page
 
 I assume that HTTP session should replicate between Tomcat's and I
want
 to
 get immediate reply from the second server, but all I get is
forwarding
 me
 to the login screen and the following entries in log:
 
 Jun 25, 2008 5:10:39 PM org.apache.catalina.ha.session.DeltaManager
 messageReceived
 SEVERE: Manager [localhost#/mas]: Unable to receive message through
TCP
 channel
 java.lang.IllegalArgumentException: Unknown object type null
 at

org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSeri
 alization(DiskPageStore.java:1211)
 at

org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevel
 CachePageMap.readObject(SecondLevelCacheSessionStore.java:403)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at

sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
 a:39)
 at

sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
 Impl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at
 java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
 at

java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753
 )
 at
 java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at
 java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at

org.apache.catalina.ha.session.DeltaRequest$AttributeInfo.readExternal(D
 eltaRequest.java:361)
 at

org.apache.catalina.ha.session.DeltaRequest.readExternal(DeltaRequest.ja
 va:255)
 at

org.apache.catalina.ha.session.DeltaManager.deserializeDeltaRequest(Delt
 aManager.java:619)
 at

org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaMan
 ager.java:1363)
 at

org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager
 .java:1320)
 at

org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaMan
 ager.java:1083)
 at

org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(Cl
 usterSessionListener.java:87)
 at

org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpClu
 ster.java:899)
 at

org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpClu
 ster.java:880)
 at

org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChann
 el.java:269)
 at

org.apache.catalina.tribes.group.ChannelInterceptorBase.messageReceived(
 ChannelInterceptorBase.java:79)
 at

org.apache.catalina.tribes.group.interceptors.TcpFailureDetector.message
 Received(TcpFailureDetector.java:110

RE: Tomcat 6 clustering problem

2008-06-25 Thread Artem D.

Just tested you suggestion - it works like a charm!
Thanks for your help!

Artem.


lzappaterrini wrote:
 
 Well in a production situation there would be one host name used and
 failover would just change which server the requests to that host name
 get routed to. In that scenario the same cookies would be used so no
 problem.
 
 You should be able to use some trickery in your hosts file to mimic
 this. Add a host name (clustertest perhaps)  that points to the first
 server's IP address, access the site, switch the IP address in the hosts
 file to the second server, verify that the second server is indeed hit
 and that the behavior is correct.
 
 I'm not sure if you are familiar with working with a hosts file so just
 know that on all Unix-like systems I have encountered it is found at
 /etc/hosts and on all Windows systems I have encountered it is found at
 C:\WINDOWS\system32\drivers\etc\hosts
 
 Larry
 
 -Original Message-
 From: Artem D. [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 25, 2008 10:05 AM
 To: users@wicket.apache.org
 Subject: RE: Tomcat 6 clustering problem
 
 
 Disabling cookies in browser made it work!
 Servers are configured with jvmRoutes jvm1 and jvm2, i.e. for the first
 server:
 
 Engine name=Catalina defaultHost=localhost jvmRoute=jvm1
 
 jsessionid request parameter while requesting the first server looks
 like
 jsessionid=3E526DD2214AEA5B5C2DAB9C6713AF26.jvm1
 
 When switching to the second server jvm2 suffix is used.
 
 What's the correct way to make it work with enabled cookies?
 
 -Artem.
 
 
 lzappaterrini wrote:
 
 Are you sure that the same JSESSIONID cookie is being sent to both
 servers? Cookies only get sent when the host value matches the host in
 the URL. Might that be your issue?  
 
 -Original Message-
 From: Artem D. [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, June 25, 2008 9:18 AM
 To: users@wicket.apache.org
 Subject: Tomcat 6 clustering problem
 
 
 Hi all,
 I've got wicket 1.4-m2 based application running on two different
 network
 hosts configured as Tomcat 6 Simple TCP cluster.
 I try to simulate failover with session replication using the
 following
 schema:
 1) Log into the first server, store some info in HTTP session
 2) Access mounted page on the first server, i.e.
 http://first.server/mounted/page
 3) Try to access the same page on the second server, i.e.
 http://second.server/mounted/page
 
 I assume that HTTP session should replicate between Tomcat's and I
 want
 to
 get immediate reply from the second server, but all I get is
 forwarding
 me
 to the login screen and the following entries in log:
 
 Jun 25, 2008 5:10:39 PM org.apache.catalina.ha.session.DeltaManager
 messageReceived
 SEVERE: Manager [localhost#/mas]: Unable to receive message through
 TCP
 channel
 java.lang.IllegalArgumentException: Unknown object type null
 at

 org.apache.wicket.protocol.http.pagestore.DiskPageStore.restoreAfterSeri
 alization(DiskPageStore.java:1211)
 at

 org.apache.wicket.protocol.http.SecondLevelCacheSessionStore$SecondLevel
 CachePageMap.readObject(SecondLevelCacheSessionStore.java:403)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at

 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
 a:39)
 at

 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
 Impl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at
 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:974)
 at
 java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1849)
 at

 java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1753
 )
 at
 java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1329)
 at
 java.io.ObjectInputStream.readObject(ObjectInputStream.java:351)
 at

 org.apache.catalina.ha.session.DeltaRequest$AttributeInfo.readExternal(D
 eltaRequest.java:361)
 at

 org.apache.catalina.ha.session.DeltaRequest.readExternal(DeltaRequest.ja
 va:255)
 at

 org.apache.catalina.ha.session.DeltaManager.deserializeDeltaRequest(Delt
 aManager.java:619)
 at

 org.apache.catalina.ha.session.DeltaManager.handleSESSION_DELTA(DeltaMan
 ager.java:1363)
 at

 org.apache.catalina.ha.session.DeltaManager.messageReceived(DeltaManager
 .java:1320)
 at

 org.apache.catalina.ha.session.DeltaManager.messageDataReceived(DeltaMan
 ager.java:1083)
 at

 org.apache.catalina.ha.session.ClusterSessionListener.messageReceived(Cl
 usterSessionListener.java:87)
 at

 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpClu
 ster.java:899)
 at

 org.apache.catalina.ha.tcp.SimpleTcpCluster.messageReceived(SimpleTcpClu
 ster.java:880)
 at

 org.apache.catalina.tribes.group.GroupChannel.messageReceived(GroupChann
 el.java:269

Re: wicket cluster on tomcat 6

2007-12-13 Thread Johan Compagner
huh?
When are you doing back by javascript in your wicket application?
Do you have clientside scripts that does fancy things?

normally if you want to go back to a previous page then just set that page
as a response page (on the serverside)

johan



On Dec 13, 2007 11:49 AM, michalb_cz [EMAIL PROTECTED] wrote:


 Any workaround? I can't do just back in history (for example by
 javascript),
 because I need rerender the back page ('cos I modify back page's model)


 Sebastiaan van Erk wrote:
 
  It has to do with the page store. Note that the back button will work,
  but clicking on links on the page after you use the back button will
  cause page expired.
 
  See:
 
  http://www.slideshare.net/jcompagner/session-stores-page-maps-and-pages/
 
  if you want the nitty gritty details.
 
  But I still think you should first verify that this is actually what is
  happening.
 
  Regards,
  Sebastiaan
 
  michalb_cz wrote:
  And the reason? Why back button won't work on cluster?
 
 
 
  Matej Knopp-2 wrote:
  Hi,
 
  at this point back button will not work across cluster (it's planned
  though). However, the failover for last accessed page should work
  anyway. If it doesn't, you have probably problem in your
  configuration.
 
  -Matej
 
 
 
 
 

 --
 View this message in context:
 http://www.nabble.com/wicket-cluster-on-tomcat-6-tp14147973p14313634.html
  Sent from the Wicket - User mailing list archive at 
 Nabble.comhttp://nabble.com/
 .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]




Re: wicket cluster on tomcat 6

2007-12-13 Thread michalb_cz

I don't do that, but when I use setResponsePage(backPage) - links on backPage
are broken from time to time (I don't know the reason)
This exception is throwed:

org.apache.wicket.WicketRuntimeException: component
formChooseCategory:tableShowBooks:rows:202:cells:8:cell:editLink not found
on page ChooseCategoryPage[id = 32], listener interface =
[RequestListenerInterface name=ILinkListener, method=public abstract void
org.apache.wicket.markup.html.link.ILinkListener.onLinkClicked()]
 at
org.apache.wicket.request.AbstractRequestCycleProcessor.resolveListenerInterfaceTarget(AbstractRequestCycleProcessor.java:411)
 at
org.apache.wicket.request.AbstractRequestCycleProcessor.resolveRenderedPage(AbstractRequestCycleProcessor.java:456)
 at
org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:139)
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1152)
 at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1248)
 at org.apache.wicket.RequestCycle.request(RequestCycle.java:489)
 at
org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:343)
 at
org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:121)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)

note that I use AjaxSelfUpdatingTimerBehavior behaviour on form, which
refresh table each second (btw the row number is changed each second)


Johan Compagner wrote:
 
 huh?
 When are you doing back by javascript in your wicket application?
 Do you have clientside scripts that does fancy things?
 
 normally if you want to go back to a previous page then just set that page
 as a response page (on the serverside)
 
 johan
 
 
 
 On Dec 13, 2007 11:49 AM, michalb_cz [EMAIL PROTECTED] wrote:
 

 Any workaround? I can't do just back in history (for example by
 javascript),
 because I need rerender the back page ('cos I modify back page's model)


 Sebastiaan van Erk wrote:
 
  It has to do with the page store. Note that the back button will work,
  but clicking on links on the page after you use the back button will
  cause page expired.
 
  See:
 
 
 http://www.slideshare.net/jcompagner/session-stores-page-maps-and-pages/
 
  if you want the nitty gritty details.
 
  But I still think you should first verify that this is actually what is
  happening.
 
  Regards,
  Sebastiaan
 
  michalb_cz wrote:
  And the reason? Why back button won't work on cluster?
 
 
 
  Matej Knopp-2 wrote:
  Hi,
 
  at this point back button will not work across cluster (it's planned
  though). However, the failover for last accessed page should work
  anyway. If it doesn't, you have probably problem in your
  configuration.
 
  -Matej
 
 
 
 
 

 --
 View this message in context:
 http://www.nabble.com/wicket-cluster-on-tomcat-6-tp14147973p14313634.html
  Sent from the Wicket - User mailing list archive at
 Nabble.comhttp://nabble.com/
 .


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


 
 

-- 
View this message in context: 
http://www.nabble.com/wicket-cluster-on-tomcat-6-tp14147973p14314938.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



wicket cluster on tomcat 6

2007-12-04 Thread michalb_cz

Lo,

I have been trying to make Tomcat cluster with Wicket, but every time when
there is some operation which use session bound information (backpage
object, models...etc.) PageExpired error occures.
It seems rather like problem in cluster configuration not in wicket, but
maybe somebody here has some experience with this. Note that everything is
ok when one of two cluster node (one of server) is turn off.
(all requests are managed by only one server) or when requests are made on
stateless pages.

Apache HTTP (as loadbalancer)
httpd.conf
JkMount  /wicketapp/* router

worker.properties
worker.list=router
# Set properties for worker1 (ajp12)
worker.worker1.type=ajp13
worker.worker1.host=server1
worker.worker1.port=8009
worker.worker1.lbfactor=1
worker.worker1.redirect=worker2
# Set properties for worker2 (ajp13)
worker.worker2.type=ajp13
worker.worker2.host=server2
worker.worker2.port=8009
worker.worker2.lbfactor=1
worker.worker2.connection_pool_timeout=600
worker.worker2.socket_keepalive=1
worker.worker2.socket_timeout=60
# Define the LB worker
worker.router.type=lb
worker.router.balance_workers=worker1,worker2

Tomcat 6
server.xml
Cluster className=org.apache.catalina.ha.tcp.SimpleTcpCluster
name=wicketapp
managerClassName=org.apache.catalina.ha.session.DeltaManager
expireSessionsOnShutdown=false
 useDirtyFlag=true

   Channel className=org.apache.catalina.tribes.group.GroupChannel
Membership 
className=org.apache.catalina.tribes.membership.McastService
mcastAddr=228.0.0.4
mcastPort=45564
mcastFrequency=500
mcastDropTime=3000/

Receiver 
className=org.apache.catalina.tribes.transport.nio.NioReceiver
tcpListenAddress=auto
tcpListenPort=11901
tcpSelectorTimeout=100
tcpThreadCount=2/

Sender
   
className=org.apache.catalina.tribes.transport.ReplicationTransmitter
replicationMode=synchronous  
Transport
className=org.apache.catalina.tribes.transport.nio.PooledParallelSender/
/Sender

   /Channel

   Valve 
className=org.apache.catalina.ha.tcp.ReplicationValve
filter=.*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;.*\.css/

   Deployer className=org.apache.catalina.ha.deploy.FarmWarDeployer
tempDir=clusterzone/war-temp/
deployDir=clusterzone/war-deploy/
watchDir=clusterzone/war-listen/
watchEnabled=true/
/Cluster

-- 
View this message in context: 
http://www.nabble.com/wicket-cluster-on-tomcat-6-tf4942245.html#a14147973
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: wicket cluster on tomcat 6

2007-12-04 Thread michalb_cz

And the reason? Why back button won't work on cluster? 



Matej Knopp-2 wrote:
 
 Hi,
 
 at this point back button will not work across cluster (it's planned
 though). However, the failover for last accessed page should work
 anyway. If it doesn't, you have probably problem in your
 configuration.
 
 -Matej
 

-- 
View this message in context: 
http://www.nabble.com/wicket-cluster-on-tomcat-6-tf4942245.html#a14151756
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: wicket cluster on tomcat 6

2007-12-04 Thread Sebastiaan van Erk
It has to do with the page store. Note that the back button will work, 
but clicking on links on the page after you use the back button will 
cause page expired.


See:

http://www.slideshare.net/jcompagner/session-stores-page-maps-and-pages/

if you want the nitty gritty details.

But I still think you should first verify that this is actually what is 
happening.


Regards,
Sebastiaan

michalb_cz wrote:
And the reason? Why back button won't work on cluster? 




Matej Knopp-2 wrote:

Hi,

at this point back button will not work across cluster (it's planned
though). However, the failover for last accessed page should work
anyway. If it doesn't, you have probably problem in your
configuration.

-Matej





smime.p7s
Description: S/MIME Cryptographic Signature


Re: java.lang.OutOfMemoryError: Java heap space on Tomcat 6

2007-10-15 Thread Nino Saturnino Martinez Vazquez Wael
If youre only running a simple form, and dont have 1000's of users it 
should be fine, something else must be wrong.


Might be your parameters.

A guy on this 
thread(http://forum.java.sun.com/thread.jspa?threadID=326216) said:


Don't set the maximum memory to above 70% of the physical memory of the 
box or it will grind to a halt. The JVM needs all of the heap to be in 
physical memory all the time.



You can adjust heap by lowering your parameters, try with 128 in both 
instead.


-Xmssize set initial Java heap size
-Xmxsize set maximum Java heap size
JVM starts with -Xms amount of memory for the heap (storing objects 
etc.) and can grow to a maximum of -Xmx amount of memory.


JKrishna wrote:

I have generated a project using QWicket. I ran the build on Tomcat 6 and the
initial user registration and user authentication worked fine. I added a
simple form and insert those values into the database using Spring +
Hibernate. While submitting the form, the values are getting inserted into
the database. But during the navigation part, the application times out with
the following error

I modified the QWicket generated code to use Wicket 1.3 beta 3 build.

Root cause:

java.lang.OutOfMemoryError: Java heap space

Complete stack:

org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of
interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at
component [MarkupContainer [Component id = trip, page =
com.tripos.page.NewTripPage, path = 3:trip.NewTripPage$NewTripForm,
isVisible = true, isVersioned = true]] threw an exception
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:197)
at
org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget.processEvents(ListenerInterfaceRequestTarget.java:73)
at
org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:90)
at
org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1032)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1108)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1177)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:500)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:261)

The environment is Tomcat 6 running on OS X Tiger on Mac Mini with 512 MB
ram. I added Java_OPTS to have JAVA_OPTS=-Xms512m -Xmx512m. 


Is this problem because of insufficient memory?


  


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: java.lang.OutOfMemoryError: Java heap space on Tomcat 6

2007-10-15 Thread Eelco Hillenius
It is probably a good idea to profile your application. With 512 MB
you should typically be able to serve a couple of thousand concurrent
sessions without problems with Wicket 1.3.

Eelco


On 10/15/07, JKrishna [EMAIL PROTECTED] wrote:

 I have generated a project using QWicket. I ran the build on Tomcat 6 and the
 initial user registration and user authentication worked fine. I added a
 simple form and insert those values into the database using Spring +
 Hibernate. While submitting the form, the values are getting inserted into
 the database. But during the navigation part, the application times out with
 the following error

 I modified the QWicket generated code to use Wicket 1.3 beta 3 build.

 Root cause:

 java.lang.OutOfMemoryError: Java heap space

 Complete stack:

 org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of
 interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at
 component [MarkupContainer [Component id = trip, page =
 com.tripos.page.NewTripPage, path = 3:trip.NewTripPage$NewTripForm,
 isVisible = true, isVersioned = true]] threw an exception
 at
 org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:197)
 at
 org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarget.processEvents(ListenerInterfaceRequestTarget.java:73)
 at
 org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:90)
 at
 org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1032)
 at org.apache.wicket.RequestCycle.step(RequestCycle.java:1108)
 at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1177)
 at org.apache.wicket.RequestCycle.request(RequestCycle.java:500)
 at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:261)

 The environment is Tomcat 6 running on OS X Tiger on Mac Mini with 512 MB
 ram. I added Java_OPTS to have JAVA_OPTS=-Xms512m -Xmx512m.

 Is this problem because of insufficient memory?


 --
 View this message in context: 
 http://www.nabble.com/java.lang.OutOfMemoryError%3A-Java-heap-space-on-Tomcat-6-tf4627444.html#a13212670
 Sent from the Wicket - User mailing list archive at Nabble.com.


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]