[lindholm42]

I just tried firing up a second instance of eclipse with a different
workspace and I got this complaint:

Subscriber: lindholm42
Product ID: E3MP (MyEclipse Professional Subscription)
License version: 3.0
Full Maintenance Included
Subscription expiration date (YYYYMMDD): 20080130
Number of licenses: 1

SUBSCRIPTION KEY PROBLEM: Too many users are using this subscription key. MyEclipse will now disable most featues. Either fewer instances of the workbench need to be run or additional subscription
keys need to be purchased through the upgrade link. The list of IPs using this key have been written to the log and are also listed here for your convenience: 137.82.28.159, 127.0.0.1

How can there be too many users when there is only me?

I tend to use different workspace for different projects and if I can only
have one active workspace at a time, ughh!

George

[Riyad Kalla]

George,
You can email [email protected] and explain your development situation and get a key that will allow this. The reason we do this is because when we started off, companies were hosting, on a central virtualized server, many copies of MyEclipse at once, so technically all those copies had the same IP so started checking for this situation. Unfortunately in our broad net we have snared some perfectly legit uses (like yours). We’ll get you fixed up soon.

[kraelen]

I stumbled onto this old post because I’m running into the same problem. MyEclipse is installed on my laptop. Using it in various wifi hotspots in coffee shops, hotels, etc. means I frequently get a different IP. This HAS to be a common situation these days. I also managed to get MyEclipse running on my usb thumb drive, so I have MyEclipse on my keychain whenever I need it. I think both are legitimate single-user scenarios that are common these days.

IP addresses are an extremely poor identifier of a machine. Not to mention, the first IP Address listed on the error is always 127.0.0.1. I mean, come on, 127.0.0.1! How can you count that?

I’m also extremely bothered that you are shipping back my internal network IP addresses to your server at all, and tracking them with regards to my account. That seems like a big violation of my privacy. I’m sure it’s in the fine print somewhere, but that doesn’t make it okay.

I know [email protected] will fix me up, but I feel you really need to figure out a better way to stop your abuse problem – one that doesn’t cause your legitimate users headaches and a feeling of alienation. I purchased MyEclipse to save me time over messing with the problems of the Eclipse WTP/J2EE tooling. But this has cost me time without me doing anything wrong.

[Riyad Kalla]

I’m also extremely bothered that you are shipping back my internal network IP addresses to your server at all, and tracking them with regards to my account. That seems like a big violation of my privacy. I’m sure it’s in the fine print somewhere, but that doesn’t make it okay.

Oh we aren’t, don’t worry about that. We just display them for debugging purposes, they aren’t being recorded on our end.

kraelen,
Have you tried restarting when that error pops up when you join a new network? We also agree that IP address may not be the best way to identify a machine, but right now the license manager isn’t equipped to fingerprint the machine… and then there are a whole new bag of issues with using finger-printed machines as the ID… (we have to cap that, then a person has 2 laptops and a desktop and has just as many problems, etc.)

[kraelen]

Okay, now I understand a little more about what MyEclipse is doing, and I feel a bit better, and I can work around the issue.

But, couldn’t you add an exception for 127.0.0.1? If I understand what’s going on correctly, one common scenarios that seems to be happening to me is this: I’ll do the standard localhost browsing, which registers as 127.0.0.1. But then I’ll ask someone on the network to look at my work by browsing to the network domain name for the local box, and register the network IP like 192.168.1.142. After that MyEclipse will complain about Too Many Users. Putting an exception on 127.0.0.1 would fix that.

[Riyad Kalla]

That’s true, but that’s not a common use-case for the mass majority of our users, if that *is* a common use-case for you though, I’d encourage you to contact [email protected] and describe your setup to them and they can probably take care of you so you don’t get nagged all the time.

We don’t want anyone going batty using our software 😉

[Author]

Posts