You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Ryan Hoegg <rh...@isisnetworks.net> on 2002/06/24 19:27:14 UTC
Installation error using JDK 1.4.0: libawt and libXp
Hello Peter, and everyone,
In the message linked below, you respond to another user with a very
similar problem to mine.
http://www.mail-archive.com/cocoon-users%40xml.apache.org/msg12493.html
I am using JDK 1.4.0, Tomcat 4.0.4, and Cocoon 2.0.2. I do not have X
installed, and my CATALINA_OPTS environment variable is
'-Djava.awt.headless=true'. After building from source, I get errors
trying to load the default Cocoon2 site. The stack trace shows an
attempt to load an SVGSerializer using batik. The error I get is:
org.apache.cocoon.ProcessingException: Error compiling sitemap:
java.lang.UnsatisfiedLinkError:
/usr/local/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open
shared object file: No such file or directory
To be sure, I created a servlet that outputs
System.getProperty("java.awt.headless"); it returns true.
Can anyone provide any insight to this situation?
Thanks,
Ryan Hoegg
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Installation error using JDK 1.4.0: libawt and libXp
Posted by Paul Gilligan <pd...@oyap.net>.
Watch out for the JDBC problems under jdk1.4 as well :)
Ryan Hoegg wrote:
> Hello Peter, and everyone,
>
> In the message linked below, you respond to another user with a very
> similar problem to mine.
>
> http://www.mail-archive.com/cocoon-users%40xml.apache.org/msg12493.html
>
> I am using JDK 1.4.0, Tomcat 4.0.4, and Cocoon 2.0.2. I do not have X
> installed, and my CATALINA_OPTS environment variable is
> '-Djava.awt.headless=true'. After building from source, I get errors
> trying to load the default Cocoon2 site. The stack trace shows an
> attempt to load an SVGSerializer using batik. The error I get is:
>
> org.apache.cocoon.ProcessingException: Error compiling sitemap:
> java.lang.UnsatisfiedLinkError:
> /usr/local/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open
> shared object file: No such file or directory
>
> To be sure, I created a servlet that outputs
> System.getProperty("java.awt.headless"); it returns true.
>
> Can anyone provide any insight to this situation?
>
> Thanks,
> Ryan Hoegg
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
[Summary] Installation error using JDK 1.4.0: libawt and libXp
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Hello thought I would repost this with the [summary] thing in light of
some of the recent threads
Ryan Hoegg wrote:
> MAINTAINERS: please skip to the end (before quoted) for a suggestion
> for the FAQ or preferably the installation guide.
>
> Hello everyone, I've got it licked.
>
> First, I thank Peter Royal who realized that to run Java AWT in
> headless mode, one must still have the X-Windows libraries installed.
> All headless means is that one need not have X running.
>
> My best guess is that the error at
> http://www.hoegg.net/error/cocoon-problem2.html was caused by the
> batik-all-1.5b3.jar that came with Cocoon. I downloaded batik-1.1.1,
> and combined all the little jars into one big batik-all-1.1.1.jar,
> which I hereby post on my site for anyone who needs it:
>
> http://www.hoegg.net/batik-all-1.1.1.jar
>
> I installed it in $CATALINA_HOME/webapps/cocoon/WEB-INF/lib and
> shutdown and restarted the server. A note for anyone putting together
> their own jar: find the AbstractDOMImplentation.class file, its
> filename is messed up with some random control chars on the end. Fix
> it and rejar. The one I posted has this fixed.
>
> I am not subscribed to cocoon-dev or batik-dev so anyone who is please
> relay the appropriate message :)
>
> MAINTAINERS: it may be worth a note in the installation guide that to
> run Batik or Cocoon in headless mode on *nix one must still have the
> X-Windows libraries installed. I'd call this a dependency of Batik,
> but then Batik seems to be a dependency of the default installation of
> Cocoon.
>
> Thanks for your help (Peter) and a great piece of software (Dev Team),
> Ryan Hoegg
> ISIS Networks
>
> Ryan Hoegg wrote:
>
>> Thanks for the idea, seems obvious once someone points it out :)
>>
>> Well, although I wanted to avoid installing the X libraries as this
>> server has no other need for them, I went ahead and did it. Lo and
>> behold, the error went away, and another was quick to replace it:
>>
>> http://www.hoegg.net/error/cocoon-problem2.html
>>
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <co...@xml.apache.org>
> For additional commands, e-mail: <co...@xml.apache.org>
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
SOLVED: Installation error using JDK 1.4.0: libawt and libXp
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
MAINTAINERS: please skip to the end (before quoted) for a suggestion for
the FAQ or preferably the installation guide.
Hello everyone, I've got it licked.
First, I thank Peter Royal who realized that to run Java AWT in headless
mode, one must still have the X-Windows libraries installed. All
headless means is that one need not have X running.
My best guess is that the error at
http://www.hoegg.net/error/cocoon-problem2.html was caused by the
batik-all-1.5b3.jar that came with Cocoon. I downloaded batik-1.1.1,
and combined all the little jars into one big batik-all-1.1.1.jar, which
I hereby post on my site for anyone who needs it:
http://www.hoegg.net/batik-all-1.1.1.jar
I installed it in $CATALINA_HOME/webapps/cocoon/WEB-INF/lib and shutdown
and restarted the server. A note for anyone putting together their own
jar: find the AbstractDOMImplentation.class file, its filename is messed
up with some random control chars on the end. Fix it and rejar. The
one I posted has this fixed.
I am not subscribed to cocoon-dev or batik-dev so anyone who is please
relay the appropriate message :)
MAINTAINERS: it may be worth a note in the installation guide that to
run Batik or Cocoon in headless mode on *nix one must still have the
X-Windows libraries installed. I'd call this a dependency of Batik, but
then Batik seems to be a dependency of the default installation of Cocoon.
Thanks for your help (Peter) and a great piece of software (Dev Team),
Ryan Hoegg
ISIS Networks
Ryan Hoegg wrote:
> Thanks for the idea, seems obvious once someone points it out :)
>
> Well, although I wanted to avoid installing the X libraries as this
> server has no other need for them, I went ahead and did it. Lo and
> behold, the error went away, and another was quick to replace it:
>
> http://www.hoegg.net/error/cocoon-problem2.html
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Installation error using JDK 1.4.0: libawt and libXp
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
Thanks for the idea, seems obvious once someone points it out :)
Well, although I wanted to avoid installing the X libraries as this
server has no other need for them, I went ahead and did it. Lo and
behold, the error went away, and another was quick to replace it:
http://www.hoegg.net/error/cocoon-problem2.html
Scoured the archives and found several posts with similar circumstances.
Unfortunately, either the solutions were nothing new and did not solve
the problem; or, the problem ended up being unsolved or in some way
different from mine. Here some are in case they may shed some light on
this.
http://www.mail-archive.com/cocoon-users%40xml.apache.org/msg11495.html
http://www.mail-archive.com/cocoon-users%40xml.apache.org/msg12960.html
http://www.mail-archive.com/cocoon-users%40xml.apache.org/msg13501.html
Sorry to come running back to you for the third time. I hope that the
answers to my problems will be more generally helpful in the archives or
the FAQ. If/when I sort it out I will try to write something coherent
up for the FAQ regarding my use of JDK1.4 without X
Thanks,
Ryan Hoegg.
Peter Royal wrote:
>On Monday 24 June 2002 04:24 pm, Ryan Hoegg wrote:
>
>>I appreciate the quick and thoughtful response, Pete. I changed
>>cocoon.xconf to use an interpreted sitemap, and succeeded only in making
>>a change in the error received. It still is asking for libXp.so, but is
>>now buried in other errors.
>>
>>I captured the error from my development server and posted it on my web
>>server here:
>>
>>http://www.hoegg.net/error/cocoon-problem.html
>>
>>It seems to me that there is something fishy about the headless awt
>>support in 1.4.0 when using Batik. Is anyone successfully running
>>Cocoon2 this way?
>>
>
>Makes me wonder about how "headless" you can be. Whether its merely no
>running X server or no X libraries on the machine at all. It might be the
>former when you're expecting the latter.
>
>>As a side note, just wanted to say I am a new user of Cocoon and am
>>looking forward to this approach to dynamic web development. Thanks to
>>all the developers for a great framework.
>>
>
>Welcome! :)
>-pete
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Installation error using JDK 1.4.0: libawt and libXp
Posted by Peter Royal <pr...@apache.org>.
On Monday 24 June 2002 04:24 pm, Ryan Hoegg wrote:
> I appreciate the quick and thoughtful response, Pete. I changed
> cocoon.xconf to use an interpreted sitemap, and succeeded only in making
> a change in the error received. It still is asking for libXp.so, but is
> now buried in other errors.
>
> I captured the error from my development server and posted it on my web
> server here:
>
> http://www.hoegg.net/error/cocoon-problem.html
>
> It seems to me that there is something fishy about the headless awt
> support in 1.4.0 when using Batik. Is anyone successfully running
> Cocoon2 this way?
Makes me wonder about how "headless" you can be. Whether its merely no
running X server or no X libraries on the machine at all. It might be the
former when you're expecting the latter.
> As a side note, just wanted to say I am a new user of Cocoon and am
> looking forward to this approach to dynamic web development. Thanks to
> all the developers for a great framework.
Welcome! :)
-pete
--
peter royal -> proyal@apache.org
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Installation error using JDK 1.4.0: libawt and libXp
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
I appreciate the quick and thoughtful response, Pete. I changed
cocoon.xconf to use an interpreted sitemap, and succeeded only in making
a change in the error received. It still is asking for libXp.so, but is
now buried in other errors.
I captured the error from my development server and posted it on my web
server here:
http://www.hoegg.net/error/cocoon-problem.html
It seems to me that there is something fishy about the headless awt
support in 1.4.0 when using Batik. Is anyone successfully running
Cocoon2 this way?
As a side note, just wanted to say I am a new user of Cocoon and am
looking forward to this approach to dynamic web development. Thanks to
all the developers for a great framework.
Thanks again,
Ryan Hoegg
Peter Royal wrote:
>On Monday 24 June 2002 01:27 pm, Ryan Hoegg wrote:
>
>>I am using JDK 1.4.0, Tomcat 4.0.4, and Cocoon 2.0.2. I do not have X
>>installed, and my CATALINA_OPTS environment variable is
>>'-Djava.awt.headless=true'. After building from source, I get errors
>>trying to load the default Cocoon2 site. The stack trace shows an
>>attempt to load an SVGSerializer using batik. The error I get is:
>>
>>org.apache.cocoon.ProcessingException: Error compiling sitemap:
>>java.lang.UnsatisfiedLinkError:
>>/usr/local/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open
>>shared object file: No such file or directory
>>
>>To be sure, I created a servlet that outputs
>>System.getProperty("java.awt.headless"); it returns true.
>>
>>Can anyone provide any insight to this situation?
>>
>
>Its failing in compiling the sitemap. Perhaps the headless property is for
>runtime only and doesn't play well at compile-time?
>
>I have X installed on my machine so I can't verify that.
>
>My best suggestion to you is to attempt to use the interpreted sitemap rather
>than the compiled one and see how that goes. In WEB-INF/cocoon.xconf at the
>bottom of the file there are comments indicating how to switch.
>-pete
>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>
Re: Installation error using JDK 1.4.0: libawt and libXp
Posted by Peter Royal <pr...@apache.org>.
On Monday 24 June 2002 01:27 pm, Ryan Hoegg wrote:
> I am using JDK 1.4.0, Tomcat 4.0.4, and Cocoon 2.0.2. I do not have X
> installed, and my CATALINA_OPTS environment variable is
> '-Djava.awt.headless=true'. After building from source, I get errors
> trying to load the default Cocoon2 site. The stack trace shows an
> attempt to load an SVGSerializer using batik. The error I get is:
>
> org.apache.cocoon.ProcessingException: Error compiling sitemap:
> java.lang.UnsatisfiedLinkError:
> /usr/local/j2sdk1.4.0/jre/lib/i386/libawt.so: libXp.so.6: cannot open
> shared object file: No such file or directory
>
> To be sure, I created a servlet that outputs
> System.getProperty("java.awt.headless"); it returns true.
>
> Can anyone provide any insight to this situation?
Its failing in compiling the sitemap. Perhaps the headless property is for
runtime only and doesn't play well at compile-time?
I have X installed on my machine so I can't verify that.
My best suggestion to you is to attempt to use the interpreted sitemap rather
than the compiled one and see how that goes. In WEB-INF/cocoon.xconf at the
bottom of the file there are comments indicating how to switch.
-pete
--
peter royal -> proyal@apache.org
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <co...@xml.apache.org>
For additional commands, e-mail: <co...@xml.apache.org>