Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3
+1 On Mon, Jul 23, 2012 at 11:05 PM, Yi Xiao wrote: > Hi devs, > > Please help to review and vote on the release of Geronimo Eclipse Plugin > (GEP) 3.0.0 RC3. > > GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, > 3.8, 4.2. > > [Known issue] > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be > built successfully on 64bit win7 and 64bit macos. See following JIRAs for > details. > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not > build GEP3.0 under win7-64bit > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not > build GEP3.0 under macos-64bit > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is > still open. > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not > build GEP with maven 3.0 > 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C > license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd > uses Eclipse Public License, so the rat check on them are failed. > > The source code zip is here: > > https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip > > https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz > > The tag is here: > > http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ > > The deployable zip file is here: > > http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip > > The p2 repo zip file is here: > > http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip > > Notice: As update site format is not recommend in eclipse, now only > provide the p2 format. > > If you would like to review and/or comment on the release notes, you can > find it here: > > http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt > > Finally, I've created a Staging Site that can be used to test the update > manager functions of Eclipse (Indigo SR2 and Juno): > > http://people.apache.org/builds/geronimo/eclipse/updates/ > > The vote will be open for the 72-hour minimum. > > [ ] +1 about time to push this out the door > [ ] 0 no opinion > [ ] -1 not this one (please explain why) > -- > Best regards! > > > John Xiao > > -- Thanks! Regards, Forrest
Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3
+1 On Wed, Jul 25, 2012 at 9:29 AM, Shawn Jiang wrote: > +1 > > > On Mon, Jul 23, 2012 at 11:05 PM, Yi Xiao wrote: > >> Hi devs, >> >> Please help to review and vote on the release of Geronimo Eclipse Plugin >> (GEP) 3.0.0 RC3. >> >> GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, >> 3.8, 4.2. >> >> [Known issue] >> 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be >> built successfully on 64bit win7 and 64bit macos. See following JIRAs for >> details. >> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not >> build GEP3.0 under win7-64bit >> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not >> build GEP3.0 under macos-64bit >> 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is >> still open. >> - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not >> build GEP with maven 3.0 >> 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C >> license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd >> uses Eclipse Public License, so the rat check on them are failed. >> >> The source code zip is here: >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip >> >> https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz >> >> The tag is here: >> >> http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ >> >> The deployable zip file is here: >> >> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip >> >> The p2 repo zip file is here: >> >> http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip >> >> Notice: As update site format is not recommend in eclipse, now only >> provide the p2 format. >> >> If you would like to review and/or comment on the release notes, you can >> find it here: >> >> http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt >> >> Finally, I've created a Staging Site that can be used to test the update >> manager functions of Eclipse (Indigo SR2 and Juno): >> >> http://people.apache.org/builds/geronimo/eclipse/updates/ >> >> The vote will be open for the 72-hour minimum. >> >> [ ] +1 about time to push this out the door >> [ ] 0 no opinion >> [ ] -1 not this one (please explain why) >> -- >> Best regards! >> >> >>John Xiao >> >> > > > -- > Shawn > -- viola Apache Geronimo
Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3
+1 On Mon, Jul 23, 2012 at 11:05 PM, Yi Xiao wrote: > Hi devs, > > Please help to review and vote on the release of Geronimo Eclipse Plugin > (GEP) 3.0.0 RC3. > > GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, > 3.8, 4.2. > > [Known issue] > 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be > built successfully on 64bit win7 and 64bit macos. See following JIRAs for > details. > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not > build GEP3.0 under win7-64bit > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not > build GEP3.0 under macos-64bit > 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is > still open. > - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not > build GEP with maven 3.0 > 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C > license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd > uses Eclipse Public License, so the rat check on them are failed. > > The source code zip is here: > > https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip > > https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz > > The tag is here: > > http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ > > The deployable zip file is here: > > http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip > > The p2 repo zip file is here: > > http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip > > Notice: As update site format is not recommend in eclipse, now only > provide the p2 format. > > If you would like to review and/or comment on the release notes, you can > find it here: > > http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt > > Finally, I've created a Staging Site that can be used to test the update > manager functions of Eclipse (Indigo SR2 and Juno): > > http://people.apache.org/builds/geronimo/eclipse/updates/ > > The vote will be open for the 72-hour minimum. > > [ ] +1 about time to push this out the door > [ ] 0 no opinion > [ ] -1 not this one (please explain why) > -- > Best regards! > > > John Xiao > > -- Shawn
[jira] [Resolved] (GERONIMO-6372) RecoveryImpl completing in-progress transactions, XidFactoryImpl needs to be smarter with matching
[
https://issues.apache.org/jira/browse/GERONIMO-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved GERONIMO-6372.
---
Resolution: Fixed
Not sure which version I should put. djencks ?
> RecoveryImpl completing in-progress transactions, XidFactoryImpl needs to be
> smarter with matching
> --
>
> Key: GERONIMO-6372
> URL: https://issues.apache.org/jira/browse/GERONIMO-6372
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
>Affects Versions: 2.2
> Environment: Aries, OSGI, camel, activemq
>Reporter: Gary Tully
>Assignee: Guillaume Nodet
> Attachments: GERONIMO-6372.patch
>
>
> Given a camel route with from("activemq:a").to("activemq:b") in a Geronimo
> managed XA transaction. On start/restart new transactions are created in
> parallel with recovery of the jms components.
> There are two issues:
> * The Recovery processing can match new transactions through the
> XidFactory.matchXX methods and rollback new work in error. (Note: a
> xa_recover of activemq correctly returns *all* prepared transactions)
> * The XidFactoryImpl(byte[] seed) can create duplicate xids which could
> potentially interfere with recovering transactions and makes it impossible to
> determine from the logs what is going on.
> Xids should be globally unique and recoverable. So they need a persistent
> unique seed (provided through configuration) and an ever increasing id.
> The current time provides a simple approach to an increasing id that negates
> the need to persist the last used id in the transaction recovery log.
> (It has the downside of regressing if the XidFactory is recreated in the same
> millisecond, but I think this is in practice improbable outside unit tests.)
> If the id component is keyed of the epoch, a recovering XidFactory can match
> only old Xids, ones created by it in a previous incarnation. In this way it
> can avoid completing newly created transactions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Vote] Geronimo Eclipse Plugin (GEP) 3.0.0 RC3
Thank you! It compiles nicely under OpenSuse 12.1 64bit; I have tested and deployed one of our Geronimo 2.2 applications usind the plugin provided from your staging-site. Great! Here is my +1 Johannes Am Tue Jul 24 04:22:48 2012 schrieb Yi Xiao: I build the source on ubuntu 10.04 64bit, run rat check and test run some simple web apps against the release, it works fine, so my +1 On Mon, Jul 23, 2012 at 11:05 PM, Yi Xiao mailto:xiaoyijhondeve...@gmail.com>> wrote: Hi devs, Please help to review and vote on the release of Geronimo Eclipse Plugin (GEP) 3.0.0 RC3. GEP 3.0.0 supports Geronimo server 3.0.0, 2.2.1, 2.1.7 and Eclipse 3.7, 3.8, 4.2. [Known issue] 1. GEP 3.0.0 uses maven-eclipsepde-plugin v1.1, which means it can not be built successfully on 64bit win7 and 64bit macos. See following JIRAs for details. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-737 Could not build GEP3.0 under win7-64bit - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-674 Could not build GEP3.0 under macos-64bit 2. Also, please use maven v2.2.1 to build GEP 3.0.0 as following JIRA is still open. - https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-694 Can not build GEP with maven 3.0 3. The plugins/org.apache.geronimo.st.v11.schemas/v11/xml.xsd uses W3C license and plugins/org.apache.geronimo.st.schemas/v30/persistence_2_0.xsd uses Eclipse Public License, so the rat check on them are failed. The source code zip is here: https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.zip https://repository.apache.org/content/repositories/orgapachegeronimo-071/org/apache/geronimo/devtools/geronimo-eclipse-plugin/3.0.0/geronimo-eclipse-plugin-3.0.0-source-release.tar.gz The tag is here: http://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/tags/geronimo-eclipse-plugin-3.0.0/ The deployable zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-deployable.zip The p2 repo zip file is here: http://people.apache.org/builds/geronimo/eclipse/3.0.0/geronimo-eclipse-plugin-3.0.0-p2repo.zip Notice: As update site format is not recommend in eclipse, now only provide the p2 format. If you would like to review and/or comment on the release notes, you can find it here: http://people.apache.org/builds/geronimo/eclipse/updates/PLUGIN_RELEASE-NOTES-3.0.0.txt Finally, I've created a Staging Site that can be used to test the update manager functions of Eclipse (Indigo SR2 and Juno): http://people.apache.org/builds/geronimo/eclipse/updates/ The vote will be open for the 72-hour minimum. [ ] +1 about time to push this out the door [ ] 0 no opinion [ ] -1 not this one (please explain why) -- Best regards! John Xiao -- Best regards! John Xiao -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna
[jira] [Resolved] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet resolved GERONIMO-6373.
---
Resolution: Fixed
Not sure which version I should put. djencks ?
> Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
> concurrency
>
>
> Key: GERONIMO-6373
> URL: https://issues.apache.org/jira/browse/GERONIMO-6373
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
>Affects Versions: 2.2.1
>Reporter: Gary Tully
>Assignee: Guillaume Nodet
> Attachments: GERONIMO-6372.patch
>
>
> HOWL XALogger supports flushPartialBuffers which is not configurable via
> Geronimo HOWLLog. It is useful in the case of low concurrency.
> It would be great to have this exposed in the HOWLLog constructor so that it
> be be configured.
> {code} /**
>* Indicates whether LogBufferManager should flush buffers
>* before they are full.
>*
>* Normally, buffers are flushed to disk only when
>* they become full. In lightly loaded situations,
>* one or more threads may have to wait until the
>* flushSleepTime expires before the buffer is written.
>* In the worst case, a single thread is using the
>* log, and every put() with sync requested will
>* be delayed flushSleepTime ms before the buffer is
>* written.
>*
>* Setting flushPartialBuffers true will allow
>* the LogBufferManager to flush buffers to disk
>* any time the channel is not busy. This improves
>* throughput in single threaded and lightly loaded
>* environments.
>*
>* By default, this feature is disabled (false) to
>* provide compatability with earlier versions of
>* this library.
>*/
> private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6372) RecoveryImpl completing in-progress transactions, XidFactoryImpl needs to be smarter with matching
[
https://issues.apache.org/jira/browse/GERONIMO-6372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned GERONIMO-6372:
-
Assignee: Guillaume Nodet
> RecoveryImpl completing in-progress transactions, XidFactoryImpl needs to be
> smarter with matching
> --
>
> Key: GERONIMO-6372
> URL: https://issues.apache.org/jira/browse/GERONIMO-6372
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
>Affects Versions: 2.2
> Environment: Aries, OSGI, camel, activemq
>Reporter: Gary Tully
>Assignee: Guillaume Nodet
> Attachments: GERONIMO-6372.patch
>
>
> Given a camel route with from("activemq:a").to("activemq:b") in a Geronimo
> managed XA transaction. On start/restart new transactions are created in
> parallel with recovery of the jms components.
> There are two issues:
> * The Recovery processing can match new transactions through the
> XidFactory.matchXX methods and rollback new work in error. (Note: a
> xa_recover of activemq correctly returns *all* prepared transactions)
> * The XidFactoryImpl(byte[] seed) can create duplicate xids which could
> potentially interfere with recovering transactions and makes it impossible to
> determine from the logs what is going on.
> Xids should be globally unique and recoverable. So they need a persistent
> unique seed (provided through configuration) and an ever increasing id.
> The current time provides a simple approach to an increasing id that negates
> the need to persist the last used id in the transaction recovery log.
> (It has the downside of regressing if the XidFactory is recreated in the same
> millisecond, but I think this is in practice improbable outside unit tests.)
> If the id component is keyed of the epoch, a recovering XidFactory can match
> only old Xids, ones created by it in a previous incarnation. In this way it
> can avoid completing newly created transactions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (GERONIMO-6373) Expose HOWL flushPartialBuffer config via HOWLLog - useful under low concurrency
[
https://issues.apache.org/jira/browse/GERONIMO-6373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guillaume Nodet reassigned GERONIMO-6373:
-
Assignee: Guillaume Nodet (was: David Jencks)
> Expose HOWL flushPartialBuffer config via HOWLLog - useful under low
> concurrency
>
>
> Key: GERONIMO-6373
> URL: https://issues.apache.org/jira/browse/GERONIMO-6373
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: transaction manager
>Affects Versions: 2.2.1
>Reporter: Gary Tully
>Assignee: Guillaume Nodet
> Attachments: GERONIMO-6372.patch
>
>
> HOWL XALogger supports flushPartialBuffers which is not configurable via
> Geronimo HOWLLog. It is useful in the case of low concurrency.
> It would be great to have this exposed in the HOWLLog constructor so that it
> be be configured.
> {code} /**
>* Indicates whether LogBufferManager should flush buffers
>* before they are full.
>*
>* Normally, buffers are flushed to disk only when
>* they become full. In lightly loaded situations,
>* one or more threads may have to wait until the
>* flushSleepTime expires before the buffer is written.
>* In the worst case, a single thread is using the
>* log, and every put() with sync requested will
>* be delayed flushSleepTime ms before the buffer is
>* written.
>*
>* Setting flushPartialBuffers true will allow
>* the LogBufferManager to flush buffers to disk
>* any time the channel is not busy. This improves
>* throughput in single threaded and lightly loaded
>* environments.
>*
>* By default, this feature is disabled (false) to
>* provide compatability with earlier versions of
>* this library.
>*/
> private boolean flushPartialBuffers = false;{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
