[BUILD] trunk: Failed for Revision: 739109
Geronimo Revision: 739109 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090130/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090130/unit-test-reports - locked 0xef684900 (a java.io.InputStreamReader) at java.io.InputStreamReader.read(InputStreamReader.java:167) at java.io.BufferedReader.fill(BufferedReader.java:136) at java.io.BufferedReader.readLine(BufferedReader.java:299) - locked 0xef684900 (a java.io.InputStreamReader) at java.io.BufferedReader.readLine(BufferedReader.java:362) at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:153) process reaper daemon prio=10 tid=0xa1c4e800 nid=0x57f runnable [0xa28ad000..0xa28ae0b0] java.lang.Thread.State: RUNNABLE at java.lang.UNIXProcess.waitForProcessExit(Native Method) at java.lang.UNIXProcess.access$900(UNIXProcess.java:20) at java.lang.UNIXProcess$1$1.run(UNIXProcess.java:132) Low Memory Detector daemon prio=10 tid=0x084f6400 nid=0x4c5 runnable [0x..0x] java.lang.Thread.State: RUNNABLE CompilerThread1 daemon prio=10 tid=0x084f3800 nid=0x4c4 waiting on condition [0x..0xa43093e8] java.lang.Thread.State: RUNNABLE CompilerThread0 daemon prio=10 tid=0x084f1400 nid=0x4c3 waiting on condition [0x..0xa438a368] java.lang.Thread.State: RUNNABLE Signal Dispatcher daemon prio=10 tid=0x084efc00 nid=0x4c2 runnable [0x..0x] java.lang.Thread.State: RUNNABLE Finalizer daemon prio=10 tid=0x084e nid=0x4c1 in Object.wait() [0xa442c000..0xa442cfb0] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0xb4ddc990 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:116) - locked 0xb4ddc990 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:132) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=10 tid=0x084db800 nid=0x4c0 in Object.wait() [0xa447e000..0xa447e130] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0xb4ddc968 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:485) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) - locked 0xb4ddc968 (a java.lang.ref.Reference$Lock) main prio=10 tid=0x08434000 nid=0x4ba in Object.wait() [0xf7ee4000..0xf7ee51f8] java.lang.Thread.State: WAITING (on object monitor) at java.lang.Object.wait(Native Method) - waiting on 0xef6842b0 (a java.lang.UNIXProcess) at java.lang.Object.wait(Object.java:485) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:165) - locked 0xef6842b0 (a java.lang.UNIXProcess) at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:143) at org.apache.maven.surefire.booter.shade.org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:95) at org.apache.maven.surefire.booter.SurefireBooter.fork(SurefireBooter.java:666) at org.apache.maven.surefire.booter.SurefireBooter.forkSuites(SurefireBooter.java:472) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesForkOnce(SurefireBooter.java:372) at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:245) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:492) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) 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
[jira] Resolved: (GERONIMO-4324) Upgrade to MyFaces v1.2.6
[ https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Bohn resolved GERONIMO-4324. Resolution: Fixed Fix Version/s: 2.0.4 update checked into trunk (rev. 739267) branches/2.1 (rev. 739268) and branches/2.0 (rev. 739269) Upgrade to MyFaces v1.2.6 - Key: GERONIMO-4324 URL: https://issues.apache.org/jira/browse/GERONIMO-4324 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: dependencies Affects Versions: 2.0.3, 2.1.4, 2.2 Reporter: Donald Woods Assignee: Joe Bohn Priority: Minor Fix For: 2.0.4, 2.1.4, 2.2 Upgrade to MyFaces v1.2.6 released on January 26, 2009 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4352) IMAP provider: accessing parts of a multipart/mixed message causes invalid command
[ https://issues.apache.org/jira/browse/GERONIMO-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor reassigned GERONIMO-4352: - Assignee: Jarek Gawor (was: Rick McGuire) IMAP provider: accessing parts of a multipart/mixed message causes invalid command -- Key: GERONIMO-4352 URL: https://issues.apache.org/jira/browse/GERONIMO-4352 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Reporter: Andreas Veithen Assignee: Jarek Gawor Attachments: 03-javamail.log, GERONIMO-4352-test.patch.txt, GERONIMO-4352.diff When accessing the content of the second part of a multipart/mixed message (see attachment), the following IMAP command is sent: FETCH 1 (BODY.PEEK[2.TEXT]) This results in an error (FETCH failed). IMAP server is GreenMail: http://www.icegreen.com/greenmail/ RFC3501 says about the TEXT part specifier: The HEADER, HEADER.FIELDS, HEADER.FIELDS.NOT, and TEXT part specifiers can be the sole part specifier or can be prefixed by one or more numeric part specifiers, provided that the numeric part specifier refers to a part of type MESSAGE/RFC822. The MIME part specifier MUST be prefixed by one or more numeric part specifiers. Since the second part is not message/rfc822, the command issued is incorrect. I believe that the correct command in this case should be: FETCH 1 (BODY.PEEK[2]) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (GERONIMO-4352) IMAP provider: accessing parts of a multipart/mixed message causes invalid command
[ https://issues.apache.org/jira/browse/GERONIMO-4352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-4352. --- Resolution: Fixed IMAP provider: accessing parts of a multipart/mixed message causes invalid command -- Key: GERONIMO-4352 URL: https://issues.apache.org/jira/browse/GERONIMO-4352 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Reporter: Andreas Veithen Assignee: Jarek Gawor Attachments: 03-javamail.log, GERONIMO-4352-test.patch.txt, GERONIMO-4352.diff When accessing the content of the second part of a multipart/mixed message (see attachment), the following IMAP command is sent: FETCH 1 (BODY.PEEK[2.TEXT]) This results in an error (FETCH failed). IMAP server is GreenMail: http://www.icegreen.com/greenmail/ RFC3501 says about the TEXT part specifier: The HEADER, HEADER.FIELDS, HEADER.FIELDS.NOT, and TEXT part specifiers can be the sole part specifier or can be prefixed by one or more numeric part specifiers, provided that the numeric part specifier refers to a part of type MESSAGE/RFC822. The MIME part specifier MUST be prefixed by one or more numeric part specifiers. Since the second part is not message/rfc822, the command issued is incorrect. I believe that the correct command in this case should be: FETCH 1 (BODY.PEEK[2]) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Release XBean 3.5 - rc2
+1 Jacek On Mon, Jan 26, 2009 at 9:18 PM, Joe Bohn joe.b...@earthlink.net wrote: I uploaded a second distribution of XBean 3.5 which should include the NOTICE/LICENSE files in all the appropriate places (I hope). The same changes are present in this candidate that were present in the last one: * SocketAddress factory example for Alex [1] * XBEAN-111 Only register Converters with the VM when requested [2] * Make dependencies optional [3] * XBEAN-114 generify xbean-naming [4] * XBEAN-115 Fix rebind of entry added using deepBind [5] * XBEAN-115 similar fix to for WritableContext for consistency [6] * try to follow apache policy and not deploy timestamped snapshots [7] * Fix classloader name when throwing a CNFE [8] * Let the tests pass on non-MacOS OSes [9] * XBEAN-120 Search for semi-annotated classes in inheritance tree (as if @Inherited's applied) [10] * XBEAN-120 Search for semi-annotated classes in inheritance tree (as if @Inherited's applied) [11] * update copyright years to include 2009 [12] * add a siteId property to assist in release [13] Please help validate this release. I'm a little concerned about xbean-spring as I noticed some errors fly by during the release process but everything eventually passed successfully. I'll start validating this in a Geronimo server image but at the moment it will only utilize xbean-naming 3.5. The staging repository is available at http://people.apache.org/~jbohn/staging-repo/xbean/ and the tag is available at http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.5/ I've run the rat tool to validate license headers. Please review and vote: [ ] +1 Release XBean 3.5 [ ] -1 Do not, because ... The vote will be open for 72 hours or longer as necessary to validate the images and get sufficient participation in the vote. [1] http://svn.apache.org/viewvc?view=revrevision=689356 [2] http://svn.apache.org/viewvc?view=revrevision=703580 [3] http://svn.apache.org/viewvc?view=revrevision=705314 [4] http://svn.apache.org/viewvc?view=revrevision=707161 [5] http://svn.apache.org/viewvc?view=revrevision=707227 [6] http://svn.apache.org/viewvc?view=revrevision=707230 [7] http://svn.apache.org/viewvc?view=revrevision=707719 [8] http://svn.apache.org/viewvc?view=revrevision=725706 [9] http://svn.apache.org/viewvc?view=revrevision=729545 [10] http://svn.apache.org/viewvc?view=revrevision=729546 [11] http://svn.apache.org/viewvc?view=revrevision=731945 [12] http://svn.apache.org/viewvc?view=revrevision=737042 [13] http://svn.apache.org/viewvc?view=revrevision=737184 Thanks, Joe -- Jacek Laskowski Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl
Re: [CANCELLED] Re: [VOTE] geronimo-jpa_2.0_spec first early access release
Any updates on item (iii)? Can we just include the notice for EA-1 and revisit for the next release? -Donald David Jencks wrote: Looks like a problem. I sent a note to legal-discuss about (iii). I'll work on setting up a new release candidate. thanks david jencks On Jan 29, 2009, at 7:46 AM, Jeremy Bauer wrote: David, While searching the JSR-317 draft for direction regarding early access naming, I found that the notice (page 2) includes the clauses below, notably item iii. Does clause iii need to be added to the NOTICE in the EA jar? Also, should the Geronimo EA NOTICE use JPA 2.0 EARLY ACCESS instead of simply JPA 2.0 in order to meet clause ii? jsr-317 draft NOTICE ... 2.Distribute implementations of the Specification to third parties for their testing and evaluation use, provided that any such implementation: (i) does not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Specification or Specifications being implemented; (ii)is clearly and prominently marked with the word UNTESTED or EARLY ACCESS or INCOMPATIBLE or UNSTABLE or BETA in any list of available builds and in proximity to every link initiating its download, where the list or link is under Licensee's control; and (iii)includes the following notice: This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP. /jsr-317 draft -Jeremy On Wed, Jan 28, 2009 at 4:25 PM, David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com wrote: I've been working with the OpenJPA project to develop the jpa 2.0 spec jar in our spec repository. They are ready for their first early access milestone release. I've staged the release here: http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 I haven't staged the site. I don't think its necessary for a early access release, but will reconsider on request. I ran rat on the project, and the autochecking thinks the legal files are ok. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks
Re: [CANCELLED] Re: [VOTE] geronimo-jpa_2.0_spec first early access release
On Jan 30, 2009, at 2:00 PM, Donald Woods wrote: Any updates on item (iii)? Can we just include the notice for EA-1 and revisit for the next release? My interpretation of Geir's response is that we can't distribute stuff with this restriction, so no, we have to wait until the conditions are changed at which point the existing jar under vote will be OK. thanks david jencks -Donald David Jencks wrote: Looks like a problem. I sent a note to legal-discuss about (iii). I'll work on setting up a new release candidate. thanks david jencks On Jan 29, 2009, at 7:46 AM, Jeremy Bauer wrote: David, While searching the JSR-317 draft for direction regarding early access naming, I found that the notice (page 2) includes the clauses below, notably item iii. Does clause iii need to be added to the NOTICE in the EA jar? Also, should the Geronimo EA NOTICE use JPA 2.0 EARLY ACCESS instead of simply JPA 2.0 in order to meet clause ii? jsr-317 draft NOTICE ... 2.Distribute implementations of the Specification to third parties for their testing and evaluation use, provided that any such implementation: (i) does not modify, subset, superset or otherwise extend the Licensor Name Space, or include any public or protected packages, classes, Java interfaces, fields or methods within the Licensor Name Space other than those required/authorized by the Specification or Specifications being implemented; (ii)is clearly and prominently marked with the word UNTESTED or EARLY ACCESS or INCOMPATIBLE or UNSTABLE or BETA in any list of available builds and in proximity to every link initiating its download, where the list or link is under Licensee's control; and (iii)includes the following notice: This is an implementation of an early-draft specification developed under the Java Community Process (JCP) and is made available for testing and evaluation purposes only. The code is not compatible with any specification of the JCP. /jsr-317 draft -Jeremy On Wed, Jan 28, 2009 at 4:25 PM, David Jencks david_jen...@yahoo.com mailto:david_jen...@yahoo.com wrote: I've been working with the OpenJPA project to develop the jpa 2.0 spec jar in our spec repository. They are ready for their first early access milestone release. I've staged the release here: http://people.apache.org/~djencks/staging-repo/specs/geronimo-jpa_2.0_spec/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0-EA-1/ The svn location is here: https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-jpa_2.0_spec-1.0-EA-1 I haven't staged the site. I don't think its necessary for a early access release, but will reconsider on request. I ran rat on the project, and the autochecking thinks the legal files are ok. Vote open for 72 hours. [ ] +1 [ ] +0 [ ] -1 thanks david jencks
[BUILD] trunk: Failed for Revision: 739478
Geronimo Revision: 739478 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090130/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090130
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 38 minutes 3 seconds
[INFO] Finished at: Fri Jan 30 21:42:09 EST 2009
[INFO] Final Memory: 630M/991M
[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/20090130/logs-2100-tomcat/test.log
[INFO] snapshot
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:2.2-SNAPSHOT: checking
for updates from codehaus-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:40.900
[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 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:00:59.543)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:28.361)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:33.394)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:16.165)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:22.799)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced SUCCESS (0:01:19.173)
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:43.129)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:47.788)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:50.752)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:41.285)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:30.190)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:28.961)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:32.019)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:00:46.558)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:00:53.103)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:01:03.357)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:26.605)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:47.962)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:36.294) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:30.321)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5
