Hi,
 
We've had our apacheds server continue to hang numerous times.  Every few we
eks in fact.  There are no messages in the error log.  In fact, the only mes
sage that I've come across is:
 
"The PDU has been fully decoded but there are still bytes in the buffer."
 
On the client side we get an error stating that we've submitted an invalid s
earch parameter, however we've confirmed that the parameter is correct.
 
We are currently on 1.0.0.  It looks like it may be related to http://issues.apach
e.org/ji.../DIRSERVER-1019
 
Any idea with 1.0.3 will be released?
 
Thanks - Lee
 ________________________________________
_________________________
You keep typing, we keep giving. Download Messenger and join the i’m Initiat
ive now.
http://im.live.com/messenger/im/home/?source=TAGLM

[ Post a follow-up to this message ]

Hi,

Lee Gerakos wrote:
> Hi,
>
> We've had our apacheds server continue to hang numerous times.  Every
> few weeks in fact.  There are no messages in the error log.  In fact,
> the only message that I've come across is:
>
> "The PDU has been fully decoded but there are still bytes in the buffer."
>
> On the client side we get an error stating that we've submitted an
> invalid search parameter, however we've confirmed that the parameter
> is correct.
>
> We are currently on 1.0.0.  It looks like it may be related to
> _http://issues.apache.org/jira/browse/DIRSERVER-1019_
May be. This is definitively a serious issue. The other message ( PDU
fully decoded) is something different, which I'm currently investigating.
>
> Any idea with 1.0.3 will be released?
No idea, but it might be sooner than expected, considering the issue you
have pointed out ...
>
> Thanks - Lee
You are welcome !
>
> ------------------------------------------------------------------------
> You keep typing, we keep giving. Download Messenger and join the i’m
> Initiative now. Join in!
> <http://im.live.com/messenger/im/hom...=CRM_WL_joinnow>


--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org

[ Post a follow-up to this message ]