[jira] [Created] (LANG-1378) Conditional expansion (variation of default value syntax)
Charles Fineman created LANG-1378: - Summary: Conditional expansion (variation of default value syntax) Key: LANG-1378 URL: https://issues.apache.org/jira/browse/LANG-1378 Project: Commons Lang Issue Type: Improvement Components: lang.text.* Affects Versions: 3.7 Reporter: Charles Fineman Fix For: 3.8 I'd like to propose an extension to the current syntax (and would consider submitting a PR for it if folks are in favor of the proposal) There is currently support for: ${undefined.number:-1234567890} I'm proposing adding: ${defined.number:?The number is ${defined.number}} My quick glance of the recursive interpolation makes me feel this would be relatively straightforward. Curious when the next version would be released (I asked because I could actually make use of this in something I'm working on right now) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NUMBERS-17) 4D capacity for ComplexUtils
[ https://issues.apache.org/jira/browse/NUMBERS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16347051#comment-16347051 ] Gilles commented on NUMBERS-17: --- Let's keep it open until we decide on the way forward (replace with streams, move to another module). Also: coverage is much too low (~15%) for {{ComplexUtils}} (mostly 3D and 4D utilities). > 4D capacity for ComplexUtils > > > Key: NUMBERS-17 > URL: https://issues.apache.org/jira/browse/NUMBERS-17 > Project: Commons Numbers > Issue Type: Improvement >Reporter: Eric Barnhill >Priority: Minor > > Adding 4D capacity to the ComplexUtils will make them compatible with the > NIfTI medical image file format which is by default in 4D. Right now neither > Java library that handles .nii files handles complex .nii files so this > library will greatly facilitate that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NUMBERS-17) 4D capacity for ComplexUtils
[ https://issues.apache.org/jira/browse/NUMBERS-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346872#comment-16346872 ] Eric Barnhill commented on NUMBERS-17: -- This was merged into master and can be closed. See commit d8766052e1f10c146fb112495abe74795d390f75 . > 4D capacity for ComplexUtils > > > Key: NUMBERS-17 > URL: https://issues.apache.org/jira/browse/NUMBERS-17 > Project: Commons Numbers > Issue Type: Improvement >Reporter: Eric Barnhill >Priority: Minor > > Adding 4D capacity to the ComplexUtils will make them compatible with the > NIfTI medical image file format which is by default in 4D. Right now neither > Java library that handles .nii files handles complex .nii files so this > library will greatly facilitate that. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (DBCP-484) Connection leak during XATransaction in high load
[ https://issues.apache.org/jira/browse/DBCP-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346724#comment-16346724 ] Emanuel Freitas commented on DBCP-484: -- Hello, For some reason (JIRA could not attach the file as there was a missing token. Please try attaching the file again.) i'm not able to atach the files. Where is a link to dropbox: [https://www.dropbox.com/s/g0oiz2wizmedeqs/dbcp-test.zip?dl=0] If you run the TeskLeak you can see that if you increase the number of threads (nthreads) you start getting some leaks. On our project I was able to fix the issue with the code that I posted above, but for this test the problem is something else. For this tests I was using a PostgreSQL database. Thanks for your help. Kind regards, Emanuel > Connection leak during XATransaction in high load > - > > Key: DBCP-484 > URL: https://issues.apache.org/jira/browse/DBCP-484 > Project: Commons Dbcp > Issue Type: Bug >Affects Versions: 2.2.0 >Reporter: Emanuel Freitas >Priority: Major > > We're experiencing a connection leak in a distributed transaction when the > system is under heavy load. We're using commons-dbcp (latest version) + > eclipselink and narayana to perform transaction coordination. > From time to time we can see a stacktrace reporting an abandoned connection. > We are trying to figure out what's the root cause and we think that might be > some issue in the commons dbcp (not sure) . More specifically, this parte of > the code: > ManagedConnection#updateTransactionStatus > {code:java} > if (transactionContext != null) { > if (transactionContext.isActive()) { > if (transactionContext != > transactionRegistry.getActiveTransactionContext()) { > throw new SQLException("Connection can not be used while enlisted > in another transaction"); > } > return; > } > // transaction should have been cleared up by TransactionContextListener, > but in > // rare cases another lister could have registered which uses the > connection before > // our listener is called. In that rare case, trigger the transaction > complete call now > transactionComplete(); > }{code} > > If the transactionContext is different than null but the state is not > "active" (ex: STATUS_ROLLEDBACK, STATUS_ROLLING_BACK, etc) it executes the > transactionComplete mothod that clears the reference to a shared connection > and after that the connection is never closed (returned to the pool). > > If we move the transactionComplete(); to an else,(see below), the connection > leak does not happen. > {code:java} > if (transactionContext != null) { > if (transactionContext.isActive()) { > if (transactionContext != > transactionRegistry.getActiveTransactionContext()) { > throw new SQLException("Connection can not be used while enlisted > in another transaction"); > } > return; > } > } else { > transactionComplete(); > }{code} > > After this the dbcp unit tests still pass but I'm not sure about this > changes. Can you please check? > Thanks > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MATH-1416) Depend on "Commons Numbers"
[ https://issues.apache.org/jira/browse/MATH-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346686#comment-16346686 ] Gilles commented on MATH-1416: -- Package {{o.a.c.math4.primes}} was removed in commit d7f522e317388fe603bf5f14194819264d57d81e (on "master"). > Depend on "Commons Numbers" > --- > > Key: MATH-1416 > URL: https://issues.apache.org/jira/browse/MATH-1416 > Project: Commons Math > Issue Type: Task >Reporter: Gilles >Priority: Major > Labels: dependency, deprecated > Fix For: 4.0 > > > The following codes with an equivalent in ["Commons > Numbers"|http://commons.apache.org/proper/commons-numbers] must be deleted > before the next major release (4.0): > * Package {{o.a.c.math4.fraction}} > * Package {{o.a.c.math4.complex}} > * Package {{o.a.c.math4.primes}} > Codes that depend on these functionalities must be updated with corresponding > calls to "Commons Numbers" classes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MATH-1446) Delete class "Fraction"
Gilles created MATH-1446: Summary: Delete class "Fraction" Key: MATH-1446 URL: https://issues.apache.org/jira/browse/MATH-1446 Project: Commons Math Issue Type: Sub-task Reporter: Gilles Replace all occurrences of that class by its equivalent in "Commons Numbers" (defined in module {{commons-numbers-fraction}}). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MATH-1445) Delete class "Complex"
Gilles created MATH-1445: Summary: Delete class "Complex" Key: MATH-1445 URL: https://issues.apache.org/jira/browse/MATH-1445 Project: Commons Math Issue Type: Sub-task Reporter: Gilles Fix For: 4.0 Replace all occurrences of that class by its equivalent in "Commons Numbers" (defined in module {{commons-numbers-complex}}). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (RNG-40) Ready for JDK 9 ?
[ https://issues.apache.org/jira/browse/RNG-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16346663#comment-16346663 ] Gilles commented on RNG-40: --- To do: write an example (in module {{commons-rng-examples}} showing that all the JARs are Java 9 module compliant. > Ready for JDK 9 ? > - > > Key: RNG-40 > URL: https://issues.apache.org/jira/browse/RNG-40 > Project: Commons RNG > Issue Type: Sub-task >Reporter: Gilles >Priority: Major > Labels: java9 > Fix For: 1.1 > > > Cf. [this post|http://markmail.org/message/j7ki3x67kd2kpavj] on the ML. -- This message was sent by Atlassian JIRA (v7.6.3#76005)