Hi Guys, I'm currently reviewing the installers before the release.
I just found that our Mac OS X installer is broken on Snow Leopard systems. On these systems, the JVM is 64-bit while the wrapper binary we use is still a 32-bit one. Launching the server ends with an error: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% STATUS | wrapper | 2010/03/09 11:24:38 | --> Wrapper Started as Console STATUS | wrapper | 2010/03/09 11:24:39 | Launching a JVM... INFO | jvm 1 | 2010/03/09 11:24:40 | Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org INFO | jvm 1 | 2010/03/09 11:24:40 | Copyright 1999-2006 Tanuki Software, Inc. All Rights Reserved. INFO | jvm 1 | 2010/03/09 11:24:40 | INFO | jvm 1 | 2010/03/09 11:24:40 | INFO | jvm 1 | 2010/03/09 11:24:40 | WARNING - Unable to load the Wrapper's native library 'libwrapper.jnilib'. INFO | jvm 1 | 2010/03/09 11:24:40 | The file is located on the path at the following location but INFO | jvm 1 | 2010/03/09 11:24:40 | could not be loaded: INFO | jvm 1 | 2010/03/09 11:24:40 | /usr/local/apacheds-1.5.6-SNAPSHOT/bin/../lib/libwrapper.jnilib INFO | jvm 1 | 2010/03/09 11:24:40 | Please verify that the file is readable by the current user INFO | jvm 1 | 2010/03/09 11:24:40 | and that the file has not been corrupted in any way. INFO | jvm 1 | 2010/03/09 11:24:40 | One common cause of this problem is running a 32-bit version INFO | jvm 1 | 2010/03/09 11:24:40 | of the Wrapper with a 64-bit version of Java, or vica versa. INFO | jvm 1 | 2010/03/09 11:24:40 | This is a 64-bit JVM. INFO | jvm 1 | 2010/03/09 11:24:40 | Reported cause: INFO | jvm 1 | 2010/03/09 11:24:40 | /usr/local/apacheds-1.5.6-SNAPSHOT/lib/libwrapper.jnilib: no suitable image found. Did find: /usr/local/apacheds-1.5.6-SNAPSHOT/lib/libwrapper.jnilib: no matching architecture in universal wrapper INFO | jvm 1 | 2010/03/09 11:24:40 | System signals will not be handled correctly. INFO | jvm 1 | 2010/03/09 11:24:40 | INFO | jvm 1 | 2010/03/09 11:24:40 | Error in WrapperListener.start callback. java.lang.NullPointerException INFO | jvm 1 | 2010/03/09 11:24:40 | java.lang.NullPointerException INFO | jvm 1 | 2010/03/09 11:24:40 | at java.io.File.<init>(File.java:222) INFO | jvm 1 | 2010/03/09 11:24:40 | at org.apache.directory.daemon.Bootstrapper.setInstallationLayout(Bootstrapper.java:83) INFO | jvm 1 | 2010/03/09 11:24:40 | at org.apache.directory.daemon.TanukiBootstrapper.start(TanukiBootstrapper.java:52) INFO | jvm 1 | 2010/03/09 11:24:40 | at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) STATUS | wrapper | 2010/03/09 11:24:41 | <-- Wrapper Stopped %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% This will require that we provide two types of installer for Mac OS X: - one for 32-bit JVMs - one for 64-bit JVMs And more importantly this will force us to move to a newer version of the Tanuki Wrapper because a 64-bit version of the wrapper for Mac OS X does not exist for the 3.2.3 version we're using. Now, I remember there has been some problems with Tanuki's licensing when they changed it a couple of years ago I think... Does anyone know if their Community editor is compatible with the Apache License ? Thanks, Pierre-Arnaud On 8 mars 2010, at 09:32, Alex Karasulu wrote: > Yeap this search performance issue will make this release useless. > > On Sun, Mar 7, 2010 at 9:37 PM, Emmanuel Lecharny <elecha...@gmail.com> wrote: >> On 3/7/10 8:21 PM, Stefan Seelmann wrote: >>> >>> Emmanuel Lecharny schrieb: >>>> >>>> On 3/7/10 12:33 PM, Stefan Seelmann wrote: >>>>> >>>>> I built the installers and tested the zip archive. When starting the >>>>> server I get lot of warn logs [1]: >>>>> - "setting the schema manager for partition...". I think those are only >>>>> info messages so should be logged in info log level. >>>>> - "Cannot normalize the value". Are that serious issues? If not we >>>>> should change the logging. I'm sure some users will complain and ask on >>>>> the >>>>> mailing list what that output means. >>>> >>>> I will investigate thse two issues. At first sight, it seems tat the >>>> first one is clearly DEBUG or INFO logs wrongly using WARN level. >>>> >>> I will hold the vote once again. Beside the mentioned issues there is also >>> a serious search performance problem. >> >> I agree. I'm also fixing some logs issues we have. >> >> Sorry, Kiran, not your fault :/ >> >> -- >> Regards, >> Cordialement, >> Emmanuel Lécharny >> www.nextury.com >> >> >> > > > > -- > Alex Karasulu > My Blog :: http://www.jroller.com/akarasulu/ > Apache Directory Server :: http://directory.apache.org > Apache MINA :: http://mina.apache.org
