Tim,
I have made numerous postings to this group suggesting there is something
wrong with the Jdk 1.3.0 and 1.3.0_01 run times. I could not get cocoon
running at all on my Solaris 2.8 system until I changed to Jdk 1.3.1 (and I
even used RC1). Can someone please put this in the cocoon faq or somewhere
on the cocoon2 web site?
Apologies for not responding earlier, but there is a lot of mail in this
list.
Cheers,
Fred
-----Original Message-----
From: Bentley, Tim [mailto:[EMAIL PROTECTED]]
Sent: 31 July 2001 07:30
To: [EMAIL PROTECTED]
Subject: RE: [C2] with Tomcat 3.2.1 under Solaris 2.6
Ok - got it working!
Over the weekend, our sysadmin installed all the correct patches to bring
Solaris up to the spec required for Java 1.3.0. Predictably, this made no
difference. However, today we installed Java 1.3.1, and that made the
difference - straight away Cocoon started working, without even having to
blow away the work directory. This strengthens my belief that it was
something to do with the class loader - presumably there was something dodgy
about the way the low level file searching, path resolution or similar was
working on Solaris which has changed in 1.3.1.
Regards,
Tim
> -----Original Message-----
> From: Bentley, Tim
> Sent: Tuesday, 31 July 2001 10:07
> To: [EMAIL PROTECTED]
> Subject: RE: [C2] with Tomcat 3.2.1 under Solaris 2.6
>
>
> Cass -
>
> > good point. unfortunately i can't say for sure, but i think you'll
> > debug it by trying to compile the files command line (at
> least that's
> > how i did).
> >
>
> Alas, that was one of the first things I tried - the compilation works
> perfectly, with no errors at all.
>
> I am 99% sure this is a classloader issue. I have added more
> logging lines
> and recompiled Cocoon, and the path and class name being passed to the
> loader look correct. I am currently working through the layers of
> classloader code, trying to see where things could be going
> wrong. Cocoon
> is using a URLClassLoader, so I guess it is possible that the
> path is being
> incorrectly resolved. Another faint possibility is that the
> repository path
> is not being correctly added to the class loader search list.
> However,
> since all of this works in other environments, and in other
> peoples' Solaris
> environments, my main hope is that I'll find something to point to the
> 'real' issue, which is most likely to be some sort of
> configuration problem.
>
>
> Regards,
>
>
> Tim
>
> ---------------------------------------------------------------------
> 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]>
---------------------------------------------------------------------
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]>
