My first guess would be that somehow or other you have hit a version of the
infamous (and often discussed) ND "session bleed". Your ND server has one
or more sets of your ND objects, called project graphs. Each session is
given exclusive access to one project graph during a web event. During a
subsequent web event, the session might get the same project graph, or
another one.
You typically develop in an environment with one project graph, and one
active session at a time. Project design flaws are hidden until you move
the code to a situation where you have either or both of:
-- One project graph used in succession by two different sessions
-- One session given different project graphs in two successive web events.
-- Curt Springer, Team ND
At 01:54 AM 9/13/99 -0700, Donald Macdonald wrote:
>I have developed a system on NT and migrated the code to the test
>environment which
>is a Sun solaris box. I am now experiencing problems with the session
>objects that I
>use within my code.
>
>For most of the time the system will perform as expected with the correct
>session
>objects returned in the page calls. Occassionaly though I will get a NULL
>POINTER
>ERROR when the session object does not now contain a value. If I hit the
>back button
>on the browser and then re-execute the code it will more often than not
>work correctly.
>I have also experienced the incorrect session data being returned during a
>call so that
>I will switch to a different user.
>
>Is there some configuartion problem within my app server?
>
>Has anyone else suffered simliar problems after migration?
>
>_________________________________________________________________________
>
>For help in using, subscribing, and unsubscribing to the discussion
>forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
>
>For dire need help, email: [EMAIL PROTECTED]
_________________________________________________________________________
For help in using, subscribing, and unsubscribing to the discussion
forums, please go to: http://www.netdynamics.com/support/visitdevfor.html
For dire need help, email: [EMAIL PROTECTED]
