I've observed the same on 7.0.01 (no patches), though the behavior
seems inconsistent with different browsers.

Following is a copy of a prior email I sent (maybe a week or 2 back)
in response to David Easter's suggestion of adding an AL that executes
the PERFORM-ACTION-EXIT-APP on close window.  It would be useful to
get some additional feedback using the referenced def so I can log it
as a defect on arswiki at http://arswiki.org/bugs

Axton Grams

--- begin message ---

I just performed a series of tests to prove/disprove some of the
behaviors of approaching the problem in this way.  Here are the
results:

- Created a user with a floating license AGRAMS
- Created 2 forms: console and ticket (in a deployable app with public
everything)
- Console form has an AL that on close runs the PERFORM-ACTION-EXIT-APP rp

These are the observations I made:
- When the user first logs in, they are usually granted a floating
read license (GOOD).  Observed once that a user was granted a floating
write license when first logging in.
- When the user submits or modifies a record, they are granted a
floating write license (GOOD)
- If a form is opened from the console, via an active link open window
action, with a target of current, and that form is closed, the
floating license is not released (BAD).  This was consistent across IE
and FireFox.
- If the user closes the Console form, the license is not released
with FireFox (BAD)
- If the user closes the Console form, the license is released with IE7 (GOOD)
- If the user clicks a button that calls the PERFORM-ACTION-EXIT-APP
rp, the user is redirected to
http://localhost/arsys/shared/logout.jsp, and the license is not
released every time on FireFox (BAD).  The behavior was inconsistent.
Sometimes it would release the license, other times it would not.
- If the user clicks a button that call the PERFORM-ACTION-EXIT-APP
rp, the user is redirected to
http://localhost/arsys/shared/logout.jsp, and the license is released
on IE7 (GOOD)

It seems there may be some problems in the MT license
allocation/release mechanisms.

This was tested using the following environment:
- Windows 2003 Server
- ARServer 7.0.01 200609271856
- Mid-Tier 7.0.01 200609271856
- Apache Tomcat/5.5.17 using 1.5.0_09
- Browsers: Firefox 2.0.0.1 and IE 7

I've posted a simple def that can be used to verify this behavior at
http://arswiki.org/dist/ars/AppClose.def

It's simple and stupid, but provides the tools to test the mid-tier.
Feel free to poke holes in my observations.

Axton Grams

--- end message ---

On 3/13/07, Wheeler, Dylan <[EMAIL PROTECTED]> wrote:
**


Hi List,
So I'm running into a problem with my licenses. We don't quite have enough
so I've been playing around trying to get the licenses freed up when I can.
I'm finding that the licenses on my server are sticking no matter what
though and I'm not sure what's keeping them there.

If I open IE and login then click the logout button on the Home Page it
should release the license right? The license is still showing as taken 15
minutes later in my admin tool.

I created an AL and put in the PERFORM-ACTION-EXIT-APP command, execute on
window close and left the run if open, permissions are set to public.
Closing the Home Page in the user tool will close out the application, but
the license is still active. Closing the window on the mid tier will leave
the license active.

Anyone run into this or have a clue what could be causing it?
ARS/Mid Tier 6.3 Patch 21
IIS on Windows 2003

-------------

Dylan Wheeler
 Production Control Analyst Principal
IT Operations
Downey Savings & Loan Association, F.A.
Email: [EMAIL PROTECTED]

This message and any attachments are for the intended recipient(s) only and
may contain privileged, confidential and/or proprietary information about
Downey Savings or its customers, which Downey Savings does not intend to
disclose to the public. If you received this message by mistake, please
notify the sender by reply e-mail and delete the message and attachments.



This message and any attachments are for the intended recipient(s) only and
may contain privileged, confidential and/or proprietary information about
Downey Savings or its customers, which Downey Savings does not intend to
disclose to the public.  If you received this message by mistake, please
notify the sender by reply e-mail and delete the message and attachments.
__20060125_______________________This posting was submitted
with HTML in it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Reply via email to