licensing issue

[aapatel]

Hello,
I keep getting the following error intermittently using lps-2.0p, any ideas!?

Error: This application is not licensed to be served to <ip.address>. Restart your server and/or see www.laszlosystems.com


ankur

[antun]

The developer (i.e. DE) license only allows you to access the LPS from the computer you're developing on and one other machine.

i.e. if you're developing on box A, you can hit it from box A and box B. But you can't hit it from box C. You can restart your servlet container on box A, and then you'll be able to hit it from box C, assuming that's the first box you hit it from.

-Antun

[aapatel]

great thanks!

[aapatel]

well it seems there might still be an issue:

The restart should only be required if the lps-2.0p context had been accessed from more than 2 distinct ip addresses and not dependent on the tomcat engine being accessed from more than 2 ip addresses.

We made sure that there is only one browser accessing the lps context but there happened to be some other session interacting with the same tomcat engine upon which the resulting message requested a restart as per the lps app...any ideas?

[antun]

I've never seen this before. As far as I know, it should only be if a Laszlo app is accessed. I think you could access JSPs in the LPS webapp, and that shouldn't affect it.

Are you sure that there's no strange cacheing going on? Are you sure that another machine isn't hitting the Laszlo app?

-Antun

[aapatel]

I am almost positive next to having a port-sniffer verify it, since the app server is residing on my laptop!

[antun]

And what's the other IP that's accessing it? Is it a box on an internal network? Is it a machine on an outside network?

-Antun

[aapatel]

the lps container does not report what other ip address is using the application. To verify, I asked all other clients for this tomcat server to stop accessing it for the time being and the error has not been raised since. I did verify with those other clients that none were using the lps webapp.

ankur

[antun]

So which computer are you accessing the LPS from when you get the error that you initially posted?

You can also have a look at the LPS log which lives at:

TOMCAT_DIR\work\Standalone\localhost\lps-2.0p\LPS\logs\lps.log

... to see what IP addresses are accessing it.

-Antun

PS Is the server that the LPS is on a Linux or Solaris box by any chance?

[aapatel]

I dug around a bit in the log files and found that the gateway server is "tring to access" the app? That does not make sense unless the application that I am executing is going out over the network back to Laszlo and then coming back...does that make sense?

ankur

[antun]

No the LPS doesn't "call home".

-Antun

That does not make sense unless the application that I am executing is going out over the network back to Laszlo and then coming back...does that make sense?

[aapatel]

lps is running on a solaris box being accessed by windox XP, both of whom are behind the same firewall.

ankur

[antun]

I've done some research, and apparently there can be some issues with *nix systems identifying themselves as other than localhost, which means you can only access them from a single machine.

This is only an issue when developing on a DE license.

If you don't hit the LPS from the Solaris box first, do you still get the problem?

-Antun

[aapatel]

Yep, because the browser access the webapp is never launched from the solaris box itself.

[bloch]

Could you post up the lps.log file?

It's burried inside the tomcat work directory for the lps web app (Antun showed you the path for tomcat4 running on windows).

Thanks!
-Eric

[aapatel]

i think it might the security doing a "sweep/probe" - I will post the file as soon as i confirmed that is not the case. ok?

[antun]

One more thing - you said it was intermittent, right? Can you tell me which apps you run that cause the error?

-Antun

[aapatel]

it is one of our test apps and it must have been the security probes because i did not notice the issue today (so far :)) Appreciate you following up and apologize for the false alarm.


ankur