Tomcat components won't start
Tomcat components will not start on starting the server. I did an offline rebuild today. What am I missing? Here is the console output. C:\GeronimoSource\geronimo>java -jar modules\assembly\target\geronimo-1.0-SNAPSHOT\bin\server.jar Booting Geronimo Kernel (in Java 1.4.2_08)... Starting Geronimo Application Server [**] 100% 22s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8080 0.0.0.0 Jetty Connector HTTP 8443 0.0.0.0 Jetty Connector HTTPS 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/console-jetty/1.0-SNAPSHOT/car RAR: geronimo/system-database/1.0-SNAPSHOT/car RAR: geronimo/system-jms/1.0-SNAPSHOT/car WAR: geronimo/remote-deploy/1.0-SNAPSHOT/car WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car Web Applications: http://Alexander:8080/ http://Alexander:8080/console http://Alexander:8080/console-standard http://Alexander:8080/remote-deploy WARNING: Some GBeans were not started successfully: TomcatResources (starting) TomcatEngine (starting) TomcatWebConnector (starting,redirectPort=8453,port=8090) TomcatAJPConnector (starting,redirectPort=8453,port=8019) TomcatWebSSLConnector (starting,port=8453,redirectPort=null) TomcatWebContainer (starting) Geronimo Application Server started
[jira] Created: (GERONIMO-1311) Geronimo server assemblies do not set execute permission on *.sh scripts
Geronimo server assemblies do not set execute permission on *.sh scripts Key: GERONIMO-1311 URL: http://issues.apache.org/jira/browse/GERONIMO-1311 Project: Geronimo Type: Bug Components: buildsystem, startup/shutdown Versions: 1.0 Reporter: John Sisson Fix For: 1.0 This was in the old modules/assembly/maven.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1152) Connector portlet does not display all WebConnectors
[ http://issues.apache.org/jira/browse/GERONIMO-1152?page=all ] Vamsavardhana Reddy closed GERONIMO-1152: - > Connector portlet does not display all WebConnectors > > > Key: GERONIMO-1152 > URL: http://issues.apache.org/jira/browse/GERONIMO-1152 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0-M5 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Assignee: Aaron Mulder > Fix For: 1.0 > Attachments: connector-moreformbuttons.patch, > connector-withdeleteconfirmation.patch, connector.patch > > Under WebServer management page, Connector portlet displays only jetty web > connectors and provides links to add only jetty connectors. It does not > display tomcat web connectors nor does it provide links to add tomcat > connectors. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1070) Network Listeners added through console are lost upon server restart
[ http://issues.apache.org/jira/browse/GERONIMO-1070?page=all ] Vamsavardhana Reddy closed GERONIMO-1070: - > Network Listeners added through console are lost upon server restart > > > Key: GERONIMO-1070 > URL: http://issues.apache.org/jira/browse/GERONIMO-1070 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0-M5 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Assignee: Aaron Mulder > Fix For: 1.0 > Attachments: saveconfig.patch > > Add new HTTP, HTTPS and AJP listeners using the "Add new HTTP listener", "Add > new HTTPS listener " and "Add new AJP listener" links provided in the "Web > Server" management page in Geronimo Console. The new listeners will be > created successfully and started. > But, once the server is stopped and started again, these listeners no longer > remain in the server. The configurations are lost!!! After the restart, > they are not listed under the "Network Listeners" in the "Web Server" > management page -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
gbuild: chef and co offlline?
Aaron, The Chariot boxes chef, timmy, and jimmy can't be reached. I checked the gbuild logs and it seems the three of them disappeared just after 8:45pm PST. Any ideas? -David
Re: [M1] Plugin hell, help desperately needed - JIRA 1308 created
Just as an fyi, this is a nice addition but doesn't really deal with
the "Plugin hell" issue David is talking about. It seems to be hit
and miss trying to get the new plugins installed and used during any
particular maven run.
From my experience it seems as if you delete your ~/.maven/cache and
~/.maven/plugins, then the cache gets rebuilt and the latest verision
of the plugin from your ~/.maven/repository is used. But as the
plugin is updated in the future, it will never reach the ~/.maven/
cache and builds will eventually start failing because of it.
There is more too it than that, David highlighted the frustrations
around the problem a bit better in his email.
-David
On Dec 7, 2005, at 7:39 PM, Donald Woods wrote:
JIRA-1308 has been opened for this and I am creating the patch
files to attach right now.
configs/geronimo-gbean-deployer/project.xml - uncomment the following
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
assemblies/j2ee-installer/project.xml - insert the following new
dependency
geronimo
geronimo-izpack-plugin
plugin
${pom.currentVersion}
-Donald
Bill Stoddard wrote:
Donald Woods wrote:
Finally got new4 goal to complete using Maven 1.1Beta2 (was
always failing with the same error you mention below), by editing
configs/geronimo-gbean-deployer/project.xml and removing the
comments from around the geronimo-packaging-plugin dependency to
re-enable it as a depend -
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
I'm running a full build now via
maven m:clean new -Dmaven.test.skip=true -Dmaven.itest.skip=true
to verify the change works repeatably before I open a JIRA and
attach the patch.
-Donald
Thanks Donald, that change got me over the failure (and I'm using
maven 1.0.2). I manually placed geronimo-packaging-plugin into
the .maven/cache. Ran into another failure to statisfy a
dependency on tranql-connector-derby-embed-local-1.1-SNAPSHOT.rar
but that's probably because I was doing an offline build.
It was a bit tricky mapping this message:
[echo] Running car:install for Geronimo Configuration for
performing service deployments
to
geronimo-gbean-deployer/project.xml
I made the connection (thank you findstr/grep) but failed to
investigate the dependencies in project.xml. Won't make that
mistake again ;-)
Will clean out .maven/cache and kick off a 'maven clean new' build
this evening and report back the results.
Bill
[jira] Commented: (GERONIMO-1192) Installer should create a config.xml for the target install
[ http://issues.apache.org/jira/browse/GERONIMO-1192?page=comments#action_12359710 ] David Jencks commented on GERONIMO-1192: applied patch except for parts already applied. Sendingassemblies/j2ee-installer/src/izpack/geronimo-izpack.xml Sendingassemblies/j2ee-installer/src/var/config/config.xml Sendingplugins/geronimo-izpack-plugin/plugin.jelly Transmitting file data ... Committed revision 355014. > Installer should create a config.xml for the target install > --- > > Key: GERONIMO-1192 > URL: http://issues.apache.org/jira/browse/GERONIMO-1192 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Installer runtime > Reporter: erik daughtrey > Assignee: David Jencks > Attachments: installer_1192_200512080036.patch > > DJ - "This could be done by adding bits associated with each configuration, > or by removing chunks from a 'universal' config.xml for the configuations we > didn't install." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1248) Problem in using a security realm added through geronimo console
[ http://issues.apache.org/jira/browse/GERONIMO-1248?page=all ] Vamsavardhana Reddy closed GERONIMO-1248: - > Problem in using a security realm added through geronimo console > > > Key: GERONIMO-1248 > URL: http://issues.apache.org/jira/browse/GERONIMO-1248 > Project: Geronimo > Type: Bug > Versions: 1.0-M5 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Assignee: Aaron Mulder > Fix For: 1.0 > > I have created a simple web application that uses a FORM authentication > method. In the deployment plan, I have configured the application to use > "geronimo-properties-realm". The application works fine. > At this point a added a new realm with name "onemore-properties-realm" > through the "Security Realms" portlet. I have modified the deployment plan > to use this newly added security realm and redeployed the application. The > security part of this application does not work anymore. I am getting the > following exception on login attempt. > 17:41:53,036 INFO [JAASJettyRealm] problem > javax.security.auth.login.LoginException: java.lang.NullPointerException: > target is null > at > org.apache.geronimo.kernel.basic.BasicProxyManager.createProxy(BasicProxyManager.java:104) > at > org.apache.geronimo.security.jaas.client.JaasLoginCoordinator.connect(JaasLoginCoordinator.java:173) > at > org.apache.geronimo.security.jaas.client.JaasLoginCoordinator.initialize(JaasLoginCoordinator.java:85) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at javax.security.auth.login.LoginContext.invoke(Unknown Source) > at javax.security.auth.login.LoginContext.access$000(Unknown Source) > at javax.security.auth.login.LoginContext$4.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.login.LoginContext.invokeModule(Unknown Source) > at javax.security.auth.login.LoginContext.login(Unknown Source) > at > org.apache.geronimo.jetty.JAASJettyRealm.authenticate(JAASJettyRealm.java:92) > at > org.mortbay.jetty.servlet.FormAuthenticator$FormCredential.authenticate(FormAuthenticator.java:305) > at > org.mortbay.jetty.servlet.FormAuthenticator.authenticate(FormAuthenticator.java:148) > at > org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.obtainUser(SecurityContextBeforeAfter.java:282) > at > org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.checkSecurityConstraints(SecurityContextBeforeAfter.java:191) > at > org.apache.geronimo.jetty.JettyWebAppContext.checkSecurityConstraints(JettyWebAppContext.java:520) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:432) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) > at org.mortbay.http.HttpServer.service(HttpServer.java:954) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) > at javax.security.auth.login.LoginContext.invoke(Unknown Source) > at javax.security.auth.login.LoginContext.access$000(Unknown Source) > at javax.security.auth.login.LoginContext$4.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.login.LoginContext.invokeModule(Unknown Source) > at javax.security.auth.login.LoginContext.login(Unknown Source) > at > org.apache.geronimo.jetty.JAASJettyRealm.authenticate(JAASJettyRealm.java:92) > at > org.mortbay.jetty.servlet.FormAuthenticator$FormCredential.authenticate(FormAuthenticator.java:305) > at > org.mortbay.jetty.servlet.FormAuthenticator.authenticate(FormAuthenticator.java:148) > at > org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.obtainUser(SecurityContextBeforeAfter.java:282) > at > org.apache.geronimo.jetty.interceptor.SecurityContextBeforeAfter.checkSecurityConstraints(SecurityContextBeforeAfter.java:191) > at > org.apache.geronimo.jetty.JettyWebAppContext.checkSec
[jira] Assigned: (GERONIMO-1192) Installer should create a config.xml for the target install
[ http://issues.apache.org/jira/browse/GERONIMO-1192?page=all ] David Jencks reassigned GERONIMO-1192: -- Assign To: David Jencks > Installer should create a config.xml for the target install > --- > > Key: GERONIMO-1192 > URL: http://issues.apache.org/jira/browse/GERONIMO-1192 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Installer runtime > Reporter: erik daughtrey > Assignee: David Jencks > Attachments: installer_1192_200512080036.patch > > DJ - "This could be done by adding bits associated with each configuration, > or by removing chunks from a 'universal' config.xml for the configuations we > didn't install." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1251) Unable to add a new realm thru "Security Realms" portlet
[ http://issues.apache.org/jira/browse/GERONIMO-1251?page=all ] Vamsavardhana Reddy closed GERONIMO-1251: - > Unable to add a new realm thru "Security Realms" portlet > > > Key: GERONIMO-1251 > URL: http://issues.apache.org/jira/browse/GERONIMO-1251 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Assignee: Aaron Mulder > Fix For: 1.0 > > Adding a new security realm thru "Security Realms" portlet results in an > error. Clicking on "show plan" button shows a plan that uses > "org/apache/geronimo/Server" as parentId. > Following exception is logged to geronimo.log > 19:05:44,984 DEBUG [Deployer] Deployment failed: > plan=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\console-deployment53507.xml, > module=null > org.apache.geronimo.common.DeploymentException: Unable to load first parent > of configuration SecurityRealmonemore-properties-realm > at > org.apache.geronimo.deployment.DeploymentContext.determineNaming(DeploymentContext.java:145) > at > org.apache.geronimo.deployment.DeploymentContext.(DeploymentContext.java:111) > at > org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:199) > at > org.apache.geronimo.deployment.service.ServiceConfigBuilder.buildConfiguration(ServiceConfigBuilder.java:167) > at > org.apache.geronimo.deployment.service.ServiceConfigBuilder$$FastClassByCGLIB$$9f173be6.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.deployment.ConfigurationBuilder$$EnhancerByCGLIB$$124a682d.buildConfiguration() > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:178) > at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:85) > at > org.apache.geronimo.deployment.Deployer$$FastClassByCGLIB$$734a235d.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:835) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:180) > at > org.apache.geronimo.deployment.plugin.local.AbstractDeployCommand.doDeploy(AbstractDeployCommand.java:103) > at > org.apache.geronimo.deployment.plugin.local.DistributeCommand.run(DistributeCommand.java:62) > at java.lang.Thread.run(Unknown Source) > Caused by: org.apache.geronimo.kernel.config.NoSuchConfigException: No > configuration with id: org/apache/geronimo/Server > at > org.apache.geronimo.kernel.config.ConfigurationManagerImpl.load(ConfigurationManagerImpl.java:116) > at > org.apache.geronimo.kernel.config.ConfigurationManagerImpl$$FastClassByCGLIB$$fbed85d2.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:118) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:800) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:36) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.kernel.config.ConfigurationManager$$EnhancerByCGLIB$$f1362611.load() > at > org.apache.geronimo.deployment.DeploymentContext.determineNaming(DeploymentContext.java:129) > ... 23 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1307) JMX connector doesn't shut down cleanly
[ http://issues.apache.org/jira/browse/GERONIMO-1307?page=all ] Dain Sundstrom reassigned GERONIMO-1307: Assign To: Matt Hogstrom > JMX connector doesn't shut down cleanly > --- > > Key: GERONIMO-1307 > URL: http://issues.apache.org/jira/browse/GERONIMO-1307 > Project: Geronimo > Type: Bug > Components: mail, deployment, management, general, OpenEJB, security, > kernel, naming, installer, eclipse-plugin, JVM-compatibility, sample apps, > gbuild > Versions: 1.0 > Reporter: David Jencks > Assignee: Matt Hogstrom > Priority: Blocker > Fix For: 1.0 > > In the last day or two this stack trace has shown up on server shutdown: > 10:58:04,204 ERROR [GBeanInstance] Problem in doStop of > geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-security/1.0-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService > java.io.IOException: javax.naming.CommunicationException [Root exception is > java.rmi.NoSuchObjectException: no such object in table] > at mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279) > at > javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:172) > at > org.apache.geronimo.jmxremoting.JMXConnector.doStop(JMXConnector.java:127) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1079) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:395) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:200) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:192) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:192) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) > at > org.apache.geronimo.kernel.config.ConfigurationManagerImpl$ShutdownHook.run(ConfigurationManagerImpl.java:277) > at > org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:406) > at > org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:383) > at org.apache.geronimo.system.main.Daemon$1.run(Daemon.java:272) > I think it appeared about the time Aaron changed the URI format for the jmx > deployer connection, but they might or might not be connected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1207) Dependency / Lifecycle Woes
[ http://issues.apache.org/jira/browse/GERONIMO-1207?page=comments#action_12359709 ] Dain Sundstrom commented on GERONIMO-1207: -- I doubt this can be fixed for 1.0. You basically have to write a new kernel to do this. > Dependency / Lifecycle Woes > --- > > Key: GERONIMO-1207 > URL: http://issues.apache.org/jira/browse/GERONIMO-1207 > Project: Geronimo > Type: Bug > Components: kernel, console > Versions: 1.0-M5 > Reporter: Aaron Mulder > Priority: Critical > Fix For: 1.0 > > 1) Create a database pool > 2) Create a SQL security realm with the database pool as a parent > 3) Verify that both are in the running state > 4) Stop the database pool > 5) Verify that both are in the stopped state > 6) Using the console "System Modules", start the security realm -- produces > all kinds of exceptions > 7) Now security realm is in the "starting" state, database pool is stopped > 8) Starting the database pool does not get the security realm out of the > "starting" state, though if you're bold with URL hacking you can start it > again and it will start. > I think that step 6 should either start both modules or leave both in the > stopped state. Being stuck in the "starting" state is terrible -- at least > if it won't automatically recover to the "running" state when the missing > dependencies come online. > Here's the stack traces from step 6. > javax.portlet.PortletException: Configuration not found > at > org.apache.geronimo.console.configmanager.ConfigManagerPortlet.processAction(ConfigManagerPortlet.java:131) > at > org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:229) > at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:158) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > at > org.apache.pluto.core.PortletServlet.service(PortletServlet.java:153) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) > at > org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) > at > org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:171) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at org.mortbay.jetty.servlet.Dispatcher.dispatch(Dispatcher.java:277) > at org.mortbay.jetty.servlet.Dispatcher.include(Dispatcher.java:163) > at > org.apache.pluto.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:120) > at > org.apache.pluto.invoker.impl.PortletInvokerImpl.action(PortletInvokerImpl.java:68) > at > org.apache.pluto.PortletContainerImpl.processPortletAction(PortletContainerImpl.java:164) > at > org.apache.pluto.portalImpl.core.PortletContainerWrapperImpl.processPortletAction(PortletContainerWrapperImpl.java:82) > at org.apache.pluto.portalImpl.Servlet.doGet(Servlet.java:227) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) > at > org.apache.geronimo.jetty.JettyServletHolder.handle(JettyServletHolder.java:99) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) > at > org.mortbay.jetty.servlet.JSR154Filter.doFilter(JSR154Filter.java:171) > at > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) > at > org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) > at > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) > at > org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) > at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) > at org.mortbay.http.HttpServer.service(HttpServer.java:954) > at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) > at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) > at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) > at > org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) > at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) > at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) >
Installer Status
The installer builds successfully under the new build process. The installer is built using the geronimo-izpack-plugin from assemblies/j2ee-installer. When the installer runs, it will create a runnable server, but the configuration is currently fixed to Jetty. I'm working to get the config.xml updated based on the configuration options selected and should complete the work tomorrow. Unfortunately, it's been a very long day and I won't make the midnight cutoff. There are two other additional pieces of work yet to do: 1. Inter-panel validation of conflicting configuration information i.e. conflicting ports 2. Selection of either Jetty or Tomcat, but not both -- Regards, Erik
[jira] Assigned: (GERONIMO-1292) Connector Portlet: List connectors in Web Server management page throws exception
[ http://issues.apache.org/jira/browse/GERONIMO-1292?page=all ] Vamsavardhana Reddy reassigned GERONIMO-1292: - Assign To: Aaron Mulder (was: Vamsavardhana Reddy) > Connector Portlet: List connectors in Web Server management page throws > exception > - > > Key: GERONIMO-1292 > URL: http://issues.apache.org/jira/browse/GERONIMO-1292 > Project: Geronimo > Type: Bug > Components: console > Versions: 1.0-M5 > Environment: Win XP, Sun JDK 1.4.2_08 > Reporter: Vamsavardhana Reddy > Assignee: Aaron Mulder > Priority: Minor > Fix For: 1.0 > Attachments: GERONIMO-1292.patch > > Listing the network listeners under web server management page throws the > following exception. > 17:02:19,037 ERROR [Servlet] Exception caught: > java.lang.NullPointerException: ObjectName 'name' parameter can't be null > at javax.management.ObjectName.(ObjectName.java:74) > at javax.management.ObjectName.getInstance(ObjectName.java:261) > at > org.apache.geronimo.console.util.KernelManagementHelper.getObject(KernelManagementHelper.java:898) > at > org.apache.geronimo.console.util.PortletManager.getWebContainer(PortletManager.java:258) > at > org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorPortlet.java:71) > ... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1310) Jetty startup noisy and corrupts the startup progress bar output
[ http://issues.apache.org/jira/browse/GERONIMO-1310?page=comments#action_12359707 ] John Sisson commented on GERONIMO-1310: --- Also shutdown seems to have same problem as Tomcat in GERONIMO-1309 > Jetty startup noisy and corrupts the startup progress bar output > > > Key: GERONIMO-1310 > URL: http://issues.apache.org/jira/browse/GERONIMO-1310 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability, web > Versions: 1.0 > Environment: Windows XP SP2 > svn revision 354983 > Reporter: John Sisson > Fix For: 1.0 > > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\bin>geronimo > run > Using GERONIMO_BASE: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT > Using GERONIMO_HOME: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT > Using GERONIMO_TMPDIR: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\var\temp > Using JRE_HOME:C:\j2sdk1.4.2_08 > Booting Geronimo Kernel (in Java 1.4.2_08)... > Starting Geronimo Application Server > [> ] 47% 18s Starting > geronimo/jetty/1.0-SNAPSHOT/car17:14:21,265 INFO [AJP13Listener] Started > AJP13Listener on 12 > 7.0.0.1:8019 > 17:14:21,265 INFO [AJP13Listener] NOTICE: AJP13 is not a secure protocol. > Please protect the port 127.0.0.1:8019 > [*>] 75% 20s Loading > geronimo/servlets-examples-j...17:14:23,421 INFO [/servlets-examples] > ContextListener: conte > xtInitialized() > 17:14:23,421 INFO [/servlets-examples] SessionListener: contextInitialized() > [**> ] 81% 21s Starting > geronimo/jsp-examples-jetty/...17:14:24,484 INFO [/jsp-examples] > ContextListener: contextIni > tialized() > 17:14:24,484 INFO [/jsp-examples] SessionListener: contextInitialized() > [**] 100% 25s Startup complete > Listening on Ports: > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 4201 0.0.0.0 ActiveIO Connector EJB > 4242 0.0.0.0 Remote Login Listener > 8019 127.0.0.1 Jetty Connector AJP13 > 8080 0.0.0.0 Jetty Connector HTTP > 8443 0.0.0.0 Jetty Connector HTTPS >61616 0.0.0.0 ActiveMQ Message Broker Connector > Started Application Modules: > EAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car > EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car > RAR: geronimo/activemq/1.0-SNAPSHOT/car > RAR: geronimo/system-database/1.0-SNAPSHOT/car > WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car > WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car > WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car > Web Applications: > http://JSLAP:8080/ > http://JSLAP:8080/console > http://JSLAP:8080/console-standard > http://JSLAP:8080/jsp-examples > http://JSLAP:8080/juddi > http://JSLAP:8080/servlets-examples > Geronimo Application Server started -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1309) Shutdown of tomcat configuration noisy and has GBeanInstanceState Errors
[
http://issues.apache.org/jira/browse/GERONIMO-1309?page=comments#action_12359705
]
David Jencks commented on GERONIMO-1309:
the problem with the tranql derby connector is already fixed in cvs.
the problem with the jmx service is already logged as GERONIMO-1307
the noise from tomcat has not yet been reported AFAIK.
> Shutdown of tomcat configuration noisy and has GBeanInstanceState Errors
>
>
> Key: GERONIMO-1309
> URL: http://issues.apache.org/jira/browse/GERONIMO-1309
> Project: Geronimo
> Type: Bug
> Components: Tomcat
> Versions: 1.0
> Environment: Windows XP SP2
> svn revision 354983
> Reporter: John Sisson
> Priority: Blocker
> Fix For: 1.0
>
> C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target>geronimo-1.0-SNAPSHOT\bin\geronimo
> run
> Using GERONIMO_BASE:
> C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT
> Using GERONIMO_HOME:
> C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT
> Using GERONIMO_TMPDIR:
> C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT\var\temp
> Using JRE_HOME:C:\j2sdk1.4.2_08
> Booting Geronimo Kernel (in Java 1.4.2_08)...
> Starting Geronimo Application Server
> [*>] 75% 25s Starting
> geronimo/servlets-examples-t...17:04:10,062 INFO [[/servlets-examples]]
> ContextListener: con
> textInitialized()
> 17:04:10,062 INFO [[/servlets-examples]] SessionListener:
> contextInitialized()
> [**> ] 81% 25s Starting
> geronimo/jsp-examples-tomcat...17:04:10,562 INFO [[/jsp-examples]]
> ContextListener: contextI
> nitialized()
> 17:04:10,562 INFO [[/jsp-examples]] SessionListener: contextInitialized()
> [**] 100% 28s Startup complete
> Listening on Ports:
> 1099 0.0.0.0 RMI Naming
> 1527 0.0.0.0 Derby Connector
> 4201 0.0.0.0 ActiveIO Connector EJB
> 4242 0.0.0.0 Remote Login Listener
> 8009 0.0.0.0 Tomcat Connector AJP
> 8080 0.0.0.0 Tomcat Connector HTTP
> 8443 0.0.0.0 Tomcat Connector HTTPS
>61616 0.0.0.0 ActiveMQ Message Broker Connector
> Started Application Modules:
> EAR: geronimo/uddi-tomcat/1.0-SNAPSHOT/car
> EAR: geronimo/webconsole-tomcat/1.0-SNAPSHOT/car
> RAR: geronimo/activemq/1.0-SNAPSHOT/car
> RAR: geronimo/system-database/1.0-SNAPSHOT/car
> WAR: geronimo/jsp-examples-tomcat/1.0-SNAPSHOT/car
> WAR: geronimo/servlets-examples-tomcat/1.0-SNAPSHOT/car
> WAR: geronimo/welcome-tomcat/1.0-SNAPSHOT/car
> Web Applications:
> http://JSLAP:8080/
> http://JSLAP:8080/console
> http://JSLAP:8080/console-standard
> http://JSLAP:8080/jsp-examples
> http://JSLAP:8080/juddi
> http://JSLAP:8080/servlets-examples
> Geronimo Application Server started
> Server shutdown begun
> 17:05:09,234 INFO [[/servlets-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
> g;@12ad974')
> 17:05:09,234 INFO [[/servlets-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
> g;@2a7640')
> 17:05:09,265 INFO [[/servlets-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
> g;@1b9808e')
> 17:05:09,265 INFO [[/servlets-examples]] SessionListener: contextDestroyed()
> 17:05:09,281 INFO [[/servlets-examples]] ContextListener: contextDestroyed()
> 17:05:09,328 INFO [[/jsp-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@15
> 49f0e')
> 17:05:09,328 INFO [[/jsp-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@96
> 52dd')
> 17:05:09,328 INFO [[/jsp-examples]] ContextListener:
> attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@11
> a67fe')
> 17:05:09,343 INFO [[/jsp-examples]] SessionListener: contextDestroyed()
> 17:05:09,343 INFO [[/jsp-examples]] ContextListener: contextDestroyed()
> 17:05:10,281 ERROR [GBeanInstanceState] Error while stopping; GBean is now in
> the FAILED state: objectName="geronimo.server:J2EEAppl
> ication=geronimo/uddi-tomcat/1.0-SNAPSHOT/car,J2EEServer=geronimo,JCAResource=uddi-db,j2eeType=JCAManagedConnectionFactory,name=jdbc
> /juddiDB"
> java.lang.Exception: Problem while updaing the persistent value of attibute:
> Attribute Name: ShutdownDatabase, Type: class java.lang
> .String, GBeanInstance:
> org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper
> at
> org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1048)
> at
> org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:395)
> at
> org.apac
[jira] Updated: (GERONIMO-1250) Console Realm Create new user results in error and gives confusing error message.
[ http://issues.apache.org/jira/browse/GERONIMO-1250?page=all ] Vamsavardhana Reddy updated GERONIMO-1250: -- Summary: Console Realm Create new user results in error and gives confusing error message. (was: Console Realm Create new user gives confusing error message.) type: Bug (was: Improvement) Fix Version: 1.0 Even though the JIRA issue is created pointing to the inconsistent error message, the problem actually is a side effect of "unable to add new user". I think this issue should be fixed in 1.0 since it affects the very basic functionality of adding users to the console realm. > Console Realm Create new user results in error and gives confusing error > message. > - > > Key: GERONIMO-1250 > URL: http://issues.apache.org/jira/browse/GERONIMO-1250 > Project: Geronimo > Type: Bug > Components: console > Environment: All > Reporter: Rick McGuire > Assignee: Vamsavardhana Reddy > Priority: Minor > Fix For: 1.0 > Attachments: GERONIMO-1250-fixmessage.patch, GERONIMO-1250.patch > > The default "out-of-the-box" configuration uses the PropertiesLoginModule, > which doesn't support adding additional userids and groups. However, the > Console Realm portlet supports Create New User and Create New Group as > options. If you try to create either a new group or user, you get an error > that the "ERROR: User already exists". The user does not already exist, so > the error doesn't really make sense. This operation is failing because the > PropertiesLoginModuleManager is throwing an exception because it doesn't > support updates, not because this is a duplicate name. The portlet is just > catching all exceptions and reporting this as a duplicate name error. It > would be nice to make this a little more granular. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1310) Jetty startup noisy and corrupts the startup progress bar output
[ http://issues.apache.org/jira/browse/GERONIMO-1310?page=all ] John Sisson updated GERONIMO-1310: -- Component: web > Jetty startup noisy and corrupts the startup progress bar output > > > Key: GERONIMO-1310 > URL: http://issues.apache.org/jira/browse/GERONIMO-1310 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability, web > Versions: 1.0 > Environment: Windows XP SP2 > svn revision 354983 > Reporter: John Sisson > Fix For: 1.0 > > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\bin>geronimo > run > Using GERONIMO_BASE: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT > Using GERONIMO_HOME: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT > Using GERONIMO_TMPDIR: > C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\var\temp > Using JRE_HOME:C:\j2sdk1.4.2_08 > Booting Geronimo Kernel (in Java 1.4.2_08)... > Starting Geronimo Application Server > [> ] 47% 18s Starting > geronimo/jetty/1.0-SNAPSHOT/car17:14:21,265 INFO [AJP13Listener] Started > AJP13Listener on 12 > 7.0.0.1:8019 > 17:14:21,265 INFO [AJP13Listener] NOTICE: AJP13 is not a secure protocol. > Please protect the port 127.0.0.1:8019 > [*>] 75% 20s Loading > geronimo/servlets-examples-j...17:14:23,421 INFO [/servlets-examples] > ContextListener: conte > xtInitialized() > 17:14:23,421 INFO [/servlets-examples] SessionListener: contextInitialized() > [**> ] 81% 21s Starting > geronimo/jsp-examples-jetty/...17:14:24,484 INFO [/jsp-examples] > ContextListener: contextIni > tialized() > 17:14:24,484 INFO [/jsp-examples] SessionListener: contextInitialized() > [**] 100% 25s Startup complete > Listening on Ports: > 1099 0.0.0.0 RMI Naming > 1527 0.0.0.0 Derby Connector > 4201 0.0.0.0 ActiveIO Connector EJB > 4242 0.0.0.0 Remote Login Listener > 8019 127.0.0.1 Jetty Connector AJP13 > 8080 0.0.0.0 Jetty Connector HTTP > 8443 0.0.0.0 Jetty Connector HTTPS >61616 0.0.0.0 ActiveMQ Message Broker Connector > Started Application Modules: > EAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car > EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car > RAR: geronimo/activemq/1.0-SNAPSHOT/car > RAR: geronimo/system-database/1.0-SNAPSHOT/car > WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car > WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car > WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car > Web Applications: > http://JSLAP:8080/ > http://JSLAP:8080/console > http://JSLAP:8080/console-standard > http://JSLAP:8080/jsp-examples > http://JSLAP:8080/juddi > http://JSLAP:8080/servlets-examples > Geronimo Application Server started -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1310) Jetty startup noisy and corrupts the startup progress bar output
Jetty startup noisy and corrupts the startup progress bar output Key: GERONIMO-1310 URL: http://issues.apache.org/jira/browse/GERONIMO-1310 Project: Geronimo Type: Bug Components: startup/shutdown, usability Versions: 1.0 Environment: Windows XP SP2 svn revision 354983 Reporter: John Sisson Fix For: 1.0 C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\bin>geronimo run Using GERONIMO_BASE: C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT Using GERONIMO_HOME: C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT Using GERONIMO_TMPDIR: C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-jetty-server\target\geronimo-1.0-SNAPSHOT\var\temp Using JRE_HOME:C:\j2sdk1.4.2_08 Booting Geronimo Kernel (in Java 1.4.2_08)... Starting Geronimo Application Server [> ] 47% 18s Starting geronimo/jetty/1.0-SNAPSHOT/car17:14:21,265 INFO [AJP13Listener] Started AJP13Listener on 12 7.0.0.1:8019 17:14:21,265 INFO [AJP13Listener] NOTICE: AJP13 is not a secure protocol. Please protect the port 127.0.0.1:8019 [*>] 75% 20s Loading geronimo/servlets-examples-j...17:14:23,421 INFO [/servlets-examples] ContextListener: conte xtInitialized() 17:14:23,421 INFO [/servlets-examples] SessionListener: contextInitialized() [**> ] 81% 21s Starting geronimo/jsp-examples-jetty/...17:14:24,484 INFO [/jsp-examples] ContextListener: contextIni tialized() 17:14:24,484 INFO [/jsp-examples] SessionListener: contextInitialized() [**] 100% 25s Startup complete Listening on Ports: 1099 0.0.0.0 RMI Naming 1527 0.0.0.0 Derby Connector 4201 0.0.0.0 ActiveIO Connector EJB 4242 0.0.0.0 Remote Login Listener 8019 127.0.0.1 Jetty Connector AJP13 8080 0.0.0.0 Jetty Connector HTTP 8443 0.0.0.0 Jetty Connector HTTPS 61616 0.0.0.0 ActiveMQ Message Broker Connector Started Application Modules: EAR: geronimo/uddi-jetty/1.0-SNAPSHOT/car EAR: geronimo/webconsole-jetty/1.0-SNAPSHOT/car RAR: geronimo/activemq/1.0-SNAPSHOT/car RAR: geronimo/system-database/1.0-SNAPSHOT/car WAR: geronimo/jsp-examples-jetty/1.0-SNAPSHOT/car WAR: geronimo/servlets-examples-jetty/1.0-SNAPSHOT/car WAR: geronimo/welcome-jetty/1.0-SNAPSHOT/car Web Applications: http://JSLAP:8080/ http://JSLAP:8080/console http://JSLAP:8080/console-standard http://JSLAP:8080/jsp-examples http://JSLAP:8080/juddi http://JSLAP:8080/servlets-examples Geronimo Application Server started -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-1309) Shutdown of tomcat configuration noisy and has GBeanInstanceState Errors
Shutdown of tomcat configuration noisy and has GBeanInstanceState Errors
Key: GERONIMO-1309
URL: http://issues.apache.org/jira/browse/GERONIMO-1309
Project: Geronimo
Type: Bug
Components: Tomcat
Versions: 1.0
Environment: Windows XP SP2
svn revision 354983
Reporter: John Sisson
Priority: Blocker
Fix For: 1.0
C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target>geronimo-1.0-SNAPSHOT\bin\geronimo
run
Using GERONIMO_BASE:
C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT
Using GERONIMO_HOME:
C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT
Using GERONIMO_TMPDIR:
C:\OpenSourceJava\geronimo\trunk\assemblies\j2ee-tomcat-server\target\geronimo-1.0-SNAPSHOT\var\temp
Using JRE_HOME:C:\j2sdk1.4.2_08
Booting Geronimo Kernel (in Java 1.4.2_08)...
Starting Geronimo Application Server
[*>] 75% 25s Starting
geronimo/servlets-examples-t...17:04:10,062 INFO [[/servlets-examples]]
ContextListener: con
textInitialized()
17:04:10,062 INFO [[/servlets-examples]] SessionListener: contextInitialized()
[**> ] 81% 25s Starting
geronimo/jsp-examples-tomcat...17:04:10,562 INFO [[/jsp-examples]]
ContextListener: contextI
nitialized()
17:04:10,562 INFO [[/jsp-examples]] SessionListener: contextInitialized()
[**] 100% 28s Startup complete
Listening on Ports:
1099 0.0.0.0 RMI Naming
1527 0.0.0.0 Derby Connector
4201 0.0.0.0 ActiveIO Connector EJB
4242 0.0.0.0 Remote Login Listener
8009 0.0.0.0 Tomcat Connector AJP
8080 0.0.0.0 Tomcat Connector HTTP
8443 0.0.0.0 Tomcat Connector HTTPS
61616 0.0.0.0 ActiveMQ Message Broker Connector
Started Application Modules:
EAR: geronimo/uddi-tomcat/1.0-SNAPSHOT/car
EAR: geronimo/webconsole-tomcat/1.0-SNAPSHOT/car
RAR: geronimo/activemq/1.0-SNAPSHOT/car
RAR: geronimo/system-database/1.0-SNAPSHOT/car
WAR: geronimo/jsp-examples-tomcat/1.0-SNAPSHOT/car
WAR: geronimo/servlets-examples-tomcat/1.0-SNAPSHOT/car
WAR: geronimo/welcome-tomcat/1.0-SNAPSHOT/car
Web Applications:
http://JSLAP:8080/
http://JSLAP:8080/console
http://JSLAP:8080/console-standard
http://JSLAP:8080/jsp-examples
http://JSLAP:8080/juddi
http://JSLAP:8080/servlets-examples
Geronimo Application Server started
Server shutdown begun
17:05:09,234 INFO [[/servlets-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
g;@12ad974')
17:05:09,234 INFO [[/servlets-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
g;@2a7640')
17:05:09,265 INFO [[/servlets-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.Strin
g;@1b9808e')
17:05:09,265 INFO [[/servlets-examples]] SessionListener: contextDestroyed()
17:05:09,281 INFO [[/servlets-examples]] ContextListener: contextDestroyed()
17:05:09,328 INFO [[/jsp-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@15
49f0e')
17:05:09,328 INFO [[/jsp-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@96
52dd')
17:05:09,328 INFO [[/jsp-examples]] ContextListener:
attributeReplaced('org.apache.catalina.WELCOME_FILES', '[Ljava.lang.String;@11
a67fe')
17:05:09,343 INFO [[/jsp-examples]] SessionListener: contextDestroyed()
17:05:09,343 INFO [[/jsp-examples]] ContextListener: contextDestroyed()
17:05:10,281 ERROR [GBeanInstanceState] Error while stopping; GBean is now in
the FAILED state: objectName="geronimo.server:J2EEAppl
ication=geronimo/uddi-tomcat/1.0-SNAPSHOT/car,J2EEServer=geronimo,JCAResource=uddi-db,j2eeType=JCAManagedConnectionFactory,name=jdbc
/juddiDB"
java.lang.Exception: Problem while updaing the persistent value of attibute:
Attribute Name: ShutdownDatabase, Type: class java.lang
.String, GBeanInstance:
org.apache.geronimo.connector.outbound.ManagedConnectionFactoryWrapper
at
org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1048)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:395)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:200)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213)
at
org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:192)
at
org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545)
at
org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213)
at
org.apache.ger
[jira] Updated: (GERONIMO-1192) Installer should create a config.xml for the target install
[ http://issues.apache.org/jira/browse/GERONIMO-1192?page=all ] erik daughtrey updated GERONIMO-1192: - Attachment: installer_1192_200512080036.patch First patch of a few. This begins to address a combined config.xml, but does not allow configuration yet. This patch includes some small additional fixes. > Installer should create a config.xml for the target install > --- > > Key: GERONIMO-1192 > URL: http://issues.apache.org/jira/browse/GERONIMO-1192 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Installer runtime > Reporter: erik daughtrey > Attachments: installer_1192_200512080036.patch > > DJ - "This could be done by adding bits associated with each configuration, > or by removing chunks from a 'universal' config.xml for the configuations we > didn't install." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1289) Include a config.xml.original file in the var/config directory in the distribution
[ http://issues.apache.org/jira/browse/GERONIMO-1289?page=all ] John Sisson closed GERONIMO-1289: - > Include a config.xml.original file in the var/config directory in the > distribution > -- > > Key: GERONIMO-1289 > URL: http://issues.apache.org/jira/browse/GERONIMO-1289 > Project: Geronimo > Type: Improvement > Versions: 1.0-M5, 1.0 > Reporter: John Sisson > Priority: Minor > Fix For: 1.0 > > Dain's suggestion from the "files in var/config directory" mail thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1289) Include a config.xml.original file in the var/config directory in the distribution
[ http://issues.apache.org/jira/browse/GERONIMO-1289?page=all ] John Sisson resolved GERONIMO-1289: --- Resolution: Fixed Committed by djencks: http://svn.apache.org/viewcvs?rev=354953&view=rev > Include a config.xml.original file in the var/config directory in the > distribution > -- > > Key: GERONIMO-1289 > URL: http://issues.apache.org/jira/browse/GERONIMO-1289 > Project: Geronimo > Type: Improvement > Versions: 1.0-M5, 1.0 > Reporter: John Sisson > Priority: Minor > Fix For: 1.0 > > Dain's suggestion from the "files in var/config directory" mail thread. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GBUILD-5) GZip large files sent in build task and results maps
[ http://issues.apache.org/jira/browse/GBUILD-5?page=all ] David Blevins closed GBUILD-5: -- Resolution: Fixed Assign To: David Blevins > GZip large files sent in build task and results maps > > > Key: GBUILD-5 > URL: http://issues.apache.org/jira/browse/GBUILD-5 > Project: GBuild > Type: Improvement > Components: agent > Reporter: David Blevins > Assignee: David Blevins > > The build output file is rather large. It should be gzipped then sent, and > deflated by the receiver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GBUILD-5) GZip large files sent in build task and results maps
GZip large files sent in build task and results maps Key: GBUILD-5 URL: http://issues.apache.org/jira/browse/GBUILD-5 Project: GBuild Type: Improvement Components: agent Reporter: David Blevins The build output file is rather large. It should be gzipped then sent, and deflated by the receiver. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Commented: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
No reason that I know of. Do you want to update the configs? -dain On Dec 7, 2005, at 7:17 PM, David Jencks wrote: Is there some important reason this gbean has a nonstandard name? Can we change it to a standard jsr77 style name??? thanks david jencks On Dec 7, 2005, at 6:59 PM, Jeremy Whitlock (JIRA) wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1151? page=comments#action_12359683 ] Jeremy Whitlock commented on GERONIMO-1151: --- While working on this, Dain found the issue and it is actually a config.xml issue. The file should look like so: 0.0.0.0 4201 I tested it with: 0.0.0.0 14201 and it started properly and the port was properly retained from the config.xml. Look forward to the commit from Dain to remedy this issue. Thanks Dain. Take care, Jeremy Changing EJB port from 4201 to another value in config.xml does not take effect --- Key: GERONIMO-1151 URL: http://issues.apache.org/jira/browse/GERONIMO-1151 Project: Geronimo Type: Bug Components: OpenEJB, startup/shutdown Versions: 1.0 Reporter: John Sisson Assignee: Jeremy Whitlock Priority: Blocker Fix For: 1.0 If the EJB port is changed in the geronimo/var/config/config.xml file, it does not take effect. For example, change 0.0.0.0 4201 to: 0.0.0.0 14201 At startup, you see.. Listening on Ports: 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1308) Continued build problems with "new" Maven goals
[ http://issues.apache.org/jira/browse/GERONIMO-1308?page=all ]
David Jencks closed GERONIMO-1308:
--
Fix Version: 1.0
Resolution: Fixed
Thanks!
Sendingassemblies/j2ee-installer/project.xml
Sendingconfigs/geronimo-gbean-deployer/project.xml
Transmitting file data ..
Committed revision 354965.
> Continued build problems with "new" Maven goals
> ---
>
> Key: GERONIMO-1308
> URL: http://issues.apache.org/jira/browse/GERONIMO-1308
> Project: Geronimo
> Type: Bug
> Components: buildsystem
> Versions: 1.0
> Environment: Clean extract and clean Repo on WinXP with Maven 1.1Beta2
> Reporter: Donald Woods
> Assignee: David Jencks
> Priority: Blocker
> Fix For: 1.0
> Attachments: Geronimo-1308.patch
>
> Continued build problems as noted in email trials -
>Re: [M1] Plugin hell, help desperately needed
>Re: A successful build
> Suggested maven m:clean new, never worked for me on a clean WinXP system.
> Fix for new4 goal, was to re-enable the following dependency -
>
> geronimo
> geronimo-packaging-plugin
> ${geronimo_version}
> plugin
>
> Fix for new5 goal, was to insert the following new dependency -
>
> geronimo
> geronimo-izpack-plugin
> plugin
> ${pom.currentVersion}
>
> Will attach the patch files for the above in a few minutes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1308) Continued build problems with "new" Maven goals
[ http://issues.apache.org/jira/browse/GERONIMO-1308?page=all ]
David Jencks reassigned GERONIMO-1308:
--
Assign To: David Jencks (was: Donald Woods)
> Continued build problems with "new" Maven goals
> ---
>
> Key: GERONIMO-1308
> URL: http://issues.apache.org/jira/browse/GERONIMO-1308
> Project: Geronimo
> Type: Bug
> Components: buildsystem
> Versions: 1.0
> Environment: Clean extract and clean Repo on WinXP with Maven 1.1Beta2
> Reporter: Donald Woods
> Assignee: David Jencks
> Priority: Blocker
> Attachments: Geronimo-1308.patch
>
> Continued build problems as noted in email trials -
>Re: [M1] Plugin hell, help desperately needed
>Re: A successful build
> Suggested maven m:clean new, never worked for me on a clean WinXP system.
> Fix for new4 goal, was to re-enable the following dependency -
>
> geronimo
> geronimo-packaging-plugin
> ${geronimo_version}
> plugin
>
> Fix for new5 goal, was to insert the following new dependency -
>
> geronimo
> geronimo-izpack-plugin
> plugin
> ${pom.currentVersion}
>
> Will attach the patch files for the above in a few minutes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: Geronimo Web Design - New Versions Updated From Feedback
Excellent work. I like #1, with the News Archive link/button from #2/#3. -Donald Epiq Geronimo Team wrote: Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team smime.p7s Description: S/MIME Cryptographic Signature
[jira] Updated: (GERONIMO-1308) Continued build problems with "new" Maven goals
[ http://issues.apache.org/jira/browse/GERONIMO-1308?page=all ]
Donald Woods updated GERONIMO-1308:
---
Geronimo Info: [Patch Available]
> Continued build problems with "new" Maven goals
> ---
>
> Key: GERONIMO-1308
> URL: http://issues.apache.org/jira/browse/GERONIMO-1308
> Project: Geronimo
> Type: Bug
> Components: buildsystem
> Versions: 1.0
> Environment: Clean extract and clean Repo on WinXP with Maven 1.1Beta2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Blocker
> Attachments: Geronimo-1308.patch
>
> Continued build problems as noted in email trials -
>Re: [M1] Plugin hell, help desperately needed
>Re: A successful build
> Suggested maven m:clean new, never worked for me on a clean WinXP system.
> Fix for new4 goal, was to re-enable the following dependency -
>
> geronimo
> geronimo-packaging-plugin
> ${geronimo_version}
> plugin
>
> Fix for new5 goal, was to insert the following new dependency -
>
> geronimo
> geronimo-izpack-plugin
> plugin
> ${pom.currentVersion}
>
> Will attach the patch files for the above in a few minutes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1308) Continued build problems with "new" Maven goals
[ http://issues.apache.org/jira/browse/GERONIMO-1308?page=all ]
Donald Woods updated GERONIMO-1308:
---
Attachment: Geronimo-1308.patch
Attaching patch file for
assemblies/j2ee-installer/project.xml
configs/geronimo-gbean-deployer/project.xml
> Continued build problems with "new" Maven goals
> ---
>
> Key: GERONIMO-1308
> URL: http://issues.apache.org/jira/browse/GERONIMO-1308
> Project: Geronimo
> Type: Bug
> Components: buildsystem
> Versions: 1.0
> Environment: Clean extract and clean Repo on WinXP with Maven 1.1Beta2
> Reporter: Donald Woods
> Assignee: Donald Woods
> Priority: Blocker
> Attachments: Geronimo-1308.patch
>
> Continued build problems as noted in email trials -
>Re: [M1] Plugin hell, help desperately needed
>Re: A successful build
> Suggested maven m:clean new, never worked for me on a clean WinXP system.
> Fix for new4 goal, was to re-enable the following dependency -
>
> geronimo
> geronimo-packaging-plugin
> ${geronimo_version}
> plugin
>
> Fix for new5 goal, was to insert the following new dependency -
>
> geronimo
> geronimo-izpack-plugin
> plugin
> ${pom.currentVersion}
>
> Will attach the patch files for the above in a few minutes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: [M1] Plugin hell, help desperately needed - JIRA 1308 created
JIRA-1308 has been opened for this and I am creating the patch files to
attach right now.
configs/geronimo-gbean-deployer/project.xml - uncomment the following
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
assemblies/j2ee-installer/project.xml - insert the following new dependency
geronimo
geronimo-izpack-plugin
plugin
${pom.currentVersion}
-Donald
Bill Stoddard wrote:
Donald Woods wrote:
Finally got new4 goal to complete using Maven 1.1Beta2 (was always
failing with the same error you mention below), by editing
configs/geronimo-gbean-deployer/project.xml and removing the comments
from around the geronimo-packaging-plugin dependency to re-enable it
as a depend -
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
I'm running a full build now via
maven m:clean new -Dmaven.test.skip=true -Dmaven.itest.skip=true
to verify the change works repeatably before I open a JIRA and attach
the patch.
-Donald
Thanks Donald, that change got me over the failure (and I'm using maven
1.0.2). I manually placed geronimo-packaging-plugin into the
.maven/cache. Ran into another failure to statisfy a dependency on
tranql-connector-derby-embed-local-1.1-SNAPSHOT.rar but that's probably
because I was doing an offline build.
It was a bit tricky mapping this message:
[echo] Running car:install for Geronimo Configuration for performing
service deployments
to
geronimo-gbean-deployer/project.xml
I made the connection (thank you findstr/grep) but failed to investigate
the dependencies in project.xml. Won't make that mistake again ;-)
Will clean out .maven/cache and kick off a 'maven clean new' build this
evening and report back the results.
Bill
smime.p7s
Description: S/MIME Cryptographic Signature
[jira] Created: (GERONIMO-1308) Continued build problems with "new" Maven goals
Continued build problems with "new" Maven goals
---
Key: GERONIMO-1308
URL: http://issues.apache.org/jira/browse/GERONIMO-1308
Project: Geronimo
Type: Bug
Components: buildsystem
Versions: 1.0
Environment: Clean extract and clean Repo on WinXP with Maven 1.1Beta2
Reporter: Donald Woods
Assigned to: Donald Woods
Priority: Blocker
Continued build problems as noted in email trials -
Re: [M1] Plugin hell, help desperately needed
Re: A successful build
Suggested maven m:clean new, never worked for me on a clean WinXP system.
Fix for new4 goal, was to re-enable the following dependency -
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
Fix for new5 goal, was to insert the following new dependency -
geronimo
geronimo-izpack-plugin
plugin
${pom.currentVersion}
Will attach the patch files for the above in a few minutes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
Re: Geronimo Web Design - New Versions Updated From Feedback
Yes, this requires some thought. I made a start at a proposal in my first response, but I certainly don't claim to know the best organization here. http://www.mail-archive.com/dev%40geronimo.apache.org/msg13619.html I usually don't like to see what appears to me as a random groupings of items or a lot of duplicate links on a page. But that's just me and I can see where it might be helpful to have the same item duplicated in several places so that different users can find them where they may expect them to be. It would be good to get some ideas from the home pages of other open source projects and from folks with a lot more experience than I concerning what a user/developer/etc... would find important for an open source project so that we could put the common items in the most obvious places and tucked away whatever isn't as common to simplify the view (but still be able to locate it without too much searching). Then again as Erin pointed out, it might be more important to just get something that looks reasonable out as quickly as possible for V1 and then enhance it as we learn more. Joe Epiq Geronimo Team wrote: Joe, You mentioned the navigation - that is an area that we could use a little bit of assistance on. I think the key areas that we could use some help on would be what are the primary navigation links (ie what should go into the tabs) and the navigation links on the left as these will be consistent thoughout the site. The area on the right can be used for featured information. Does anyone have ideas about what should appear on these areas? Epiq Team Joe Bohn wrote: #1 is the style that I like the best. Looks really good! We just need to decide on the content in the various locations/tabs. Joe Epiq Geronimo Team wrote: Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot
Re: [jira] Commented: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
Is there some important reason this gbean has a nonstandard name? Can we change it to a standard jsr77 style name??? thanks david jencks On Dec 7, 2005, at 6:59 PM, Jeremy Whitlock (JIRA) wrote: [ http://issues.apache.org/jira/browse/GERONIMO-1151? page=comments#action_12359683 ] Jeremy Whitlock commented on GERONIMO-1151: --- While working on this, Dain found the issue and it is actually a config.xml issue. The file should look like so: 0.0.0.0 4201 I tested it with: 0.0.0.0 14201 and it started properly and the port was properly retained from the config.xml. Look forward to the commit from Dain to remedy this issue. Thanks Dain. Take care, Jeremy Changing EJB port from 4201 to another value in config.xml does not take effect -- - Key: GERONIMO-1151 URL: http://issues.apache.org/jira/browse/GERONIMO-1151 Project: Geronimo Type: Bug Components: OpenEJB, startup/shutdown Versions: 1.0 Reporter: John Sisson Assignee: Jeremy Whitlock Priority: Blocker Fix For: 1.0 If the EJB port is changed in the geronimo/var/config/config.xml file, it does not take effect. For example, change 0.0.0.0 4201 to: 0.0.0.0 14201 At startup, you see.. Listening on Ports: 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
[ http://issues.apache.org/jira/browse/GERONIMO-1151?page=all ] Dain Sundstrom closed GERONIMO-1151: Resolution: Fixed Sendingtrunk/assemblies/j2ee-installer/src/var/config/config.xml Sendingtrunk/assemblies/j2ee-jetty-server/src/var/config/config.xml Sendingtrunk/assemblies/j2ee-tomcat-server/src/var/config/config.xml Transmitting file data ... Committed revision 354952. > Changing EJB port from 4201 to another value in config.xml does not take > effect > --- > > Key: GERONIMO-1151 > URL: http://issues.apache.org/jira/browse/GERONIMO-1151 > Project: Geronimo > Type: Bug > Components: OpenEJB, startup/shutdown > Versions: 1.0 > Reporter: John Sisson > Assignee: Jeremy Whitlock > Priority: Blocker > Fix For: 1.0 > > If the EJB port is changed in the geronimo/var/config/config.xml file, it > does not take effect. > For example, change > > > 0.0.0.0 > 4201 > > > to: > > > 0.0.0.0 > 14201 > > > At startup, you see.. > Listening on Ports: > 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
[ http://issues.apache.org/jira/browse/GERONIMO-1151?page=comments#action_12359684 ] David Blevins commented on GERONIMO-1151: - Make sure that when we create app clients we have them point to the right port. > Changing EJB port from 4201 to another value in config.xml does not take > effect > --- > > Key: GERONIMO-1151 > URL: http://issues.apache.org/jira/browse/GERONIMO-1151 > Project: Geronimo > Type: Bug > Components: OpenEJB, startup/shutdown > Versions: 1.0 > Reporter: John Sisson > Assignee: Jeremy Whitlock > Priority: Blocker > Fix For: 1.0 > > If the EJB port is changed in the geronimo/var/config/config.xml file, it > does not take effect. > For example, change > > > 0.0.0.0 > 4201 > > > to: > > > 0.0.0.0 > 14201 > > > At startup, you see.. > Listening on Ports: > 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
[ http://issues.apache.org/jira/browse/GERONIMO-1151?page=comments#action_12359683 ] Jeremy Whitlock commented on GERONIMO-1151: --- While working on this, Dain found the issue and it is actually a config.xml issue. The file should look like so: 0.0.0.0 4201 I tested it with: 0.0.0.0 14201 and it started properly and the port was properly retained from the config.xml. Look forward to the commit from Dain to remedy this issue. Thanks Dain. Take care, Jeremy > Changing EJB port from 4201 to another value in config.xml does not take > effect > --- > > Key: GERONIMO-1151 > URL: http://issues.apache.org/jira/browse/GERONIMO-1151 > Project: Geronimo > Type: Bug > Components: OpenEJB, startup/shutdown > Versions: 1.0 > Reporter: John Sisson > Assignee: Jeremy Whitlock > Priority: Blocker > Fix For: 1.0 > > If the EJB port is changed in the geronimo/var/config/config.xml file, it > does not take effect. > For example, change > > > 0.0.0.0 > 4201 > > > to: > > > 0.0.0.0 > 14201 > > > At startup, you see.. > Listening on Ports: > 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Geronimo Web Design - New Versions Updated From Feedback
You know... we could potentially use this theme for Confluence, same look and feel, just backed up by wiki. http://adaptivist.com/ is a good example of a non-wiki looking website backed by Confluence. Anyways, just a thought. Amazing eye candy though :-] I still kinda like the rounded fauxtabs in #2, but must admit that #1 is really appealing too... so is #3 actually. --jason On 12/7/05, Epiq Geronimo Team <[EMAIL PROTECTED]> wrote: > Here are three new designs: > > http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm > > These designs are based loosely on version 1 of the previous designs > posted and we have tried to incorporate the feedback we have received > regarding headers and navigation into the design. The current left nav > bar has used the existing web site navigation. Let us know what you think. > > The Epiq Team >
Console JIRAs with patches
I have a few console JIRAs waiting to be reviewed and hopefully integrated. If possible, could somebody take a look at these before we fork the code tonight? These are strictly look and feel enhancements (Matt?) - GERONIMO-1122 Update config views improvement http://issues.apache.org/jira/browse/GERONIMO-1122 - GERONIMO-1300 "Powered by" on welcome pages http://issues.apache.org/jira/browse/GERONIMO-1300 These are management improvements / console defect fixes (Aaron?) - GERONIMO-1130 JSR77 like Container Stats Mgmt API & Jetty impl. http://issues.apache.org/jira/browse/GERONIMO-1130 - GERONIMO-1270 JMS portlet Exception http://issues.apache.org/jira/browse/GERONIMO-1270 This last one is a quick fix to avoid the error. I'll cycle back and rework this code for the Listable/WriteableRepository improvements when we have most of the major console bugs fixed. Thanks, Joe -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot
[jira] Assigned: (GERONIMO-1122) Updated view of configurations
[ http://issues.apache.org/jira/browse/GERONIMO-1122?page=all ] Joe Bohn reassigned GERONIMO-1122: -- Assign To: Joe Bohn > Updated view of configurations > -- > > Key: GERONIMO-1122 > URL: http://issues.apache.org/jira/browse/GERONIMO-1122 > Project: Geronimo > Type: Improvement > Components: console > Versions: 1.0 > Environment: all > Reporter: Joe Bohn > Assignee: Joe Bohn > Fix For: 1.0 > Attachments: cfgtable.patch, cfgtable.patch2 > > This was originally part of the filter jira (922) but since it appears that > it will not make it I pulled this small modification out. It is an > improvement (at least I think it is) to the configuration views so that it is > easier to see which configurations are associated with other items and what > they can do against them. It also puts the more important information > (configuration name) on the left instead of the right. > The look and feel jira(s) may change all of this completely but I think this > is better than what we have now and some portion (table, ordering, etc...) > could be kept in the new look and feel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1122) Updated view of configurations
[ http://issues.apache.org/jira/browse/GERONIMO-1122?page=all ] Joe Bohn updated GERONIMO-1122: --- Attachment: cfgtable.patch2 Here is an improved version of the table that matches our epiq look and feel better than the earlier version. Use cfgtable.patch2 > Updated view of configurations > -- > > Key: GERONIMO-1122 > URL: http://issues.apache.org/jira/browse/GERONIMO-1122 > Project: Geronimo > Type: Improvement > Components: console > Versions: 1.0 > Environment: all > Reporter: Joe Bohn > Fix For: 1.0 > Attachments: cfgtable.patch, cfgtable.patch2 > > This was originally part of the filter jira (922) but since it appears that > it will not make it I pulled this small modification out. It is an > improvement (at least I think it is) to the configuration views so that it is > easier to see which configurations are associated with other items and what > they can do against them. It also puts the more important information > (configuration name) on the left instead of the right. > The look and feel jira(s) may change all of this completely but I think this > is better than what we have now and some portion (table, ordering, etc...) > could be kept in the new look and feel. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Geronimo Web Design - New Versions Updated From Feedback
Joe, You mentioned the navigation - that is an area that we could use a little bit of assistance on. I think the key areas that we could use some help on would be what are the primary navigation links (ie what should go into the tabs) and the navigation links on the left as these will be consistent thoughout the site. The area on the right can be used for featured information. Does anyone have ideas about what should appear on these areas? Epiq Team Joe Bohn wrote: #1 is the style that I like the best. Looks really good! We just need to decide on the content in the various locations/tabs. Joe Epiq Geronimo Team wrote: Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team
Re: Geronimo Web Design - New Versions Updated From Feedback
#1 is the style that I like the best. Looks really good! We just need to decide on the content in the various locations/tabs. Joe Epiq Geronimo Team wrote: Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot
Re: Geronimo Web Design - New Versions Updated From Feedback
Epiq Geronimo Team wrote: Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team #1 again. Great work. John
Re: Geronimo Web Design - New Versions Updated From Feedback
On 12/7/05, Epiq Geronimo Team <[EMAIL PROTECTED]> wrote:
> Here are three new designs:
>
> http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm
>
> These designs are based loosely on version 1 of the previous designs
> posted and we have tried to incorporate the feedback we have received
> regarding headers and navigation into the design. The current left nav
> bar has used the existing web site navigation. Let us know what you think.
I'm torn because I like them all ;-). But I think I prefer #1 best.
Nice work!
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61Ehttp://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
[jira] Assigned: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
[ http://issues.apache.org/jira/browse/GERONIMO-1151?page=all ] Dain Sundstrom reassigned GERONIMO-1151: Assign To: Jeremy Whitlock It's all yours, Jeremy, but we need this finished today. > Changing EJB port from 4201 to another value in config.xml does not take > effect > --- > > Key: GERONIMO-1151 > URL: http://issues.apache.org/jira/browse/GERONIMO-1151 > Project: Geronimo > Type: Bug > Components: OpenEJB, startup/shutdown > Versions: 1.0 > Reporter: John Sisson > Assignee: Jeremy Whitlock > Priority: Blocker > Fix For: 1.0 > > If the EJB port is changed in the geronimo/var/config/config.xml file, it > does not take effect. > For example, change > > > 0.0.0.0 > 4201 > > > to: > > > 0.0.0.0 > 14201 > > > At startup, you see.. > Listening on Ports: > 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1151) Changing EJB port from 4201 to another value in config.xml does not take effect
[ http://issues.apache.org/jira/browse/GERONIMO-1151?page=comments#action_12359672 ] Jeremy Whitlock commented on GERONIMO-1151: --- I would like to work on this issue. I am an OpenEJB committer and think I've found the issue. I will be sure to check other EJB attributes also. Take care, Jeremy > Changing EJB port from 4201 to another value in config.xml does not take > effect > --- > > Key: GERONIMO-1151 > URL: http://issues.apache.org/jira/browse/GERONIMO-1151 > Project: Geronimo > Type: Bug > Components: OpenEJB, startup/shutdown > Versions: 1.0 > Reporter: John Sisson > Priority: Blocker > Fix For: 1.0 > > If the EJB port is changed in the geronimo/var/config/config.xml file, it > does not take effect. > For example, change > > > 0.0.0.0 > 4201 > > > to: > > > 0.0.0.0 > 14201 > > > At startup, you see.. > Listening on Ports: > 4201 0.0.0.0 ActiveIO Connector EJB -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Confluence link on the welcome pages
FYI, this is done. I just reimported the documentation draft into the GDOCv1 space. I also renamed MAIN to GERONIMO, and DEV to GDEV, to support a more flexible namespace to allow sub-projects a space if they want. I will see about getting email notifications enabled for this instance. --jason
Re: [Vote] Alternate Proposal for Branch V1.0 for Geronimo at 23:59 PST 12/7
Matt Hogstrom wrote: One more time. Based on wildly popular feedback. Here is an alternate branching proposal. [ ] +1 Branch V1.0 at 23:59 PST 12/7 [ ] -1 Defer branching provide proposed alternative +1 - on the basis that it is a branch and not a tag.
Geronimo Web Design - New Versions Updated From Feedback
Here are three new designs: http://www.epiqtech.com/corp/products/technology/opensource/apachegeronimoweb2.htm These designs are based loosely on version 1 of the previous designs posted and we have tried to incorporate the feedback we have received regarding headers and navigation into the design. The current left nav bar has used the existing web site navigation. Let us know what you think. The Epiq Team
[jira] Commented: (GERONIMO-1130) Implement WebServer Manager (statistics gathering/reporting) management interface
[ http://issues.apache.org/jira/browse/GERONIMO-1130?page=comments#action_12359664 ] Joe Bohn commented on GERONIMO-1130: One more comment .. then handling of multiple containers within a single server is only about 50% complete with this patch. More work is necessary on the jsp & portlet for full support of multiple containers. > Implement WebServer Manager (statistics gathering/reporting) management > interface > - > > Key: GERONIMO-1130 > URL: http://issues.apache.org/jira/browse/GERONIMO-1130 > Project: Geronimo > Type: New Feature > Components: management, console > Versions: 1.0-M5 > Environment: all > Reporter: Joe Bohn > Assignee: Joe Bohn > Fix For: 1.x > Attachments: StatsJetty5.1.5.patch, StatsJetty5.1.7rc05.patch > > Jetty has a statistics gathering and reporting capability that is support in > the console via the Web Server Manager portlet. We should provide similar > monitoring capabilities for tomcat. > However, the Jetty implementation is tightly bound to Jetty. We need a more > generic interface build upon the principles of JSR77 to address statistical > information for the web server (both jetty and tomcat). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1130) Implement WebServer Manager (statistics gathering/reporting) management interface
[ http://issues.apache.org/jira/browse/GERONIMO-1130?page=all ] Joe Bohn updated GERONIMO-1130: --- Geronimo Info: [Patch Available] > Implement WebServer Manager (statistics gathering/reporting) management > interface > - > > Key: GERONIMO-1130 > URL: http://issues.apache.org/jira/browse/GERONIMO-1130 > Project: Geronimo > Type: New Feature > Components: management, console > Versions: 1.0-M5 > Environment: all > Reporter: Joe Bohn > Assignee: Joe Bohn > Fix For: 1.x > Attachments: StatsJetty5.1.5.patch, StatsJetty5.1.7rc05.patch > > Jetty has a statistics gathering and reporting capability that is support in > the console via the Web Server Manager portlet. We should provide similar > monitoring capabilities for tomcat. > However, the Jetty implementation is tightly bound to Jetty. We need a more > generic interface build upon the principles of JSR77 to address statistical > information for the web server (both jetty and tomcat). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1130) Implement WebServer Manager (statistics gathering/reporting) management interface
[ http://issues.apache.org/jira/browse/GERONIMO-1130?page=comments#action_12359663 ] Joe Bohn commented on GERONIMO-1130: Oops .. I forgot to mention the reason for the 3 patches. Some additional values for the statistics were added to Jetty 5.1.7rc0 (although a few more are still needed). The one patch includes code for this newer version of Jetty. The other patch is for the current version of Jetty that we include, 5.1.5. > Implement WebServer Manager (statistics gathering/reporting) management > interface > - > > Key: GERONIMO-1130 > URL: http://issues.apache.org/jira/browse/GERONIMO-1130 > Project: Geronimo > Type: New Feature > Components: management, console > Versions: 1.0-M5 > Environment: all > Reporter: Joe Bohn > Assignee: Joe Bohn > Fix For: 1.x > Attachments: StatsJetty5.1.5.patch, StatsJetty5.1.7rc05.patch > > Jetty has a statistics gathering and reporting capability that is support in > the console via the Web Server Manager portlet. We should provide similar > monitoring capabilities for tomcat. > However, the Jetty implementation is tightly bound to Jetty. We need a more > generic interface build upon the principles of JSR77 to address statistical > information for the web server (both jetty and tomcat). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1130) Implement WebServer Manager (statistics gathering/reporting) management interface
[ http://issues.apache.org/jira/browse/GERONIMO-1130?page=all ] Joe Bohn updated GERONIMO-1130: --- Attachment: StatsJetty5.1.5.patch StatsJetty5.1.7rc05.patch These patches are an initial implementation of a JSR77-like web container statistics management interface and an implementation on Jetty. They also update the statistics view and provide a friendly message until we get tomcat implemented. I had to take some liberties with the JSR77 style interface to be able to enable/disable and reset statsitics in a consistent manner between different containers. Aaron, Please take a look and let me know what you think. I know it's late ... so I'm not sure if you want to try to include this in V1 or not? Even if this isn't perfect it's a lot further along the way than what we currently have and I'd like to get the code integrated if possible. > Implement WebServer Manager (statistics gathering/reporting) management > interface > - > > Key: GERONIMO-1130 > URL: http://issues.apache.org/jira/browse/GERONIMO-1130 > Project: Geronimo > Type: New Feature > Components: management, console > Versions: 1.0-M5 > Environment: all > Reporter: Joe Bohn > Assignee: Joe Bohn > Fix For: 1.x > Attachments: StatsJetty5.1.5.patch, StatsJetty5.1.7rc05.patch > > Jetty has a statistics gathering and reporting capability that is support in > the console via the Web Server Manager portlet. We should provide similar > monitoring capabilities for tomcat. > However, the Jetty implementation is tightly bound to Jetty. We need a more > generic interface build upon the principles of JSR77 to address statistical > information for the web server (both jetty and tomcat). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [M1] Plugin hell, help desperately needed
Donald Woods wrote:
Finally got new4 goal to complete using Maven 1.1Beta2 (was always
failing with the same error you mention below), by editing
configs/geronimo-gbean-deployer/project.xml and removing the comments
from around the geronimo-packaging-plugin dependency to re-enable it as
a depend -
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
I'm running a full build now via
maven m:clean new -Dmaven.test.skip=true -Dmaven.itest.skip=true
to verify the change works repeatably before I open a JIRA and attach
the patch.
-Donald
Thanks Donald, that change got me over the failure (and I'm using maven 1.0.2). I manually placed
geronimo-packaging-plugin into the .maven/cache. Ran into another failure to statisfy a dependency on
tranql-connector-derby-embed-local-1.1-SNAPSHOT.rar but that's probably because I was doing an offline build.
It was a bit tricky mapping this message:
[echo] Running car:install for Geronimo Configuration for performing
service deployments
to
geronimo-gbean-deployer/project.xml
I made the connection (thank you findstr/grep) but failed to investigate the dependencies in project.xml.
Won't make that mistake again ;-)
Will clean out .maven/cache and kick off a 'maven clean new' build this evening
and report back the results.
Bill
[jira] Closed: (GERONIMO-1295) Deploy & Undeploy no longer affect config.xml; next startup dies
[ http://issues.apache.org/jira/browse/GERONIMO-1295?page=all ] Dain Sundstrom closed GERONIMO-1295: Resolution: Fixed I needed to call attributeChanged in addConfiguration, removeConfiguration and setReference. Sending trunk/modules/system/src/java/org/apache/geronimo/system/configuration/LocalAttributeManager.java Transmitting file data . Committed revision 354878. > Deploy & Undeploy no longer affect config.xml; next startup dies > > > Key: GERONIMO-1295 > URL: http://issues.apache.org/jira/browse/GERONIMO-1295 > Project: Geronimo > Type: Bug > Components: deployment > Versions: 1.0-M5 > Reporter: Aaron Mulder > Assignee: Dain Sundstrom > Priority: Blocker > Fix For: 1.0 > > I just updated, and now if I deploy an app it is not written to config.xml, > and if I undeploy an app it is not marked as disabled. Therefore after > undeploying, the server won't start any more because config.xml refers to > configurations that are no longer in the config store. > to reproduce: > - Build modules/assembly > - Start the server > - Run java -jar target/geronimo-1.0-SNAPSHOT/bin/deployer.jar undeploy > geronimo/console-jetty/1.0-SNAPSHOT/car > - Stop the server > - Start the server -- it dies during startup -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [M1] Plugin hell, help desperately needed
Finally got new4 goal to complete using Maven 1.1Beta2 (was always
failing with the same error you mention below), by editing
configs/geronimo-gbean-deployer/project.xml and removing the comments
from around the geronimo-packaging-plugin dependency to re-enable it as
a depend -
geronimo
geronimo-packaging-plugin
${geronimo_version}
plugin
I'm running a full build now via
maven m:clean new -Dmaven.test.skip=true -Dmaven.itest.skip=true
to verify the change works repeatably before I open a JIRA and attach
the patch.
-Donald
Bill Stoddard wrote:
Bill Stoddard wrote:
David Jencks wrote:
In the geronimo project we are experiencing severe problems with our
build related to plugins. Any advice on how to improve this
situation would be appreciated.
Perhaps this is stating the obvious, but on the off chance it is
useful, here goes...
I am consistently getting this failure in new4:
...
multiproject:install-callback:
[echo] Running car:install for Geronimo Configuration for
performing service deployments
BUILD FAILED
File.. C:\home\apache\geronimo\maven.xml
Element... maven:reactor
Line.. 58
Column 112
Unable to obtain goal [multiproject:install-callback] -- C:\Documents
and
Settings\Administrator\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly:256:30:
No goal [car:install]
Total time: 9 seconds
Goal [car:install] is implemented by the geronimo-packaging-plugin.
After my build fails, I check the maven cache and I only see the
following two plugins:
dir c:/Documents and Settings/Administrator/.maven/cache/
geronimo-dependency-plugin-1.0-SNAPSHOT
geronimo-deployment-plugin-1.0-SNAPSHOT
No packaging plugin. Do you think the plugin was removed from the
cache or did it not get put in the cache in the first place?
Going to try an experiment... run sysinternals filemon watching for
file geronimo-packaging-plugin-1.0-SNAPSHOT, kick off a build and
watch what happens. If the file is never created, that will be a
useful clue.
Bill
David,
Ran filemon while doing an offline build. File CREATE and DELETE log
entries here:
114:19:26 PMjava.exe:1256DELETE
C:\home\apache\geronimo\plugins\geronimo-packaging-plugin\target\geronimo-packaging-plugin-1.0-SNAPSHOT.jar
SUCCESS
154:23:07 PMjava.exe:1256CREATE
C:\home\apache\geronimo\plugins\geronimo-packaging-plugin\target\geronimo-packaging-plugin-1.0-SNAPSHOT.jar
SUCCESSOptions: OverwriteIf Access: All
7984:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar
SUCCESS Options: OverwriteIf Access: All
8584:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar.md5
SUCCESSOptions: OverwriteIf Access: All
8884:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar.sha1
SUCCESSOptions: OverwriteIf Access: All
9184:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom
SUCCESS Options: OverwriteIf Access: All
9564:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom.md5
SUCCESS Options: OverwriteIf Access: All
9864:23:07 PMjava.exe:1256CREATEC:\Documents and
Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom.sha1
SUCCESSOptions: OverwriteIf Access: All
I was expecting to see something showing up in the maven cache. Is this
what you would expect to see?
Bill
smime.p7s
Description: S/MIME Cryptographic Signature
[jira] Closed: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
[ http://issues.apache.org/jira/browse/GERONIMO-1299?page=all ] David Jencks closed GERONIMO-1299: -- Fix Version: 1.0 Resolution: Fixed > Refresh servlet-examples and jsp-examples war files > --- > > Key: GERONIMO-1299 > URL: http://issues.apache.org/jira/browse/GERONIMO-1299 > Project: Geronimo > Type: Bug > Components: sample apps > Versions: 1.0 > Reporter: Dave Colasurdo > Assignee: David Jencks > Priority: Minor > Fix For: 1.0 > Attachments: geronimo-jsp-examples-tomcat-5.5.12-1.war, > geronimo-servlet-examples-tomcat-5.5.12-1.war, newexamples-12-06-05.patch > > There are several aspects of the Tomcat examples that are inappropriate for > Jetty. Have updated the examples as follows: > Updates to "geronimo-servlet-examples-tomcat-5.5.12-1.war": > -index.html - removed "Please refer to the README file provide with > this Tomcat release regarding how to configure and start the provided web > server." > -WEB-INF/web.xml - Commented out Servlet > Mapped Filter invoker > > Updates to "geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples": > -index.html - removed "of course, we recommend href="http://jakarta.apache.org/tomcat/";>Tomcat." > Also updated the dependencies relating to the war revision id.. Will include > a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
[ http://issues.apache.org/jira/browse/GERONIMO-1299?page=all ] David Jencks reopened GERONIMO-1299: forgot version > Refresh servlet-examples and jsp-examples war files > --- > > Key: GERONIMO-1299 > URL: http://issues.apache.org/jira/browse/GERONIMO-1299 > Project: Geronimo > Type: Bug > Components: sample apps > Versions: 1.0 > Reporter: Dave Colasurdo > Assignee: David Jencks > Priority: Minor > Fix For: 1.0 > Attachments: geronimo-jsp-examples-tomcat-5.5.12-1.war, > geronimo-servlet-examples-tomcat-5.5.12-1.war, newexamples-12-06-05.patch > > There are several aspects of the Tomcat examples that are inappropriate for > Jetty. Have updated the examples as follows: > Updates to "geronimo-servlet-examples-tomcat-5.5.12-1.war": > -index.html - removed "Please refer to the README file provide with > this Tomcat release regarding how to configure and start the provided web > server." > -WEB-INF/web.xml - Commented out Servlet > Mapped Filter invoker > > Updates to "geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples": > -index.html - removed "of course, we recommend href="http://jakarta.apache.org/tomcat/";>Tomcat." > Also updated the dependencies relating to the war revision id.. Will include > a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
[ http://issues.apache.org/jira/browse/GERONIMO-1299?page=all ] David Jencks closed GERONIMO-1299: -- Resolution: Fixed The wars have already made it into a repo. Sendingconfigs/jsp-examples-jetty/project.properties Sendingconfigs/jsp-examples-jetty/project.xml Sendingconfigs/jsp-examples-tomcat/project.properties Sendingconfigs/jsp-examples-tomcat/project.xml Sendingconfigs/servlets-examples-jetty/project.properties Sendingconfigs/servlets-examples-jetty/project.xml Sendingconfigs/servlets-examples-tomcat/project.properties Sendingconfigs/servlets-examples-tomcat/project.xml Sendingetc/project.properties Transmitting file data . Committed revision 354872. > Refresh servlet-examples and jsp-examples war files > --- > > Key: GERONIMO-1299 > URL: http://issues.apache.org/jira/browse/GERONIMO-1299 > Project: Geronimo > Type: Bug > Components: sample apps > Versions: 1.0 > Reporter: Dave Colasurdo > Assignee: David Jencks > Priority: Minor > Fix For: 1.0 > Attachments: geronimo-jsp-examples-tomcat-5.5.12-1.war, > geronimo-servlet-examples-tomcat-5.5.12-1.war, newexamples-12-06-05.patch > > There are several aspects of the Tomcat examples that are inappropriate for > Jetty. Have updated the examples as follows: > Updates to "geronimo-servlet-examples-tomcat-5.5.12-1.war": > -index.html - removed "Please refer to the README file provide with > this Tomcat release regarding how to configure and start the provided web > server." > -WEB-INF/web.xml - Commented out Servlet > Mapped Filter invoker > > Updates to "geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples": > -index.html - removed "of course, we recommend href="http://jakarta.apache.org/tomcat/";>Tomcat." > Also updated the dependencies relating to the war revision id.. Will include > a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GERONIMO-1299) Refresh servlet-examples and jsp-examples war files
[ http://issues.apache.org/jira/browse/GERONIMO-1299?page=all ] David Jencks reassigned GERONIMO-1299: -- Assign To: David Jencks > Refresh servlet-examples and jsp-examples war files > --- > > Key: GERONIMO-1299 > URL: http://issues.apache.org/jira/browse/GERONIMO-1299 > Project: Geronimo > Type: Bug > Components: sample apps > Versions: 1.0 > Reporter: Dave Colasurdo > Assignee: David Jencks > Priority: Minor > Attachments: geronimo-jsp-examples-tomcat-5.5.12-1.war, > geronimo-servlet-examples-tomcat-5.5.12-1.war, newexamples-12-06-05.patch > > There are several aspects of the Tomcat examples that are inappropriate for > Jetty. Have updated the examples as follows: > Updates to "geronimo-servlet-examples-tomcat-5.5.12-1.war": > -index.html - removed "Please refer to the README file provide with > this Tomcat release regarding how to configure and start the provided web > server." > -WEB-INF/web.xml - Commented out Servlet > Mapped Filter invoker > > Updates to "geronimo-jsp-examples-tomcat-5.5.12-1.warjsp-examples": > -index.html - removed "of course, we recommend href="http://jakarta.apache.org/tomcat/";>Tomcat." > Also updated the dependencies relating to the war revision id.. Will include > a patch for this -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: GNU JavaMail - SMTP, POP3 and IMAP4
To use this code would require the GNU JavaMail to change their license to Apache (or something BSDish), and since GNU is the backer of the *GPL licenses, I doubt they would change it. Just like an Apache project would never change to a GPL license. Kinda sucks to have these walls in the open source world, but such is life. -dain On Dec 7, 2005, at 1:40 PM, Bilal Bhatti wrote: I know some of the MAIL implementations were evaluated. However, I don't remember GNU JavaMail as being one of them. http://www.gnu.org/software/classpathx/javamail/ It claims to implement JavaMail 1.3 specifications and has SMTP, IMAP4rev1, POP3, mbox and Maildir support. It is released under GPL. If it was already mentioned, ignore the email. Bilal
GNU JavaMail - SMTP, POP3 and IMAP4
I know some of the MAIL implementations were evaluated. However, I don't remember GNU JavaMail as being one of them. http://www.gnu.org/software/classpathx/javamail/ It claims to implement JavaMail 1.3 specifications and has SMTP, IMAP4rev1, POP3, mbox and Maildir support. It is released under GPL. If it was already mentioned, ignore the email. Bilal
Re: [M1] Plugin hell, help desperately needed
Bill Stoddard wrote: David Jencks wrote: In the geronimo project we are experiencing severe problems with our build related to plugins. Any advice on how to improve this situation would be appreciated. Perhaps this is stating the obvious, but on the off chance it is useful, here goes... I am consistently getting this failure in new4: ... multiproject:install-callback: [echo] Running car:install for Geronimo Configuration for performing service deployments BUILD FAILED File.. C:\home\apache\geronimo\maven.xml Element... maven:reactor Line.. 58 Column 112 Unable to obtain goal [multiproject:install-callback] -- C:\Documents and Settings\Administrator\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly:256:30: No goal [car:install] Total time: 9 seconds Goal [car:install] is implemented by the geronimo-packaging-plugin. After my build fails, I check the maven cache and I only see the following two plugins: dir c:/Documents and Settings/Administrator/.maven/cache/ geronimo-dependency-plugin-1.0-SNAPSHOT geronimo-deployment-plugin-1.0-SNAPSHOT No packaging plugin. Do you think the plugin was removed from the cache or did it not get put in the cache in the first place? Going to try an experiment... run sysinternals filemon watching for file geronimo-packaging-plugin-1.0-SNAPSHOT, kick off a build and watch what happens. If the file is never created, that will be a useful clue. Bill David, Ran filemon while doing an offline build. File CREATE and DELETE log entries here: 11 4:19:26 PM java.exe:1256 DELETE C:\home\apache\geronimo\plugins\geronimo-packaging-plugin\target\geronimo-packaging-plugin-1.0-SNAPSHOT.jar SUCCESS 15 4:23:07 PM java.exe:1256 CREATE C:\home\apache\geronimo\plugins\geronimo-packaging-plugin\target\geronimo-packaging-plugin-1.0-SNAPSHOT.jar SUCCESS Options: OverwriteIf Access: All 798 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar SUCCESS Options: OverwriteIf Access: All 858 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar.md5 SUCCESS Options: OverwriteIf Access: All 888 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\plugins\geronimo-packaging-plugin-1.0-SNAPSHOT.jar.sha1 SUCCESS Options: OverwriteIf Access: All 918 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom SUCCESS Options: OverwriteIf Access: All 956 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom.md5 SUCCESS Options: OverwriteIf Access: All 986 4:23:07 PM java.exe:1256 CREATE C:\Documents and Settings\Administrator\.maven\repository\geronimo\poms\geronimo-packaging-plugin-1.0-SNAPSHOT.pom.sha1 SUCCESS Options: OverwriteIf Access: All I was expecting to see something showing up in the maven cache. Is this what you would expect to see? Bill
Re: [M1] Plugin hell, help desperately needed
David Jencks wrote: In the geronimo project we are experiencing severe problems with our build related to plugins. Any advice on how to improve this situation would be appreciated. Perhaps this is stating the obvious, but on the off chance it is useful, here goes... I am consistently getting this failure in new4: ... multiproject:install-callback: [echo] Running car:install for Geronimo Configuration for performing service deployments BUILD FAILED File.. C:\home\apache\geronimo\maven.xml Element... maven:reactor Line.. 58 Column 112 Unable to obtain goal [multiproject:install-callback] -- C:\Documents and Settings\Administrator\.maven\cache\maven-multiproject-plugin-1.4.1\plugin.jelly:256:30: No goal [car:install] Total time: 9 seconds Goal [car:install] is implemented by the geronimo-packaging-plugin. After my build fails, I check the maven cache and I only see the following two plugins: dir c:/Documents and Settings/Administrator/.maven/cache/ geronimo-dependency-plugin-1.0-SNAPSHOT geronimo-deployment-plugin-1.0-SNAPSHOT No packaging plugin. Do you think the plugin was removed from the cache or did it not get put in the cache in the first place? Going to try an experiment... run sysinternals filemon watching for file geronimo-packaging-plugin-1.0-SNAPSHOT, kick off a build and watch what happens. If the file is never created, that will be a useful clue. Bill
[jira] Closed: (GERONIMO-884) Geronimo Tooling: new wtp requires server startup shutdown timeout values
[ http://issues.apache.org/jira/browse/GERONIMO-884?page=all ] Sachin Patel closed GERONIMO-884: - > Geronimo Tooling: new wtp requires server startup shutdown timeout values > -- > > Key: GERONIMO-884 > URL: http://issues.apache.org/jira/browse/GERONIMO-884 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M4 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Priority: Minor > Attachments: patch.txt, patch2.txt > > - Without specifiying timeout values, when launching geronimo, a dialog box > pops up in post .7 version of WTP stating server startup failed. > - Trace statements where not shown in console due to plugin renames and wrong > Trace class was used. This patch also fixes this issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-968) .classpath change for org.eclipse.geronimo.core didn't make it in patch
[ http://issues.apache.org/jira/browse/GERONIMO-968?page=all ] Sachin Patel closed GERONIMO-968: - > .classpath change for org.eclipse.geronimo.core didn't make it in patch > --- > > Key: GERONIMO-968 > URL: http://issues.apache.org/jira/browse/GERONIMO-968 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > change from 936 for org.eclipse.geronimo.core didn't make it into the fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-885) Geronimo Tooling: security page/wizard
[ http://issues.apache.org/jira/browse/GERONIMO-885?page=all ] Sachin Patel closed GERONIMO-885: - > Geronimo Tooling: security page/wizard > --- > > Key: GERONIMO-885 > URL: http://issues.apache.org/jira/browse/GERONIMO-885 > Project: Geronimo > Type: Improvement > Components: eclipse-plugin > Versions: 1.0-M4 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: SecurityRoleWizard.zip, patch.txt, patch.txt > > The provided patch enables the previously disabled security page. This is > the first part of the security page to define security roles. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-888) Introduce dp export operations
[ http://issues.apache.org/jira/browse/GERONIMO-888?page=all ] Sachin Patel closed GERONIMO-888: - > Introduce dp export operations > -- > > Key: GERONIMO-888 > URL: http://issues.apache.org/jira/browse/GERONIMO-888 > Project: Geronimo > Type: Improvement > Components: eclipse-plugin > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Priority: Minor > Attachments: patch.txt > > Eclipse WTP allows multiple components to be defined within a project or each > project can be its own component. Either way each j2ee components deployment > plans are scattered within the workspace for a given application. An > extendable deployment export operation is needed to aggregate the dp plans > for a given app and export them out as a single geronimo-application.xml > file. This operation is implemented using the WTP operation framework which > will eventually allow the operation to be embedded as part of a post op > during WTP Ear file export operation. > The following patch is the initial drop of a stubbed out implementation for > the AbstractDataModelOperation and AbstractDataModelProvider which will allow > this capability. > The EarExportOperation is wtp is missing extended op support in wtp... > Eclipse bugzilla 107203 opened. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-899) Geronimo Tooling: need server overview page
[ http://issues.apache.org/jira/browse/GERONIMO-899?page=all ] Sachin Patel closed GERONIMO-899: - > Geronimo Tooling: need server overview page > --- > > Key: GERONIMO-899 > URL: http://issues.apache.org/jira/browse/GERONIMO-899 > Project: Geronimo > Type: New Feature > Components: eclipse-plugin > Versions: 1.0-M4 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: pluginxmlpatch.txt, securitysectionpatch.txt > > A server overview form page is needed for the geronimo IServer instance to > modify server name, ports, runtime location, etc... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-902) Geronimo Tooling: delete all .cvsignore
[ http://issues.apache.org/jira/browse/GERONIMO-902?page=all ] Sachin Patel closed GERONIMO-902: - > Geronimo Tooling: delete all .cvsignore > --- > > Key: GERONIMO-902 > URL: http://issues.apache.org/jira/browse/GERONIMO-902 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Priority: Trivial > > The .cvsignore files from each of the plugins accidently got included in the > original code drop. These should be deleted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1055) Geronimo schema validation errors
[ http://issues.apache.org/jira/browse/GERONIMO-1055?page=all ] Sachin Patel closed GERONIMO-1055: -- > Geronimo schema validation errors > - > > Key: GERONIMO-1055 > URL: http://issues.apache.org/jira/browse/GERONIMO-1055 > Project: Geronimo > Type: Bug > Components: general > Versions: 1.0 > Reporter: Sachin Patel > Assignee: Sachin Patel > Fix For: 1.0 > > When feeding the geronimo schemas through validators the following validation > errors occur... > geronimo-connector-1.0.xsd > -- > line 387 > s4s-elt-invalid-content.1: The content of 'descriptionType' is invalid. > Element 'attribute' is invalid, misplaced, or occurs too often. > line 387 > src-resolve.4.2: Error resolving component 'xml:lang'. It was detected that > 'xml:lang' is in namespace 'http://www.w3.org/XML/1998/namespace', but > components from this namespace are not referenceable from schema document > 'geronimo-connector-1.0.xsd'. If this is the incorrect namespace, perhaps the > prefix of 'xml:lang' needs to be changed. If this is the correct namespace, > then an appropriate 'import' tag should be added to > 'geronimo-connector-1.0.xsd'. > geronimo-security-1.0.xsd > - > line 77 > s4s-elt-invalid-content.1: The content of 'descriptionType' is invalid. > Element 'attribute' is invalid, misplaced, or occurs too often. > line 77 > src-resolve.4.2: Error resolving component 'xml:lang'. It was detected that > 'xml:lang' is in namespace 'http://www.w3.org/XML/1998/namespace', but > components from this namespace are not referenceable from schema document > 'geronimo-security-1.0.xsd'. If this is the incorrect namespace, perhaps the > prefix of 'xml:lang' needs to be changed. If this is the correct namespace, > then an appropriate 'import' tag should be added to > 'geronimo-security-1.0.xsd'. > geronimo-service-1.0.xsd > > line 41 > src-import.1.1: The namespace attribute > 'http://geronimo.apache.org/xml/ns/deployment-1.0' of an element > information item must not be the same as the targetNamespace of the schema it > exists in. > line 41 > src-resolve: Cannot resolve the name 'dependencyType' to a(n) 'type > definition' component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-907) remove workaround for copying plan to .deployable
[ http://issues.apache.org/jira/browse/GERONIMO-907?page=all ] Sachin Patel closed GERONIMO-907: - > remove workaround for copying plan to .deployable > - > > Key: GERONIMO-907 > URL: http://issues.apache.org/jira/browse/GERONIMO-907 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > WTP is keeping in sync the source and the .deployable folder and it is no > longer necessary to copy the deployment plan into the .deployables folder. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-913) General updates
[ http://issues.apache.org/jira/browse/GERONIMO-913?page=all ] Sachin Patel closed GERONIMO-913: - > General updates > --- > > Key: GERONIMO-913 > URL: http://issues.apache.org/jira/browse/GERONIMO-913 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > Need to get the sandbox fully updated with latest changes. Batching fixes > togather. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-909) Null check needed in fillTableItems()
[ http://issues.apache.org/jira/browse/GERONIMO-909?page=all ] Sachin Patel closed GERONIMO-909: - > Null check needed in fillTableItems() > - > > Key: GERONIMO-909 > URL: http://issues.apache.org/jira/browse/GERONIMO-909 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Priority: Minor > Attachments: geronimo.core.patch.txt, geronimo.ui.patch.txt, patch.txt > > Secuirty roles section won't display if no roles are defined. Need a null > check to display and empty table. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-914) Need IUndoableOperation operations for setting security
[ http://issues.apache.org/jira/browse/GERONIMO-914?page=all ] Sachin Patel closed GERONIMO-914: - > Need IUndoableOperation operations for setting security > --- > > Key: GERONIMO-914 > URL: http://issues.apache.org/jira/browse/GERONIMO-914 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt, patch2.txt > > Implementing ServerEditor section requires a call to > execute(IUndoableOperations) to set any configuration information for the > server. For the security section, IUndoableOperations needed to be defined > to set the server username and password. Otherwise the editor will not be > marked dirty if modifications to those fields are made. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-916) Source in new files is duplicated
[ http://issues.apache.org/jira/browse/GERONIMO-916?page=all ] Sachin Patel closed GERONIMO-916: - > Source in new files is duplicated > - > > Key: GERONIMO-916 > URL: http://issues.apache.org/jira/browse/GERONIMO-916 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > New files introducd in 909 are corrupt. The source in each of the files is > duplicated multiple times. The attach patch cleans this up. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-919) Refactor utility methods and WTPOperations
[ http://issues.apache.org/jira/browse/GERONIMO-919?page=all ] Sachin Patel closed GERONIMO-919: - > Refactor utility methods and WTPOperations > -- > > Key: GERONIMO-919 > URL: http://issues.apache.org/jira/browse/GERONIMO-919 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > Too many duplicate utitily methods scattered around. Refactor static methods > to GeronimoUtils. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-915) NPE on selection change event
[ http://issues.apache.org/jira/browse/GERONIMO-915?page=all ] Sachin Patel closed GERONIMO-915: - > NPE on selection change event > - > > Key: GERONIMO-915 > URL: http://issues.apache.org/jira/browse/GERONIMO-915 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Attachments: patch.txt > > java.lang.NullPointerException > at > org.apache.geronimo.ui.actions.LaunchGeronimoConsoleAction.selectionChanged(LaunchGeronimoConsoleAction.java:87) > at > org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:200) > at > org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:122) > at > org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:269) > at org.eclipse.ui.internal.PluginAction.(PluginAction.java:108) > at > org.eclipse.ui.internal.ObjectPluginAction.(ObjectPluginAction.java:37) > at > org.eclipse.ui.internal.ActionDescriptor.createAction(ActionDescriptor.java:258) > at > org.eclipse.ui.internal.ActionDescriptor.(ActionDescriptor.java:168) > at > org.eclipse.ui.internal.ActionDescriptor.(ActionDescriptor.java:100) > at > org.eclipse.ui.internal.ObjectActionContributor.createActionDescriptor(ObjectActionContributor.java:176) > at > org.eclipse.ui.internal.PluginActionBuilder.readElement(PluginActionBuilder.java:155) > at > org.eclipse.ui.internal.ObjectActionContributor.readElement(ObjectActionContributor.java:252) > at > org.eclipse.ui.internal.registry.RegistryReader.readElements(RegistryReader.java(Compiled > Code)) > at > org.eclipse.ui.internal.registry.RegistryReader.readElementChildren(RegistryReader.java:127) > at > org.eclipse.ui.internal.ObjectActionContributor.readConfigElement(ObjectActionContributor.java:223) > at > org.eclipse.ui.internal.ObjectActionContributor.isApplicableTo(ObjectActionContributor.java:192) > at > org.eclipse.ui.internal.ObjectContributorManager.isApplicableTo(ObjectContributorManager.java:274) > at > org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:124) > at > org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:246) > at > org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:273) > at > org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:285) > at > org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:372) > at org.eclipse.jface.action.MenuManager.access$0(MenuManager.java:369) > at > org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:386) > at > org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:117) > at > org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java(Compiled Code)) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Inlined > Compiled Code)) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Compiled Code)) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java(Compiled Code)) > at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:3337) > at org.eclipse.swt.widgets.Control.windowProc(Control.java(Compiled > Code)) > at > org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java(Compiled > Code)) > at org.eclipse.swt.widgets.Display.windowProc(Display.java(Compiled > Code)) > at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) > at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:225) > at org.eclipse.swt.widgets.Display.runPopups(Display.java(Compiled > Code)) > at > org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code)) > at > org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code)) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) > at > org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) > at > org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) > at > org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) > at > sun.reflect.DelegatingMethodAccessorImpl.inv
[jira] Closed: (GERONIMO-936) Reconfigure plugin .classpath to follow Maven convention
[ http://issues.apache.org/jira/browse/GERONIMO-936?page=all ] Sachin Patel closed GERONIMO-936: - > Reconfigure plugin .classpath to follow Maven convention > > > Key: GERONIMO-936 > URL: http://issues.apache.org/jira/browse/GERONIMO-936 > Project: Geronimo > Type: Bug > Components: eclipse-plugin > Versions: 1.0-M5 > Reporter: Sachin Patel > Assignee: Geir Magnusson Jr > Priority: Minor > Fix For: 1.0 > Attachments: patch.txt > > Each plugin .classpath file should be reconfigured to follow Maven > conventions with output in target/classes. This will keep and use the same > output folder when building with Maven or within Eclipse IDE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1242) Client Interceptors
[ http://issues.apache.org/jira/browse/GERONIMO-1242?page=all ] Alan Cabrera updated GERONIMO-1242: --- Component: CORBA > Client Interceptors > --- > > Key: GERONIMO-1242 > URL: http://issues.apache.org/jira/browse/GERONIMO-1242 > Project: Geronimo > Type: Sub-task > Components: CORBA > Reporter: Kresten Krab Thorup > Assignee: Alan Cabrera > Attachments: interceptor.diff.gz > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1245) Backward M5 deployment capability broken
[ http://issues.apache.org/jira/browse/GERONIMO-1245?page=all ]
Sachin Patel resolved GERONIMO-1245:
Resolution: Won't Fix
Concensus was to no support this.
> Backward M5 deployment capability broken
>
>
> Key: GERONIMO-1245
> URL: http://issues.apache.org/jira/browse/GERONIMO-1245
> Project: Geronimo
> Type: Bug
> Components: deployment
> Versions: 1.0
> Reporter: Sachin Patel
> Fix For: 1.0
>
> The deployment capability using the 1.0 snapshot deployment jars to deploy to
> M5 is broken do to the following change made in
> org.apache.geronimo.deployment.plugin.local.StartCommand
> In M5 the list below contained ObjectName entries
> // Load and start the module
> List list = configurationManager.loadRecursive(moduleID);
> for (int j = 0; j < list.size(); j++) {
> ObjectName name = (ObjectName) list.get(j);
> ...
> This was changed to use a list of URI's
> List list = configurationManager.loadRecursive(moduleID);
> for (int j = 0; j < list.size(); j++) {
> URI name = (URI) list.get(j);
> This of course causing a ClassCastException at the point.
> Can we introduce additional code to support backward compatibility to M5?
> How hard would this be? I assume there are other areas like this that also
> need to be fixed. I can help out if needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-1055) Geronimo schema validation errors
[ http://issues.apache.org/jira/browse/GERONIMO-1055?page=all ] Sachin Patel resolved GERONIMO-1055: Resolution: Fixed Assign To: Sachin Patel > Geronimo schema validation errors > - > > Key: GERONIMO-1055 > URL: http://issues.apache.org/jira/browse/GERONIMO-1055 > Project: Geronimo > Type: Bug > Components: general > Versions: 1.0 > Reporter: Sachin Patel > Assignee: Sachin Patel > Fix For: 1.0 > > When feeding the geronimo schemas through validators the following validation > errors occur... > geronimo-connector-1.0.xsd > -- > line 387 > s4s-elt-invalid-content.1: The content of 'descriptionType' is invalid. > Element 'attribute' is invalid, misplaced, or occurs too often. > line 387 > src-resolve.4.2: Error resolving component 'xml:lang'. It was detected that > 'xml:lang' is in namespace 'http://www.w3.org/XML/1998/namespace', but > components from this namespace are not referenceable from schema document > 'geronimo-connector-1.0.xsd'. If this is the incorrect namespace, perhaps the > prefix of 'xml:lang' needs to be changed. If this is the correct namespace, > then an appropriate 'import' tag should be added to > 'geronimo-connector-1.0.xsd'. > geronimo-security-1.0.xsd > - > line 77 > s4s-elt-invalid-content.1: The content of 'descriptionType' is invalid. > Element 'attribute' is invalid, misplaced, or occurs too often. > line 77 > src-resolve.4.2: Error resolving component 'xml:lang'. It was detected that > 'xml:lang' is in namespace 'http://www.w3.org/XML/1998/namespace', but > components from this namespace are not referenceable from schema document > 'geronimo-security-1.0.xsd'. If this is the incorrect namespace, perhaps the > prefix of 'xml:lang' needs to be changed. If this is the correct namespace, > then an appropriate 'import' tag should be added to > 'geronimo-security-1.0.xsd'. > geronimo-service-1.0.xsd > > line 41 > src-import.1.1: The namespace attribute > 'http://geronimo.apache.org/xml/ns/deployment-1.0' of an element > information item must not be the same as the targetNamespace of the schema it > exists in. > line 41 > src-resolve: Cannot resolve the name 'dependencyType' to a(n) 'type > definition' component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1193) Installer should include schema files for components included in the install target
[ http://issues.apache.org/jira/browse/GERONIMO-1193?page=all ] David Jencks closed GERONIMO-1193: -- Fix Version: 1.0 Resolution: Fixed > Installer should include schema files for components included in the install > target > --- > > Key: GERONIMO-1193 > URL: http://issues.apache.org/jira/browse/GERONIMO-1193 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Maven, installer runtime > Reporter: erik daughtrey > Assignee: David Jencks > Fix For: 1.0 > Attachments: installer_1193.patch > > DJ: "This should proceed by fixing the xmlbeans plugin to put schemas in the > same place the xmlbeans ant task does, and by extracting all such schemas > from our dependencies. This needs to be added to the assembly plugin: it is > not installer specific." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (GERONIMO-1193) Installer should include schema files for components included in the install target
[ http://issues.apache.org/jira/browse/GERONIMO-1193?page=all ] David Jencks reopened GERONIMO-1193: forgot the version > Installer should include schema files for components included in the install > target > --- > > Key: GERONIMO-1193 > URL: http://issues.apache.org/jira/browse/GERONIMO-1193 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Maven, installer runtime > Reporter: erik daughtrey > Assignee: David Jencks > Fix For: 1.0 > Attachments: installer_1193.patch > > DJ: "This should proceed by fixing the xmlbeans plugin to put schemas in the > same place the xmlbeans ant task does, and by extracting all such schemas > from our dependencies. This needs to be added to the assembly plugin: it is > not installer specific." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1193) Installer should include schema files for components included in the install target
[ http://issues.apache.org/jira/browse/GERONIMO-1193?page=all ] David Jencks closed GERONIMO-1193: -- Resolution: Fixed Assign To: David Jencks Applied with slight modifications to primarily delete commented out code in plugins. Sendingassemblies/j2ee-installer/maven.xml Sendingassemblies/j2ee-installer/project.xml Sendingassemblies/j2ee-installer/src/izpack/geronimo-izpack.xml Sendingassemblies/j2ee-installer/src/izpack/izpack-process.xml Sendingassemblies/j2ee-installer/src/var/config/config.xml Sendingplugins/geronimo-assembly-plugin/plugin.jelly Sendingplugins/geronimo-izpack-plugin/plugin.jelly Transmitting file data ... Committed revision 354848. > Installer should include schema files for components included in the install > target > --- > > Key: GERONIMO-1193 > URL: http://issues.apache.org/jira/browse/GERONIMO-1193 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Maven, installer runtime > Reporter: erik daughtrey > Assignee: David Jencks > Attachments: installer_1193.patch > > DJ: "This should proceed by fixing the xmlbeans plugin to put schemas in the > same place the xmlbeans ant task does, and by extracting all such schemas > from our dependencies. This needs to be added to the assembly plugin: it is > not installer specific." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GBUILD-4) StringIndexOutOfBoundsException on bad record
[ http://issues.apache.org/jira/browse/GBUILD-4?page=all ] David Blevins closed GBUILD-4: -- Resolution: Fixed > StringIndexOutOfBoundsException on bad record > - > > Key: GBUILD-4 > URL: http://issues.apache.org/jira/browse/GBUILD-4 > Project: GBuild > Type: Bug > Components: reports > Reporter: David Blevins > Assignee: David Blevins > > Don't parse bad records. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (GBUILD-4) StringIndexOutOfBoundsException on bad record
[ http://issues.apache.org/jira/browse/GBUILD-4?page=all ] David Blevins reassigned GBUILD-4: -- Assign To: David Blevins > StringIndexOutOfBoundsException on bad record > - > > Key: GBUILD-4 > URL: http://issues.apache.org/jira/browse/GBUILD-4 > Project: GBuild > Type: Bug > Components: reports > Reporter: David Blevins > Assignee: David Blevins > > Don't parse bad records. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1193) Installer should include schema files for components included in the install target
[ http://issues.apache.org/jira/browse/GERONIMO-1193?page=all ] erik daughtrey updated GERONIMO-1193: - Geronimo Info: [Patch Available] > Installer should include schema files for components included in the install > target > --- > > Key: GERONIMO-1193 > URL: http://issues.apache.org/jira/browse/GERONIMO-1193 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Maven, installer runtime > Reporter: erik daughtrey > Attachments: installer_1193.patch > > DJ: "This should proceed by fixing the xmlbeans plugin to put schemas in the > same place the xmlbeans ant task does, and by extracting all such schemas > from our dependencies. This needs to be added to the assembly plugin: it is > not installer specific." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-1193) Installer should include schema files for components included in the install target
[ http://issues.apache.org/jira/browse/GERONIMO-1193?page=all ] erik daughtrey updated GERONIMO-1193: - Attachment: installer_1193.patch This patch installs car files during assembly and supplies a fixed config.xml for startup. The installer isn't really configurable yet and there's still a failure in processing at the end of install. However, processing may not even be used and the failed exec is just a placeholder for now. This fixed install will install jetty. > Installer should include schema files for components included in the install > target > --- > > Key: GERONIMO-1193 > URL: http://issues.apache.org/jira/browse/GERONIMO-1193 > Project: Geronimo > Type: New Feature > Components: installer > Versions: 1.0 > Environment: Maven, installer runtime > Reporter: erik daughtrey > Attachments: installer_1193.patch > > DJ: "This should proceed by fixing the xmlbeans plugin to put schemas in the > same place the xmlbeans ant task does, and by extracting all such schemas > from our dependencies. This needs to be added to the assembly plugin: it is > not installer specific." -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-1266) Geronimo Izpack installer does not set shell scripts as executable
[ http://issues.apache.org/jira/browse/GERONIMO-1266?page=comments#action_12359623 ] erik daughtrey commented on GERONIMO-1266: -- This has been fixed and this JIRA can be closed. > Geronimo Izpack installer does not set shell scripts as executable > -- > > Key: GERONIMO-1266 > URL: http://issues.apache.org/jira/browse/GERONIMO-1266 > Project: Geronimo > Type: Bug > Components: installer > Versions: 1.0 > Reporter: John Sisson > Assignee: John Sisson > Fix For: 1.0 > > I will do this after my new shell scripts are checked in. > Basically we need to have an stage="never" os="unix" keep="true"> line for each file to be marked > executable. Unfortunately I don't think there is a way to have a wildcard > for all *.sh files, we need to name each one explicitly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GBUILD-4) StringIndexOutOfBoundsException on bad record
StringIndexOutOfBoundsException on bad record - Key: GBUILD-4 URL: http://issues.apache.org/jira/browse/GBUILD-4 Project: GBuild Type: Bug Components: reports Reporter: David Blevins Don't parse bad records. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Statistics Management and Jetty/Tomcat
Greg I've modified the list below to add what we would like to present in Geronimo. Jeff and/or Anita, Do you think we can get comparable information from tomcat? We would also need to know how to enable, disable, and reset these statistics for tomcat. Joe Greg Wilkins wrote: These new stats methods are in Jetty CVS if you want them in a hurry. I'll update the snapshot releases tomorrow. cheers Greg Wilkins wrote: So would you be OK with the following stats: private transient long _statsStartedAt=0;// time stats collection started private transient int _connections; // total number of connections made to server private transient int _connectionsOpen; // number of connections currently open private transient int _connectionsOpenMin; // min number of connections open simultaneously private transient int _connectionsOpenMax; // max number of connections open simultaneously private transient long _connectionsDurationMin; // min duration of a connection private transient long _connectionsDurationMax; // max duration of a connection private transient long _connectionsDurationTotalTime;// total duration of all coneection private transient long _connectionsDurationCount;// total number of connections created (I guess this would be the same as _connections above so perhaps we don't need it again in this form) private transient int _errors; // total bad requests to the server private transient int _requests; // total requests made to the server private transient int _requestsActive; // number of requests currently being handled private transient int _requestsActiveMin;// min number of connections handled simultaneously private transient int _requestsActiveMax;// max number of connections handled simultaneously private transient int _connectionsRequestsMin; // min requests per connection private transient int _connectionsRequestsMax; // max requests per connection private transient int _connectionsRequestsCurrent; // The number of connection requests currently in progress (I guess this would be no different than the _connectionsOpen above ... so perhaps we don't need this again in this form) private transient long _requestsDurationMin; // min request duration private transient long _requestsDurationMax; // max request duration private transient long _requestsDurationTotalTime; // total request duration time private transient long _requestsDurationCount; // total number of requests (I guess this would be no different than _requests above ... so perhaps we don't need it again in this form) -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot
Re: Statistics Management and Jetty/Tomcat
Greg, Sorry for the delay in getting back to you on this. I did try out Jetty5.1.7rc0 and have the following results. However, before I tell you the results I need to mention that it doesn't appear that this Geronimo function is going to make Geronimo V1. I don't think anybody else needs a new Jetty image and I don't think this function is critical enough to force the issue before we cut the Geronimo V1 image. Things went fairly well with the new image. There were no major problems. Here's what I noticed: There were some missing APIs that didn't make it from my list to your list in a later append: - getConnectionsRequestsCurrent() - getRequestsDurationCount() - getConnectionsDurationCount() There were some other strange things I observed as well: - A number of fields are never set greater than zero - errors (hopefully because there were no errors) - RequestsActiveMin (I guess it's fair to say zero is the low) - ConnectionsOpenMin (ditto) - RequestsDurationMin - this was strange because I would see this get set sometimes for a few seconds and then get reset to zero. I also notices that when I initially began collecting the Stats it took some time before I would get the initial values (kept returning zero's). It seemed that the more impatient I was (hitting refresh often) ... the longer it took to get any valid data back. I also noticed that the number for some things (like the total requests) grew at an unreasonable rate initially (like with each request I made to the server the total would jump by 20-25. However, after a bit longer the number became more accurate and each refresh I did resulted in just one additional request in the total. Thanks again for working on this. Even though it doesn't look like we'll exploit these additional values in Geronimo v1 we will certainly need them in the near future. Thanks, Joe Greg Wilkins wrote: Joe Bohn wrote: That's correct. In fact, at the moment I'm just trying to get a more generic management implementation of the container stats in the style of the JSR77 stats ... but I'm not really looking for the JSR77 servlet stats right now. You mentioned in another note that you were hoping to create a new jetty image soon. Yep - I'd like to get a 5.1.7 out by mid week before apachecon. So I'll add these methods today and make a snapshot. If you can test ASAP that will help with the timing. I think our needs to complete what we are already receiving in part from Jetty would be met if you could provide these container statistics: - getConnectionsOpenMin - getConnectionsRequestsMin - getConnectionsRequestsCurrent - getConnectionsDurationMin - getConnectionsDurationCount - getConnectionsDurationTotal - getRequestsActiveMin - getRequestsDurationMin - getRequestsDurationCount - getRequestsDurationTotal I'm not sure all these make sense? ConnectionsRequests is a stat about the number of requests per connection (OK badly named), as such there is no current value. Also the getRequestsActiveMin is going to be zero - unless you have a stats reset method that can be called on a busy server. Also some of the Counts and Totals are already provided (eg RequestDurationCount is just the number of requests). So would you be OK with the following stats: private transient long _statsStartedAt=0;// time stats collection started private transient int _connections; // total number of connections made to server private transient int _connectionsOpen; // number of connections currently open private transient int _connectionsOpenMin; // min number of connections open simultaneously private transient int _connectionsOpenMax; // max number of connections open simultaneously private transient long _connectionsDurationMin; // min duration of a connection private transient long _connectionsDurationMax; // max duration of a connection private transient long _connectionsDurationTotal;// total duration of all coneection private transient int _errors; // total bad requests to the server private transient int _requests; // total requests made to the server private transient int _requestsActive; // number of requests currently being handled private transient int _requestsActiveMin;// min number of connections handled simultaneously private transient int _requestsActiveMax;// max number of connections handled simultaneously private transient int _connectionsRequestsMin; // min requests per connection private transient int _connectionsRequestsMax; // max requests per connection private transient long _requestsDurationMin; // min request duration private transient long _requestsDurationMax; // max request duration private transient long _requ
[jira] Created: (GERONIMO-1307) JMX connector doesn't shut down cleanly
JMX connector doesn't shut down cleanly --- Key: GERONIMO-1307 URL: http://issues.apache.org/jira/browse/GERONIMO-1307 Project: Geronimo Type: Bug Components: mail, deployment, management, general, OpenEJB, security, kernel, naming, installer, eclipse-plugin, JVM-compatibility, sample apps, gbuild Versions: 1.0 Reporter: David Jencks Priority: Blocker Fix For: 1.0 In the last day or two this stack trace has shown up on server shutdown: 10:58:04,204 ERROR [GBeanInstance] Problem in doStop of geronimo.server:J2EEApplication=null,J2EEModule=geronimo/j2ee-security/1.0-SNAPSHOT/car,J2EEServer=geronimo,j2eeType=GBean,name=JMXService java.io.IOException: javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: no such object in table] at mx4j.remote.resolver.rmi.Resolver.unbindServer(Resolver.java:279) at javax.management.remote.rmi.RMIConnectorServer.stop(RMIConnectorServer.java:172) at org.apache.geronimo.jmxremoting.JMXConnector.doStop(JMXConnector.java:127) at org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1079) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:395) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:200) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:192) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) at org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:192) at org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:545) at org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:213) at org.apache.geronimo.kernel.config.ConfigurationManagerImpl$ShutdownHook.run(ConfigurationManagerImpl.java:277) at org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:406) at org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:383) at org.apache.geronimo.system.main.Daemon$1.run(Daemon.java:272) I think it appeared about the time Aaron changed the URI format for the jmx deployer connection, but they might or might not be connected. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-406) Move assembly out of modules
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ] David Jencks closed GERONIMO-406: - Resolution: Duplicate Forgot about this copy, I just reopened as GERONIMO-1306 > Move assembly out of modules > > > Key: GERONIMO-406 > URL: http://issues.apache.org/jira/browse/GERONIMO-406 > Project: Geronimo > Type: Improvement > Components: buildsystem > Versions: 1.0-M4 > Reporter: David Jencks > Assignee: David Jencks > Fix For: 1.0 > > The main reason for the uber-build is really the circular dependency between > the modules in geronimo "modules" and openejb. Openejb requires many of the > geronimo modules, and geronimo assembly requires openejb. > This could be fixed by moving geronimo assembly out of modules. I suggest > making a bunch of assemblies, starting with assembly/default which will > include current modules/assembly. > The result is that projects can be built in this order: > howl > geronimo/spec > tranql > tranql-connector > geronimo/modules > activemq > openejb > geronimo/assembly > This can be done by a normal continuous integration tool rather than the > uber-build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1306) Remove modules/assembly build
[ http://issues.apache.org/jira/browse/GERONIMO-1306?page=all ] David Jencks closed GERONIMO-1306: -- Resolution: Fixed Deleting modules/assembly Sendingmodules/deploy-tool/project.xml Deleting modules/deploy-tool/src/java/org/apache/geronimo/deployment/Bootstrap.java Deleting modules/deploy-tool/src/java/org/apache/geronimo/deployment/ShutdownBootstrap.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandDeploy.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandDistribute.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandListModules.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandListTargets.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandLogin.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandPackage.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandRedeploy.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandStart.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/DeployTool.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/ServerConnection.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/StopServer.java Deleting modules/installer Transmitting file data svn: Commit succeeded, but other errors follow: svn: Error bumping revisions post-commit (details follow): Update makes it look like Updated to revision 354830. > Remove modules/assembly build > - > > Key: GERONIMO-1306 > URL: http://issues.apache.org/jira/browse/GERONIMO-1306 > Project: Geronimo > Type: Improvement > Components: buildsystem > Versions: 1.0 > Reporter: David Jencks > Assignee: David Jencks > Fix For: 1.0 > > We are only testing and shipping the assemblies/* servers so we should remove > the obsolete modules/assembly server build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-1294) Remove offline deployment capabilities from deployer.jar
[ http://issues.apache.org/jira/browse/GERONIMO-1294?page=all ] David Jencks closed GERONIMO-1294: -- Resolution: Fixed Fixed in this possibly unnumbered revision Deleting modules/assembly Sendingmodules/deploy-tool/project.xml Deleting modules/deploy-tool/src/java/org/apache/geronimo/deployment/Bootstrap.java Deleting modules/deploy-tool/src/java/org/apache/geronimo/deployment/ShutdownBootstrap.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandDeploy.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandDistribute.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandListModules.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandListTargets.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandLogin.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandPackage.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandRedeploy.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/CommandStart.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/DeployTool.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/ServerConnection.java Sending modules/deploy-tool/src/java/org/apache/geronimo/deployment/cli/StopServer.java Deleting modules/installer Transmitting file data svn: Commit succeeded, but other errors follow: svn: Error bumping revisions post-commit (details follow): update makes it look like Updated to revision 354830. > Remove offline deployment capabilities from deployer.jar > > > Key: GERONIMO-1294 > URL: http://issues.apache.org/jira/browse/GERONIMO-1294 > Project: Geronimo > Type: Improvement > Components: deployment > Versions: 1.0-M5 > Reporter: Aaron Mulder > Assignee: David Jencks > Fix For: 1.0 > Attachments: offline-deploy.patch > > David asked for a patch that removes offline deployment from the deployer.jar > tool. So, here it is. I haven't tested this since it breaks the assembly > module, but hey, it looks right and compiles. :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: SMTP Authentication
The best comparison char I could find on this is http:// members.elysium.pl/brush/smtp-auth/server.html and it from 23.10.2000 so about 5 years old. Anyway, it looks like if we can get LOGIN, PLAIN, CRAM-MD5 and DIGEST-MD5 working with start tls, we will have the basics covered. -dain On Dec 7, 2005, at 9:45 AM, Rick McGuire wrote: Sasl is the challenge/response algorithm for simple server authentication (Simple Authentication and Security Layer). The SMTP spec on authentication defines everything in terms of SASL operations (http://www.networksorcery.com/enp/rfc/rfc2554.txt). Even PLAIN and LOGIN are SASL operations. The Java SASL API added in 5.0 provides a nice extendable framework for SASL operations with support for a lot more than the simple operations. http:// java.sun.com/j2se/1.5.0/docs/guide/security/sasl/sasl-refguide.html. Using the SASL APIs is very nice, as would allow Geronimo to support almost anything a server would throw at as for free, as long it was a mechanism supported by the security provider implementation. Anyway, I've got code for LOGIN and PLAIN already written, and am almost done with a CRAM-MD5 version. This sounds like it will be sufficient for the short term. Rick Dain Sundstrom wrote: From my experience, most servers and clients are just using LOGIN and PLAIN with TLS sometimes. I'm not very familiar with Sasl; can you explain how it fits into a mail client or server? Thanks, -dain On Dec 7, 2005, at 8:37 AM, Rick McGuire wrote: I've looking at the issues of doing SMTP authentication, and after reading the SMTP spec, starting coding up a solution using the Java Sasl API, which was doing most of the heavy lifting for me. This morning, however, I finally noticed the critical words in the Sasl Javadoc"since Java 1.5". Since we're not in a position to support Java 1.5 yet, that definitely tossed a speed bump in my path. LOGIN and PLAIN authentication are pretty simple to do without Sasl, and I believe I can also figure out how to do CRAM_MD5. Other forms of authentication are probably a bit beyond my current experience with crypto/security. How sophisticated do we need to be with this? Are LOGIN and PLAIN sufficient (combined with TLS support)? Note that this question also applies to the POP3 and IMAP implementations, since they also use Sasl authentication mechanisms. Rick
