[jira] Updated: (GERONIMO-3838) memory (probably related to sessions) leak
[ https://issues.apache.org/jira/browse/GERONIMO-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-3838: --- Attachment: Geronimo-3838-TomcatWebAppContext.patch Geronimo-3838-ManagerGBean.patch I divided the patch for two files. The one Geronimo-3838-ManagerGBean.patch is to make ManagerGBean to support PersistenceManager configuration. And the other one is I am not quite sure. If I write TomcatManager in the plan file, it says that Manager element is expected, but if I write TomcatManager, it would say that no reference name "Manager" is found. Could anyone give some comments, for I found WADITomcatClusteringBuilder has reference to that static string. Thanks ! > memory (probably related to sessions) leak > -- > > Key: GERONIMO-3838 > URL: https://issues.apache.org/jira/browse/GERONIMO-3838 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Memory Leaks, Tomcat >Affects Versions: 2.0.2, 2.1.1 > Environment: tested with JDK 1.5 running on Windows XP and FreeBSD6.2 >Reporter: Radim Kolar >Priority: Critical > Fix For: 2.2 > > Attachments: Geronimo-3838-ManagerGBean.patch, > Geronimo-3838-TomcatWebAppContext.patch > > > There is memory leak and it can be repeated very easily, so it should be very > easy to catch > Install Geronimo and then run some kind of benchmarking software against its > admin UI login page, for example > program ab from Apache HTTP. This is realistic attack scenario, because lot > of denial of service attacks are doing this (requesting one page many times). > Watching memory used graph in admin console shows free memory slowly > decreasing. After all available memory is exhausted, application server stops > serving new requests and never restores ifself back to working state. > I think that it is caused by allocating sessions without limiting total > number of sessions to keep in memory and possibly to swap sessions out to > file. There needs to be user-configurable setting for preventing this, it > would be nice to add such setting to Admin console. > Its very important to get this bug fixed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-3838) memory (probably related to sessions) leak
[ https://issues.apache.org/jira/browse/GERONIMO-3838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-3838: --- Attachment: (was: Geronimo-3838.patch) > memory (probably related to sessions) leak > -- > > Key: GERONIMO-3838 > URL: https://issues.apache.org/jira/browse/GERONIMO-3838 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Memory Leaks, Tomcat >Affects Versions: 2.0.2, 2.1.1 > Environment: tested with JDK 1.5 running on Windows XP and FreeBSD6.2 >Reporter: Radim Kolar >Priority: Critical > Fix For: 2.2 > > > There is memory leak and it can be repeated very easily, so it should be very > easy to catch > Install Geronimo and then run some kind of benchmarking software against its > admin UI login page, for example > program ab from Apache HTTP. This is realistic attack scenario, because lot > of denial of service attacks are doing this (requesting one page many times). > Watching memory used graph in admin console shows free memory slowly > decreasing. After all available memory is exhausted, application server stops > serving new requests and never restores ifself back to working state. > I think that it is caused by allocating sessions without limiting total > number of sessions to keep in memory and possibly to swap sessions out to > file. There needs to be user-configurable setting for preventing this, it > would be nice to add such setting to Admin console. > Its very important to get this bug fixed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4306) Plugin list won't be updated after installing a new server plugin
[ https://issues.apache.org/jira/browse/GERONIMO-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4306. --- Resolution: Fixed Assignee: Jarek Gawor Committed a fix (based on your patch) to trunk (revision 696919) and branches/2.1 (revision 696920). Thanks! > Plugin list won't be updated after installing a new server plugin > - > > Key: GERONIMO-4306 > URL: https://issues.apache.org/jira/browse/GERONIMO-4306 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: console >Affects Versions: 2.1.3 >Reporter: Rex Wang >Assignee: Jarek Gawor > Fix For: 2.1.4, 2.2 > > Attachments: GERONIMO-4306.patch > > > Steps: > 1. Login web console > 2. Go to "Plugin -> Assemble Server" portlet, and click the button - > "Assemble a server", then get the current plugin list. > 3. Go to "Plugin -> Install Plugins" portlet to install a new plugin > 4. Go back to the "Assemble Server", and click the button, then the list is > not updated. > Proposed fix: > 1. > In "AssemblyListHandler.java", we cached the plugin list in portlet session, > and that won't be updated after installing a new plugin by web console. > If we add codes to refresh the session after installing a plugin in "Install > Plugins" portlet, it seems to solve this problem. But it does not work for > using the gsh to install new plugins. > So, we have to let the AssemblyListHandler load the plugin list each time we > open the portlet. And good news is that I did not see any significant > performance falling. > 2. > And another method to solve this problem is that "ask user to logout and > login back when they install some plugins if they want to see their plugins > list in the 'assemble Server' portlet", but is it acceptable? > If the #1 is more reasonable, I can provide a patch. > Thanks > Rex -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Geronimo 2.1&2.2 Documentatio
Hi David, Thanks for your comments. I will update this "Plugin basics" page based on your thoughts. I feel sorry that some documents seem incomplete in the new structure, as we have just restructured the Geronimo 2.2 documents, and started to pull in some content.. Thanks. Ying Tang (Sophia) 2008/9/18 David Jencks <[EMAIL PROTECTED]> > I took a look at this new page and am very sorry to report that I don't > think it's an improvement. While the idea of having a summary page like > this seems reasonable much of the content seems to be inaccurate or have > unfortunate emphasis: > > Plugins are actually system modules. > - plugins can be system modules, applications, classloader definitions, and > plugin groups. Everything is a plugin in geronimo :-) I'm reluctant to use > both of the terms "module" and "plugin"; module seems to me like it's > undefined whereas plugin has a specific meaning in geronimo. I think what > you can safely say is that geronimo servers are assemblages of plugins. > An assembly, then, is a grouping of modules that provides a Geronimo server > instance with its feature set. > -s/modules/plugins > > Assemblies are the different ways you can create a server out of the > various modules available. > -s/modules/plugins > > Plugins are very dependent and sensitive to server versions. As such, > plugins that are compiled against one server version (like Geronimo 2.1) > might not deploy or function correctly in new releases (such as Geronimo > 2.1.3). Just as you must redeploy your applications when migrating to > updated server releases, you must regenerate any existing plugins for > different server levels. > -To the extent this is true it is basically a bug. We're trying to find > ways to keep plugin compatibility between 2.x.* versions. For instance, > we're using artifact aliases in the 2.1.3 release to indicate each plugin > can replace the 2.1.2 version. > > Last but not least, when installing plugins you need Internet access so > the plugin installer can retrieve all the necessary dependencies from the > online repositories. > -No, you need access to plugin repositories that contain the required > plugins and libraries. This can be online, offline, corporate, local, a cd, > another geronimo server,. > > Starting with Geronimo 2.2, the servers are assembled entirely out of > plugins. > -s/2.2/2.1 > > * Most plugins are modules, describing a classloader and services and > possibly containing classes and resources. > * Plugins also contain descriptive information and include additional > instructions on how the plugin fits into a server. > * Information about multiple plugins can be collected into a plugin > catalog, often located in a maven repository > * A plugin repository is basically a plugin catalog together with a > maven-structured repository containing plugins. > * Plugins can be installed from a plugin repository into an existing > Geronimo server using GShell commands or the Geronimo Administration > Console. > * Plugin metadata for an existing plugin in a Geronimo server can be > edited (to some extent) in the administrative console. > * A new server containing a specified set of plugins can be extracted > from an existing server using GShell commands or the Geronimo Administration > Console. > * The dependency system assures that the resulting server has all > needed plugins to operate. > > This list seems badly organized and incomplete to me. I'd prefer something > like this: > > What is a plugin? > - plugins have an identifier with groupId, artifactId, version, and type. > (It's possible to have a plugin without a moduleId but this is not > currently used) > - a plugin can define a classloader in which case: > -- a plugin with a classloader can define geronimo services (gbeans) that > can use classes in the classloader (and its parents) > -- other plugins can depend on this classloader (i.e. have this classloader > as a parent). > -- the plugin can contain classes which are made available in the > classloader. This is used mostly for javaee application plugins, where the > application classes are packed in the plugin. > - a plugin can contain resources that are unpacked into the server upon > installation (typically into the var/ directory in a plugin-specific > location) > - a plugin includes a list of dependencies. This is intended to normally > be effectively the same as the classloader dependencies, if there is a > classloader. > - a plugin without a classloader definition still includes a list of > dependencies. These are typically used as "plugin groups" to install a set > of plugins at once. > > Plugins can contain both server functionality and application functionality > or both. For instance, you can include a web server configuration in a web > app plugin. > > How do I find plugins? > - plugins are listed in plugin catalogs which contain information about the > plugins (typically name and descr
[BUILD] trunk: Failed for Revision: 696890
Geronimo Revision: 696890 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 37 minutes 58 seconds
[INFO] Finished at: Thu Sep 18 21:41:43 EDT 2008
[INFO] Final Memory: 364M/1007M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/logs-2100-tomcat/test.log
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:39.722
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 32 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deployFAILURE (0:01:06.491) Java
returned: 1
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:32.034)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:18.811)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:17.060)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:16.108)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:50.269) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:47.026)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.537)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:46.391)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:43.950)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:30.543)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.233)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:28.947)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:40.584)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:47.728)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.228)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise
[jira] Resolved: (GERONIMO-4311) Deployment of service-refs with wsdl with external wsdl/xsd imports fails
[
https://issues.apache.org/jira/browse/GERONIMO-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jarek Gawor resolved GERONIMO-4311.
---
Resolution: Fixed
Fix Version/s: 2.2
2.1.4
Assignee: Jarek Gawor
Committed fixes to trunk (revision 696894) and branches/2.1 (revision 696895).
> Deployment of service-refs with wsdl with external wsdl/xsd imports fails
> -
>
> Key: GERONIMO-4311
> URL: https://issues.apache.org/jira/browse/GERONIMO-4311
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: webservices
>Affects Versions: 2.1.3, 2.2
>Reporter: Jarek Gawor
>Assignee: Jarek Gawor
> Fix For: 2.1.4, 2.2
>
>
> Deployment of applications with service-refs with wsdl that has external wsdl
> or xsd imports will fail with RuntimeException, for example:
> {code}
> org.apache.geronimo.common.DeploymentException: File does not exist in the
> module http://java.sun.com/xml/ns/javaee/javaee_5.xsd
> at
> org.apache.geronimo.jaxws.builder.EndpointInfoBuilder.build(EndpointInfoBuilder.java:157)
> at
> org.apache.geronimo.cxf.builder.CXFServiceRefBuilder.createService(CXFServiceRefBuilder.java:59)
>
> Caused by: java.lang.RuntimeException: File does not exist in the module
> http://java.sun.com/xml/ns/javaee/javaee_5.xsd
> at
> org.apache.geronimo.jaxws.builder.EndpointInfoBuilder$JarWSDLLocator.getImportInputSource(EndpointInfoBuilder.java:404)
> at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
> at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
> {code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4311) Deployment of service-refs with wsdl with external wsdl/xsd imports fails
Deployment of service-refs with wsdl with external wsdl/xsd imports fails
-
Key: GERONIMO-4311
URL: https://issues.apache.org/jira/browse/GERONIMO-4311
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: webservices
Affects Versions: 2.1.3, 2.2
Reporter: Jarek Gawor
Deployment of applications with service-refs with wsdl that has external wsdl
or xsd imports will fail with RuntimeException, for example:
{code}
org.apache.geronimo.common.DeploymentException: File does not exist in the
module http://java.sun.com/xml/ns/javaee/javaee_5.xsd
at
org.apache.geronimo.jaxws.builder.EndpointInfoBuilder.build(EndpointInfoBuilder.java:157)
at
org.apache.geronimo.cxf.builder.CXFServiceRefBuilder.createService(CXFServiceRefBuilder.java:59)
Caused by: java.lang.RuntimeException: File does not exist in the module
http://java.sun.com/xml/ns/javaee/javaee_5.xsd
at
org.apache.geronimo.jaxws.builder.EndpointInfoBuilder$JarWSDLLocator.getImportInputSource(EndpointInfoBuilder.java:404)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
at com.ibm.wsdl.xml.WSDLReaderImpl.parseSchema(Unknown Source)
{code}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Lets use gshell for all startup stuff
Lets change the scripts in bin that don't use gshell to use gshell. Then the helper scripts such as setjavaenv.sh will only be used for starting gshell and I hopefully they won't need most of their current contents. As noted in GERONIMO-4093 I'm not OK with requiring JAVA_HOME to be defined on systems that don't need it, and I took matters into my own hands and restored the old behavior of using "java" if JAVA_HOME is not defined. I'm barely literate in bash so there may well be a better solution. thanks david jencks
[jira] Commented: (GERONIMO-4093) gsh scripts are not using setjavaenv or optional setenv script
[ https://issues.apache.org/jira/browse/GERONIMO-4093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632446#action_12632446 ] David Jencks commented on GERONIMO-4093: I'm not OK with requiring people to define JAVA_HOME on mac. I've committed something that eliminates this requirement, rev 696852. I'm happy to vote against any proposed releases that do require defining JAVA_HOME. I still think most of the script crud is not appropriate since it is for starting gshell, NOT geronimo. How much control does anyone need to start gshell? > gsh scripts are not using setjavaenv or optional setenv script > -- > > Key: GERONIMO-4093 > URL: https://issues.apache.org/jira/browse/GERONIMO-4093 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) >Affects Versions: 2.1, 2.1.1, 2.1.2, 2.2 >Reporter: Donald Woods >Assignee: Donald Woods > Fix For: 2.2 > > > gsh scripts are not allowing users to provide the optional setjavaenv > scripts, like the previous geronimo/deploy scripts allowed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Continuous TCK Testing
I would like to be involved too. But, I don't have any experience with either AntHill or Hudson. Has anyone used Continuum? Would that be harder/easier to configure and use than the other two? Jay Kevan Miller wrote: > As many of you know, we have two apache.org machines for TCK testing of > Geronimo (phoebe and selene). We used the machines for certification of > our 2.1.3 release. However, this testing was run manually. It's time to > get continuous, automatic TCK testing running on these machines. > > We had the basic setup running on GBuild machines. IIRC, this was built > around AntHill -- Jason Dillon knows it best. There are other testing > systems available (e.g. Hudson) which could be used for this task. > > What do others think? What underlying technology should we use? Who > wants to get involved? > > I think this discussion should be on our dev@ mailing list. TCK should > be for test specific discussions. > > --kevan >
[BUILD] trunk: Failed for Revision: 696769
Geronimo Revision: 696769 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 17 seconds
[INFO] Finished at: Thu Sep 18 15:41:39 EDT 2008
[INFO] Final Memory: 378M/1007M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/logs-1500-tomcat/test.log
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:43.012
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 32 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deployFAILURE (0:01:07.222) Java
returned: 1
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:29.948)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:19.928)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:17.290)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:12.772)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:50.688) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:46.987)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:43.258)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:01:08.984)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:43.511)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.545)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:27.261)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:29.606)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:43.535)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:47.961)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.887)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise
Re: Continuous TCK Testing
I am all for this idea. I don't really know about anthill but I did look into hudson a little bit a while ago. It seems like it would meet our requirements but I haven't actually used the technology so I'm not sure how well it works. If we already have a solution, I'm not sure why we wouldn't go with that, though. Is there any reason we wouldn't want to use a setup similar to what we had before using anthill? I'd be happy to get involved, especially if it makes it easier to verify tck when release time comes around. I'm kind of curious about how this would work, though. I assume someone would commit some code and this would trigger a tck test with the new code. How would errors be reported? Would we have to have all committers sign the NDA so we can report details of failures to whoever committed the changes? On Thu, Sep 18, 2008 at 1:50 PM, Kevan Miller <[EMAIL PROTECTED]>wrote: > As many of you know, we have two apache.org machines for TCK testing of > Geronimo (phoebe and selene). We used the machines for certification of our > 2.1.3 release. However, this testing was run manually. It's time to get > continuous, automatic TCK testing running on these machines. > > We had the basic setup running on GBuild machines. IIRC, this was built > around AntHill -- Jason Dillon knows it best. There are other testing > systems available (e.g. Hudson) which could be used for this task. > > What do others think? What underlying technology should we use? Who wants > to get involved? > > I think this discussion should be on our dev@ mailing list. TCK should be > for test specific discussions. > > --kevan > > -- ~Jason Warner
Continuous TCK Testing
As many of you know, we have two apache.org machines for TCK testing of Geronimo (phoebe and selene). We used the machines for certification of our 2.1.3 release. However, this testing was run manually. It's time to get continuous, automatic TCK testing running on these machines. We had the basic setup running on GBuild machines. IIRC, this was built around AntHill -- Jason Dillon knows it best. There are other testing systems available (e.g. Hudson) which could be used for this task. What do others think? What underlying technology should we use? Who wants to get involved? I think this discussion should be on our dev@ mailing list. TCK should be for test specific discussions. --kevan
Re: Privacy Clause in Google Analytics Terms of Service
On Sep 17, 2008, at 5:40 PM, Joe Bohn wrote: I'd be fine with either option. It's certainly simple enough to add the privacy clause. We can do that for now even if we decide to remove Analytics entirely later on. I personally haven't been checking the Google Analytics very often but perhaps others have been making more use of it? I've looked at it from time to time, but can't say that I've really used it... I have learned this week that there's more information available than I originally knew about. For example, you can find the domain names of visitors to the site (not individual ip addresses) -- you can see the domain names of visitors to the download.html page. IMO, there is the potential for abuse of this information. Any Google Analytics data should be treated as private to our project. If we're able to use the information to improve access to our web site, provide better information, etc -- that's great. However, the data needs to stay within our project. --kevan
[BUILD] trunk: Failed for Revision: 696651
Geronimo Revision: 696651 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/build-0900.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 17 seconds
[INFO] Finished at: Thu Sep 18 09:42:52 EDT 2008
[INFO] Final Memory: 377M/1008M
[INFO]
TESTSUITE RESULTS (Failures only)
=
See detailed results at
http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html
Assembly: tomcat
=
See the full test.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/logs-0900-tomcat/test.log
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/server.log
[INFO] User extensions:
/home/geronimo/geronimo/trunk/testsuite/target/selenium/user-extensions.js
Selenium Server started
[INFO] [geronimo:start-server {execution: start}]
[INFO] Using assembly configuration: tomcat
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-snapshots
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from apache.snapshots
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:41.182
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/2.2-SNAPSHOT/testsuite-2.2-SNAPSHOT.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 32 test build(s)
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deployRUNNING
[INFO] commands-testsuite/deployFAILURE (0:01:06.571) Java
returned: 1
[INFO] commands-testsuite/gshellRUNNING
[INFO] commands-testsuite/gshellSUCCESS (0:00:30.057)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:18.926)
[INFO] commands-testsuite/shutdown RUNNING
[INFO] commands-testsuite/shutdown SUCCESS (0:00:16.748)
[INFO] concurrent-testsuite/concurrent-basicRUNNING
[INFO] concurrent-testsuite/concurrent-basicSUCCESS (0:06:15.888)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:00:50.452) Java
returned: 1
[INFO] console-testsuite/basic RUNNING
[INFO] console-testsuite/basic SUCCESS (0:01:46.360)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:46.422)
[INFO] corba-testsuite/corba-marshalRUNNING
[INFO] corba-testsuite/corba-marshalSUCCESS (0:00:56.304)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:48.409)
[INFO] deployment-testsuite/deployment-testsRUNNING
[INFO] deployment-testsuite/deployment-testsSUCCESS (0:00:31.053)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:31.939)
[INFO] deployment-testsuite/manifestcp-testsRUNNING
[INFO] deployment-testsuite/manifestcp-testsSUCCESS (0:00:30.410)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:40.632)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:46.274)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:51.464)
[INFO] enterprise-testsuite/sec-client RUNNING
[INFO] enterprise
[BUILD] trunk: Failed for Revision: 696581
Geronimo Revision: 696581 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/build-0300.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 40 minutes 55 seconds [INFO] Finished at: Thu Sep 18 03:44:29 EDT 2008 [INFO] Final Memory: 394M/924M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20080918/logs-0300-tomcat/test.log Booting Geronimo Kernel (in Java 1.5.0_12)... Module 1/75 org.apache.geronimo.framework/j2ee-system/2.2-SNAPSHOT/car started in .000s Module 2/75 org.apache.geronimo.framework/jee-specs/2.2-SNAPSHOT/car started in .000s Module 3/75 org.apache.geronimo.framework/rmi-naming/2.2-SNAPSHOT/car started in .184s Module 4/75 org.apache.geronimo.plugins.classloaders/geronimo-javaee-deployment_1.1MR3_spec/2.2-SNAPSHOT/car started in .001s Module 5/75 org.apache.geronimo.framework/xmlbeans/2.2-SNAPSHOT/car started in .000s Module 6/75 org.apache.geronimo.framework/plugin/2.2-SNAPSHOT/car started in .744s Module 7/75 org.apache.geronimo.framework/geronimo-gbean-deployer/2.2-SNAPSHOT/car started in .342s Module 8/75 org.apache.geronimo.framework/j2ee-security/2.2-SNAPSHOT/car started in .282s Module 9/75 org.apache.geronimo.configs/j2ee-server/2.2-SNAPSHOT/car started in .099s Module 10/75 org.apache.geronimo.framework/transformer-agent/2.2-SNAPSHOT/car started in .000s Module 11/75 org.apache.geronimo.plugins.classloaders/geronimo-schema-jee_5/2.2-SNAPSHOT/car started in .000s Module 12/75 org.apache.geronimo.configs/webservices-common/2.2-SNAPSHOT/car started in .000s Module 13/75 org.apache.geronimo.configs/transaction/2.2-SNAPSHOT/car started in .358s Module 14/75 org.apache.geronimo.framework/server-security-config/2.2-SNAPSHOT/car started in .078s Module 15/75 org.apache.geronimo.configs/derby/2.2-SNAPSHOT/car started in .001s Module 16/75 org.apache.geronimo.configs/system-database/2.2-SNAPSHOT/car started in 5.450s Module 17/75 org.apache.geronimo.configs/activemq-broker/2.2-SNAPSHOT/car started in 2.184s Module 18/75 org.apache.geronimo.configs/openjpa/2.2-SNAPSHOT/car started in .008s Module 19/75 org.apache.geronimo.plugins.classloaders/xbean-finder/2.2-SNAPSHOT/car started in .000s Module 20/75 org.apache.geronimo.configs/openejb/2.2-SNAPSHOT/car 03:50:32,721 WARN [service] Property "Cache" not supported by "Default Stateful Container" 03:50:32,721 WARN [service] Property "Passivator" not supported by "Default Stateful Container" 03:50:32,721 WARN [service] Property "TimeOut" not supported by "Default Stateful Container" 03:50:32,721 WARN [service] Property "PoolSize" not supported by "Default Stateful Container" 03:50:32,722 WARN [service] Property "BulkPassivate" not supported by "Default Stateful Container" started in 1.099s Module 21/75 org.apache.geronimo.configs/axis/2.2-SNAPSHOT/car started in .148s Module 22/75 org.apache.geronimo.configs/axis2/2.2-SNAPSHOT/car started in .001s Module 23/75 org.apache.geronimo.configs/axis2-ejb/2.2-SNAPSHOT/car started in .000s Module 24/75 org.apache.geronimo.configs/j2ee-corba-yoko/2.2-SNAPSHOT/car started in .863s Module 25/75 org.apache.geronimo.configs/jasper/2.2-SNAPSHOT/car started in .002s Module 26/75 org.apache.geronimo.configs/tomcat6/2.2-SNAPSHOT/car started in 2.377s Module 27/75 org.apache.geronimo.config
[jira] Closed: (GERONIMO-4309) Credentials in list of allowed plugin repositories should be encrypted
[ https://issues.apache.org/jira/browse/GERONIMO-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4309. -- Resolution: Fixed Fixed in rev 696579, using the EncryptionManager to obscure the pw. This only obscures he pawwsords against casual exampination, the key is not stored securely so this is definitley susceptible to easy attacks. > Credentials in list of allowed plugin repositories should be encrypted > -- > > Key: GERONIMO-4309 > URL: https://issues.apache.org/jira/browse/GERONIMO-4309 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: Plugins >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > In GERONIMO-4304 I introduced a plugin repository registry with user-password > credentials for the repos. The password should be encrypted like the other > passwords in our config files. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
