naviserver-devel — Developer discussion

Re: [naviserver-devel] ns_cache_forever

[Stephen D. <sd...@gm...>]

Works for me.


On 7/11/06, Vlad Seryakov <vl...@cr...> wrote:
> I guess it is stable now
>
> Zoran Vasiljevic wrote:
> > Hi,
> >
> > No, no it is not as you think!
> > I just wanted to ask: do we have now a stable
> > *existing* interface of this beast?
> > I would like to prepare to new a release and will
> > not like to adjust our Tcl code on a daily basis.
> > We only use ns_cache_create and ns_cache_flush and
> > ns_cache_eval.
> >
> > I do not mind adding new commands. I do mind changing
> > the existing w/o a very good reason.
> >
> > Cheers
> > Zoran
> >
> >
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > naviserver-devel mailing list
> > nav...@li...
> > https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >
>
> --
> Vlad Seryakov
> 571 262-8608 office
> vl...@cr...
> http://www.crystalballinc.com/vlad/
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>

Re: [naviserver-devel] ns_cache_forever

[Vlad S. <vl...@cr...>]

I guess it is stable now

Zoran Vasiljevic wrote:
> Hi,
> 
> No, no it is not as you think!
> I just wanted to ask: do we have now a stable
> *existing* interface of this beast?
> I would like to prepare to new a release and will
> not like to adjust our Tcl code on a daily basis.
> We only use ns_cache_create and ns_cache_flush and
> ns_cache_eval.
> 
> I do not mind adding new commands. I do mind changing
> the existing w/o a very good reason.
> 
> Cheers
> Zoran
> 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

[naviserver-devel] ns_cache_forever

[Zoran V. <zv...@ar...>]

Hi,

No, no it is not as you think!
I just wanted to ask: do we have now a stable
*existing* interface of this beast?
I would like to prepare to new a release and will
not like to adjust our Tcl code on a daily basis.
We only use ns_cache_create and ns_cache_flush and
ns_cache_eval.

I do not mind adding new commands. I do mind changing
the existing w/o a very good reason.

Cheers
Zoran

Re: [naviserver-devel] ns_cache is still broken

[Stephen D. <sd...@gm...>]

On 7/10/06, Zoran Vasiljevic <zv...@ar...> wrote:
>
> Am 10.07.2006 um 20:34 schrieb Stephen Deasey:
>
> > Limits will save the day, and cure world
> > hunger...
>
> ... and win the next world football cup in South Africa
> in four years  :-)
>

...unless it comes to penalties.

[naviserver-devel] Opened twice

[Bernd E. <eid...@we...>]

(if you are on the tracker list:)

Sorry, there is no reload detection on the feature request page on 
sourceforge. So my reload posted the message again, please ignore, i closed 
the second one.

Re: [naviserver-devel] what the heck is this!?

[Zoran V. <zv...@ar...>]

Am 11.07.2006 um 13:46 schrieb Zoran Vasiljevic:

>
> I will investigate this in some more detail and patch
> the Tcl code correspondingly.

I have checked the fix into core-8-4-branch in Tcl project
and updated the HEAD (8.5) as well.

This affects all platforms.

Cheers,
Zoran

Re: [naviserver-devel] what the heck is this!?

[Zoran V. <zv...@ar...>]

Am 10.07.2006 um 17:03 schrieb Zoran Vasiljevic:

>
> The problem is:

The problem is that the Tcl finalization is pretty
ill-designed as it was retro-fitted in the Tcl lib
in the attempt to make one-shoe-fit-all principle.
The thread-wise finalization makes TSD vansih before
async handlers get deleted so the Tcl_AsyncDelete gets
a fresh new TSD pointer and fails.

This can be solved only by patching Tcl library and
making Tcl_AsyncDelete aware of that fact. This is not
Darwin related and can happen really on every OS.

I will investigate this in some more detail and patch
the Tcl code correspondingly.

Cheers,
Zoran 

Re: [naviserver-devel] ns_cache is still broken

[Zoran V. <zv...@ar...>]

Am 10.07.2006 um 20:34 schrieb Stephen Deasey:

> Limits will save the day, and cure world
> hunger...

... and win the next world football cup in South Africa
in four years  :-)

Cheers,
Zoran

Re: [naviserver-devel] NS_FATAL

[Vlad S. <vl...@cr...>]

right

Stephen Deasey wrote:
> On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
>> This is from AS 3.3.1
>>
>> typedef enum {
>>      Ns_DrvIdName,
>>      Ns_DrvIdStart,
>>      Ns_DrvIdAccept,
>>      Ns_DrvIdStop,
>>      Ns_DrvIdInit,
>>      Ns_DrvIdRead,
>>      Ns_DrvIdWrite,
>>      Ns_DrvIdClose,
>>      Ns_DrvIdFree,
>>      Ns_DrvIdPeer,
>>      Ns_DrvIdLocation,
>>      Ns_DrvIdHost,
>>      Ns_DrvIdPort,
>>      Ns_DrvIdSendFd,
>>      Ns_DrvIdSendFile,
>>      Ns_DrvIdDetach,
>>      Ns_DrvIdConnectionFd,
>>      Ns_DrvIdMoveContext,
>>      Ns_DrvIdPeerPort
>> } Ns_DrvId;
>>
>>
>> AS 3.x had sock driver basically only and it seems too much work for
>> every driver to reimplement the whole thing, so i would see a driver to
>> be able to reuse as much as possible what already exists in the server
>> and if needed can implement some specific functions.
>> In this case, UDP would implement Recv/Send only, no Accept, the rest
>> continues as usual.
>> Also, i would leave for the driver to decide how run, in own thread or
>> in the main thread. For some rare UDP requests for example which are
>> used for signaling only, having separate thread is too much overhead.
>>
> 
> 
> Right, that's too much to implement.  The core server should handle
> threading etc.
> 
> I guess it's worth clarifying what the "driver" is.  It's not
> multi-protocol support.  It's transport.  Plain sockets, SSL,
> peer2peer network, etc.  Protocol sits on top.  Many protocols use SSL
> for example, and it should be possible to reuse the SSL socket driver
> with each of them.
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

Re: [naviserver-devel] NS_FATAL

[Stephen D. <sd...@gm...>]

On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
> This is from AS 3.3.1
>
> typedef enum {
>      Ns_DrvIdName,
>      Ns_DrvIdStart,
>      Ns_DrvIdAccept,
>      Ns_DrvIdStop,
>      Ns_DrvIdInit,
>      Ns_DrvIdRead,
>      Ns_DrvIdWrite,
>      Ns_DrvIdClose,
>      Ns_DrvIdFree,
>      Ns_DrvIdPeer,
>      Ns_DrvIdLocation,
>      Ns_DrvIdHost,
>      Ns_DrvIdPort,
>      Ns_DrvIdSendFd,
>      Ns_DrvIdSendFile,
>      Ns_DrvIdDetach,
>      Ns_DrvIdConnectionFd,
>      Ns_DrvIdMoveContext,
>      Ns_DrvIdPeerPort
> } Ns_DrvId;
>
>
> AS 3.x had sock driver basically only and it seems too much work for
> every driver to reimplement the whole thing, so i would see a driver to
> be able to reuse as much as possible what already exists in the server
> and if needed can implement some specific functions.
> In this case, UDP would implement Recv/Send only, no Accept, the rest
> continues as usual.
> Also, i would leave for the driver to decide how run, in own thread or
> in the main thread. For some rare UDP requests for example which are
> used for signaling only, having separate thread is too much overhead.
>


Right, that's too much to implement.  The core server should handle
threading etc.

I guess it's worth clarifying what the "driver" is.  It's not
multi-protocol support.  It's transport.  Plain sockets, SSL,
peer2peer network, etc.  Protocol sits on top.  Many protocols use SSL
for example, and it should be possible to reuse the SSL socket driver
with each of them.

Re: [naviserver-devel] NS_FATAL

[Vlad S. <vl...@cr...>]

This is from AS 3.3.1

typedef enum {
     Ns_DrvIdName,
     Ns_DrvIdStart,
     Ns_DrvIdAccept,
     Ns_DrvIdStop,
     Ns_DrvIdInit,
     Ns_DrvIdRead,
     Ns_DrvIdWrite,
     Ns_DrvIdClose,
     Ns_DrvIdFree,
     Ns_DrvIdPeer,
     Ns_DrvIdLocation,
     Ns_DrvIdHost,
     Ns_DrvIdPort,
     Ns_DrvIdSendFd,
     Ns_DrvIdSendFile,
     Ns_DrvIdDetach,
     Ns_DrvIdConnectionFd,
     Ns_DrvIdMoveContext,
     Ns_DrvIdPeerPort
} Ns_DrvId;


AS 3.x had sock driver basically only and it seems too much work for 
every driver to reimplement the whole thing, so i would see a driver to 
be able to reuse as much as possible what already exists in the server 
and if needed can implement some specific functions.
In this case, UDP would implement Recv/Send only, no Accept, the rest 
continues as usual.
Also, i would leave for the driver to decide how run, in own thread or 
in the main thread. For some rare UDP requests for example which are 
used for signaling only, having separate thread is too much overhead.

Stephen Deasey wrote:
> On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
>> i agree, driver interface in the 3.x days was much better and flexible,
>> i was using it and tried to hack 4.x since then.
> 
> 
> It's not bad if all you want to do is Send/Revc, but it seems we
> don't.  Let's come up with a plan for what functions we need. Accept
> should go back in, for example.  Any ideas how we can cleanly handle
> UDP?
> 
> 
> 
>> Stephen Deasey wrote:
>>> On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
>>>> NS_FATAL in context of these functions means unrecoverable error, but if
>>>> name is not very good it can be changed
>>> Here's some code checking for NS_FATAL and recovering...
>>>
>>>     if (status == NS_FATAL || sockPtr->reqPtr == NULL || !SetServer(sockPtr)) {
>>>         SockRelease(sockPtr, SOCK_SERVERREJECT, 0);
>>>         return NS_ERROR;
>>>     }
>>>
>>> It's not just the name though, the distinction seems meaningless, and
>>> indeed different parts of the code are confused about what it means.
>>>
>>> We need to switch back to a socket driver interface with multiple
>>> functions, as in the 3.x days. Pushing everything through:
>>>
>>>     typedef int (Ns_DriverProc)(Ns_DriverCmd cmd, Ns_Sock *sock,
>>>                                           struct iovec *bufs, int nbufs);
>>>
>>> just isn't working.  Check out the comments for the new NsDriver*
>>> wrappers, even the long existing DriverKeep and DriverClose don't make
>>> a lot of sense.
>>>
>>>
>>>
>>>> Stephen Deasey wrote:
>>>>> NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
>>>>> in Ns_Fatal(...): and the server exits.
>>>>>
>>>>> Anyway, the following two disagree.  Whether they intend "request
>>>>> cannot be parsed" or "driver function not supported", NS_FATAL isn't
>>>>> the way to say it.
>>>>>
>>>>>
>>>>> /*
>>>>>  *----------------------------------------------------------------------
>>>>>  *
>>>>>  * Ns_DriverSetRequest --
>>>>>  *
>>>>>  *      Parses request line and sets as current Request struct, should be
>>>>>  *      in the form: METHOD URL ?PROTO?
>>>>>  *
>>>>>  * Results:
>>>>>  *      NS_ERROR in case of empty line
>>>>>  *      NS_FATAL if request cannot be parsed.
>>>>>  *      NS_OK if parsed sucessfully
>>>>>  *
>>>>>  * Side effects:
>>>>>  *      This is supposed to be called from drivers before the
>>>>>  *      socket is queued, usually from DriverQueue command.
>>>>>  *      Primary purpose is to allow non-HTTP drivers to setup
>>>>>  *      request line so registered callback proc will be called
>>>>>  *      during connection processing
>>>>>  *
>>>>>  *----------------------------------------------------------------------
>>>>>  */
>>>>>
>>>>> /*
>>>>>  *----------------------------------------------------------------------
>>>>>  *
>>>>>  * SockQueue --
>>>>>  *
>>>>>  *      Puts socket into connection queue
>>>>>  *
>>>>>  *      Call driver's queue handler for the last checks before actual
>>>>>  *      connection enqueue. NS_ERROR is valid here because that means
>>>>>  *      driver does not implement this call, we care about NS_FATAL status
>>>>>  *      only which means we cannot queue this socket. It is driver's
>>>>> responsibility
>>>>>  *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
>>>>>  *      for all non-HTTP or not-parsed sockets this call will fail
>>>>>  *
>>>>>  * Results:
>>>>>  *      NS_OK if queued,
>>>>>  *      NS_ERROR if socket closed because of error
>>>>>  *      NS_TIMEOUT if queue is full
>>>>>  *
>>>>>  * Side effects:
>>>>>  *      None
>>>>>  *
>>>>>  *----------------------------------------------------------------------
>>>>>  */
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------------
>>>>> Using Tomcat but need to do more? Need to support web services, security?
>>>>> Get stuff done quickly with pre-integrated technology to make your job easier
>>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>>>> _______________________________________________
>>>>> naviserver-devel mailing list
>>>>> nav...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>>>
>>>> --
>>>> Vlad Seryakov
>>>> 571 262-8608 office
>>>> vl...@cr...
>>>> http://www.crystalballinc.com/vlad/
>>>>
>>>>
>>>>
>>>> -------------------------------------------------------------------------
>>>> Using Tomcat but need to do more? Need to support web services, security?
>>>> Get stuff done quickly with pre-integrated technology to make your job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>>> _______________________________________________
>>>> naviserver-devel mailing list
>>>> nav...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>>
>>>
>>> -------------------------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, security?
>>> Get stuff done quickly with pre-integrated technology to make your job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> naviserver-devel mailing list
>>> nav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>
>> --
>> Vlad Seryakov
>> 571 262-8608 office
>> vl...@cr...
>> http://www.crystalballinc.com/vlad/
>>
>>
>>
>> -------------------------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

Re: [naviserver-devel] NS_FATAL

[Stephen D. <sd...@gm...>]

On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
> i agree, driver interface in the 3.x days was much better and flexible,
> i was using it and tried to hack 4.x since then.


It's not bad if all you want to do is Send/Revc, but it seems we
don't.  Let's come up with a plan for what functions we need. Accept
should go back in, for example.  Any ideas how we can cleanly handle
UDP?



> Stephen Deasey wrote:
> > On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
> >> NS_FATAL in context of these functions means unrecoverable error, but if
> >> name is not very good it can be changed
> >
> > Here's some code checking for NS_FATAL and recovering...
> >
> >     if (status == NS_FATAL || sockPtr->reqPtr == NULL || !SetServer(sockPtr)) {
> >         SockRelease(sockPtr, SOCK_SERVERREJECT, 0);
> >         return NS_ERROR;
> >     }
> >
> > It's not just the name though, the distinction seems meaningless, and
> > indeed different parts of the code are confused about what it means.
> >
> > We need to switch back to a socket driver interface with multiple
> > functions, as in the 3.x days. Pushing everything through:
> >
> >     typedef int (Ns_DriverProc)(Ns_DriverCmd cmd, Ns_Sock *sock,
> >                                           struct iovec *bufs, int nbufs);
> >
> > just isn't working.  Check out the comments for the new NsDriver*
> > wrappers, even the long existing DriverKeep and DriverClose don't make
> > a lot of sense.
> >
> >
> >
> >> Stephen Deasey wrote:
> >>> NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
> >>> in Ns_Fatal(...): and the server exits.
> >>>
> >>> Anyway, the following two disagree.  Whether they intend "request
> >>> cannot be parsed" or "driver function not supported", NS_FATAL isn't
> >>> the way to say it.
> >>>
> >>>
> >>> /*
> >>>  *----------------------------------------------------------------------
> >>>  *
> >>>  * Ns_DriverSetRequest --
> >>>  *
> >>>  *      Parses request line and sets as current Request struct, should be
> >>>  *      in the form: METHOD URL ?PROTO?
> >>>  *
> >>>  * Results:
> >>>  *      NS_ERROR in case of empty line
> >>>  *      NS_FATAL if request cannot be parsed.
> >>>  *      NS_OK if parsed sucessfully
> >>>  *
> >>>  * Side effects:
> >>>  *      This is supposed to be called from drivers before the
> >>>  *      socket is queued, usually from DriverQueue command.
> >>>  *      Primary purpose is to allow non-HTTP drivers to setup
> >>>  *      request line so registered callback proc will be called
> >>>  *      during connection processing
> >>>  *
> >>>  *----------------------------------------------------------------------
> >>>  */
> >>>
> >>> /*
> >>>  *----------------------------------------------------------------------
> >>>  *
> >>>  * SockQueue --
> >>>  *
> >>>  *      Puts socket into connection queue
> >>>  *
> >>>  *      Call driver's queue handler for the last checks before actual
> >>>  *      connection enqueue. NS_ERROR is valid here because that means
> >>>  *      driver does not implement this call, we care about NS_FATAL status
> >>>  *      only which means we cannot queue this socket. It is driver's
> >>> responsibility
> >>>  *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
> >>>  *      for all non-HTTP or not-parsed sockets this call will fail
> >>>  *
> >>>  * Results:
> >>>  *      NS_OK if queued,
> >>>  *      NS_ERROR if socket closed because of error
> >>>  *      NS_TIMEOUT if queue is full
> >>>  *
> >>>  * Side effects:
> >>>  *      None
> >>>  *
> >>>  *----------------------------------------------------------------------
> >>>  */
> >>>
> >>>
> >>> -------------------------------------------------------------------------
> >>> Using Tomcat but need to do more? Need to support web services, security?
> >>> Get stuff done quickly with pre-integrated technology to make your job easier
> >>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> >>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >>> _______________________________________________
> >>> naviserver-devel mailing list
> >>> nav...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >>>
> >> --
> >> Vlad Seryakov
> >> 571 262-8608 office
> >> vl...@cr...
> >> http://www.crystalballinc.com/vlad/
> >>
> >>
> >>
> >> -------------------------------------------------------------------------
> >> Using Tomcat but need to do more? Need to support web services, security?
> >> Get stuff done quickly with pre-integrated technology to make your job easier
> >> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> >> _______________________________________________
> >> naviserver-devel mailing list
> >> nav...@li...
> >> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >>
> >
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > naviserver-devel mailing list
> > nav...@li...
> > https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >
>
> --
> Vlad Seryakov
> 571 262-8608 office
> vl...@cr...
> http://www.crystalballinc.com/vlad/
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>

Re: [naviserver-devel] NS_FATAL

[Vlad S. <vl...@cr...>]

i agree, driver interface in the 3.x days was much better and flexible, 
i was using it and tried to hack 4.x since then.

Stephen Deasey wrote:
> On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
>> NS_FATAL in context of these functions means unrecoverable error, but if
>> name is not very good it can be changed
> 
> Here's some code checking for NS_FATAL and recovering...
> 
>     if (status == NS_FATAL || sockPtr->reqPtr == NULL || !SetServer(sockPtr)) {
>         SockRelease(sockPtr, SOCK_SERVERREJECT, 0);
>         return NS_ERROR;
>     }
> 
> It's not just the name though, the distinction seems meaningless, and
> indeed different parts of the code are confused about what it means.
> 
> We need to switch back to a socket driver interface with multiple
> functions, as in the 3.x days. Pushing everything through:
> 
>     typedef int (Ns_DriverProc)(Ns_DriverCmd cmd, Ns_Sock *sock,
>                                           struct iovec *bufs, int nbufs);
> 
> just isn't working.  Check out the comments for the new NsDriver*
> wrappers, even the long existing DriverKeep and DriverClose don't make
> a lot of sense.
> 
> 
> 
>> Stephen Deasey wrote:
>>> NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
>>> in Ns_Fatal(...): and the server exits.
>>>
>>> Anyway, the following two disagree.  Whether they intend "request
>>> cannot be parsed" or "driver function not supported", NS_FATAL isn't
>>> the way to say it.
>>>
>>>
>>> /*
>>>  *----------------------------------------------------------------------
>>>  *
>>>  * Ns_DriverSetRequest --
>>>  *
>>>  *      Parses request line and sets as current Request struct, should be
>>>  *      in the form: METHOD URL ?PROTO?
>>>  *
>>>  * Results:
>>>  *      NS_ERROR in case of empty line
>>>  *      NS_FATAL if request cannot be parsed.
>>>  *      NS_OK if parsed sucessfully
>>>  *
>>>  * Side effects:
>>>  *      This is supposed to be called from drivers before the
>>>  *      socket is queued, usually from DriverQueue command.
>>>  *      Primary purpose is to allow non-HTTP drivers to setup
>>>  *      request line so registered callback proc will be called
>>>  *      during connection processing
>>>  *
>>>  *----------------------------------------------------------------------
>>>  */
>>>
>>> /*
>>>  *----------------------------------------------------------------------
>>>  *
>>>  * SockQueue --
>>>  *
>>>  *      Puts socket into connection queue
>>>  *
>>>  *      Call driver's queue handler for the last checks before actual
>>>  *      connection enqueue. NS_ERROR is valid here because that means
>>>  *      driver does not implement this call, we care about NS_FATAL status
>>>  *      only which means we cannot queue this socket. It is driver's
>>> responsibility
>>>  *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
>>>  *      for all non-HTTP or not-parsed sockets this call will fail
>>>  *
>>>  * Results:
>>>  *      NS_OK if queued,
>>>  *      NS_ERROR if socket closed because of error
>>>  *      NS_TIMEOUT if queue is full
>>>  *
>>>  * Side effects:
>>>  *      None
>>>  *
>>>  *----------------------------------------------------------------------
>>>  */
>>>
>>>
>>> -------------------------------------------------------------------------
>>> Using Tomcat but need to do more? Need to support web services, security?
>>> Get stuff done quickly with pre-integrated technology to make your job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> naviserver-devel mailing list
>>> nav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>
>> --
>> Vlad Seryakov
>> 571 262-8608 office
>> vl...@cr...
>> http://www.crystalballinc.com/vlad/
>>
>>
>>
>> -------------------------------------------------------------------------
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

Re: [naviserver-devel] NS_FATAL

[Stephen D. <sd...@gm...>]

On 7/10/06, Vlad Seryakov <vl...@cr...> wrote:
> NS_FATAL in context of these functions means unrecoverable error, but if
> name is not very good it can be changed

Here's some code checking for NS_FATAL and recovering...

    if (status == NS_FATAL || sockPtr->reqPtr == NULL || !SetServer(sockPtr)) {
        SockRelease(sockPtr, SOCK_SERVERREJECT, 0);
        return NS_ERROR;
    }

It's not just the name though, the distinction seems meaningless, and
indeed different parts of the code are confused about what it means.

We need to switch back to a socket driver interface with multiple
functions, as in the 3.x days. Pushing everything through:

    typedef int (Ns_DriverProc)(Ns_DriverCmd cmd, Ns_Sock *sock,
                                          struct iovec *bufs, int nbufs);

just isn't working.  Check out the comments for the new NsDriver*
wrappers, even the long existing DriverKeep and DriverClose don't make
a lot of sense.



> Stephen Deasey wrote:
> > NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
> > in Ns_Fatal(...): and the server exits.
> >
> > Anyway, the following two disagree.  Whether they intend "request
> > cannot be parsed" or "driver function not supported", NS_FATAL isn't
> > the way to say it.
> >
> >
> > /*
> >  *----------------------------------------------------------------------
> >  *
> >  * Ns_DriverSetRequest --
> >  *
> >  *      Parses request line and sets as current Request struct, should be
> >  *      in the form: METHOD URL ?PROTO?
> >  *
> >  * Results:
> >  *      NS_ERROR in case of empty line
> >  *      NS_FATAL if request cannot be parsed.
> >  *      NS_OK if parsed sucessfully
> >  *
> >  * Side effects:
> >  *      This is supposed to be called from drivers before the
> >  *      socket is queued, usually from DriverQueue command.
> >  *      Primary purpose is to allow non-HTTP drivers to setup
> >  *      request line so registered callback proc will be called
> >  *      during connection processing
> >  *
> >  *----------------------------------------------------------------------
> >  */
> >
> > /*
> >  *----------------------------------------------------------------------
> >  *
> >  * SockQueue --
> >  *
> >  *      Puts socket into connection queue
> >  *
> >  *      Call driver's queue handler for the last checks before actual
> >  *      connection enqueue. NS_ERROR is valid here because that means
> >  *      driver does not implement this call, we care about NS_FATAL status
> >  *      only which means we cannot queue this socket. It is driver's
> > responsibility
> >  *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
> >  *      for all non-HTTP or not-parsed sockets this call will fail
> >  *
> >  * Results:
> >  *      NS_OK if queued,
> >  *      NS_ERROR if socket closed because of error
> >  *      NS_TIMEOUT if queue is full
> >  *
> >  * Side effects:
> >  *      None
> >  *
> >  *----------------------------------------------------------------------
> >  */
> >
> >
> > -------------------------------------------------------------------------
> > Using Tomcat but need to do more? Need to support web services, security?
> > Get stuff done quickly with pre-integrated technology to make your job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > naviserver-devel mailing list
> > nav...@li...
> > https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> >
>
> --
> Vlad Seryakov
> 571 262-8608 office
> vl...@cr...
> http://www.crystalballinc.com/vlad/
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>

Re: [naviserver-devel] NS_FATAL

[Vlad S. <vl...@cr...>]

NS_FATAL in context of these functions means unrecoverable error, but if 
name is not very good it can be changed

Stephen Deasey wrote:
> NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
> in Ns_Fatal(...): and the server exits.
> 
> Anyway, the following two disagree.  Whether they intend "request
> cannot be parsed" or "driver function not supported", NS_FATAL isn't
> the way to say it.
> 
> 
> /*
>  *----------------------------------------------------------------------
>  *
>  * Ns_DriverSetRequest --
>  *
>  *      Parses request line and sets as current Request struct, should be
>  *      in the form: METHOD URL ?PROTO?
>  *
>  * Results:
>  *      NS_ERROR in case of empty line
>  *      NS_FATAL if request cannot be parsed.
>  *      NS_OK if parsed sucessfully
>  *
>  * Side effects:
>  *      This is supposed to be called from drivers before the
>  *      socket is queued, usually from DriverQueue command.
>  *      Primary purpose is to allow non-HTTP drivers to setup
>  *      request line so registered callback proc will be called
>  *      during connection processing
>  *
>  *----------------------------------------------------------------------
>  */
> 
> /*
>  *----------------------------------------------------------------------
>  *
>  * SockQueue --
>  *
>  *      Puts socket into connection queue
>  *
>  *      Call driver's queue handler for the last checks before actual
>  *      connection enqueue. NS_ERROR is valid here because that means
>  *      driver does not implement this call, we care about NS_FATAL status
>  *      only which means we cannot queue this socket. It is driver's
> responsibility
>  *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
>  *      for all non-HTTP or not-parsed sockets this call will fail
>  *
>  * Results:
>  *      NS_OK if queued,
>  *      NS_ERROR if socket closed because of error
>  *      NS_TIMEOUT if queue is full
>  *
>  * Side effects:
>  *      None
>  *
>  *----------------------------------------------------------------------
>  */
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

[naviserver-devel] NS_FATAL

[Stephen D. <sd...@gm...>]

NS_FATAL doesn't make any sense.  Fatal means unrecoverable error, as
in Ns_Fatal(...): and the server exits.

Anyway, the following two disagree.  Whether they intend "request
cannot be parsed" or "driver function not supported", NS_FATAL isn't
the way to say it.


/*
 *----------------------------------------------------------------------
 *
 * Ns_DriverSetRequest --
 *
 *      Parses request line and sets as current Request struct, should be
 *      in the form: METHOD URL ?PROTO?
 *
 * Results:
 *      NS_ERROR in case of empty line
 *      NS_FATAL if request cannot be parsed.
 *      NS_OK if parsed sucessfully
 *
 * Side effects:
 *      This is supposed to be called from drivers before the
 *      socket is queued, usually from DriverQueue command.
 *      Primary purpose is to allow non-HTTP drivers to setup
 *      request line so registered callback proc will be called
 *      during connection processing
 *
 *----------------------------------------------------------------------
 */

/*
 *----------------------------------------------------------------------
 *
 * SockQueue --
 *
 *      Puts socket into connection queue
 *
 *      Call driver's queue handler for the last checks before actual
 *      connection enqueue. NS_ERROR is valid here because that means
 *      driver does not implement this call, we care about NS_FATAL status
 *      only which means we cannot queue this socket. It is driver's
responsibility
 *      to allocate Request structure via Ns_DriverSetRequest call, otherwise
 *      for all non-HTTP or not-parsed sockets this call will fail
 *
 * Results:
 *      NS_OK if queued,
 *      NS_ERROR if socket closed because of error
 *      NS_TIMEOUT if queue is full
 *
 * Side effects:
 *      None
 *
 *----------------------------------------------------------------------
 */

[naviserver-devel] Segfault in async writer

[Stephen D. <sd...@gm...>]

This crashes most of the time to me:

#0  0x00539d34 in NsWriterQueue (conn=0x9507838, nsend=2048,
chan=0x96af320, fp=0x0, fd=-1, data=0x0) at driver.c:2927
2927        Ns_Log(Notice, "Writer: %d: started sock=%d, fd=%d:
size=%u, flags=%X: %s",
(gdb) bt
#0  0x00539d34 in NsWriterQueue (conn=0x9507838, nsend=2048,
chan=0x96af320, fp=0x0, fd=-1, data=0x0) at driver.c:2927
#1  0x005347f7 in ConnSend (conn=0x9507838, nsend=2048,
chan=0x96af320, fp=0x0, fd=-1) at connio.c:955
#2  0x0053418f in Ns_ConnSendChannel (conn=0x9507838, chan=0x96af320,
nsend=2048) at connio.c:581
#3  0x0054cc94 in ReturnOpen (conn=0x9507838, status=200,
type=0x578319 "*/*", chan=0x96af320, fp=0x0, fd=-1, len=2048) at
return.c:1380
#4  0x0054cae8 in Ns_ConnReturnOpenChannel (conn=0x9507838,
status=200, type=0x578319 "*/*", chan=0x96af320, len=2048) at
return.c:1263
#5  0x0053e04f in ReturnRange (conn=0x9507838, rangesPtr=0xb0fb20e0,
chan=0x96af320, data=0x0, len=2048, type=0x578319 "*/*") at
fastpath.c:922
#6  0x0053d803 in FastReturn (servPtr=0x94fa218, conn=0x9507838,
status=200, type=0x578319 "*/*",
    file=0xb0fb21f0
"/home/sd/ns/naviserver-cfix/tests/testserver/pages/2048bytes",
stPtr=0xb0fb2184) at fastpath.c:579
#7  0x0053d132 in NsFastPathProc (arg=0x94fa218, conn=0x9507838) at
fastpath.c:304
#8  0x0054740d in Ns_ConnRunRequest (conn=0x9507838) at op.c:259
#9  0x00549fe4 in ConnRun (connPtr=0x9507838) at queue.c:735
#10 0x00549b39 in NsConnThread (arg=0x9633a90) at queue.c:591
#11 0x003b12bb in NsThreadMain (arg=0x9630ae0) at thread.c:224
#12 0x003b2338 in ThreadMain (arg=0x9630ae0) at pthread.c:736
#13 0x0010640b in start_thread () from /lib/libpthread.so.0
#14 0x00b67b7e in clone () from /lib/libc.so.6

(gdb) print *wrSockPtr

$1 = {nextPtr = 0x78787878, sockPtr = 0x78787878, data = 0x78787878
<Address 0x78787878 out of bounds>, fd = 2021161080, nread =
2021161080,
  nsent = 2021161080, size = 2021161080, flags = 2021161080, bufsize =
2021161080, buf = 0x78787878 <Address 0x78787878 out of bounds>}


The sock has already been pushed to another queue by this point.

Re: [naviserver-devel] ns_confuse (was ns_cache)

[Stephen D. <sd...@gm...>]

On 7/10/06, Zoran Vasiljevic <zv...@ar...> wrote:
>
> Am 10.07.2006 um 15:49 schrieb Zoran Vasiljevic:
>
> >
> > As the subject says, I'm mostly ns_confused.
>
> ... and tired... Just forget about that. The thing
> is I should have tested from two threads at the
> same time...
>
> Uaaaahhhhhhh....
>


Don't forget top make that an actual test case next time...  :-)

Re: [naviserver-devel] ns_cache is still broken

[Stephen D. <sd...@gm...>]

On 7/10/06, Rick Cobb <rc...@kn...> wrote:
> We do something fairly strange on our commands that might be useful
> here.  We treat the string argument for a duration or timer as having 3
> potential signs: "-", "+", and "@".  Dash and plus *always* mean
> relative-to-now.  @ always means absolute time.
>
> Any given option or argument documents whether its *default sign* is
> -,+, or @.  For expirations, we usually say that the default is "+". So
> "-expiry 5" is 5 seconds from now, while "-expiry @5" expired a long
> time ago.
>
> And it makes parsing a timer or duration a standard operation throughout
> our code.  Unfortunately, it's in our C++ stuff, so not really suitable
> for the Naviserver core.
>
> Hope this helps --
> -- ReC


Yeah, I was wondering about this.

Using straight numbers the underlying Tcl obj has it's internal rep
shimmered to Long or Ns_Time, which seems like an advantage.  What
swung it for me was the recent roll over of Unix time to an extra
digit.  Trying to add a number that large to the current time is
clearly an error as the time will overflow, so that seemed like a good
place to put the cutoff point.

Maybe the signs are more readable in code?  I'm hoping you wont have
to manually set this much. Limits will save the day, and cure world
hunger...

Re: [naviserver-devel] ns_cache is still broken

[Rick C. <rc...@Kn...>]

We do something fairly strange on our commands that might be useful
here.  We treat the string argument for a duration or timer as having 3
potential signs: "-", "+", and "@".  Dash and plus *always* mean
relative-to-now.  @ always means absolute time.

Any given option or argument documents whether its *default sign* is
-,+, or @.  For expirations, we usually say that the default is "+". So
"-expiry 5" is 5 seconds from now, while "-expiry @5" expired a long
time ago.

And it makes parsing a timer or duration a standard operation throughout
our code.  Unfortunately, it's in our C++ stuff, so not really suitable
for the Naviserver core.

Hope this helps --
-- ReC

-----Original Message-----
From: nav...@li...
[mailto:nav...@li...] On Behalf Of
Stephen Deasey
Sent: Saturday, July 08, 2006 3:05 PM
To: nav...@li...
Subject: Re: [naviserver-devel] ns_cache is still broken

On 6/28/06, Vlad Seryakov <vl...@cr...> wrote:
> I also have question what is the meaning of changing -ttl
> relativeSeconds into -expires absolutetime.
>
> Now Tcl code looks bloated with all -expires [expr [ns_time]+3600]
lines
> not counting that this is much slower than doing such incrementing C.
>
> May be we can keep both parameters, -ttl as relative and -expires as
> absolute?
>


I changed it to make -timeout and -expiry regular.  But you're right,
it's ugly when you just want to specify an offset from now such as +3
seconds.

I've changed it in CVS so that small -timeout and -expiry times are
treated as offsets from now, and large values are treated as absolute
times in the future.


------------------------------------------------------------------------
-
Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D=
121642
_______________________________________________
naviserver-devel mailing list
nav...@li...
https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] what the heck is this!?

[Zoran V. <zv...@ar...>]

Am 10.07.2006 um 16:56 schrieb Zoran Vasiljevic:

>
> Am 10.07.2006 um 16:44 schrieb Vlad Seryakov:
>
>> I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the
>> right version.
>
> Well, no...
>
> Reading symbols for shared libraries .++ done
> [10/Jul/2006:16:55:09][23983.2684415384][-main-] Notice: binder:  
> started
> [10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain:
> NaviServer/4.99.2 starting
> [10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain:
> security info: uid=0, euid=0, gid=0, egid=0
> [10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain: Tcl
> version: 8.4.13
> [10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain: max
> files: FD_SETSIZE = 1024, rl_cur = 12288, rl_max = 12288
>
>
> [10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: serv:
> stopping server: lexxsrv
> [10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: serv:
> connection threads stopped
> [10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: sched:
> shutdown pending
> [10/Jul/2006:16:56:12][23983.25245184][-driver-] Notice: exiting
> [10/Jul/2006:16:56:12][23983.25176064][-sched-] Notice: sched:
> shutdown started
> [10/Jul/2006:16:56:12][23983.25176064][-sched-] Notice: sched:
> shutdown complete
> [10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: socks:
> shutdown pending
> [10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: nscp: shutdown
> [10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: socks:
> shutdown complete
> [10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: driver:
> shutdown complete
> [10/Jul/2006:16:56:12][23983.25345536][-tclthread-] Notice: Scheduler
> thread exiting
>
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
> [Switching to process 23983 thread 0x3613]
> 0x0a016204 in Tcl_AsyncDelete (async=0x3a51508) at /Users/zoran/sf/
> tcl/unix/../generic/tclAsync.c:297
> 297             while (prevPtr->nextPtr != asyncPtr) {
> (gdb)
>
>

The problem is:

Breakpoint 1, Tcl_AsyncDelete (async=0x3a51508) at /Users/zoran/sf/ 
tcl/unix/../generic/tclAsync.c:285
285         ThreadSpecificData *tsdPtr = TCL_TSD_INIT(&dataKey);
(gdb) print *tsdPtr
$1 = {
   firstHandler = 0x27e880,
   lastHandler = 0x3ab6d08,
   asyncReady = 0,
   asyncActive = 48307496,
   asyncMutex = 0x0
}
(gdb) cont
Continuing.

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
0x0a016204 in Tcl_AsyncDelete (async=0x3a51508) at /Users/zoran/sf/ 
tcl/unix/../generic/tclAsync.c:297
297             while (prevPtr->nextPtr != asyncPtr) {


You see: Tcl_AsyncDelete is called two times with
the same async handler. This can never work.

How come you call it twice?
Zoran

>
>
>
>>
>> Zoran Vasiljevic wrote:
>>> Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:
>>>
>>>> That is strange, what version of Tcl is it?
>>>
>>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
>>> NaviServer/4.99.2 starting
>>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
>>> security info: uid=0, euid=0, gid=0, egid=0
>>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain: Tcl
>>> version: 8.4.12
>>>
>>>
>>>> Zoran Vasiljevic wrote:
>>>>> Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
>>>>>
>>>>>> Does it happen all the time
>>>>> Every time I stop the server. Just did a fresh checkout and
>>>>> recompile:
>>>>>
>>>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>>>> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
>>>>> [Switching to process 23748 thread 0x3803]
>>>>> 0x0a016204 in Tcl_AsyncDelete (async=0x3821688) at /Users/zoran/ 
>>>>> sf/
>>>>> tcl/unix/../generic/tclAsync.c:297
>>>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>>>> (gdb) print prevPtr
>>>>> $1 = (AsyncHandler *) 0x0
>>>>> (gdb) list
>>>>> 292             if (tsdPtr->firstHandler == NULL) {
>>>>> 293                 tsdPtr->lastHandler = NULL;
>>>>> 294             }
>>>>> 295         } else {
>>>>> 296             prevPtr = tsdPtr->firstHandler;
>>>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>>>> 298                 prevPtr = prevPtr->nextPtr;
>>>>> 299             }
>>>>> 300             prevPtr->nextPtr = asyncPtr->nextPtr;
>>>>> 301             if (tsdPtr->lastHandler == asyncPtr) {
>>>>> (gdb) print *tsdPtr
>>>>> $2 = {
>>>>>    firstHandler = 0x0,
>>>>>    lastHandler = 0x0,
>>>>>    asyncReady = 0,
>>>>>    asyncActive = 0,
>>>>>    asyncMutex = 0x33a64c8
>>>>> }
>>>>> (gdb)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------ 
>>>>> -
>>>>> --
>>>>> ----
>>>>> Using Tomcat but need to do more? Need to support web services,
>>>>> security?
>>>>> Get stuff done quickly with pre-integrated technology to make your
>>>>> job easier
>>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>>>> Geronimo
>>>>> http://sel.as-us.falkag.net/sel?
>>>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>>>> _______________________________________________
>>>>> naviserver-devel mailing list
>>>>> nav...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>>>
>>>> -- 
>>>> Vlad Seryakov
>>>> 571 262-8608 office
>>>> vl...@cr...
>>>> http://www.crystalballinc.com/vlad/
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> -
>>>> --
>>>> ---
>>>> Using Tomcat but need to do more? Need to support web services,
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make your
>>>> job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?
>>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>>> _______________________________________________
>>>> naviserver-devel mailing list
>>>> nav...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> -
>>> ----
>>> Using Tomcat but need to do more? Need to support web services,
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?
>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> naviserver-devel mailing list
>>> nav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>
>>
>> -- 
>> Vlad Seryakov
>> 571 262-8608 office
>> vl...@cr...
>> http://www.crystalballinc.com/vlad/
>>
>>
>>
>> --------------------------------------------------------------------- 
>> -
>> ---
>> Using Tomcat but need to do more? Need to support web services,
>> security?
>> Get stuff done quickly with pre-integrated technology to make your
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>> Geronimo
>> http://sel.as-us.falkag.net/sel?
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] what the heck is this!?

[Zoran V. <zv...@ar...>]

Am 10.07.2006 um 16:44 schrieb Vlad Seryakov:

> I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the
> right version.

Well, no...

Reading symbols for shared libraries .++ done
[10/Jul/2006:16:55:09][23983.2684415384][-main-] Notice: binder: started
[10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain:  
NaviServer/4.99.2 starting
[10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain:  
security info: uid=0, euid=0, gid=0, egid=0
[10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain: Tcl  
version: 8.4.13
[10/Jul/2006:16:55:10][23983.2684415384][-main-] Notice: nsmain: max  
files: FD_SETSIZE = 1024, rl_cur = 12288, rl_max = 12288


[10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: serv:  
stopping server: lexxsrv
[10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: serv:  
connection threads stopped
[10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: sched:  
shutdown pending
[10/Jul/2006:16:56:12][23983.25245184][-driver-] Notice: exiting
[10/Jul/2006:16:56:12][23983.25176064][-sched-] Notice: sched:  
shutdown started
[10/Jul/2006:16:56:12][23983.25176064][-sched-] Notice: sched:  
shutdown complete
[10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: socks:  
shutdown pending
[10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: nscp: shutdown
[10/Jul/2006:16:56:12][23983.25171456][-socks-] Notice: socks:  
shutdown complete
[10/Jul/2006:16:56:12][23983.2684415384][-main-] Notice: driver:  
shutdown complete
[10/Jul/2006:16:56:12][23983.25345536][-tclthread-] Notice: Scheduler  
thread exiting

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
[Switching to process 23983 thread 0x3613]
0x0a016204 in Tcl_AsyncDelete (async=0x3a51508) at /Users/zoran/sf/ 
tcl/unix/../generic/tclAsync.c:297
297             while (prevPtr->nextPtr != asyncPtr) {
(gdb)





>
> Zoran Vasiljevic wrote:
>> Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:
>>
>>> That is strange, what version of Tcl is it?
>>
>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
>> NaviServer/4.99.2 starting
>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:
>> security info: uid=0, euid=0, gid=0, egid=0
>> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain: Tcl
>> version: 8.4.12
>>
>>
>>> Zoran Vasiljevic wrote:
>>>> Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
>>>>
>>>>> Does it happen all the time
>>>> Every time I stop the server. Just did a fresh checkout and
>>>> recompile:
>>>>
>>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>>> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
>>>> [Switching to process 23748 thread 0x3803]
>>>> 0x0a016204 in Tcl_AsyncDelete (async=0x3821688) at /Users/zoran/sf/
>>>> tcl/unix/../generic/tclAsync.c:297
>>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>>> (gdb) print prevPtr
>>>> $1 = (AsyncHandler *) 0x0
>>>> (gdb) list
>>>> 292             if (tsdPtr->firstHandler == NULL) {
>>>> 293                 tsdPtr->lastHandler = NULL;
>>>> 294             }
>>>> 295         } else {
>>>> 296             prevPtr = tsdPtr->firstHandler;
>>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>>> 298                 prevPtr = prevPtr->nextPtr;
>>>> 299             }
>>>> 300             prevPtr->nextPtr = asyncPtr->nextPtr;
>>>> 301             if (tsdPtr->lastHandler == asyncPtr) {
>>>> (gdb) print *tsdPtr
>>>> $2 = {
>>>>    firstHandler = 0x0,
>>>>    lastHandler = 0x0,
>>>>    asyncReady = 0,
>>>>    asyncActive = 0,
>>>>    asyncMutex = 0x33a64c8
>>>> }
>>>> (gdb)
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------- 
>>>> --
>>>> ----
>>>> Using Tomcat but need to do more? Need to support web services,
>>>> security?
>>>> Get stuff done quickly with pre-integrated technology to make your
>>>> job easier
>>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>>> Geronimo
>>>> http://sel.as-us.falkag.net/sel?
>>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>>> _______________________________________________
>>>> naviserver-devel mailing list
>>>> nav...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>>
>>> -- 
>>> Vlad Seryakov
>>> 571 262-8608 office
>>> vl...@cr...
>>> http://www.crystalballinc.com/vlad/
>>>
>>>
>>>
>>> -------------------------------------------------------------------- 
>>> --
>>> ---
>>> Using Tomcat but need to do more? Need to support web services,
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel?
>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> naviserver-devel mailing list
>>> nav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Using Tomcat but need to do more? Need to support web services,  
>> security?
>> Get stuff done quickly with pre-integrated technology to make your  
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
>> Geronimo
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>
>
> -- 
> Vlad Seryakov
> 571 262-8608 office
> vl...@cr...
> http://www.crystalballinc.com/vlad/
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] what the heck is this!?

[Vlad S. <vl...@cr...>]

I use 8.4.13 and AOLserver mentions on 4.5 release that 8.4.13 is the 
right version.

Zoran Vasiljevic wrote:
> Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:
> 
>> That is strange, what version of Tcl is it?
> 
> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:  
> NaviServer/4.99.2 starting
> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:  
> security info: uid=0, euid=0, gid=0, egid=0
> [10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain: Tcl  
> version: 8.4.12
> 
> 
>> Zoran Vasiljevic wrote:
>>> Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
>>>
>>>> Does it happen all the time
>>> Every time I stop the server. Just did a fresh checkout and
>>> recompile:
>>>
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
>>> [Switching to process 23748 thread 0x3803]
>>> 0x0a016204 in Tcl_AsyncDelete (async=0x3821688) at /Users/zoran/sf/
>>> tcl/unix/../generic/tclAsync.c:297
>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>> (gdb) print prevPtr
>>> $1 = (AsyncHandler *) 0x0
>>> (gdb) list
>>> 292             if (tsdPtr->firstHandler == NULL) {
>>> 293                 tsdPtr->lastHandler = NULL;
>>> 294             }
>>> 295         } else {
>>> 296             prevPtr = tsdPtr->firstHandler;
>>> 297             while (prevPtr->nextPtr != asyncPtr) {
>>> 298                 prevPtr = prevPtr->nextPtr;
>>> 299             }
>>> 300             prevPtr->nextPtr = asyncPtr->nextPtr;
>>> 301             if (tsdPtr->lastHandler == asyncPtr) {
>>> (gdb) print *tsdPtr
>>> $2 = {
>>>    firstHandler = 0x0,
>>>    lastHandler = 0x0,
>>>    asyncReady = 0,
>>>    asyncActive = 0,
>>>    asyncMutex = 0x33a64c8
>>> }
>>> (gdb)
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------- 
>>> ----
>>> Using Tomcat but need to do more? Need to support web services,  
>>> security?
>>> Get stuff done quickly with pre-integrated technology to make your  
>>> job easier
>>> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
>>> Geronimo
>>> http://sel.as-us.falkag.net/sel? 
>>> cmd=lnk&kid=120709&bid=263057&dat=121642
>>> _______________________________________________
>>> naviserver-devel mailing list
>>> nav...@li...
>>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>>
>> -- 
>> Vlad Seryakov
>> 571 262-8608 office
>> vl...@cr...
>> http://www.crystalballinc.com/vlad/
>>
>>
>>
>> ---------------------------------------------------------------------- 
>> ---
>> Using Tomcat but need to do more? Need to support web services,  
>> security?
>> Get stuff done quickly with pre-integrated technology to make your  
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
>> Geronimo
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/

Re: [naviserver-devel] what the heck is this!?

[Zoran V. <zv...@ar...>]

Am 10.07.2006 um 16:31 schrieb Vlad Seryakov:

> That is strange, what version of Tcl is it?

[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:  
NaviServer/4.99.2 starting
[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain:  
security info: uid=0, euid=0, gid=0, egid=0
[10/Jul/2006:16:35:26][23776.2684415384][-main-] Notice: nsmain: Tcl  
version: 8.4.12


>
> Zoran Vasiljevic wrote:
>> Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
>>
>>> Does it happen all the time
>>
>> Every time I stop the server. Just did a fresh checkout and
>> recompile:
>>
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
>> [Switching to process 23748 thread 0x3803]
>> 0x0a016204 in Tcl_AsyncDelete (async=0x3821688) at /Users/zoran/sf/
>> tcl/unix/../generic/tclAsync.c:297
>> 297             while (prevPtr->nextPtr != asyncPtr) {
>> (gdb) print prevPtr
>> $1 = (AsyncHandler *) 0x0
>> (gdb) list
>> 292             if (tsdPtr->firstHandler == NULL) {
>> 293                 tsdPtr->lastHandler = NULL;
>> 294             }
>> 295         } else {
>> 296             prevPtr = tsdPtr->firstHandler;
>> 297             while (prevPtr->nextPtr != asyncPtr) {
>> 298                 prevPtr = prevPtr->nextPtr;
>> 299             }
>> 300             prevPtr->nextPtr = asyncPtr->nextPtr;
>> 301             if (tsdPtr->lastHandler == asyncPtr) {
>> (gdb) print *tsdPtr
>> $2 = {
>>    firstHandler = 0x0,
>>    lastHandler = 0x0,
>>    asyncReady = 0,
>>    asyncActive = 0,
>>    asyncMutex = 0x33a64c8
>> }
>> (gdb)
>>
>>
>>
>>
>> --------------------------------------------------------------------- 
>> ----
>> Using Tomcat but need to do more? Need to support web services,  
>> security?
>> Get stuff done quickly with pre-integrated technology to make your  
>> job easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
>> Geronimo
>> http://sel.as-us.falkag.net/sel? 
>> cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> naviserver-devel mailing list
>> nav...@li...
>> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
>>
>
> -- 
> Vlad Seryakov
> 571 262-8608 office
> vl...@cr...
> http://www.crystalballinc.com/vlad/
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services,  
> security?
> Get stuff done quickly with pre-integrated technology to make your  
> job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache  
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel

Re: [naviserver-devel] what the heck is this!?

[Vlad S. <vl...@cr...>]

That is strange, what version of Tcl is it?

Zoran Vasiljevic wrote:
> Am 10.07.2006 um 16:25 schrieb Vlad Seryakov:
> 
>> Does it happen all the time
> 
> Every time I stop the server. Just did a fresh checkout and
> recompile:
> 
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x00000004
> [Switching to process 23748 thread 0x3803]
> 0x0a016204 in Tcl_AsyncDelete (async=0x3821688) at /Users/zoran/sf/ 
> tcl/unix/../generic/tclAsync.c:297
> 297             while (prevPtr->nextPtr != asyncPtr) {
> (gdb) print prevPtr
> $1 = (AsyncHandler *) 0x0
> (gdb) list
> 292             if (tsdPtr->firstHandler == NULL) {
> 293                 tsdPtr->lastHandler = NULL;
> 294             }
> 295         } else {
> 296             prevPtr = tsdPtr->firstHandler;
> 297             while (prevPtr->nextPtr != asyncPtr) {
> 298                 prevPtr = prevPtr->nextPtr;
> 299             }
> 300             prevPtr->nextPtr = asyncPtr->nextPtr;
> 301             if (tsdPtr->lastHandler == asyncPtr) {
> (gdb) print *tsdPtr
> $2 = {
>    firstHandler = 0x0,
>    lastHandler = 0x0,
>    asyncReady = 0,
>    asyncActive = 0,
>    asyncMutex = 0x33a64c8
> }
> (gdb)
> 
> 
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> naviserver-devel mailing list
> nav...@li...
> https://lists.sourceforge.net/lists/listinfo/naviserver-devel
> 

-- 
Vlad Seryakov
571 262-8608 office
vl...@cr...
http://www.crystalballinc.com/vlad/