Thanks Kiran and Emmanuel for the quick responses. Kiran you wrote: "One workaround is to make sure the server has no active write connections at the time of shutdown."
The reboot was at 2:21. We don't have manual writing to apacheDS at that time. We have a user integration running at 03:00 every night, but that shouldn't have effected this since its only later. So no one should have been actively writing to apacheDS at that time. What else could have caused the issue? Emmanuel you wrote: "AFAIR, the Windows installer only works with a 32 bit wrapper, which expect to use a 32 bits JVM" There is a 64bit apacheDS instalaltion package that we used. It's working fine otherwise but apacheds gives that warning each time it starts. Isn't apacheDS meant yo be used with 64bit Java? Thanks for the help. -- John On Tue, Apr 7, 2015 at 4:08 PM, Emmanuel Lécharny <[email protected]> wrote: > Le 07/04/15 14:44, Kiran Ayyagari a écrit : > > On Tue, Apr 7, 2015 at 8:17 PM, Emmanuel Lécharny <[email protected]> > > wrote: > > > >> Le 07/04/15 13:31, Kiran Ayyagari a écrit : > >>> On Tue, Apr 7, 2015 at 6:36 PM, John Peter <[email protected]> wrote: > >>> > >>>> Hi, > >>>> > >>>> I'm using apacheds 2.0.0 M_19. > >>>> > >>>> The server had a scheduled montly reboot at 2015/04/02 02:21:51. > >>>> > >>>> After the reboot we noticed that the apacheDS port is open, but logins > >> are > >>>> failing. > >>>> > >>>> What we did is a manual restart of the apacheDS service and it started > >>>> working again. > >>>> > >>>> Below is the apacheDS wrapper.log. > >>>> > >>>> After the reboot which didn't work we can see a > >>>> java.lang.ArrayIndexOutOfBoundsException: > >>>> -11870. What might be causing this? > >>>> > >>> during shutdown the JDBM partition was not cleanly closed > >>> by the server, this can happen due to various reasons, and there is > >>> no fix for this issue. > >>> > >>> One workaround is to make sure the server has no active write > connections > >>> at the > >>> time of shutdown. > >>> > >>> We are working on Mavibot, a new backend, to prevent these kind of > issues > >>> from happening and it will replace JDBM. > >> I think this is not the problem here. Looking at the logs, we see : > >> > >> INFO | jvm 1 | 2015/03/05 03:08:33 | This is a 64-bit > JVM. > >> INFO | jvm 1 | 2015/03/05 03:08:33 | Reported cause: > >> INFO | jvm 1 | 2015/03/05 03:08:33 | > >> D:\ApacheDS\lib\wrapper.dll: Can't load IA 32-bit .dll on a AMD 64-bit > >> platform > >> > >> > >> AFAIR, the Windows installer only works with a 32 bit wrapper, which > >> expect to use a 32 bits JVM. The installed JVM is a 64 bits one, which > >> explain the failure. Restarting by hand works because this time, the > user > >> launch the 64 bits JVM with the 64 bits library. > >> This is an issue we can't fix with Tanuki wrapper, as it only supports > 32 > >> bits JVM in its free installer. We have to consider switching to another > >> installer (YAJSW ?) > >> > >> hmm, the below error is a clear JDBM issue > > callback. java.lang.Error: ERR_554 double get for block 41 630 > > INFO | jvm 1 | 2015/04/02 09:25:56 | java.lang.Error: ERR_554 double > > get for block 41 630 > > Ah, you are right. I think then we have 2 problems :/ > >
