Hi all,

We have problem on resetting license like when users hang we can not free the license even we already kill the users login and tbase.

The only thing we can do to reset the license is to kill it using licmon6.1 -k. Afterwards I will restart the license using the command:

# licd6.1 sleep 60

Is killing of license will cause problems if there's ongoing transactions/processes on Baan?

Is there any other work around available?

thanks and best regards,

julia

Hi Julia,

We are using the same procedure like the one you said. In fact, we have a script which does this and this script is in crontab. It is run every morning at 6. I did not notice any problem because of that, although there were job daemons that were running.

There may be problems with users who try to connect in the timeframe between running licmon6.1 -k and licd6.1. But I guess this is not a problem for you. You should not have job daemons that start at that hour.

There is another problem that I faced: I was running session "Delete Tables" exaclty in the moment when the licence daemon was restarted. I got an error message "No licence server available" in a white bw window. But the session kept running, so everything was all right. I did not notice any other strange behaviour.

Maybe other people have seen more than me. I am looking forward to what they say.

Cordiali saluti / Best Regards,

I have had problems in the past due to a licence reset.

If your licenses keep hanging due to bw failures you can use the resource parameter ds_timeout_detect (see solution 3312).

If the bshell crashes you have no other possibility than resetting the licence deamon.

Regards,
Han

The license daemon not releasing licenses is an old sore in the license management of Baan. Compare it to a program that a small memory leak. The easiest solution is indeed to have the license daemon restarted in automated way. Existing user connections should not experience any effect from the restart.

We too use to restart the licence daemon via Cron during the night but found that planning engines that we left running over night would be aborted by the reset process.

So you may find some existing user connections do indeed get affected.


PJ