[jira] Resolved: (GERONIMODEVTOOLS-594) Geronimo server can't be deleted when it has been stopped in GEP
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Delos Dai resolved GERONIMODEVTOOLS-594. Resolution: Fixed There are two reasons blocking the deleting. 1) URLClassLoader used in GeronimoRuntimeDelegate will never close the file it opened. This is an known issue of URLClassLoader, so replace it with JarFileClassLoader defined in Geronimo code. But it cause st.core depends on the runtime plugin, such runtime.v22. Although it works fine now, to avoid potential issues, suggest Geronimo server can place JarFileClassLoader into packages of runtime.common 2) The new function of account management in GEP will open user account properties under /var/security/ for reading&writing. The file has to be closed once reading or writing has been completed. #817504 for trunk and #817506 for 2.1.5 branch. > Geronimo server can't be deleted when it has been stopped in GEP > > > Key: GERONIMODEVTOOLS-594 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-594 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin >Affects Versions: 2.1.5, 2.2.0 >Reporter: Delos Dai >Assignee: Delos Dai >Priority: Minor > Fix For: 2.1.5, 2.2.0 > > > 1. In eclipse, create an server instance with GEP > 2. start the server instance in eclipse > 3. stop the server instance in eclipse > 4. delete the Geronimo server from file system, with file browser(such as > "windows explorer" > The server is not able to be deleted from file system. > Since the server has been stopped, the server should be able to be deleted > from file system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4887) java.lang.SecurityException: Invalid login when edit a running jmx server
[ https://issues.apache.org/jira/browse/GERONIMO-4887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vanessa Wang updated GERONIMO-4887: Description: 1 add a jmx localhost server 2 enable query for this server 3 click edit server Exception occurs: ava.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authenticator.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:224) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:191) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:310) at sun.rmi.transport.Transport$1.run(Transport.java:171) at java.security.AccessController.doPrivileged(AccessController.java:284) at sun.rmi.transport.Transport.serviceCall(Transport.java:167) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:547) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:802) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:661) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:735) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:267) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:245) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:154) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(RMIServerImpl_Stub.java:52) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2323) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:288-) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:259) at org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:105) at jsp.WEB_002dINF.view.monitoringEditServer_jsp._jspService(monitoringEditServer_jsp.java:177) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488) at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106) at org.apache.geronimo.monitoring.console.MonitoringPortlet.doEdit(MonitoringPortlet.java:407) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:253) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488) at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101) at org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:173) at org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152) at jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
[BUILD] branches/2.1: Failed for Revision: 817504
Geronimo Revision: 817504 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090922/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090922/unit-test-reports Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.5-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.5-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.5-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:183) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.5-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.1.5-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache-snapshots (http://repository.apache.org/snapshots), codehaus-snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.plugin
[jira] Assigned: (GERONIMO-4863) no other graphs can be chosen when I click "Modify this view" of a view
[ https://issues.apache.org/jira/browse/GERONIMO-4863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-4863: -- Assignee: Rex Wang > no other graphs can be chosen when I click "Modify this view" of a view > -- > > Key: GERONIMO-4863 > URL: https://issues.apache.org/jira/browse/GERONIMO-4863 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.2 > Environment: jdk6 > window xp sp2 >Reporter: Bin He >Assignee: Rex Wang > Attachments: monitoring.patch > > > 1、create a ejb server under monitoting porlet > 2、create several graphs(their names are 'a'、'b'、'c'、''d、'f') which belong to > the created ejb server > 3、create a new view ,and choose "a " graph to be shown in the view > 4、delete 'a' graph . So at this time you click the created view, there is no > graph shown and it's normal. > 5、next click "Modify this view" .There is nothing under the Graphs.I think > this is a problem because there still exists four graphs that can be chosen. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4875) "edit" button shows under "Created" label when i create a new view
[ https://issues.apache.org/jira/browse/GERONIMO-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-4875: -- Assignee: Rex Wang > "edit" button shows under "Created" label when i create a new view > - > > Key: GERONIMO-4875 > URL: https://issues.apache.org/jira/browse/GERONIMO-4875 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 > Environment: jdk6 > windows xp sp2 >Reporter: Bin He >Assignee: Rex Wang >Priority: Minor > Attachments: fix_view_layout.patch > > > Start server > Click monitoring porlet > Create a new view and you can see that the "edit" button is under "Created" > label.and there is nothing under "Modified" label and "Actions" label. > In geronomo 2114 and geronimo 2115 ,under "Created" and "Modified" is some > time ,under "Actions" is the Edit button. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4884) Using the default port number may cause unexpected build failure
[ https://issues.apache.org/jira/browse/GERONIMO-4884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-4884: -- Assignee: Rex Wang > Using the default port number may cause unexpected build failure > > > Key: GERONIMO-4884 > URL: https://issues.apache.org/jira/browse/GERONIMO-4884 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.2 >Reporter: Siqi Du >Assignee: Rex Wang >Priority: Minor > Fix For: 2.2 > > Attachments: fix_unittest.patch > > > When a geronimo is running -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4887) java.lang.SecurityException: Invalid login when edit a running jmx server
java.lang.SecurityException: Invalid login when edit a running jmx server - Key: GERONIMO-4887 URL: https://issues.apache.org/jira/browse/GERONIMO-4887 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1.5 Environment: Windows XP JDK1.5 Reporter: Vanessa Wang Priority: Minor 1 add a jmx localhost server 2 enable query for this server 3 click edit server Exception occurs: ava.lang.SecurityException: Invalid login at org.apache.geronimo.jmxremoting.Authenticator.authenticate(Authentica tor.java:73) at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.j ava:224) at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.jav a:191) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:310) at sun.rmi.transport.Transport$1.run(Transport.java:171) at java.security.AccessController.doPrivileged(AccessController.java:284 ) at sun.rmi.transport.Transport.serviceCall(Transport.java:167) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:5 47) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTranspor t.java:802) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport .java:661) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:735) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Stream RemoteCall.java:267) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java: 245) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:154) at javax.management.remote.rmi.RMIServerImpl_Stub.newClient(RMIServerImp l_Stub.java:52) at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.j ava:2323) at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:28 8-) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFacto ry.java:259) at org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnect or.java:105) at jsp.WEB_002dINF.view.monitoringEditServer_jsp._jspService(monitoringE ditServer_jsp.java:177) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:551) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:488) at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(P ortletRequestDispatcherImpl.java:106) at org.apache.geronimo.monitoring.console.MonitoringPortlet.doEdit(Monit oringPortlet.java:407) at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:253) at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:144) at org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208 ) at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisp atcher.java:646) at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationD ispatcher.java:551) at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDis patcher.java:488) at org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPort letInvokerService.java:167) at org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPort let
[jira] Created: (GERONIMODEVTOOLS-594) Geronimo server can't be deleted when it has been stopped in GEP
Geronimo server can't be deleted when it has been stopped in GEP Key: GERONIMODEVTOOLS-594 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-594 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.1.5, 2.2.0 Reporter: Delos Dai Assignee: Delos Dai Priority: Minor Fix For: 2.1.5, 2.2.0 1. In eclipse, create an server instance with GEP 2. start the server instance in eclipse 3. stop the server instance in eclipse 4. delete the Geronimo server from file system, with file browser(such as "windows explorer" The server is not able to be deleted from file system. Since the server has been stopped, the server should be able to be deleted from file system. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: 2.2 progress
That's great! I still hope the patch for GERONIMO-4874 can be committed. Should be a safe change. -Jack On Tue, Sep 22, 2009 at 8:26 AM, David Jencks wrote: > > On Sep 21, 2009, at 5:21 PM, David Jencks wrote: > > I think things are moving along for 2.2. >> >> - our last internal dependency, the tomcat fork, seems to have passed its >> vote, although I'd prefer it if Kevan would take a look. >> > > Um, need to look first, kevan already voted. > thanks > david jencks > > > >> - ActiveMQ is pushing release candidates. The first one showed no tck >> problems in geronimo. >> >> - OpenEJB IIUC is pretty much ready to release. >> >> --- >> >> Stuff to do: >> >> - tranql has been getting some attention lately. We should try to find a >> jdbc expert verify the list of non-fatal SQLCodes. I would like to >> rearrange tranql svn, but otherwise I'm OK with the code for now. After we >> verify stuff works I can release this. >> >> - We have a pluto fix that I'm hoping we can duplicate in geronimo >> somehow. IIRC we have a couple of pluto driver classes replaced in geronimo >> already, I hope we can do the same with this pluto fix. Pushing a pluto 1.x >> release could be difficult. >> >> - We don't know yet whether the maven release plugin and apache-release >> profile will work with geronimo. >> >> - review the jiras carefully. >> >> -- >> >> I'm hopeful that we may be able to release 2.2 this week. I'll ask again >> that if you are working on something you want to get in please reply to this >> message with a description and time estimate. >> >> many thanks >> david jencks >> >> >
[jira] Updated: (GERONIMO-4823) role-based administration capabilities
[ https://issues.apache.org/jira/browse/GERONIMO-4823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vanessa Wang updated GERONIMO-4823: Attachment: monitor-role-215-jetty&tomcat.patch patch for g21 jetty and tomcat > role-based administration capabilities > -- > > Key: GERONIMO-4823 > URL: https://issues.apache.org/jira/browse/GERONIMO-4823 > Project: Geronimo > Issue Type: New Feature > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.5, 2.2 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Attachments: monitor-role-215-jetty&tomcat.patch, monitor-role.patch > > > Provide role-based administration capabilities. > * Add a monitor group in geronimo-admin realm > * Only grant monitor group the permission to use the 4 portlets through > reconfiguring the filter rules > in console/console-portal-driver > 1, Monitoring portlet > 2, Information > 3, Java System Info > 4, Thread Pools > * Monitor group user can't create server/view/graph -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Proposed tranql svn reorganization
2009/9/22 Jack Cai > I think it's a good idea. A small problem that I see is currently all the > vendor connectors have different version numbers. If we are going to put > them under the same folder, shall we bump them to the same version? > So, if I update one vendor and change its version, I should update all the vendors' version? -Rex > -Jack > > > On Tue, Sep 22, 2009 at 4:41 AM, David Jencks wrote: > >> I've been irked for a while with the tranql svn organization and just bit >> myself by not being careful enough to check the extent of the changes IDEA >> made. I'd like to reorganize svn to make life clearer and simpler. >> >> 1. There are basically 2 projects, the query language itself which is not >> really under active development at the moment, and the j2ca connector >> framework which occasionally gets tweaked. I'd like to separate them. >> >> 2. We have a lot of foo/bar/trunk type directories. Our experience in the >> geronimo specs projects is that maven 2 has no problem with separately >> versioned subprojects all under trunk. >> >> So, I'd like to propose >> >> ql/ >> +/branches >> +/tags >> +/trunk >> >> ra/ >> +/branches >> +/tags >> +/trunk >> >> >> Under ra/trunk we'd have connector, connector-ra, and the individual >> vendor directories such as derby, oracle, etc. >> >> Thoughts? In particular does anyone think moving the existing tags will >> cause problems? >> >> thanks >> david jencks >> >> >
Re: Proposed tranql svn reorganization
I think it's a good idea. A small problem that I see is currently all the vendor connectors have different version numbers. If we are going to put them under the same folder, shall we bump them to the same version? -Jack On Tue, Sep 22, 2009 at 4:41 AM, David Jencks wrote: > I've been irked for a while with the tranql svn organization and just bit > myself by not being careful enough to check the extent of the changes IDEA > made. I'd like to reorganize svn to make life clearer and simpler. > > 1. There are basically 2 projects, the query language itself which is not > really under active development at the moment, and the j2ca connector > framework which occasionally gets tweaked. I'd like to separate them. > > 2. We have a lot of foo/bar/trunk type directories. Our experience in the > geronimo specs projects is that maven 2 has no problem with separately > versioned subprojects all under trunk. > > So, I'd like to propose > > ql/ > +/branches > +/tags > +/trunk > > ra/ > +/branches > +/tags > +/trunk > > > Under ra/trunk we'd have connector, connector-ra, and the individual vendor > directories such as derby, oracle, etc. > > Thoughts? In particular does anyone think moving the existing tags will > cause problems? > > thanks > david jencks > >
[jira] Updated: (GERONIMO-4870) NameService returns IOR pointing to host 0.0.0.0
[
https://issues.apache.org/jira/browse/GERONIMO-4870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4870:
--
Priority: Major (was: Blocker)
It's surely not an critical issue since the users could workaround this by
setting the correct hostname/ip.
> NameService returns IOR pointing to host 0.0.0.0
>
>
> Key: GERONIMO-4870
> URL: https://issues.apache.org/jira/browse/GERONIMO-4870
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CORBA
>Affects Versions: 2.2
> Environment: 2.2-SNAPSHOT
> Build 2009.09.10-08:12:53.147-0400
>Reporter: Jürgen Weber
>Assignee: Shawn Jiang
>
> For ServerHostname=0.0.0.0 NameService returns IOR pointing to host 0.0.0.0
> which then cannot be reached.
> See
> http://www.nabble.com/NameService-returns-IOR-pointing-to-host-0.0.0.0-td25391214s134.html
> Reproduce: install Corba MyTime sample.
> public static void main(String[] args) throws Exception
> {
> org.omg.CORBA.ORB orb = org.omg.CORBA.ORB.init(args,null);
> NamingContextExt nc =
>
> NamingContextExtHelper.narrow(orb.resolve_initial_references("NameService"));
> org.omg.CORBA.Object o = nc.resolve(nc.to_name("MyTime"));
> System.out.println(orb.object_to_string(o));
> }
> The IOR parses to
> object key is
> <#AB#AC#AB11252863023#00_RootPOA#00IdentityTokenNoSecurity#00corba-mytime-ejb-2.0.2.jar/MyTime#00#00corba-mytime-ejb-2.0.2.jar/MyTime>;
> no trustworthy most-specific-type info; unrecognized ORB type;
> reachable with IIOP 1.2 at host "0.0.0.0", port 6882
> (Blocker because Corba with EJB on server listening on all adresses does not
> work)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4836) Default Pluto URL parser could not hanle semicolon in the parameter values
[ https://issues.apache.org/jira/browse/GERONIMO-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758106#action_12758106 ] Ivan commented on GERONIMO-4836: Go ahead to commit the changes to 2.2 At revision: 817485, so that we could have more time to do the testing, I will leave this JIRA open until Geronimo 2.2 is released. The changes include: a. fix semicolon in the parameter value b. Use 0xz as the escape string for those special string c. Remove the duplicate slash in the url, it may cause issues in Jetty build with compact attribute off. > Default Pluto URL parser could not hanle semicolon in the parameter values > -- > > Key: GERONIMO-4836 > URL: https://issues.apache.org/jira/browse/GERONIMO-4836 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, Tomcat >Affects Versions: 2.2 >Reporter: Ivan > Fix For: 2.2 > > > While the input parameter contains semicolon, there will be some issues while > handlering those parameters. Seem that Pluto would ignore those parameters > after the semicolon. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4836) Default Pluto URL parser could not hanle semicolon in the parameter values
[ https://issues.apache.org/jira/browse/GERONIMO-4836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan reassigned GERONIMO-4836: -- Assignee: Ivan > Default Pluto URL parser could not hanle semicolon in the parameter values > -- > > Key: GERONIMO-4836 > URL: https://issues.apache.org/jira/browse/GERONIMO-4836 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console, Tomcat >Affects Versions: 2.2 >Reporter: Ivan >Assignee: Ivan > Fix For: 2.2 > > > While the input parameter contains semicolon, there will be some issues while > handlering those parameters. Seem that Pluto would ignore those parameters > after the semicolon. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758103#action_12758103 ] Jack Cai commented on GERONIMO-4222: Thanks Forrest for trying out the patch! Guess the problem is because you still have some tranql-connector-1.4.jar in your repo which get loaded by the server (each vendor RAR contains a copy of this jar). Once we replace all the 1.4 jars with the updated jars, the problem shall go away. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4658) Console should let you add/edit artifact-aliases. When installing a jar, you should be able to add an artifact alias so it replaces something else.
[ https://issues.apache.org/jira/browse/GERONIMO-4658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor Fang updated GERONIMO-4658: -- Attachment: GERONIMO-4658.patch > Console should let you add/edit artifact-aliases. When installing a jar, you > should be able to add an artifact alias so it replaces something else. > > > Key: GERONIMO-4658 > URL: https://issues.apache.org/jira/browse/GERONIMO-4658 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 >Reporter: David Jencks > Fix For: 2.2 > > Attachments: GERONIMO-4658.patch > > > Should be able to edit artifact-aliases in the console. I think they are > available through the local attribute manager gbean. They can certainly be > installed there. > In particular, when adding a jar, you should be able to add an artifact alias > at the same time so it replaces something else. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4826) Some monitoring fields are always zero.
[
https://issues.apache.org/jira/browse/GERONIMO-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang resolved GERONIMO-4826.
---
Resolution: Fixed
Added the hints to the help page of monitoring portlet in branch 21, branch 22,
and trunk. I'm wondering if we have document somewhere to address this
monitoring attributes difference between
Jetty connector and Tomcat connector ?
> Some monitoring fields are always zero.
> ---
>
> Key: GERONIMO-4826
> URL: https://issues.apache.org/jira/browse/GERONIMO-4826
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>
> It's strange, we need to figure out why they are always zero.
> {noformat}
> TomcatWebConnector
> Active Request Count (always zero)
> Busy Threads Current
> Busy Threads Max
> Busy Threads Min (always zero)
> Bytes Received
> Bytes Sent
> Error Count
> Open Connections Current (always zero)
> Open Connections Max (always zero)
> Open Connections Min (always zero)
> Request Time Count
> Request Time MaxTime
> Request Time MinTime (always zero)
> Request Time TotalTime
> {noformat}
> {noformat}
> TomcatWebSSLConnector
> Active Request Count (always zero)
> Busy Threads Current
> Busy Threads Max
> Busy Threads Min (always zero)
> Bytes Received
> Bytes Sent
> Error Count
> Open Connections Current(always zero)
> Open Connections Max (always zero)
> Open Connections Min(always zero)
> Request Time Count
> Request Time MaxTime
> Request Time MinTime (always zero)
> Request Time TotalTime
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4826) Some monitoring fields are always zero.
[
https://issues.apache.org/jira/browse/GERONIMO-4826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758100#action_12758100
]
Shawn Jiang commented on GERONIMO-4826:
---
For this one:
{noformat}
Active Request Count (always zero)
{noformat}
I saw a help message in help of monitoring portlet:
{noformat}
"Hint : Try 'Request Count' for JettyWebConnector"
{noformat}
Seems this is a known issue.I suggest to also add
{noformat}
"Hint : Try 'Open Connections' for JettyWebConnector"
{noformat}
> Some monitoring fields are always zero.
> ---
>
> Key: GERONIMO-4826
> URL: https://issues.apache.org/jira/browse/GERONIMO-4826
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.3, 2.1.4, 2.1.5, 2.2
>Reporter: Shawn Jiang
>Assignee: Shawn Jiang
>
> It's strange, we need to figure out why they are always zero.
> {noformat}
> TomcatWebConnector
> Active Request Count (always zero)
> Busy Threads Current
> Busy Threads Max
> Busy Threads Min (always zero)
> Bytes Received
> Bytes Sent
> Error Count
> Open Connections Current (always zero)
> Open Connections Max (always zero)
> Open Connections Min (always zero)
> Request Time Count
> Request Time MaxTime
> Request Time MinTime (always zero)
> Request Time TotalTime
> {noformat}
> {noformat}
> TomcatWebSSLConnector
> Active Request Count (always zero)
> Busy Threads Current
> Busy Threads Max
> Busy Threads Min (always zero)
> Bytes Received
> Bytes Sent
> Error Count
> Open Connections Current(always zero)
> Open Connections Max (always zero)
> Open Connections Min(always zero)
> Request Time Count
> Request Time MaxTime
> Request Time MinTime (always zero)
> Request Time TotalTime
> {noformat}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4849) Such warning will be shown after deleted a remote monitoring server via JMX
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4849. --- Resolution: Fixed Applied the patch to branch 21, branch 22, trunk. Thanks Siqi for the patch ! > Such warning will be shown after deleted a remote monitoring server via JMX > --- > > Key: GERONIMO-4849 > URL: https://issues.apache.org/jira/browse/GERONIMO-4849 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.2 > Environment: winxp sp3, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang > Fix For: 2.2 > > Attachments: monitor_jmx_2.1.patch, monitoring_jmx.patch > > > The following warning will be shown after these steps. > First, create a remote monitoring server via JMX and meanwhile, start the > remote server. Then, you delete the monitoring server and stop the remote > server. You will see the following information via log or command line. > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: >
[jira] Assigned: (GERONIMO-4849) Such warning will be shown after deleted a remote monitoring server via JMX
[ https://issues.apache.org/jira/browse/GERONIMO-4849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang reassigned GERONIMO-4849: - Assignee: Shawn Jiang > Such warning will be shown after deleted a remote monitoring server via JMX > --- > > Key: GERONIMO-4849 > URL: https://issues.apache.org/jira/browse/GERONIMO-4849 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.2 > Environment: winxp sp3, jdk 1.6 >Reporter: Shiny Cheng >Assignee: Shawn Jiang > Fix For: 2.2 > > Attachments: monitor_jmx_2.1.patch, monitoring_jmx.patch > > > The following warning will be shown after these steps. > First, create a remote monitoring server via JMX and meanwhile, start the > remote server. Then, you delete the monitoring server and stop the remote > server. You will see the following information via log or command line. > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > WARN [misc] Failed to restart: java.io.IOException: Failed to get a RMI > stub: javax.naming.ServiceUnavailableException [Root exception is > java.rmi.ConnectException: Connection refused to host: 9.123.233.70; nested > exception is: > java.net.ConnectException: Connection refused: connect] > WARN [rmi] Failed to call the method close():java.rmi.ConnectException: > Connection refused to host: 9.123.233.70; nested exception is: > java.net.ConnectException: Connection refused: connect > WARN [misc] Failed to check connection: java.net.ConnectException: > Connection refused: connect > WARN [misc] stopping > I wonder maybe the
[jira] Resolved: (GERONIMO-4882) some doc update in G22 might be caused by bugs in code.
[ https://issues.apache.org/jira/browse/GERONIMO-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4882. --- Resolution: Fixed Fix Version/s: 3.0 2.2 #2 is not applicable to this JIRA. Fixed #1 and #3, we need to 1, test farming and native tomcat clustering function. 2, update doc to reflect the changes. > some doc update in G22 might be caused by bugs in code. > --- > > Key: GERONIMO-4882 > URL: https://issues.apache.org/jira/browse/GERONIMO-4882 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: documentation >Affects Versions: 2.2 >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Fix For: 2.2, 3.0 > > > Following Doc changes are all related j2eeType, which might be bugs when > migrating the GBean to annotation version. I guess j2eeType is missed during > the migration. > 1, Farming: http://cwiki.apache.org/GMOxDOC21/farming.html >http://cwiki.apache.org/GMOxDOC22/farming-using-deployment.html > 2, Tomcat Virtual host: > http://cwiki.apache.org/GMOxDOC21/configuring-virtual-hosts-in-geronimo-tomcat.html > > http://cwiki.apache.org/GMOxDOC22/configuring-virtual-host-in-tomcat.html > (not sure if it's working now, not rested recently.) > 3, Tomcat native clustering:Details in > https://issues.apache.org/jira/browse/GERONIMO-4804 > Doc in G2.2 > http://cwiki.apache.org/GMOxDOC22/tomcat-native-clustering.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 817461
Geronimo Revision: 817461 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/unit-test-reports [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-2 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20.0 -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-2 from the specified remote repositories: amq-protobuf-staging (https://repository.apache.org/content/repositories/activemq-staging-036/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), snapshots (http://snapshots.repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), amq-staging (https://repository.apache.org/content/repositories/activemq-staging-030/), ibiblio.org (http://repo.exist.com/maven2), tomcat-fork-staging (https://repository.apache.org/content/repositories/geronimo-staging-035/), codehaus.org (http://repository.codehaus.org), jpa-spec-staging (https://repository.apache.org/content/repositories/geronimo-staging-021/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:599) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.ext.tomcat -DartifactId=jasper -Dversion=6.0.20.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-2 2) org.apache.geronimo.ext.tomcat:jasper:jar:6.0.20.0 -- 1 required artifact is missing. for artifact: org.codehaus.mojo.jspc:jspc-maven-plugin:maven-plugin:2.0-alpha-2 from the specified remote repositories: amq-protobuf-staging (https://repository.apache.org/content/repositories/activemq-staging-036/), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots), snapshots (http://snapshots.repository.codehaus.org), apache-snapshots (http://people.apache.org/repo/m2-snapshot-repository), amq-staging (https://repository.apache.org/content/repositories/activemq
[jira] Resolved: (GERONIMO-4886) Request Time Count attribute does not exist in connector mbean.
[ https://issues.apache.org/jira/browse/GERONIMO-4886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn Jiang resolved GERONIMO-4886. --- Resolution: Fixed Fix Version/s: 3.0 2.2 2.1.5 Fixed in 21branch, 22 branch, and trunk. > Request Time Count attribute does not exist in connector mbean. > --- > > Key: GERONIMO-4886 > URL: https://issues.apache.org/jira/browse/GERONIMO-4886 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0 > Environment: tomcat build. >Reporter: Shawn Jiang >Assignee: Shawn Jiang > Fix For: 2.1.5, 2.2, 3.0 > > > Request Time Count attribute is always null when using JMX to monitor tomcat > connectors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4886) Request Time Count attribute does not exist in connector mbean.
Request Time Count attribute does not exist in connector mbean. --- Key: GERONIMO-4886 URL: https://issues.apache.org/jira/browse/GERONIMO-4886 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: monitoring Affects Versions: 2.1.4, 2.1.5, 2.2, 3.0 Environment: tomcat build. Reporter: Shawn Jiang Assignee: Shawn Jiang Request Time Count attribute is always null when using JMX to monitor tomcat connectors. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[RESULT] [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try
Vote passes with 6 +1 (xuhaihong, jmchugh, kmiller, jbohn, dwoods, djencks) and no other votes. I'll promote the staged artifacts and move the site. many thanks! david jencks On Sep 18, 2009, at 6:56 PM, David Jencks wrote: I've removed the leftover archetype scripts, fixed up the pom names so the NOTICE files look nicer, added license goo to the script sources in the unreleased archetype, as well as a script to remove the goo, and tried again. I think this answers all the problems Kevan and Joe found except getting my key in to the appropriate KEYS file. For various reasons we are now using a forked copy of tomcat derived from the tomcat 6.0.20 release, built with maven, with maven dependencies, etc etc. The code changes from tomcat 6.0.20 are: r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line GERONIMO-4566 port fix for tomcats https://issues.apache.org/bugzilla/show_bug.cgi?id=47378 r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1 line GERONIMO-3451 "Restricted listeners property file not found" error logged during Tomcat server startup (Patch from Shawn Jiang) r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Some customizations of Tomcat properties. Server info is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the future. r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in MapperListener.registerHost(). I would expect that this fix would be in 6.0.22. So prolly won't require merging in the future r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This includes revision numbers 784303 and 784304. Does not include 787519, which should already be in 6.0.20 r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line fill-in ServerInfo properties - but I can't add that to archetype as ant task will fail Staging repo: https://repository.apache.org/content/repositories/geronimo-staging-035/ site staged at: http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/ svn tag at: https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.20.0 The structure is a still little weird but I still don't really want to spend time fixing it up. [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks david jencks
Re: 2.2 progress
On Sep 21, 2009, at 5:21 PM, David Jencks wrote: I think things are moving along for 2.2. - our last internal dependency, the tomcat fork, seems to have passed its vote, although I'd prefer it if Kevan would take a look. Um, need to look first, kevan already voted. thanks david jencks - ActiveMQ is pushing release candidates. The first one showed no tck problems in geronimo. - OpenEJB IIUC is pretty much ready to release. --- Stuff to do: - tranql has been getting some attention lately. We should try to find a jdbc expert verify the list of non-fatal SQLCodes. I would like to rearrange tranql svn, but otherwise I'm OK with the code for now. After we verify stuff works I can release this. - We have a pluto fix that I'm hoping we can duplicate in geronimo somehow. IIRC we have a couple of pluto driver classes replaced in geronimo already, I hope we can do the same with this pluto fix. Pushing a pluto 1.x release could be difficult. - We don't know yet whether the maven release plugin and apache- release profile will work with geronimo. - review the jiras carefully. -- I'm hopeful that we may be able to release 2.2 this week. I'll ask again that if you are working on something you want to get in please reply to this message with a description and time estimate. many thanks david jencks
OSGI progress
Over the weekend I got my sandbox osgi framework to build and generate all the plugins as osgi bundles. This involves running some of the geronimo server on osgi/felix inside maven. The dependency management system seems to work OK at least for starting bundles. I also started doing a little bit of code cleanup. I think the next step will be to get the framework server running in standalone karaf or felix. Hopefully this will be no harder than getting it running in embedded felix in maven. thanks david jencks
2.2 progress
I think things are moving along for 2.2. - our last internal dependency, the tomcat fork, seems to have passed its vote, although I'd prefer it if Kevan would take a look. - ActiveMQ is pushing release candidates. The first one showed no tck problems in geronimo. - OpenEJB IIUC is pretty much ready to release. --- Stuff to do: - tranql has been getting some attention lately. We should try to find a jdbc expert verify the list of non-fatal SQLCodes. I would like to rearrange tranql svn, but otherwise I'm OK with the code for now. After we verify stuff works I can release this. - We have a pluto fix that I'm hoping we can duplicate in geronimo somehow. IIRC we have a couple of pluto driver classes replaced in geronimo already, I hope we can do the same with this pluto fix. Pushing a pluto 1.x release could be difficult. - We don't know yet whether the maven release plugin and apache- release profile will work with geronimo. - review the jiras carefully. -- I'm hopeful that we may be able to release 2.2 this week. I'll ask again that if you are working on something you want to get in please reply to this message with a description and time estimate. many thanks david jencks
[jira] Assigned: (GERONIMO-4834) artifact aliasing does not seem to work for configuration id's
[ https://issues.apache.org/jira/browse/GERONIMO-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks reassigned GERONIMO-4834: -- Assignee: Vamsavardhana Reddy > artifact aliasing does not seem to work for configuration id's > -- > > Key: GERONIMO-4834 > URL: https://issues.apache.org/jira/browse/GERONIMO-4834 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 2.1.4 >Reporter: Vamsavardhana Reddy >Assignee: Vamsavardhana Reddy > Fix For: 2.1.5, 2.2 > > > Artifact aliasing does not seem to work for configuration ids. I have > encountered the following problem while trying to change the JPA provider > from OpenJPA to TopLink. > I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace > openjpa car. I have added the following line in artifact_aliases.properties: > org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car > But when I start the server, openjpa//car is getting started as openejb//car > has a dependency on openjpa//car. Ideally I would expect toplink//car to be > used by openejb//car because of the aliasing above. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4834) artifact aliasing does not seem to work for configuration id's
[ https://issues.apache.org/jira/browse/GERONIMO-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12758075#action_12758075 ] David Jencks commented on GERONIMO-4834: I think vamsi told me that the problem was that you may need to include two lines for each alias, with and without the version in the left hand side. I think this is explained in the comment at the top of artifact-aliases.properties, but not in every pom you may write :-). Vamsi, could you verify this and close the issue if appropriate? > artifact aliasing does not seem to work for configuration id's > -- > > Key: GERONIMO-4834 > URL: https://issues.apache.org/jira/browse/GERONIMO-4834 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: core >Affects Versions: 2.1.4 >Reporter: Vamsavardhana Reddy > Fix For: 2.1.5, 2.2 > > > Artifact aliasing does not seem to work for configuration ids. I have > encountered the following problem while trying to change the JPA provider > from OpenJPA to TopLink. > I have created a configuration o.a.g.configs/toplink/2.1.4/car to replace > openjpa car. I have added the following line in artifact_aliases.properties: > org.apache.geronimo.configs/openjpa//car=org.apache.geronimo.configs/toplink/2.1.4/car > But when I start the server, openjpa//car is getting started as openejb//car > has a dependency on openjpa//car. Ideally I would expect toplink//car to be > used by openejb//car because of the aliasing above. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Desirable non-automated testing for 2.2
There are three areas that I think need some manual testing for 2.2 if anyone can take a look at these I'd really appreciate it. 1. activemq embedded web console. (NOT the amq support in our web console). We are running the native amq web console as a plugin in 2.2. I noticed that the latest 5.3.0 release candidate tried to pull in an enormous number of new dependencies, which I excluded. I have no idea if the console still works :-) 2. CA Helper app. I have some trouble remembering how this works, but I looked at the front page a few days ago and wasn't convinced it was working. It might be that you need to set up some stuff for it to work on before it looks like it is working it could be just fine. 3. There's been a lot of churn in the tranql wrappers in the last few days. We really need to make sure they all work before I release them. I've just pushed snapshots of everything. Many thanks david jencks
[BUILD] branches/2.2: Failed for Revision: 817349
Geronimo Revision: 817349 built with tests included
See the full build-1400.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/build-1400.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 80 minutes 6 seconds
[INFO] Finished at: Mon Sep 21 15:26:26 EDT 2009
[INFO] Final Memory: 325M/975M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/logs-1400-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/logs-1400-jetty/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:56.134
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:21.131)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:40.492)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:46.645)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:23.564)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:21.283)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:41.540) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:13.642)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:58.991)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:03.871)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:52.647)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:39.440)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.447)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:40.799)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:53.790)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:25.271)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.541)
[INFO] enterprise-testsuite/sec-client-tests RUNNING
[INFO] enterprise-testsuite/sec-client-tests SUCCESS (0:00:36.710)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:01:00.044)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:58.781)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.760)
[INFO] web-testsuite/test-2.5-servlets
Proposed tranql svn reorganization
I've been irked for a while with the tranql svn organization and just bit myself by not being careful enough to check the extent of the changes IDEA made. I'd like to reorganize svn to make life clearer and simpler. 1. There are basically 2 projects, the query language itself which is not really under active development at the moment, and the j2ca connector framework which occasionally gets tweaked. I'd like to separate them. 2. We have a lot of foo/bar/trunk type directories. Our experience in the geronimo specs projects is that maven 2 has no problem with separately versioned subprojects all under trunk. So, I'd like to propose ql/ +/branches +/tags +/trunk ra/ +/branches +/tags +/trunk Under ra/trunk we'd have connector, connector-ra, and the individual vendor directories such as derby, oracle, etc. Thoughts? In particular does anyone think moving the existing tags will cause problems? thanks david jencks
[BUILD] trunk: Failed for Revision: 817372
Geronimo Revision: 817372 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/unit-test-reports
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 12 source files to
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/test-classes
[WARNING]
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/src/test/java/org/apache/geronimo/jetty7/ClassLoaderTest.java:[50,77]
[deprecation] toURL() in java.io.File has been deprecated
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.jetty7.ApplicationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.393 sec
Running org.apache.geronimo.jetty7.connector.ConnectorGBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.apache.geronimo.jetty7.GBeanInfoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.geronimo.jetty7.SecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.011 sec
Running org.apache.geronimo.jetty7.ClassLoaderTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Running org.apache.geronimo.jetty7.ContainerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.065 sec
Running org.apache.geronimo.jetty7.StatTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.078 sec
Running org.apache.geronimo.jetty7.connector.HTTPConnectorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec
Running org.apache.geronimo.jetty7.security.BuiltInAuthMethodTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Results :
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/geronimo-jetty7-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-jetty7/3.0-SNAPSHOT/geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Jetty :: Jetty 7
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757938#action_12757938 ] Forrest Xia commented on GERONIMO-4222: --- Results of some tries: 1. Derby ones work 2. PostgreSQL local one works 3. MySQl local one works However, there are some strange classloader problem when I am trying application-wide datasource. If the classloader behavior keeps as default(parent first), then PostgreSQL and MySQL local datasource cannot be created, and throw an exception as below: org/tranql/connector/jdbc/AbstractLocalDataSourceMCF.(Ljavax/sql/ConnectionPoolDataSource;Z)V java.lang.NoSuchMethodError: org/tranql/connector/jdbc/AbstractLocalDataSourceMCF.(Ljavax/sql/ConnectionPoolDataSource;Z)V at org.tranql.connector.postgresql.PGSimpleLocalMCF.(PGSimpleLocalMCF.java:34) So I add to the deployment plan and then they work fine! > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] branches/2.2: Failed for Revision: 817214
Geronimo Revision: 817214 built with tests included
See the full build-0800.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/build-0800.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 107 minutes
[INFO] Finished at: Mon Sep 21 10:01:02 EDT 2009
[INFO] Final Memory: 321M/959M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/logs-0800-tomcat/
Assembly: jetty
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090921/logs-0800-jetty/
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-jetty7-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-jetty7-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-jetty7-javaee5/2.2-SNAPSHOT/geronimo-jetty7-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/2.2/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/2.2/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:52.739
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/2.2/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:21.509)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:40.834)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:45.855)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:23.541)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:31.338)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:37.571) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:14.048)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:57.045)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:00.009)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:51.802)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:38.841)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:33.475)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:40.516)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:53.853)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:22.077)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.509)
[INFO] enterprise-testsuite/sec-client-tests RUNNING
[INFO] enterprise-testsuite/sec-client-tests SUCCESS (0:00:35.838)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:59.014)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:59.292)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:37.314)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[jira] Closed: (GERONIMO-4761) MBean not found exception: agent-car-jmx
[
https://issues.apache.org/jira/browse/GERONIMO-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang closed GERONIMO-4761.
-
Resolution: Invalid
Fix Version/s: 3.0
2.2
2.1.5
This become invalid after following JIRA is fixed.
https://issues.apache.org/jira/browse/GERONIMO-4883
> MBean not found exception: agent-car-jmx
> -
>
> Key: GERONIMO-4761
> URL: https://issues.apache.org/jira/browse/GERONIMO-4761
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.5, 2.2
> Environment: From console
>Reporter: Chi Runhua
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2, 3.0
>
> Attachments: GERONIMO-4761.patch
>
>
> 1. Log in to console and go to *Monitoring* portlet,
> 2. Click *Add a new server* and choose protocol as JMX
> 3. Fill in other fields as requested, then click *Add*
> Exception thrown from command line:
> {code}
> java.lang.Exception: [ERROR] Required mbean not found: agent-car-jmx
> at
> org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:123)
> at
> org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:55)
> at
> jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:271)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
> at
> org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
> at
> org.apache.geronimo.monitoring.console.MonitoringPortlet.doEdit(MonitoringPortlet.java:412)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:253)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
> at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
> at
> org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
> at
> org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
> at
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
> at
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
> at
> jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(d
[jira] Assigned: (GERONIMO-4761) MBean not found exception: agent-car-jmx
[
https://issues.apache.org/jira/browse/GERONIMO-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang reassigned GERONIMO-4761:
-
Assignee: Shawn Jiang
> MBean not found exception: agent-car-jmx
> -
>
> Key: GERONIMO-4761
> URL: https://issues.apache.org/jira/browse/GERONIMO-4761
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: monitoring
>Affects Versions: 2.1.5, 2.2
> Environment: From console
>Reporter: Chi Runhua
>Assignee: Shawn Jiang
>Priority: Minor
> Attachments: GERONIMO-4761.patch
>
>
> 1. Log in to console and go to *Monitoring* portlet,
> 2. Click *Add a new server* and choose protocol as JMX
> 3. Fill in other fields as requested, then click *Add*
> Exception thrown from command line:
> {code}
> java.lang.Exception: [ERROR] Required mbean not found: agent-car-jmx
> at
> org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:123)
> at
> org.apache.geronimo.monitoring.console.MRCConnector.(MRCConnector.java:55)
> at
> jsp.WEB_002dINF.view.monitoringNormal_jsp._jspService(monitoringNormal_jsp.java:271)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(PortletRequestDispatcherImpl.java:106)
> at
> org.apache.geronimo.monitoring.console.MonitoringPortlet.normalView(MonitoringPortlet.java:455)
> at
> org.apache.geronimo.monitoring.console.MonitoringPortlet.doEdit(MonitoringPortlet.java:412)
> at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:253)
> at javax.portlet.GenericPortlet.render(GenericPortlet.java:175)
> at org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:153)
> at
> org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:208)
> at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:693)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167)
> at
> org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPortletInvokerService.java:101)
> at
> org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainerImpl.java:172)
> at
> org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:152)
> at
> jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dskin_jsp.java:102)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
> at
> org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
> at
> org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
> at
> org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrary.java:968)
> at
> jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEach_005f0(default_002dtheme_jsp.java:215)
> at
> jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002dtheme_jsp.java:120)
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70
[BUILD] trunk: Failed for Revision: 817235
Geronimo Revision: 817235 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/unit-test-reports
[INFO]
[INFO] Building Geronimo Plugins, Jetty :: Jetty 7
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.alwaysonprofileactiva...@54145414
[WARNING] Component returned which is not the same manager. Ignored.
component=org.apache.maven.profiles.activation.fileprofileactiva...@54145414
[WARNING] Component
Re: [VOTE] release geronimo's forked mavenized tomcat 6.0.20.0 2nd try
+1 Donald David Jencks wrote: I've removed the leftover archetype scripts, fixed up the pom names so the NOTICE files look nicer, added license goo to the script sources in the unreleased archetype, as well as a script to remove the goo, and tried again. I think this answers all the problems Kevan and Joe found except getting my key in to the appropriate KEYS file. For various reasons we are now using a forked copy of tomcat derived from the tomcat 6.0.20 release, built with maven, with maven dependencies, etc etc. The code changes from tomcat 6.0.20 are: r814083 | djencks | 2009-09-11 16:36:16 -0700 (Fri, 11 Sep 2009) | 1 line GERONIMO-4566 port fix for tomcats https://issues.apache.org/bugzilla/show_bug.cgi?id=47378 r799220 | xuhaihong | 2009-07-30 02:53:30 -0700 (Thu, 30 Jul 2009) | 1 line GERONIMO-3451 "Restricted listeners property file not found" error logged during Tomcat server startup (Patch from Shawn Jiang) r790767 | kevan | 2009-07-02 17:09:12 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Some customizations of Tomcat properties. Server info is now: Apache Geronimo (Embedded Tomcat). Will want to merge in the future. r790765 | kevan | 2009-07-02 17:06:02 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of 783305 from tomcat/tc6.0.x/trunk/. Fixes NPE in MapperListener.registerHost(). I would expect that this fix would be in 6.0.22. So prolly won't require merging in the future r790742 | kevan | 2009-07-02 14:41:08 -0700 (Thu, 02 Jul 2009) | 1 line GERONIMO-4685 Merge of Tomcat patches from 6.0.18 to 6.0.20. This includes revision numbers 784303 and 784304. Does not include 787519, which should already be in 6.0.20 r790359 | gawor | 2009-07-01 13:23:00 -0700 (Wed, 01 Jul 2009) | 1 line fill-in ServerInfo properties - but I can't add that to archetype as ant task will fail Staging repo: https://repository.apache.org/content/repositories/geronimo-staging-035/ site staged at: http://people.apache.org/~djencks/staging-site/maven/external/tomcat-parent-6.0.20/6.0.20.0/ svn tag at: https://svn.apache.org/repos/asf/geronimo/external/tags/tomcat-parent-6.0.20.0 The structure is a still little weird but I still don't really want to spend time fixing it up. [ ] +1 go for it [ ] 0 [ ] -1 whoa, hold on a minute Vote open 72 hours thanks david jencks
[jira] Assigned: (GERONIMO-4833) javax.resource.ResourseException in too many graphs in one view after disable server
[ https://issues.apache.org/jira/browse/GERONIMO-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai reassigned GERONIMO-4833: -- Assignee: Jack Cai > javax.resource.ResourseException in too many graphs in one view after disable > server > > > Key: GERONIMO-4833 > URL: https://issues.apache.org/jira/browse/GERONIMO-4833 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.1.4 > Environment: Windows XP sp2 > Sun jdk 1.5 >Reporter: Vanessa Wang >Assignee: Jack Cai > > 1 add a jmx server > 2 add a view with more than 15 graphs > 3 disable the jmx server > 4 click the new view you just added > error occur: > SQL state: null > SQL error: 0 > java.sql.SQLException > at > org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:6) > at > org.apache.geronimo.monitoring.console.util.DBManager.createConnectin(DBManager.java:53) > at > org.apache.geronimo.monitoring.console.util.DBManager.(DBManagr.java:39) > at > org.apache.geronimo.monitoring.console.GraphsBuilder.buildOneDB(GrapsBuilder.java:48) > at > jsp.WEB_002dINF.view.monitoringPage_jsp._jspService(monitoringPage_jp.java:139) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(ortletRequestDispatcherImpl.java:106) > at > org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonioringPortlet.java:313) > at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) > at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) > at > org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:141) > at > org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:20) > at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPorletInvokerService.java:167) > at > org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPorletInvokerService.java:101) > at > org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainermpl.java:173) > at > org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:12) > at > jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dkin_jsp.java:102) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrar.java:968) > at > jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspx_meth_c_005fforEac_005f0(default_002dtheme_jsp.java:238) > at > jsp.WEB_002dINF.themes.default_002dtheme_jsp._jspService(default_002theme_jsp.java:124) > at org
[jira] Commented: (GERONIMO-4833) javax.resource.ResourseException in too many graphs in one view after disable server
[ https://issues.apache.org/jira/browse/GERONIMO-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757865#action_12757865 ] Jack Cai commented on GERONIMO-4833: There are quite a few problems in the monitoring code in branch 2.1. Fortunately David has heavily refactored the code for 2.2. For now, I will be creating a fix just for this problem for 2.1. > javax.resource.ResourseException in too many graphs in one view after disable > server > > > Key: GERONIMO-4833 > URL: https://issues.apache.org/jira/browse/GERONIMO-4833 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: monitoring >Affects Versions: 2.1.4 > Environment: Windows XP sp2 > Sun jdk 1.5 >Reporter: Vanessa Wang > > 1 add a jmx server > 2 add a view with more than 15 graphs > 3 disable the jmx server > 4 click the new view you just added > error occur: > SQL state: null > SQL error: 0 > java.sql.SQLException > at > org.tranql.connector.jdbc.DataSource.getConnection(DataSource.java:6) > at > org.apache.geronimo.monitoring.console.util.DBManager.createConnectin(DBManager.java:53) > at > org.apache.geronimo.monitoring.console.util.DBManager.(DBManagr.java:39) > at > org.apache.geronimo.monitoring.console.GraphsBuilder.buildOneDB(GrapsBuilder.java:48) > at > jsp.WEB_002dINF.view.monitoringPage_jsp._jspService(monitoringPage_jp.java:139) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.include(ortletRequestDispatcherImpl.java:106) > at > org.apache.geronimo.monitoring.console.MonitoringPortlet.doView(MonioringPortlet.java:313) > at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) > at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) > at > org.apache.geronimo.console.BasePortlet.render(BasePortlet.java:141) > at > org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:20) > at org.apache.pluto.core.PortletServlet.doGet(PortletServlet.java:139) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:693) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPorletInvokerService.java:167) > at > org.apache.pluto.core.DefaultPortletInvokerService.render(DefaultPorletInvokerService.java:101) > at > org.apache.pluto.core.PortletContainerImpl.doRender(PortletContainermpl.java:173) > at > org.apache.pluto.driver.tags.PortletTag.doStartTag(PortletTag.java:12) > at > jsp.WEB_002dINF.themes.portlet_002dskin_jsp._jspService(portlet_002dkin_jsp.java:102) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(AppicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDisatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(Applicationispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDipatcher.java:488) > at > org.apache.jasper.runtime.JspRuntimeLibrary.include(JspRuntimeLibrar.java:968) > at > jsp.WEB_002dINF.themes.default_002dt
[BUILD] trunk: Failed for Revision: 817173
Geronimo Revision: 817173 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090921/unit-test-reports
[INFO] Copying 3 resources
[INFO] [compiler:testCompile]
[INFO] Compiling 12 source files to
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/test-classes
[WARNING]
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/src/test/java/org/apache/geronimo/jetty7/ClassLoaderTest.java:[50,77]
[deprecation] toURL() in java.io.File has been deprecated
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/surefire-reports
---
T E S T S
---
Running org.apache.geronimo.jetty7.ApplicationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.405 sec
Running org.apache.geronimo.jetty7.connector.ConnectorGBeanTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 sec
Running org.apache.geronimo.jetty7.GBeanInfoTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.079 sec
Running org.apache.geronimo.jetty7.SecurityTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.012 sec
Running org.apache.geronimo.jetty7.ClassLoaderTest
Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.031 sec
Running org.apache.geronimo.jetty7.ContainerTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.062 sec
Running org.apache.geronimo.jetty7.StatTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.083 sec
Running org.apache.geronimo.jetty7.connector.HTTPConnectorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Running org.apache.geronimo.jetty7.security.BuiltInAuthMethodTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec
Results :
Tests run: 22, Failures: 0, Errors: 0, Skipped: 0
[INFO] [jar:jar]
[INFO] Building jar:
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/geronimo/geronimo/trunk/plugins/jetty7/geronimo-jetty7/target/geronimo-jetty7-3.0-SNAPSHOT.jar
to
/home/geronimo/.m2/repository/org/apache/geronimo/modules/geronimo-jetty7/3.0-SNAPSHOT/geronimo-jetty7-3.0-SNAPSHOT.jar
[INFO]
[INFO] Building Geronimo Plugins, Jetty :: Jetty 7
[INFO]task-segment: [install]
[INFO]
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/resources
[INFO] skip non existing resourceDirectory
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [car:validate-configuration]
[INFO] [car:prepare-plan]
[INFO] Generated:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/target/work/plan.xml
[INFO] [car:verify-no-dependency-change]
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.xml
if you are happy with the dependency changes.
[INFO]
[INFO] Trace
org.apache.maven.BuildFailureException: Dependencies have changed:
Removed dependencies are saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.removed.xml
Tree listing is saved here:
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/treeListing.txt
Delete
/home/geronimo/geronimo/trunk/plugins/jetty7/jetty7/src/main/history/dependencies.xml
if you are happy with the dependency changes.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:580)
[jira] Commented: (GERONIMO-4222) Database pool unusable after database unavailable for awhile
[ https://issues.apache.org/jira/browse/GERONIMO-4222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757852#action_12757852 ] David Jencks commented on GERONIMO-4222: Jack, I was working on the sqlstate exception sorter and just implemented ConnectionPoolDataSource wrapping before I saw your work. I'll compare our approaches and look at the vendor wrappers tomorrow. Radim, I haven't looked into this in a long time, but I think that the standard behavior for uncommitted work when putting a connection back in the pool is to commit it. However, the problem we are dealing with here is that on a connection error, after removing the connection from the pool so it won't be used ever again, we are not trying to rollback work on it before destroying it. If we could tell if the connection was actually still usable, we wouldn't close it at all if the rollback could succeed... so two things to do are to improve our decision of when to close the connection (using a ConnectionPoolDataSource, and a better ExceptionSorter) and trying to rollback before destroy just in case we were wrong about needing to destroy the connection. > Database pool unusable after database unavailable for awhile > > > Key: GERONIMO-4222 > URL: https://issues.apache.org/jira/browse/GERONIMO-4222 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.0.2, 2.1.3, 2.1.4 > Environment: Red Hat Enterprise Linux Server v5.2 > WAS-CE v2.0.0.1, based on Geronimo v2.0.2 >Reporter: David Frahm >Assignee: Jack Cai > Fix For: Wish List > > Attachments: before and after wasce restart.txt, connector.patch, > PGtrial.patch, stacktrace.txt, > tranql-connector-derby-embed-local-1.5-SNAPSHOT.rar, > tranql-connector-derby-embed-xa-1.5-SNAPSHOT.rar, > tranql-connector-mysql-local-1.3-SNAPSHOT.rar, > tranql-connector-mysql-xa-1.3-SNAPSHOT.rar, > tranql-connector-postgresql-common-1.1.jar, > tranql-connector-postgresql-local-1.2-SNAPSHOT.rar, > tranql-connector-postgresql-xa-1.2-SNAPSHOT.rar, vendors.patch > > > I have frequent trouble with my database pool to an AS/400. The database is > taken down every night for backup, and at least once a week the connection > pool is unusable after the database comes back up. Restarting the connection > pool makes everything work again. > We are new to Geronimo/WAS-CE -- just this one app on one server -- so I > don't have anything to compare to. However, we have had this same issue with > a couple 1.x/1.1.x versions before we upgraded to v2. Also, there are > several WebSphere (full WAS, not WAS-CE) apps that do not have this trouble. > Configuration Info > Driver: JTOpen v6.1 (com.ibm.as400.access.AS400JDBCDriver) > Pool Min Size: 0 > Pool Max Size: 100 > Blocking Timeout: 5000 > Idle Timeout: 15 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4862) it tells "java.net.ConnectException" when i shutdown the server after i change the log level
[ https://issues.apache.org/jira/browse/GERONIMO-4862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757840#action_12757840 ] Bin He commented on GERONIMO-4862: -- The error is still there.But the error is the same with the error occured in latest build in GERONIMO-4876. > it tells "java.net.ConnectException" when i shutdown the server after i > change the log level > - > > Key: GERONIMO-4862 > URL: https://issues.apache.org/jira/browse/GERONIMO-4862 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.2 > Environment: jdk6 > windows xp sp2 >Reporter: Bin He >Priority: Minor > > 1、start server > 2、click "Server Logs" > 3、then change "log level" of "Log Manager" to any other level > 4、click "update" > 5、shutdown the server and an error shows: > java.net.ConnectException: Connection refused: connect > at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:352) > at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:214) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:201) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377) > at java.net.Socket.connect(Socket.java:530) > at java.net.Socket.connect(Socket.java:480) > at java.net.Socket.(Socket.java:377) > at java.net.Socket.(Socket.java:220) > at > org.apache.jk.common.ChannelSocket.unLockSocket(ChannelSocket.java:487) > at org.apache.jk.common.ChannelSocket.pause(ChannelSocket.java:284) > at org.apache.jk.server.JkMain.pause(JkMain.java:683) > at org.apache.jk.server.JkCoyoteHandler.pause(JkCoyoteHandler.java:153) > at org.apache.catalina.connector.Connector.pause(Connector.java:1073) > at > org.apache.catalina.core.StandardService.stop(StandardService.java:563) > at > org.apache.geronimo.tomcat.TomcatContainer.doStop(TomcatContainer.java:253) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339) > at > org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661) > at > org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638) > at > org.apache.geronimo.console.servermanager.ServerManagerPortlet.processAction(ServerManagerPortlet.java:65) > at > org.apache.pluto.core.PortletServlet.dispatch(PortletServlet.java:218) > at org.apache.pluto.core.PortletServlet.doPost(PortletServlet.java:145) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:713) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) > at > org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646) > at > org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551) > at > org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488) > at > org.apache.pluto.core.DefaultPortletInvokerService.invoke(DefaultPortletInvokerService.java:167) > at > org.apache.pluto.core.DefaultPortletInvokerService.action(DefaultPortletInvokerService.java:85) > at > org.apache.pluto.core.PortletContainerImpl.doAction(PortletContainerImpl.java:217) > at > org.apache.pluto.driver.PortalDriverServlet.doGet(PortalDriverServlet.java:121) > at > org.apache.pluto.driver.PortalD
[jira] Commented: (GERONIMO-4876) "java.lang.Exception" when I shutdown the server
[ https://issues.apache.org/jira/browse/GERONIMO-4876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757839#action_12757839 ] Bin He commented on GERONIMO-4876: -- I checked this jira in latest build . "java.lang.Exception" is not there. But "java.net.ConnectException" is still there. > "java.lang.Exception" when I shutdown the server > - > > Key: GERONIMO-4876 > URL: https://issues.apache.org/jira/browse/GERONIMO-4876 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: connector >Affects Versions: 2.2 > Environment: jdk6 > windows xp sp2 >Reporter: Bin He >Priority: Minor > > start server > shutdown server using "shutdown.bat" > It shows an error: > 2009-09-15 13:07:51,367 WARN [ConnectorGBean] TomcatWebConnector connector > failed > 2009-09-15 13:07:51,445 ERROR [GBeanInstanceState] Error while stopping; > GBean is now in the FAILED state: > abstractName="org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car,j2eeType=GBean,name=TomcatWebConnector" > java.lang.Exception: Problem while updaing the persistent value of attibute: > Attribute Name: keystoreFile, Type: class java.lang.String, GBeanInstance: > Tomcat Connector HTTP BIO > at > org.apache.geronimo.gbean.runtime.GBeanInstance.destroyInstance(GBeanInstance.java:1080) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStop(GBeanInstanceState.java:340) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:189) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.stop(GBeanInstanceState.java:150) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.stop(GBeanInstance.java:546) > at > org.apache.geronimo.kernel.basic.BasicKernel.stopGBean(BasicKernel.java:421) > at > org.apache.geronimo.kernel.config.KernelConfigurationManager$ShutdownHook.run(KernelConfigurationManager.java:339) > at > org.apache.geronimo.kernel.basic.BasicKernel.notifyShutdownHooks(BasicKernel.java:661) > at > org.apache.geronimo.kernel.basic.BasicKernel.shutdown(BasicKernel.java:638) > at org.apache.geronimo.kernel.KernelGBean.shutdown(KernelGBean.java:382) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:599) > at > org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(ReflectionMethodInvoker.java:34) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:130) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:850) > at > org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:237) > at > org.apache.geronimo.system.jmx.MBeanGBeanBridge.invoke(MBeanGBeanBridge.java:172) > at > com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:848) > at > com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:773) > at > javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1437) > at > javax.management.remote.rmi.RMIConnectionImpl.access$200(RMIConnectionImpl.java:83) > at > javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1275) > at > java.security.AccessController.doPrivileged(AccessController.java:284) > at > javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1377) > at > javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:799) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMe
[BUILD] branches/2.1: Failed for Revision: 817165
Geronimo Revision: 817165 built with tests included See the full build-0200.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090921/build-0200.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090921/unit-test-reports org.apache.geronimo.modules:geronimo-tomcat6:jar:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.geronimo.specs:geronimo-jpa_1.0_spec:jar:1.1.2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-jpa_1.0_spec -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-jpa_1.0_spec -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-tomcat6:jar:2.1.5-SNAPSHOT 2) org.apache.geronimo.ext.tomcat:catalina:jar:6.0.20-SNAPSHOT 3) org.apache.geronimo.specs:geronimo-jpa_1.0_spec:jar:1.1.2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-tomcat6:jar:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache-snapshots (http://repository.apache.org/snapshots/), codehaus-snapshots (http://snapshots.repository.codehaus.org), apache-incubator (http://people.apache.org/repo/m2-incubating-repository/) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:575) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.geronimo.specs:geronimo-jpa_1.0_spec:jar:1.1.2-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-jpa_1.0_spec -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.specs -DartifactId=geronimo-jpa_1.0_spec -Dversion=1.1.2-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.modules:geronimo-tomcat6:jar:2.1.5-SNAPSHOT 2) org.apache.geronimo.ext.tomcat:catalina:jar:6.0.20-SNAPSHOT 3) org.apache.geronimo.specs:geronimo-jpa_1.0_spec:jar:1.1.2-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.modules:geronimo-tomcat6:jar:2.1.5-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http
