licenses getting revoked

The Jazz licenses will be reset if the web application's work directory
is deleted. When you restart your server, do you do anything other than
just stop and start it? Are you using Tomcat or WebSphere?

I haven't heard anything about licenses just vanishing when a server is
running. Is there a particular action that you are doing that leads to
the licenses being reset?

Matt Lavin
Jazz Server Team


millarde wrote:

I have installed the licenses several times and "something"
happens that bounces them out at some point. They seem fine for
several days, then one day I get an email from someone saying
"did you realize our Jazz license is about to expire?"

Happened again over the weekend. Since I don't do much admin of the
server (though I did reboot the machine on Friday), I'm expecting it
is one of two things -- restarting the server or the automated weekly
DB2 backup.

Any ideas/suggestions? The license expires on Tuesday, so I'm assuming
I'm just out of luck if there isn't a fix for this.

Thanks...Millard

P.S.: I tagged this onto a similar issue on jazz.extend, but they
don't seem to get as much activity over there and I'm running out of
time.

Note it's a known limitation that installing an activation key on the server
does not update repotools. However it will not affect the operation of
repotools as it can still read from the repository.

See
repotools should respect installed server keys (58494)
Suppress trial warning in repotools (59472)

--
Ritchie Schacher
Jazz Server Development

"millarde" <millarde> wrote in message
news:gbpq66$o80$1@localhost.localdomain...

I have installed the licenses several times and "something"
happens that bounces them out at some point. They seem fine for
several days, then one day I get an email from someone saying
"did you realize our Jazz license is about to expire?"

Happened again over the weekend. Since I don't do much admin of the
server (though I did reboot the machine on Friday), I'm expecting it
is one of two things -- restarting the server or the automated weekly
DB2 backup.

Any ideas/suggestions? The license expires on Tuesday, so I'm assuming
I'm just out of luck if there isn't a fix for this.

Thanks...Millard

P.S.: I tagged this onto a similar issue on jazz.extend, but they
don't seem to get as much activity over there and I'm running out of
time.

The Jazz licenses will be reset if the web application's work directory is deleted. When you restart your server, do you do anything other than just stop and start it? Are you using Tomcat or WebSphere?

Tomcat. It has been pretty much fire-and-forget. I only take the server down if I need to do some other sort of maintenance on the box (so, not often at all). I use the Start menu items for stopping and starting the server. I used the DB2 wizard to schedule a regular backup. That's it.

How do I identify the "web application's work directory"?

Tomcat's work directory for the Jazz.war is
<jazz>/server/tomcat/work/Catalina/localhost/jazz. If that
directory is deleted, any licenses installed through the web UI would
need to be installed again.

I don't know of any case where a license would be lost while a server is
running, but I'm interested to hear if you see the problem again, or if
you figure out what action triggers the license to be lost.

Matt Lavin
Jazz Server Team


millarde wrote:

lavinmwrote:
The Jazz licenses will be reset if the web application's work
directory is deleted. When you restart your server, do you do
anything other than just stop and start it? Are you using Tomcat or
WebSphere?

Tomcat. It has been pretty much fire-and-forget. I only take the
server down if I need to do some other sort of maintenance on the box
(so, not often at all). I use the Start menu items for stopping and
starting the server. I used the DB2 wizard to schedule a regular
backup. That's it.

How do I identify the "web application's work directory"?

I don't know of any case where a license would be lost while a server is
running, but I'm interested to hear if you see the problem again, or if
you figure out what action triggers the license to be lost.

Courtesy of a required security patch, I stopped my Jazz server (using the Windows start menu shortcut), applied the patch, then restarted. Jazz is set to automatically start when the system is rebooted. After everything was up and running again, I stopped Jazz, expecting to find additional updates that needed to be applied. It was all cool, so I just started Jazz again, started up RTC, and started working on a new Project Area. I get a "no license" type error. I open web client, check License Key Management -- my perm licenses are missing and my temporary ones expired. Had to install the licenses, again.

So it seems like stopping/starting the Tomcat server is all it really takes. But perhaps the license was lost somewhere else, but didn't manifest itself until the server was restarted. I'll try to squeeze in some time to just start/stop/reboot to see if that's all it takes.

Some other people have been seeing the problem and bug 63213 is tracking
it. If you subscribe yourself to that bug then you can get updates on
the problem, and perhaps you can contribute a reproducible way to make
the licenses get removed.

Matt Lavin
Jazz Server Team


millarde wrote:

lavinmwrote:

I don't know of any case where a license would be lost while a
server is
running, but I'm interested to hear if you see the problem again, or
if
you figure out what action triggers the license to be lost.


Courtesy of a required security patch, I stopped my Jazz server (using
the Windows start menu shortcut), applied the patch, then restarted.
Jazz is set to automatically start when the system is rebooted.
After everything was up and running again, I stopped Jazz, expecting
to find additional updates that needed to be applied. It was all
cool, so I just started Jazz again, started up RTC, and started
working on a new Project Area. I get a "no license" type
error. I open web client, check License Key Management -- my perm
licenses are missing and my temporary ones expired. Had to install
the licenses, again.

So it seems like stopping/starting the Tomcat server is all it really
takes. But perhaps the license was lost somewhere else, but didn't
manifest itself until the server was restarted. I'll try to squeeze
in some time to just start/stop/reboot to see if that's all it takes.