You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Peter Nabbefeld <Pe...@gmx.de> on 2004/11/11 13:14:14 UTC
M3 does not start
Hello,
I've tried Geronimo the first time and got this (full output copied,
because I didn't know which part to copy):
C:\Programme\j2sdk_nb\geronimo-1.0-M3>set
GERONIMO_HOME=C:\Programme\j2sdk_nb\geronimo-1.0-M3
C:\Programme\j2sdk_nb\geronimo-1.0-M3>set
JDK_HOME=C:\Programme\j2sdk_nb\j2sdk1.5.0
C:\Programme\j2sdk_nb\geronimo-1.0-M3>cd /d
C:\Programme\j2sdk_nb\geronimo-1.0-M3
C:\Programme\j2sdk_nb\geronimo-1.0-M3>"C:\Programme\j2sdk_nb\j2sdk1.5.0\bin\java"
-jar bin\server.jar org/apache/geroni
mo/Server
13:05:30,121 INFO [Daemon] Server startup begun
13:05:30,362 INFO [Kernel] Starting boot
13:05:31,163 INFO [Kernel] Booted
13:05:31,393 INFO [ConfigurationManagerImpl] Loaded Configuration
geronimo.config:name="org/apache/geronimo/System"
13:05:31,874 INFO [Configuration] Started configuration
org/apache/geronimo/System
13:05:32,264 INFO [RMIRegistryService] Started RMI Registry on port 1099
13:05:32,294 INFO [ReadOnlyRepository] Repository root is
file:/C:/Programme/j2sdk_nb/geronimo-1.0-M3/repository/
13:05:32,515 INFO [ConfigurationManagerImpl] Loaded Configuration
geronimo.config:name="org/apache/geronimo/Server"
13:05:35,970 INFO [HttpServer] Statistics on = false for
org.apache.geronimo.jetty.JettyServer@1de45e2
13:05:36,540 INFO [Configuration] Started configuration
org/apache/geronimo/Server
13:05:37,592 INFO [LoginService] Login server has been started
13:05:37,612 INFO [ThreadPool] Thread pool DefaultThreadPool started
13:05:37,652 INFO [SecurityServiceMBean] Security service started
13:05:37,672 INFO [HttpServer] Version Jetty/5.1.RC1
13:05:37,682 INFO [Container] Started
org.apache.geronimo.jetty.JettyServer@1de45e2
13:05:37,842 WARN [GBeanMBean] RuntimeError thrown from doFail
java.lang.NullPointerException
at org.mortbay.util.ThreadedServer.stop(ThreadedServer.java:531)
at org.mortbay.http.SocketListener.stop(SocketListener.java:211)
at
org.apache.geronimo.jetty.connector.JettyConnector.doFail(JettyConnector.java:69)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.doFail(GBeanMBean.java:633)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.doSafeFail(AbstractManagedObject.java:619)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:519)
at
org.apache.geronimo.gbean.jmx.SingleProxy.attemptFullStart(SingleProxy.java:154)
at
org.apache.geronimo.gbean.jmx.SingleProxy.addTarget(SingleProxy.java:119)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanReference.handleNotification(GBeanMBeanReference.java:307)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerIn
terceptor.java:1652)
at
javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at
javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.sendNotification(AbstractManagedObject.java:267)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:532)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(AbstractManagedObject.java:305)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:329)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:288)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:283)
at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:375)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
13:05:37,872 WARN [SingleProxy] Exception occured while attempting to
fully start: objectName=geronimo.server:container
=Jetty,port=8080,type=WebConnector
java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at
org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:394)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:466)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:50)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.doStart(GBeanMBean.java:616)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:511)
at
org.apache.geronimo.gbean.jmx.SingleProxy.attemptFullStart(SingleProxy.java:154)
at
org.apache.geronimo.gbean.jmx.SingleProxy.addTarget(SingleProxy.java:119)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanReference.handleNotification(GBeanMBeanReference.java:307)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor$ListenerWrapper.handleNotification(DefaultMBeanServerIn
terceptor.java:1652)
at
javax.management.NotificationBroadcasterSupport.handleNotification(NotificationBroadcasterSupport.java:221)
at
javax.management.NotificationBroadcasterSupport.sendNotification(NotificationBroadcasterSupport.java:184)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.sendNotification(AbstractManagedObject.java:267)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:532)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(AbstractManagedObject.java:305)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:329)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:288)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:283)
at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:375)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
13:05:37,963 WARN [GBeanMBean] RuntimeError thrown from doFail
java.lang.NullPointerException
at org.mortbay.util.ThreadedServer.stop(ThreadedServer.java:531)
at org.mortbay.http.SocketListener.stop(SocketListener.java:211)
at
org.apache.geronimo.jetty.connector.JettyConnector.doFail(JettyConnector.java:69)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.doFail(GBeanMBean.java:633)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.doSafeFail(AbstractManagedObject.java:619)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:519)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(AbstractManagedObject.java:305)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:329)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:288)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:283)
at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:375)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
13:05:37,993 INFO [Kernel] Starting kernel shutdown
13:05:37,993 INFO [PersistentConfigurationList] Configuration list was
not saved. Kernel was never fully started.
13:05:38,003 INFO [LoginService] Login server has been stopped
13:05:38,003 INFO [ThreadPool] Thread pool DefaultThreadPool stopped
13:05:38,003 INFO [SecurityServiceMBean] Security service stopped
13:05:38,003 INFO [Container] Stopped
org.apache.geronimo.jetty.JettyServer@1de45e2
13:05:38,003 INFO [Configuration] Stopping configuration
org/apache/geronimo/Server
13:05:38,293 INFO [RMIRegistryService] Stopped RMI Registry
13:05:38,303 INFO [Configuration] Stopping configuration
org/apache/geronimo/System
13:05:38,313 INFO [Kernel] Kernel shutdown complete
org.apache.geronimo.kernel.config.InvalidConfigException: Invalid GBean
configuration for geronimo.config:name="org/apac
he/geronimo/Server"
at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:379)
at org.apache.geronimo.system.main.Daemon.main(Daemon.java:150)
Caused by: java.net.BindException: Address already in use: JVM_Bind
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at
org.mortbay.util.ThreadedServer.newServerSocket(ThreadedServer.java:394)
at org.mortbay.util.ThreadedServer.open(ThreadedServer.java:466)
at
org.apache.geronimo.jetty.connector.JettyConnector.doStart(JettyConnector.java:50)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.doStart(GBeanMBean.java:616)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.attemptFullStart(AbstractManagedObject.java:511)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.start(AbstractManagedObject.java:305)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:329)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at
org.apache.geronimo.gbean.jmx.AbstractManagedObject.startRecursive(AbstractManagedObject.java:343)
at
org.apache.geronimo.gbean.jmx.GBeanMBean$11.invoke(GBeanMBean.java:1036)
at
org.apache.geronimo.gbean.jmx.GBeanMBeanOperation.invoke(GBeanMBeanOperation.java:142)
at
org.apache.geronimo.gbean.jmx.GBeanMBean.invoke(GBeanMBean.java:844)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:288)
at org.apache.geronimo.kernel.Kernel.invoke(Kernel.java:283)
at
org.apache.geronimo.kernel.Kernel.startRecursiveGBean(Kernel.java:375)
... 1 more
13:05:38,373 INFO [Daemon] Server shutdown begun
13:05:38,373 INFO [Daemon] Server shutdown completed
======================================================
BTW: The start command in the readme uses other URL, which I'd also tested:
java -jar bin\server.jar org/apache/geronimo/DebugConsole
BTW-2: In Wiki it is metioned, that Geronimo does an autosearch for
tools.jar - is there also a parameter so I can Geronimo tell where to
look for it?
Kind regards
Peter Nabbefeld
Re: M3 does not start
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I hadn't thought of the problem of configuring the ports if
there's something running on them that you're unable to shut down.
It would be interesting to provide a tool that does nothing but
let you adjust the default network ports -- that could be used by (for
example) a graphical installer to let you customize the installation.
An alternative would be for a fancier installer to actually
perform the plan deployments that are currently done by the assembly
module; it would take a bit longer, but let you customize any of the
settings during installation. That might be better, if a little longer to
run.
Aaron
On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> Aaron Mulder schrieb:
>
> > Peter,
> > That's not so easy -- neither changing the default Jetty port nor
> > disabling Jetty. You need to either build a new server configuration for
> > yourself (replace the org/apache/geronimo/Server configuration) or edit
> > the details of that configuration via JMX changes at runtime. We don't
> > give you the source you need to do the first with the milestone (though
> > you can get it from the SVN repository), and as far as I know we don't
> > give you a good tool to make runtime JMX changes.
>
> I've noticed two serialized objects in config-store/4 - do they also
> contain the jetty config? Or is the information included in
> org.mortbay.jetty-5.1-SNAPSHOT.jar?
>
> In the first case, it should be easy to implement a tool (implied there
> is enough time ;-) ). In the second, there will be needed a patch to
> access configuration data either from serialized or xml data (last one
> preferred).
>
> BTW: I don't believe JMX would be a good idea to (initially) change port
> data, as this would make it impossible to install Geronimo into a "life"
> environment - You cannot force the admin to shutdown a probably large
> web site to install geronimo.
>
> >
> > We're hoping to provide some more robust management tools and
> > configuration procedures in the next milestone release. In the mean time,
> > let me know if you're interested in the "manual procedure" for altering
> > your default server configuration.
>
> IMO, this is definitly the wrong way. If I'm succesful with some tools,
> I'd prefer to supply them back. However, please don't wait for them, as
> I'm not got much spare time currently.
>
> Kind regards
>
> Peter
>
> >
> > Aaron
> >
> > On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> >
> >>Hi Aaron,
> >>
> >>Thank You for the quick response - You've been right. Could You probably
> >>add something like 'Needed Resources' add to the wiki? Such a big stack
> >>output sometimes becomes confusing, particularly if the cause for it is
> >>in the middle of the output. ;-)
> >>
> >>Two more questions:
> >>1. As Geronimo is currently an installation for testing with it, I'd
> >>like to change the default port - where can I do that?
> >>
> >>2. I'll want to use my existing Tomcat installation with Geronimo - how
> >>can I disable Jetty? Best would be, if I could simply disable it and
> >>possibly re-enable later.
> >>
> >>Kind regards
> >>
> >>Peter
> >>
> >>
> >>
> >>
> >>Aaron Mulder schrieb:
> >>
> >>
> >>> My guess is that this is the important part:
> >>>
> >>>On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> >>>
> >>>
> >>>>fully start: objectName=geronimo.server:container
> >>>>=Jetty,port=8080,type=WebConnector
> >>>>java.net.BindException: Address already in use: JVM_Bind
> >>>> at java.net.PlainSocketImpl.socketBind(Native Method)
> >>>> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
> >>>> at java.net.ServerSocket.bind(ServerSocket.java:319)
> >>>> at java.net.ServerSocket.<init>(ServerSocket.java:185)
> >>>
> >>>
> >>> In other words, it seems like something is already listening on
> >>>port 8080 -- perhaps Tomcat or a different Geronimo instance?
> >>>
> >>>Aaron
> >>>
> >>
> >>
> >
>
>
Re: M3 does not start
Posted by Jeremy Boynes <jb...@gluecode.com>.
Peter Nabbefeld wrote:
> Aaron Mulder schrieb:
>
>> Peter,
>> That's not so easy -- neither changing the default Jetty port nor
>> disabling Jetty. You need to either build a new server configuration for
>> yourself (replace the org/apache/geronimo/Server configuration) or edit
>> the details of that configuration via JMX changes at runtime. We don't
>> give you the source you need to do the first with the milestone (though
>> you can get it from the SVN repository), and as far as I know we don't
>> give you a good tool to make runtime JMX changes.
>
>
> I've noticed two serialized objects in config-store/4 - do they also
> contain the jetty config? Or is the information included in
> org.mortbay.jetty-5.1-SNAPSHOT.jar?
>
The files inside the config store are not intended for general
modification - one reason we use serialization for persisting the data.
> In the first case, it should be easy to implement a tool (implied there
> is enough time ;-) ). In the second, there will be needed a patch to
> access configuration data either from serialized or xml data (last one
> preferred).
>
There is an XML definition - the deployment plan used to build the
default server configuration.
> BTW: I don't believe JMX would be a good idea to (initially) change port
> data, as this would make it impossible to install Geronimo into a "life"
> environment - You cannot force the admin to shutdown a probably large
> web site to install geronimo.
>
We're tackling this two ways.
Firstly, we will be providing a console tool that lets someone do this
kind of configuration easily. The intention is to make it easier to set
up the server than wading through a collection of XML files. However,
this does mean we have to be able to boot the server the first time :-)
Secondly, we allow users to redefine the server configuration completely
by re-deploying the default configurations which are stored as XML files.
What this means for the guy who wants to install Geronimo in a live
environment is that they can stage the server configuration elsewhere
and then copy their customized server to the production environment.
They can stage it either by booting it and using the console or by
editing the XML plan and redeploying.
Hopefully this solves both problems - ease of use for new user and full
control of the configuration for an experienced admin.
--
Jeremy
PS If I had an admin running a large web site I would hope they didn't
experiment with new software on a production system ;-)
Re: M3 does not start
Posted by Peter Nabbefeld <Pe...@gmx.de>.
Aaron Mulder schrieb:
> Peter,
> That's not so easy -- neither changing the default Jetty port nor
> disabling Jetty. You need to either build a new server configuration for
> yourself (replace the org/apache/geronimo/Server configuration) or edit
> the details of that configuration via JMX changes at runtime. We don't
> give you the source you need to do the first with the milestone (though
> you can get it from the SVN repository), and as far as I know we don't
> give you a good tool to make runtime JMX changes.
I've noticed two serialized objects in config-store/4 - do they also
contain the jetty config? Or is the information included in
org.mortbay.jetty-5.1-SNAPSHOT.jar?
In the first case, it should be easy to implement a tool (implied there
is enough time ;-) ). In the second, there will be needed a patch to
access configuration data either from serialized or xml data (last one
preferred).
BTW: I don't believe JMX would be a good idea to (initially) change port
data, as this would make it impossible to install Geronimo into a "life"
environment - You cannot force the admin to shutdown a probably large
web site to install geronimo.
>
> We're hoping to provide some more robust management tools and
> configuration procedures in the next milestone release. In the mean time,
> let me know if you're interested in the "manual procedure" for altering
> your default server configuration.
IMO, this is definitly the wrong way. If I'm succesful with some tools,
I'd prefer to supply them back. However, please don't wait for them, as
I'm not got much spare time currently.
Kind regards
Peter
>
> Aaron
>
> On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
>
>>Hi Aaron,
>>
>>Thank You for the quick response - You've been right. Could You probably
>>add something like 'Needed Resources' add to the wiki? Such a big stack
>>output sometimes becomes confusing, particularly if the cause for it is
>>in the middle of the output. ;-)
>>
>>Two more questions:
>>1. As Geronimo is currently an installation for testing with it, I'd
>>like to change the default port - where can I do that?
>>
>>2. I'll want to use my existing Tomcat installation with Geronimo - how
>>can I disable Jetty? Best would be, if I could simply disable it and
>>possibly re-enable later.
>>
>>Kind regards
>>
>>Peter
>>
>>
>>
>>
>>Aaron Mulder schrieb:
>>
>>
>>> My guess is that this is the important part:
>>>
>>>On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
>>>
>>>
>>>>fully start: objectName=geronimo.server:container
>>>>=Jetty,port=8080,type=WebConnector
>>>>java.net.BindException: Address already in use: JVM_Bind
>>>> at java.net.PlainSocketImpl.socketBind(Native Method)
>>>> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
>>>> at java.net.ServerSocket.bind(ServerSocket.java:319)
>>>> at java.net.ServerSocket.<init>(ServerSocket.java:185)
>>>
>>>
>>> In other words, it seems like something is already listening on
>>>port 8080 -- perhaps Tomcat or a different Geronimo instance?
>>>
>>>Aaron
>>>
>>
>>
>
Re: M3 does not start
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Peter,
That's not so easy -- neither changing the default Jetty port nor
disabling Jetty. You need to either build a new server configuration for
yourself (replace the org/apache/geronimo/Server configuration) or edit
the details of that configuration via JMX changes at runtime. We don't
give you the source you need to do the first with the milestone (though
you can get it from the SVN repository), and as far as I know we don't
give you a good tool to make runtime JMX changes.
We're hoping to provide some more robust management tools and
configuration procedures in the next milestone release. In the mean time,
let me know if you're interested in the "manual procedure" for altering
your default server configuration.
Aaron
On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> Hi Aaron,
>
> Thank You for the quick response - You've been right. Could You probably
> add something like 'Needed Resources' add to the wiki? Such a big stack
> output sometimes becomes confusing, particularly if the cause for it is
> in the middle of the output. ;-)
>
> Two more questions:
> 1. As Geronimo is currently an installation for testing with it, I'd
> like to change the default port - where can I do that?
>
> 2. I'll want to use my existing Tomcat installation with Geronimo - how
> can I disable Jetty? Best would be, if I could simply disable it and
> possibly re-enable later.
>
> Kind regards
>
> Peter
>
>
>
>
> Aaron Mulder schrieb:
>
> > My guess is that this is the important part:
> >
> > On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> >
> >>fully start: objectName=geronimo.server:container
> >>=Jetty,port=8080,type=WebConnector
> >>java.net.BindException: Address already in use: JVM_Bind
> >> at java.net.PlainSocketImpl.socketBind(Native Method)
> >> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
> >> at java.net.ServerSocket.bind(ServerSocket.java:319)
> >> at java.net.ServerSocket.<init>(ServerSocket.java:185)
> >
> >
> > In other words, it seems like something is already listening on
> > port 8080 -- perhaps Tomcat or a different Geronimo instance?
> >
> > Aaron
> >
>
>
Re: M3 does not start
Posted by Peter Nabbefeld <Pe...@gmx.de>.
Hi Aaron,
Thank You for the quick response - You've been right. Could You probably
add something like 'Needed Resources' add to the wiki? Such a big stack
output sometimes becomes confusing, particularly if the cause for it is
in the middle of the output. ;-)
Two more questions:
1. As Geronimo is currently an installation for testing with it, I'd
like to change the default port - where can I do that?
2. I'll want to use my existing Tomcat installation with Geronimo - how
can I disable Jetty? Best would be, if I could simply disable it and
possibly re-enable later.
Kind regards
Peter
Aaron Mulder schrieb:
> My guess is that this is the important part:
>
> On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
>
>>fully start: objectName=geronimo.server:container
>>=Jetty,port=8080,type=WebConnector
>>java.net.BindException: Address already in use: JVM_Bind
>> at java.net.PlainSocketImpl.socketBind(Native Method)
>> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
>> at java.net.ServerSocket.bind(ServerSocket.java:319)
>> at java.net.ServerSocket.<init>(ServerSocket.java:185)
>
>
> In other words, it seems like something is already listening on
> port 8080 -- perhaps Tomcat or a different Geronimo instance?
>
> Aaron
>
Re: M3 does not start
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
My guess is that this is the important part:
On Thu, 11 Nov 2004, Peter Nabbefeld wrote:
> fully start: objectName=geronimo.server:container
> =Jetty,port=8080,type=WebConnector
> java.net.BindException: Address already in use: JVM_Bind
> at java.net.PlainSocketImpl.socketBind(Native Method)
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
> at java.net.ServerSocket.bind(ServerSocket.java:319)
> at java.net.ServerSocket.<init>(ServerSocket.java:185)
In other words, it seems like something is already listening on
port 8080 -- perhaps Tomcat or a different Geronimo instance?
Aaron