- This topic has 6 replies, 3 voices, and was last updated 20 years ago by
.
-
Posts
-
We are using Eclipse3/myEclipse/Tomcat4 in a multi-users configuration sharing a physical linux box. Thus each user must have different ports assigned for their individual tomcat instances.
Although the port can be assigned manually and updated in the tomcat’s server.xml file, it’s more scalable/less maintenance to update the port dynamically at runtime when starting up Tomcat. Can a callback hook or external script be made available so we could customize the ports for Tomcat? The hook must be executed sequentially before the launch of Tomcat.
We plan to just ping the existing ports specified in server.xml and renumber them to a free/unused ports if they’re already taken by some server process.
In all honestly I don’t know that we would provide something at this level… are you aware of any IDE that does something like this?
Oracle JDeveloper provides this capability to reassign Tomcat ports when conflict is detected. Although this feature is not commonly available, it’s critical to our need. We currently has to modify a different open-source plugin to implement this requirement instead of using MyEclipse stop/start server functionality. If a callback hook is not feasible, would it be possible to expose some extension point so we can build own own plugin to customize the Tomcat launch? For example, besides port assignment, we are passing in pre-defined JVM properties for log directory, life cycle, classpath, etc… as standard configuration for webapp under development.
If a callback hook is not feasible, would it be possible to expose some extension point so we can build own own plugin to customize the Tomcat launch?
It’s certainly feasible, but it’s not on our current development plan. However there might be an easier way to do this.
For example, besides port assignment, we are passing in pre-defined JVM properties for log directory, life cycle, classpath, etc… as standard configuration for webapp under development.
You can pass all the JVM arguments you’d like simply by configuring the connector on the “Optional Java VM Arguments” located Window > Preferences > MyEclipse > Application Servers > Tomcat 4 > JDK. Here you can specify all the -D (or other) options you like, one per line. That should provide you with plenty of flexibility to specify a different port per developer as well as pass your other configuration arguments.
Scott, thanks for the suggestion. For the port assignment, this is not applicable because the ports are configured inside the tomcat’s server.xml file, not as JVM properties.
For other JVM properties, it’s true that they can be defined per user’s appserver instance. However, these values are changeable by any Eclipse user in their local workspace. Having the hook gives us the ability to enforce specific JVM properties and be sure it’s not corrupted or maniuplated by users. We can also inject site-wide configuration changes by making only 1 plugin changes rather than having to redo MyEclipse plugin preferences for every users on the system. This single localized change helps maintenance and support team greatly.
If this type of enhancement is not likely to be implemented in the short term, may we know what kind of license is required to obtain source code for MyEclipse in case we can customize the Tomcat launch ourselves? We are currently purchasing ~30 licenses for pilot projects. If enterprise license is involved for high hundreds of developers, it could be important that we can customize your plugin to our company’s specific requirement. You can PM me directly w/ licensing info instead of hijacking this thread.
Actually, this discussion needs to be taken up with subscriptions@genuitec.com. They’re best equipped to answer your questions from here. Please drop them an email and I’m sure they’ll be able to answer your questions.
