RE: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-24 Thread Karl Oie 

Just a little warning of a problem I experienced, it was wrong of me to say
that this should go into the tomcat.sh because if you kill the framebuffer
while tomcat is running, horrible things happens. this script should go into
a separate scriptfile and be started/stopped before/after tomcat.

mvh karl


karl wrote:

> if [ "$1" = "stop" ] ; then
> # kill off any framebuffer running, kill kill kill :-)
> kill -TERM `/sbin/pidof Xvfb`
> elif [ "$1"="start" -o "$1"="run" ] ; then
> # start up a virtual framebuffer for cocoon2's rendering
> Xvfb :1 -screen 0 320x240x24 &
> fi
>
> this setsup a virtual framebuffer for x to run in, now all the
> batik and svg
> stuff works without running a real x server.


-
Please check that your question has not already been answered in the
FAQ before posting. 

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

Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-24 Thread Jan Warnstam 

Both the db problems and the SVG problems disappeared as the X11 problem
was solved via Xfvb, or so it seems anyway. Do you still have problems
with the two first issues even though you have a working X connection?

Regards,
 Jan Warnstam
 Developer, Euronetics

Arnaud Vandyck wrote:

> I  cannot  do   that  to  (but  on  MacOSX   hsqldb  works  fine  with
> cocoon2!). So I did create a postgresql db to use with cocoon2 and put
> the jar file  for postgres in WEB-INF/lib and modify  the entry in the
> cocoon.xconf. You can find the table here:
>
> http://vbstefi30.fapse.ulg.ac.be/help/cocoon_employee.sql
>
> [of course it's free! GPL, ASL, copyleft and what ever you want;))]
>
> > Also, there is a complaint that the sitemap handler's sitemap is not
> > available. This is also the error being printed on the error message
> > page  being   displayed  in   the  browser  as   I  try   to  access
> > :8081/cocoon/. Check the third and last log snapshot below:
>
> Well, I think it's because of the svg problem.


-
Please check that your question has not already been answered in the
FAQ before posting. 

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

Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-24 Thread Jan Warnstam 

I have now tried to uncomment the SVG Serializer parts in the sitemap.xmap
(restoring the file to the original status without any changes compared to the
CVS version) and Cocoon 2 still works!

It seems that the only necessary fix was to add the Xvfb call in the init.d
script. I did not even have to move/copy any .jar files as it is written in the
/cocoon2/install.html instructions; it works fine anyway now.

Yours,
 Jan Warnstam
 Developer, Euronetics

Jan Warnstam wrote:

> I will experiment tomorrow with uncommenting the commented parts in the
> sitemap.xmap file and see if Cocoon 2 still starts after doing that. :)


-
Please check that your question has not already been answered in the
FAQ before posting. 

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

Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-23 Thread Jan Warnstam 

Karl Oie wrote:

> goto http://www.xfree86.org and get the xvfb package, i had the same
> problem, so i included this in the tomcat.sh after i installed Xvfb:
>
> if [ "$1" = "stop" ] ; then
> # kill off any framebuffer running, kill kill kill :-)
> kill -TERM `/sbin/pidof Xvfb`
> elif [ "$1"="start" -o "$1"="run" ] ; then
> # start up a virtual framebuffer for cocoon2's rendering
> Xvfb :1 -screen 0 320x240x24 &
> fi
>
> this setsup a virtual framebuffer for x to run in, now all the batik and svg
> stuff works without running a real x server.

Thank you! That worked, in combination with commenting the SVG Serialization
parts of the sitemap.xmap file.

I will experiment tomorrow with uncommenting the commented parts in the
sitemap.xmap file and see if Cocoon 2 still starts after doing that. :)

Many thanks,
 Jan Warnstam
 Developer, Euronetics


-
Please check that your question has not already been answered in the
FAQ before posting. 

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

RE: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-23 Thread Karl Oie 

goto http://www.xfree86.org and get the xvfb package, i had the same
problem, so i included this in the tomcat.sh after i installed Xvfb:

if [ "$1" = "stop" ] ; then
# kill off any framebuffer running, kill kill kill :-)
kill -TERM `/sbin/pidof Xvfb`
elif [ "$1"="start" -o "$1"="run" ] ; then
# start up a virtual framebuffer for cocoon2's rendering
Xvfb :1 -screen 0 320x240x24 &
fi

this setsup a virtual framebuffer for x to run in, now all the batik and svg
stuff works without running a real x server.


mvh karl oie




-Original Message-
From: Arnaud Vandyck [mailto:[EMAIL PROTECTED]]
Sent: 23. august 2001 18:24
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian


From: Jan Warnstam <[EMAIL PROTECTED]>
Subject: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian
Date: Thu, 23 Aug 2001 17:42:53 +0200
Message-ID: <[EMAIL PROTECTED]>

> First, I suspect that, since I  am running both Cocoon and Tomcat on
> a remote  server (which I  access via SSH)  the Tomcat engine  has a
> problem with opening an X connection when AWT is invoked by Cocoon 2
> (is it? it's a guess). I  tried to patch this by setting the DISPLAY
> environment variable to localhost:47 in the /etc/init.d/tomcat shell
> script  but  that  did not  make  it  work,  though it  changed  the
> behaviour since Tomcat stopped crashing  and we got an error message
> in  the browser  instead.  Check  the log  snapshot  from cocoon.log
> below:

I'm  waiting  for  a better  solution  but  I  commented all  the  svg
references in  the sitemap... but there  was a discussion  a week ago,
maybe you'll find an alternative in the archive.

> Now, also  it seems  that our Cocoon  2 is having  problems reaching
> JdbcConnection, look below:

I  cannot  do   that  to  (but  on  MacOSX   hsqldb  works  fine  with
cocoon2!). So I did create a postgresql db to use with cocoon2 and put
the jar file  for postgres in WEB-INF/lib and modify  the entry in the
cocoon.xconf. You can find the table here:

http://vbstefi30.fapse.ulg.ac.be/help/cocoon_employee.sql

[of course it's free! GPL, ASL, copyleft and what ever you want;))]

> Also, there is a complaint that the sitemap handler's sitemap is not
> available. This is also the error being printed on the error message
> page  being   displayed  in   the  browser  as   I  try   to  access
> :8081/cocoon/. Check the third and last log snapshot below:

Well, I think it's because of the svg problem.

Hope it helps,

--Arnaud


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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


-
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faqs.html>

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

Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-23 Thread Arnaud Vandyck 

From: Jan Warnstam <[EMAIL PROTECTED]>
Subject: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian
Date: Thu, 23 Aug 2001 17:42:53 +0200
Message-ID: <[EMAIL PROTECTED]>

> First, I suspect that, since I  am running both Cocoon and Tomcat on
> a remote  server (which I  access via SSH)  the Tomcat engine  has a
> problem with opening an X connection when AWT is invoked by Cocoon 2
> (is it? it's a guess). I  tried to patch this by setting the DISPLAY
> environment variable to localhost:47 in the /etc/init.d/tomcat shell
> script  but  that  did not  make  it  work,  though it  changed  the
> behaviour since Tomcat stopped crashing  and we got an error message
> in  the browser  instead.  Check  the log  snapshot  from cocoon.log
> below:

I'm  waiting  for  a better  solution  but  I  commented all  the  svg
references in  the sitemap... but there  was a discussion  a week ago,
maybe you'll find an alternative in the archive.

> Now, also  it seems  that our Cocoon  2 is having  problems reaching
> JdbcConnection, look below:

I  cannot  do   that  to  (but  on  MacOSX   hsqldb  works  fine  with
cocoon2!). So I did create a postgresql db to use with cocoon2 and put
the jar file  for postgres in WEB-INF/lib and modify  the entry in the
cocoon.xconf. You can find the table here:

http://vbstefi30.fapse.ulg.ac.be/help/cocoon_employee.sql

[of course it's free! GPL, ASL, copyleft and what ever you want;))]

> Also, there is a complaint that the sitemap handler's sitemap is not
> available. This is also the error being printed on the error message
> page  being   displayed  in   the  browser  as   I  try   to  access
> :8081/cocoon/. Check the third and last log snapshot below:

Well, I think it's because of the svg problem. 

Hope it helps,

--Arnaud


-
Please check that your question has not already been answered in the
FAQ before posting. 

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

Re: Problems with Cocoon 2 with Tomcat 3.2.3-1 on Debian

2001-08-23 Thread java guru 

Hi.,

1. X problem is that some of the c2 components
requiring x server...

2. Second problem is that c2 not setup to talk to
hsqldb that ships with c2 by default..

Both of these are discusses numerous times..please
look into the mail archive..


 --- Jan Warnstam <[EMAIL PROTECTED]> wrote:
> I are having trouble installing Cocoon 2 (via the
> CVS as described on
> http://xml.apache.org/cocoon2/install.html). I am
> using it together with
> a Tomcat 3.2.3-1 Debian package and some problems
> have occured.
> 
> First, I suspect that, since I am running both
> Cocoon and Tomcat on a
> remote server (which I access via SSH) the Tomcat
> engine has a problem
> with opening an X connection when AWT is invoked by
> Cocoon 2 (is it? it's
> a guess). I tried to patch this by setting the
> DISPLAY environment
> variable to localhost:47 in the /etc/init.d/tomcat
> shell script but that
> did not make it work, though it changed the
> behaviour since Tomcat
> stopped crashing and we got an error message in the
> browser instead.
> Check the log snapshot from cocoon.log below:
> 
> 8<
> ERROR   (2001-08-23) 15:32.25:365   [cocoon  ]
> (/cocoon/)
> Thread-22/Handler: Error compiling sitemap
> java.lang.InternalError: Can't connect to X11 window
> server using
> 'localhost:47' as the value of the DISPLAY variable.
>  at
> sun.awt.X11GraphicsEnvironment.initDisplay(Native
> Method)
>  at
>
sun.awt.X11GraphicsEnvironment.(X11GraphicsEnvironment.java:59)
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:120)
>  at
>
java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:58)
> 
>  at
> sun.awt.motif.MToolkit.(MToolkit.java:57)
>  at java.lang.Class.forName0(Native Method)
>  at java.lang.Class.forName(Class.java:120)
>  at java.awt.Toolkit$2.run(Toolkit.java:512)
>  at
> java.security.AccessController.doPrivileged(Native
> Method)
>  at
> java.awt.Toolkit.getDefaultToolkit(Toolkit.java:503)
>  at
>
java.awt.SystemColor.updateSystemColors(SystemColor.java:342)
>  at
> java.awt.SystemColor.(SystemColor.java:335)
> 8<
> 
> Now, also it seems that our Cocoon 2 is having
> problems reaching
> JdbcConnection, look below:
> 
> 8<
> DEBUG   (2001-08-23) 15:32.06:297   [cocoon  ]
> (Unknown-URI)
> Unknown-thread/AbstractPool:
>
org.apache.avalon.excalibur.datasource.JdbcConnection:
> could not be
> instantiated.
> java.sql.SQLException: File input/output error:
> ${install.war}/cocoon/WEB-INF/db/cocoondb.properties
>  at org.hsqldb.Trace.getError(Trace.java:180)
>  at org.hsqldb.Trace.getError(Trace.java:144)
>  at org.hsqldb.Trace.error(Trace.java:205)
>  at org.hsqldb.Log.saveProperties(Log.java:621)
>  at org.hsqldb.Log.create(Log.java:512)
>  at org.hsqldb.Log.open(Log.java:159)
>  at org.hsqldb.Database.(Database.java:96)
>  at
>
org.hsqldb.jdbcConnection.openStandalone(jdbcConnection.java:926)
>  at
>
org.hsqldb.jdbcConnection.(jdbcConnection.java:682)
>  at
> org.hsqldb.jdbcDriver.connect(jdbcDriver.java:116)
>  at
>
java.sql.DriverManager.getConnection(DriverManager.java:517)
>  at
>
java.sql.DriverManager.getConnection(DriverManager.java:177)
>  at
>
org.apache.avalon.excalibur.datasource.JdbcConnectionFactory.newInstance(JdbcConnectionFactory.java:77)
> 
>  at
>
org.apache.avalon.excalibur.pool.AbstractPool.newPoolable(AbstractPool.java:72)
> 
>  at
>
org.apache.avalon.excalibur.pool.HardResourceLimitingPool.newPoolable(HardResourceLimitingPool.java:95)
> 
>  at
>
org.apache.avalon.excalibur.datasource.JdbcConnectionPool.newPoolable(JdbcConnectionPool.java:51)
> 
>  at
>
org.apache.avalon.excalibur.pool.AbstractPool.internalGrow(AbstractPool.java:113)
> 
> ---8<---
> 
> Also, there is a complaint that the sitemap
> handler's sitemap is not
> available. This is also the error being printed on
> the error message page
> being displayed in the browser as I try to access
> :8081/cocoon/. Check
> the third and last log snapshot below:
> 
> DEBUG   (2001-08-23) 15:32.25:370   [cocoon  ]
> (/cocoon/)
> Thread-22/AbstractEnvironment: Changing Cocoon
> context(sitemap.xmap) to
> prefix()
> DEBUG   (2001-08-23) 15:32.25:370   [cocoon  ]
> (/cocoon/)
> Thread-22/AbstractEnvironment:  from
> context(file:/var/lib/tomcat/webapps/cocoon/) and
> prefix()
> DEBUG   (2001-08-23) 15:32.25:370   [cocoon  ]
> (/cocoon/)
> Thread-22/AbstractEnvironment:  at URI
> DEBUG   (2001-08-23) 15:32.25:371   [cocoon  ]
> (/cocoon/)
> Thread-22/AbstractEnvironment: New context is
> file:/var/lib/tomcat/webapps/cocoon/
> ERROR   (2001-08-23) 15:32.25:372   [cocoon  ]
> (/cocoon/)
> Thread-22/CocoonServlet: Problem with servlet
> org.apache.cocoon.ProcessingException: The sitemap
> handler's sitemap is
> not available. Please check
>
/var/lib/tomcat/webapps/cocoon/WEB-INF/logs/cocoon.log
> for the exact
> error.
>  at
>
org.apache.cocoon.sitemap.Manager.setupProcessing(Manager.java:184)
>  at
>
org.apache.cocoon.sitemap.Manager.invoke(Manager.java:102)
>  at
> org.apac