You've got a real vintage piece of equipment there. SunOS 2.7, better known as Solaris 7, stems from the 20th century. (The current version is Solaris 10).
IIRC before Solaris 9 a lot of patches were recommended to install for using Java. Do you have all these? Also, were the libraries built on that old system, or maybe they come from a more recent system. Anyway, on Solaris there is the "truss" command to trace system calls. That often gives a good hint for where the problem lays. HTH, Alfred. On Wed, 2007-10-10 at 08:14 +0200, Derek Hohls wrote: > Joerg > > I agree its strange. Apart from setting the debug levels for the log > files, > what else can we look at? I had assumed it was something to do with > the > MySQL driver - does Cocoon have any special requirements/needs for > how this should/should not operate? > > Thanks > Derek > > PS Who is "Toby"? > > >>> Joerg Heinicke <[EMAIL PROTECTED]> 2007/10/10 02:18 AM >>> > On 09.10.2007 10:45 Uhr, Derek Hohls wrote: > > > We are trying to install Cocoon 2.1.8 under SunOS (version 5.7). > The > > "vanilla" version of Cocoon installs and runs fine. However, as > soon > > as we try and add a mySQL driver to the lib directory, and alter the > > cocoon.xconf file, the Cocoon startup reaches a certain point - and > then > > Tomcat stops (see below). The last line in the Cocoon log file is: > > > > WARN (2007-10-09) 16:35.07:712 [core.manager] (Unknown-URI) > > Unknown-Thread/ExcaliburComponentManager: disposing of handler for > > unreleased component. role > [org.apache.cocoon.forms.event.WidgetListenerBuilderSelector] > > > > Note - the exact same configuration of > Cocoon/driver/Java/configuration > > is deployed and running on a Linux server platform without any > problems. > > > > Given that the log file is not very forthcoming, how do we go about > > getting Cocoon to work on this platform? > > > > (PS We have Cocoon 2.1.4 running DB apps OK on the same server, so > > I assume this is because of some version differences in Cocoon...?) > > > > Thanks > > Derek > > > > PS Nothing in the archives I can find that addresses this problem > except > > http://marc.info/?l=xml-cocoon-users&m=113356786000252&w=2 > > which was not answered, although the same "end point" was reached > > i.e. a final entry in the Tomcat error log, stating: > > INFO [main] (QuartzScheduler.java:399) - Scheduler Cocoon_ > $_Tue_Oct_09_16:11:35_SAST_2007 started. > > All this sounds really weird. Seems to be only in a very special > environment setup where it fails. But since Toby is still around on > the > list and has not given up with Cocoon he might have figured that out. > Otherwise you probably need to debug very deeply into maybe not even > only Cocoon but also Tomcat to figure out what's happening on loading > the DB driver. > > Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
