Ok. .... so there are bugs :-) Maybe even significant bugs! Maybe
even bugs that make it totally useless as is!! But its a good idea...
I'll look into this when I get a chance. I think maybe I'm calling
the wrong method on the persistent configuration list to find out
what's installed?
thanks for the test drive!
david jencks
On Oct 29, 2008, at 11:08 AM, Joe Bohn wrote:
I can create a server instance now. :-)
However, I was under the impression that this would clone the
existing server instance. Is there still more to be done for that
or did I misunderstand?
I started with the tomcat javaee5 server assembly and ran the new-
instance gshell command expecting to get a second server instance
that looked exactly like the javaee5 tomcat instance. I then
changed the port offset for the new instance, updated the server
name in GERONIMO_OPTS, and started the new server instance. The new
instance is basically just a bootstrap assembly. As you can see
from the messages below, it looks like just RMI Naming and JMX
Remoting Connector were started.
Booting Geronimo Kernel (in Java 1.5.0_16)...
Starting Geronimo Application Server v2.2-SNAPSHOT
[****************************************] 100% 1s Startup complete
Listening on Ports:
1109 127.0.0.1 RMI Naming
10009 127.0.0.1 JMX Remoting Connector
Geronimo Application Server started
Joe
David Jencks wrote:
umm..., added, now you can find the next thing I left out :-/
david jencks
On Oct 29, 2008, at 8:44 AM, Joe Bohn wrote:
David,
I think you must have forgotten something in the check-in. When I
attempt to create a new instance I get the following error from
gshell:
/> deploy/new-instance -n myserver1
ERROR NotFoundException: geronimo-commands:new-server-instance
Joe
Joe Bohn wrote:
This sounds really cool David! I'm hoping to give it a test
drive soon.
Joe
David Jencks wrote:
For a long time we've been talking about having an easy way to
create lots of server instances sharing the same geronimo
installation (GERONIMO-3123). After staring at the farm demo
long enough I realized that we could use almost the same
technique to "clone" a server instance as used to install the
same plugins on all the instances sharing a geronimo install.
The var directory was originally created by unpacking stuff out
of all the plugins installed in the server. So we can create a
new var directory for the new server instance by creating a
ServerInfo set up for the new instance (i.e. knowing where the
server is, i.e. the var directory), creating a
PluginInstallerGBean around it, and installing all the plugins
that are installed on the original server. After fixing a few
bugs, this amounts to unpacking the stuff out of all these
plugins into the new var directory.
This seems like a pretty elegant solution to me.
There's a new gshell command
deploy/new-instance -n server1
See GERONIMO-4382
thanks
david jencks
