[jira] Resolved: (DAEMON-147) Error in documentation
[ https://issues.apache.org/jira/browse/DAEMON-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved DAEMON-147. - Resolution: Fixed > Error in documentation > -- > > Key: DAEMON-147 > URL: https://issues.apache.org/jira/browse/DAEMON-147 > Project: Commons Daemon > Issue Type: Bug >Affects Versions: 1.0.2 >Reporter: David Newcomb >Priority: Minor > > --StopMode --StartMode > Description says "Can one of jvmjava or exe" but the default is "executable" > which is not one of the list. > --LogLevel > Description says "Defines the logging level and can be either error, info, > warn or debug" but the default is "INFO" which is not in the list of > possible. Is the option case insensitive > Formatting of example has broken down in sections: Installing services, > Updating services and Debugging services. > In section "Procrun monitor application" > //MS//Monitor service Put the icon in the system try <--- > should by "tray" > In section: Command line parameters > --StartMethod MainMethod name if differs then main > Description doesn't mean anything! It suggests the only value is "Main" or > "main". > Do you mean "--StartMethod main Method name if differs from main" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-152) Prunsrv could check service type before modifying it
[ https://issues.apache.org/jira/browse/DAEMON-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated DAEMON-152: Summary: Prunsrv could check service type before modifying it (was: Prunsrv could check service type before deleting it) > Prunsrv could check service type before modifying it > > > Key: DAEMON-152 > URL: https://issues.apache.org/jira/browse/DAEMON-152 > Project: Commons Daemon > Issue Type: Improvement > Components: Procrun >Reporter: Sebb > > When prunsrv creates a service, it creates additional registry entries under > HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ProcRun > 2.0\ > To prevent accidental changes to other services, prunsrv could check that > this entry exists before allowing any modifications to the service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-152) Prunsrv could check service type before deleting it
Prunsrv could check service type before deleting it --- Key: DAEMON-152 URL: https://issues.apache.org/jira/browse/DAEMON-152 Project: Commons Daemon Issue Type: Improvement Components: Procrun Reporter: Sebb When prunsrv creates a service, it creates additional registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\ProcRun 2.0\ To prevent accidental changes to other services, prunsrv could check that this entry exists before allowing any modifications to the service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-151) Enable/Disable fields on the Start/Stop panels according to which Mode is selected
Enable/Disable fields on the Start/Stop panels according to which Mode is selected -- Key: DAEMON-151 URL: https://issues.apache.org/jira/browse/DAEMON-151 Project: Commons Daemon Issue Type: Improvement Components: Procrun Reporter: Sebb Priority: Minor Some of the Start/Stop panel fields are only appropriate for certain modes. It would be useful if the irrelevant fields were disabled depending on the mode. At present, only the Start/StopImage fields are processed. However the Class: field does not apply to mode=exe and the Method field only applies to mode=jvm -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAEMON-134) The field DaemonLoader.Context.controller is hiding a field from type DaemonLoader
[ https://issues.apache.org/jira/browse/DAEMON-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved DAEMON-134. - Resolution: Fixed URL: http://svn.apache.org/viewvc?rev=925051&view=rev Log: DAEMON-134 The field DaemonLoader.Context.controller is hiding a field from type DaemonLoader Modified: commons/proper/daemon/trunk/src/java/org/apache/commons/daemon/support/DaemonLoader.java > The field DaemonLoader.Context.controller is hiding a field from type > DaemonLoader > -- > > Key: DAEMON-134 > URL: https://issues.apache.org/jira/browse/DAEMON-134 > Project: Commons Daemon > Issue Type: Bug >Reporter: Sebb >Priority: Minor > > The field DaemonLoader.Context.controller is hiding a field from type > DaemonLoader. > It's confusing to have two fields called "controller" in the same source file. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (MATH-354) compiler dependency in RandomDataImpl.getPoisson(double mean)
[ https://issues.apache.org/jira/browse/MATH-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Phil Steitz resolved MATH-354. -- Resolution: Fixed Fix Version/s: 2.1 The method has been rewritten in version 2.1. The current version no longer includes the compiler-dependent code referenced in this issue. > compiler dependency in RandomDataImpl.getPoisson(double mean) > - > > Key: MATH-354 > URL: https://issues.apache.org/jira/browse/MATH-354 > Project: Commons Math > Issue Type: Bug >Affects Versions: 2.0 > Environment: jre1.5/jre1.6 >Reporter: Michael Sammeth > Fix For: 2.1 > > > Hi, > in RandomDataImpl.getPoisson(double mean) I got the following problem in the > case mean>= 6.0: > in the branch if (u <= c1): > if (x < -mu) > w = Double.POSITIVE_INFINITY; > implicits that (int) (mu+ x) < 0 > I found that for some compiler/run-time environments the subsequent update of > the "accept" value then fails, as by the right hand side of the comparison > leads to an Exception in MathUtils.factorialLog((int) (mu + x)). Some > compiler/jre combinations, however, skip evaluating the right side as by > isInfinity(w). > To ensure stability, I currently worked around by an explicit > if(Double.isInfinity(w)) branch, however, I would like to ask whether there > is a more elegant way to ensure general functionality of that method. > Thank you, micha. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (LANG-606) EqualsBuilder causes StackOverflowException
[
https://issues.apache.org/jira/browse/LANG-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Sauder updated LANG-606:
---
Attachment: EqualsBuilderCyclicalObjectReferences-v01.patch
Strange. I created the patch with svn diff >
EqualsBuilderCyclicalObjectReferences.patch. When I then reverted all files
(svn revert -R .) and tried to apply the patch it did not apply cleanly on my
system either.
After some research I found out that I probably hit a subversion bug
(http://subversion.tigris.org/issues/show_bug.cgi?id=2164).
Well to workaround this problem instead of using svn diff I used the old
fashion but working diff utility.
This patch now applies cleanly with the command patch -p1 -i
EqualsBuilderCyclicalObjectReferences-v01.patch.
> EqualsBuilder causes StackOverflowException
> ---
>
> Key: LANG-606
> URL: https://issues.apache.org/jira/browse/LANG-606
> Project: Commons Lang
> Issue Type: Bug
> Components: lang.builder.*
>Affects Versions: 2.5
>Reporter: Oliver Sauder
>Priority: Minor
> Fix For: 3.0
>
> Attachments: EqualsBuilderCyclicalObjectReferences-v01.patch,
> EqualsBuilderCyclicalObjectReferences.patch
>
>
> EqualsBuilder causes StackOverflowException when comparing objects with
> cyclical object references.
> e,g.
> static class TestObjectReference {
> @SuppressWarnings("unused")
> private TestObjectReference reference;
> @SuppressWarnings("unused")
> private TestObject one;
>
> public TestObjectReference(int one) {
> this.one = new TestObject(one);
> }
>
> public void setObjectReference(
> TestObjectReference reference) {
> this.reference = reference;
> }
> @Override
> public boolean equals(Object obj) {
> return EqualsBuilder.reflectionEquals(this, obj);
> }
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (MATH-354) compiler dependency in RandomDataImpl.getPoisson(double mean)
compiler dependency in RandomDataImpl.getPoisson(double mean) - Key: MATH-354 URL: https://issues.apache.org/jira/browse/MATH-354 Project: Commons Math Issue Type: Bug Affects Versions: 2.0 Environment: jre1.5/jre1.6 Reporter: Michael Sammeth Hi, in RandomDataImpl.getPoisson(double mean) I got the following problem in the case mean>= 6.0: in the branch if (u <= c1): if (x < -mu) w = Double.POSITIVE_INFINITY; implicits that (int) (mu+ x) < 0 I found that for some compiler/run-time environments the subsequent update of the "accept" value then fails, as by the right hand side of the comparison leads to an Exception in MathUtils.factorialLog((int) (mu + x)). Some compiler/jre combinations, however, skip evaluating the right side as by isInfinity(w). To ensure stability, I currently worked around by an explicit if(Double.isInfinity(w)) branch, however, I would like to ask whether there is a more elegant way to ensure general functionality of that method. Thank you, micha. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-150) Defaults for Log file name prefixes
Defaults for Log file name prefixes --- Key: DAEMON-150 URL: https://issues.apache.org/jira/browse/DAEMON-150 Project: Commons Daemon Issue Type: Improvement Components: Procrun Reporter: Sebb Priority: Minor Stdout and stderr use the fixed prefix 'service' for the log file names. This makes it impossible to use the same log directory for multiple services It would be better to prefix stdout and stderr with either the ServiceName or the LogPrefix. Also, perhaps LogPrefix should default to the ServiceName. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DAEMON-149) Default LogPath is not honoured
[ https://issues.apache.org/jira/browse/DAEMON-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved DAEMON-149. - Resolution: Fixed That's a documentation bug. The LogFile actually defaults to: %SystemRoot%\System32\LogFiles\Apache (at least on Win/XP) The directory is created if needed. The documentation has been updated. > Default LogPath is not honoured > --- > > Key: DAEMON-149 > URL: https://issues.apache.org/jira/browse/DAEMON-149 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Reporter: David Newcomb >Priority: Minor > Fix For: 1.0.3 > > > According to the documentation default values exist for the following command > line options. > --LogPath %SystemRoot%\System\LogFiles\Apache > --LogPrefix jakarta_service_ > --LogLevelINFO > If I create the folder %SystemRoot%\System\LogFiles\Apache then run my usual > tomcat6 command line (without specifying LogPath, LogPrefix or LogLevel) then > the log file is not created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAEMON-147) Error in documentation
[ https://issues.apache.org/jira/browse/DAEMON-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847035#action_12847035 ] Sebb commented on DAEMON-147: - Thanks, these have all been fixed in SVN and will be in the next release of the website. > Error in documentation > -- > > Key: DAEMON-147 > URL: https://issues.apache.org/jira/browse/DAEMON-147 > Project: Commons Daemon > Issue Type: Bug >Affects Versions: 1.0.2 >Reporter: David Newcomb >Priority: Minor > > --StopMode --StartMode > Description says "Can one of jvmjava or exe" but the default is "executable" > which is not one of the list. > --LogLevel > Description says "Defines the logging level and can be either error, info, > warn or debug" but the default is "INFO" which is not in the list of > possible. Is the option case insensitive > Formatting of example has broken down in sections: Installing services, > Updating services and Debugging services. > In section "Procrun monitor application" > //MS//Monitor service Put the icon in the system try <--- > should by "tray" > In section: Command line parameters > --StartMethod MainMethod name if differs then main > Description doesn't mean anything! It suggests the only value is "Main" or > "main". > Do you mean "--StartMethod main Method name if differs from main" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (LANG-597) Add more utility methods for generic types
[ https://issues.apache.org/jira/browse/LANG-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David M. Sledge updated LANG-597: - Attachment: (was: TypeUtils-Added-Utitlities-Lang-597-2010-03-03.patch) > Add more utility methods for generic types > -- > > Key: LANG-597 > URL: https://issues.apache.org/jira/browse/LANG-597 > Project: Commons Lang > Issue Type: Improvement > Components: lang.reflect.* > Environment: Java 1.5+ >Reporter: David M. Sledge >Priority: Minor > Fix For: 3.0 > > Attachments: TypeUtils-Added-Utitlities-Lang-597-2010-03-18.patch > > > Added type utilities include: > * checking if one type can be assigned to another type > * determining if a value can be assigned to a given generic type > * for a class that declares type variables, determining what the type > arguments would be based on a generic sub or super type > * determining if a group of types satisfy the bounds of a group of type > variables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (LANG-597) Add more utility methods for generic types
[ https://issues.apache.org/jira/browse/LANG-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David M. Sledge updated LANG-597: - Attachment: TypeUtils-Added-Utitlities-Lang-597-2010-03-18.patch Done, done, and done. This new patch is against the latest in svn as of 2010-03-18 11:45 am Mountain. > Add more utility methods for generic types > -- > > Key: LANG-597 > URL: https://issues.apache.org/jira/browse/LANG-597 > Project: Commons Lang > Issue Type: Improvement > Components: lang.reflect.* > Environment: Java 1.5+ >Reporter: David M. Sledge >Priority: Minor > Fix For: 3.0 > > Attachments: TypeUtils-Added-Utitlities-Lang-597-2010-03-18.patch > > > Added type utilities include: > * checking if one type can be assigned to another type > * determining if a value can be assigned to a given generic type > * for a class that declares type variables, determining what the type > arguments would be based on a generic sub or super type > * determining if a group of types satisfy the bounds of a group of type > variables -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-149) Default LogPath is not honoured
Default LogPath is not honoured --- Key: DAEMON-149 URL: https://issues.apache.org/jira/browse/DAEMON-149 Project: Commons Daemon Issue Type: Bug Components: Procrun Reporter: David Newcomb Priority: Minor Fix For: 1.0.3 According to the documentation default values exist for the following command line options. --LogPath %SystemRoot%\System\LogFiles\Apache --LogPrefix jakarta_service_ --LogLevel INFO If I create the folder %SystemRoot%\System\LogFiles\Apache then run my usual tomcat6 command line (without specifying LogPath, LogPrefix or LogLevel) then the log file is not created. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-148) Incorrect case on parameter causes silent failure
Incorrect case on parameter causes silent failure - Key: DAEMON-148 URL: https://issues.apache.org/jira/browse/DAEMON-148 Project: Commons Daemon Issue Type: Bug Components: Procrun Reporter: David Newcomb Fix For: 1.0.3 Unknown parameters passed to procrun halt command line option processing, silently ignoring the other options, then reports as successful. For example: C:\Data\tomcat\bin\tomcat6.exe //US//Tomcat ^ --LogPath C:\Data\tomcat\logs ^ --LogPrefix commons-daemon ^ --LogLevel debug ^ --Description "Apache Tomcat - Company app" ^ --StartClass org.apache.catalina.startup.Bootstrap ^ --StopClass org.apache.catalina.startup.Bootstrap ^ --StartParams start ^ --StopParams stop ^ --DependsOn MySQL ^ --StartMode jvm ^ --StopMode jvm ^ --JvmOptions -Dcatalina.base=C:\Data\tomcat ^ --JvmOptions -Dcatalina.home=C:\Data\tomcat ^ --JvmOptions -Djava.endorsed.dirs=C:\Data\tomcat\endorsed ^ --classpath C:\Data\tomcat\bin\bootstrap.jar ^ --JvmOptions -Djava.io.tmpdir=C:\Data\tomcat\temp ^ --JvmOptions -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager ^ --JvmOptions -Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties ^ --JvmOptions -Dcom.sun.management.jmxremote ^ --JvmOptions -Dcom.sun.management.jmxremote.port=8181 ^ --JvmOptions -Dcom.sun.management.jmxremote.authenticate=false ^ --JvmOptions -Dcom.sun.management.jmxremote.ssl=false ^ --JvmOptions -XX:+HeapDumpOnOutOfMemoryError ^ --JvmMs 256 ^ --JvmMx 512 ^ --Jvm c:\data\java\bin\server\jvm.dll ^ --JavaHome c:\data\java ^ --Startup auto The "--classpath C:\Data\tomcat\bin\bootstrap.jar ^" line introduces an invalid command line parameter. It should be --Classpath instead of --classpath. The log reads: [2010-03-18 16:56:00] [debug] ( prunsrv.c:1412) Commons Daemon procrun log initialized [2010-03-18 16:56:00] [info] Commons Daemon procrun (1.0.3.0) started [2010-03-18 16:56:00] [info] Updating service... [2010-03-18 16:56:00] [error] ( service.c:126 ) The specified service does not exist as an installed service. [2010-03-18 16:56:00] [debug] ( prunsrv.c:507 ) Installing service... [2010-03-18 16:56:00] [info] Service Tomcat name [2010-03-18 16:56:00] [debug] ( prunsrv.c:559 ) Setting service description Apache Tomcat - Quantel Dino [2010-03-18 16:56:00] [info] Service 'Tomcat' installed [2010-03-18 16:56:00] [info] Commons Daemon procrun finished Showing that the installation was successful. However if you load up tomcat6w then you can see in the Java tab that the last option to be processed was "--JvmOptions -Djava.endorsed.dirs" every other entry after that is ignored. This creates an ordering issue with the command line options. If the LogPath is at the end of the parameter list then no output file will be created. As a result running the service always fails. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONFIGURATION-412) Cannot use DatabaseConfiguration if the datasource has autocommit = false
[ https://issues.apache.org/jira/browse/CONFIGURATION-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846986#action_12846986 ] Stefano Bertini commented on CONFIGURATION-412: --- I think that the DatabaseConfiguration should always perform a commit, otherwise the class would not be usable without autocommit = true. Infact, without autocommit = true, sql statements issued by the code would never be committed to the database. > Cannot use DatabaseConfiguration if the datasource has autocommit = false > - > > Key: CONFIGURATION-412 > URL: https://issues.apache.org/jira/browse/CONFIGURATION-412 > Project: Commons Configuration > Issue Type: Bug >Affects Versions: 1.2 > Environment: Windows / Linux - Database Oracle 11 >Reporter: Stefano Bertini >Priority: Critical > > If using a DatabaseConfiguration object with a datasource that has > *autocommit = false*, the setProperty method fails with a *duplicate key* > error. > This happens because in the setProperty method the two calls > _clearProperty(key)_ and _addProperty(key, value)_ can retrieve two different > connections from the database. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DAEMON-146) -Xms and -Xmx are included twice
[ https://issues.apache.org/jira/browse/DAEMON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846862#action_12846862 ] Mladen Turk commented on DAEMON-146: I will leave this open, just because of double -XmsN -XmsN. Your example misses setting classpath so no wonder why it cannot load. Next take a look at Java documentation. The MUST NOT be space between -Xms256m > -Xms and -Xmx are included twice > - > > Key: DAEMON-146 > URL: https://issues.apache.org/jira/browse/DAEMON-146 > Project: Commons Daemon > Issue Type: Bug > Components: Procrun >Reporter: David Newcomb >Priority: Minor > Fix For: 1.0.3 > > > Command line: > "C:\Data\tomcat\bin\tomcat6.exe" //US//Tomcat ^ > --Description "Apache Tomcat - Company App" ^ > --StartClass org.apache.catalina.startup.Bootstrap ^ > --StopClass org.apache.catalina.startup.Bootstrap ^ > --StartParams start ^ > --StopParams stop ^ > --DependsOn MySQL ^ > --StartMode jvm ^ > --StopMode jvm ^ > --JvmOptions "-Dcatalina.base=C:\Data\tomcat" ^ > --JvmOptions "-Dcatalina.home=C:\Data\tomcat" ^ > --JvmOptions "-Djava.endorsed.dirs=C:\Data\tomcat\endorsed" ^ > --JvmOptions "-Djava.io.tmpdir=C:\Data\tomcat\temp" ^ > --JvmOptions > "-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" ^ > --JvmOptions > "-Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties" ^ > --JvmOptions "-Dcom.sun.management.jmxremote" ^ > --JvmOptions "-Dcom.sun.management.jmxremote.port=8181" ^ > --JvmOptions "-Dcom.sun.management.jmxremote.authenticate=false" ^ > --JvmOptions "-Dcom.sun.management.jmxremote.ssl=false" ^ > --JvmOptions "-XX:+HeapDumpOnOutOfMemoryError" ^ > --JvmMs 256 ^ > --JvmMx 512 ^ > --Jvm c:\data\java\bin\server\jvm.dll ^ > --JavaHome c:\data\java ^ > --Startup auto > Produces debug of: > [2010-03-18 10:11:15] [debug] ( prunsrv.c:1412) Commons Daemon procrun log > initialized > [2010-03-18 10:11:15] [info] Commons Daemon procrun (1.0.3.0) started > [2010-03-18 10:11:15] [info] Running 'Tomcat' Service... > [2010-03-18 10:11:15] [debug] ( prunsrv.c:1189) Inside ServiceMain... > [2010-03-18 10:11:15] [info] Starting service... > [2010-03-18 10:11:15] [debug] ( javajni.c:441 ) Jvm Option[0] -Xms256m > [2010-03-18 10:11:15] [debug] ( javajni.c:447 ) Jvm Option[1] -Xmx512m > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[2] > -Dcatalina.base=C:\Data\tomcat > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[3] > -Dcatalina.home=C:\Data\tomcat > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[4] > -Djava.endorsed.dirs=C:\Data\tomcat\endorsed > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[5] > -Djava.io.tmpdir=C:\Data\tomcat\temp > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[6] > -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[7] > -Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[8] > -Dcom.sun.management.jmxremote > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[9] > -Dcom.sun.management.jmxremote.port=8181 > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[10] > -Dcom.sun.management.jmxremote.authenticate=false > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[11] > -Dcom.sun.management.jmxremote.ssl=false > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[12] > -XX:+HeapDumpOnOutOfMemoryError > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[13] > -Djava.class.path= > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[14] -Xms256m > [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[15] -Xmx512m > [2010-03-18 10:11:16] [error] ( javajni.c:611 ) FindClass > org/apache/catalina/startup/Bootstrap failed > [2010-03-18 10:11:16] [error] ( prunsrv.c:999 ) Failed loading main > org/apache/catalina/startup/Bootstrap class > [2010-03-18 10:11:16] [error] ( prunsrv.c:1304) ServiceStart returned 3 > [2010-03-18 10:11:16] [info] Run service finished. > [2010-03-18 10:11:16] [error] ( prunsrv.c:1477) Commons Daemon procrun failed > with exit value: 4 > Xms and Xmx are specified twice. > There is also no space between Xms 256m and Xmx 512m. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-147) Error in documentation
[ https://issues.apache.org/jira/browse/DAEMON-147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Newcomb updated DAEMON-147: - Priority: Minor (was: Major) > Error in documentation > -- > > Key: DAEMON-147 > URL: https://issues.apache.org/jira/browse/DAEMON-147 > Project: Commons Daemon > Issue Type: Bug >Affects Versions: 1.0.2 >Reporter: David Newcomb >Priority: Minor > > --StopMode --StartMode > Description says "Can one of jvmjava or exe" but the default is "executable" > which is not one of the list. > --LogLevel > Description says "Defines the logging level and can be either error, info, > warn or debug" but the default is "INFO" which is not in the list of > possible. Is the option case insensitive > Formatting of example has broken down in sections: Installing services, > Updating services and Debugging services. > In section "Procrun monitor application" > //MS//Monitor service Put the icon in the system try <--- > should by "tray" > In section: Command line parameters > --StartMethod MainMethod name if differs then main > Description doesn't mean anything! It suggests the only value is "Main" or > "main". > Do you mean "--StartMethod main Method name if differs from main" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-147) Error in documentation
Error in documentation -- Key: DAEMON-147 URL: https://issues.apache.org/jira/browse/DAEMON-147 Project: Commons Daemon Issue Type: Bug Affects Versions: 1.0.2 Reporter: David Newcomb --StopMode --StartMode Description says "Can one of jvmjava or exe" but the default is "executable" which is not one of the list. --LogLevel Description says "Defines the logging level and can be either error, info, warn or debug" but the default is "INFO" which is not in the list of possible. Is the option case insensitive Formatting of example has broken down in sections: Installing services, Updating services and Debugging services. In section "Procrun monitor application" //MS// Monitor service Put the icon in the system try <--- should by "tray" In section: Command line parameters --StartMethod MainMethod name if differs then main Description doesn't mean anything! It suggests the only value is "Main" or "main". Do you mean "--StartMethod main Method name if differs from main" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (DAEMON-146) -Xms and -Xmx are included twice
[ https://issues.apache.org/jira/browse/DAEMON-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Newcomb updated DAEMON-146: - Description: Command line: "C:\Data\tomcat\bin\tomcat6.exe" //US//Tomcat ^ --Description "Apache Tomcat - Company App" ^ --StartClass org.apache.catalina.startup.Bootstrap ^ --StopClass org.apache.catalina.startup.Bootstrap ^ --StartParams start ^ --StopParams stop ^ --DependsOn MySQL ^ --StartMode jvm ^ --StopMode jvm ^ --JvmOptions "-Dcatalina.base=C:\Data\tomcat" ^ --JvmOptions "-Dcatalina.home=C:\Data\tomcat" ^ --JvmOptions "-Djava.endorsed.dirs=C:\Data\tomcat\endorsed" ^ --JvmOptions "-Djava.io.tmpdir=C:\Data\tomcat\temp" ^ --JvmOptions "-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" ^ --JvmOptions "-Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties" ^ --JvmOptions "-Dcom.sun.management.jmxremote" ^ --JvmOptions "-Dcom.sun.management.jmxremote.port=8181" ^ --JvmOptions "-Dcom.sun.management.jmxremote.authenticate=false" ^ --JvmOptions "-Dcom.sun.management.jmxremote.ssl=false" ^ --JvmOptions "-XX:+HeapDumpOnOutOfMemoryError" ^ --JvmMs 256 ^ --JvmMx 512 ^ --Jvm c:\data\java\bin\server\jvm.dll ^ --JavaHome c:\data\java ^ --Startup auto Produces debug of: [2010-03-18 10:11:15] [debug] ( prunsrv.c:1412) Commons Daemon procrun log initialized [2010-03-18 10:11:15] [info] Commons Daemon procrun (1.0.3.0) started [2010-03-18 10:11:15] [info] Running 'Tomcat' Service... [2010-03-18 10:11:15] [debug] ( prunsrv.c:1189) Inside ServiceMain... [2010-03-18 10:11:15] [info] Starting service... [2010-03-18 10:11:15] [debug] ( javajni.c:441 ) Jvm Option[0] -Xms256m [2010-03-18 10:11:15] [debug] ( javajni.c:447 ) Jvm Option[1] -Xmx512m [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[2] -Dcatalina.base=C:\Data\tomcat [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[3] -Dcatalina.home=C:\Data\tomcat [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[4] -Djava.endorsed.dirs=C:\Data\tomcat\endorsed [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[5] -Djava.io.tmpdir=C:\Data\tomcat\temp [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[6] -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[7] -Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[8] -Dcom.sun.management.jmxremote [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[9] -Dcom.sun.management.jmxremote.port=8181 [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[10] -Dcom.sun.management.jmxremote.authenticate=false [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[11] -Dcom.sun.management.jmxremote.ssl=false [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[12] -XX:+HeapDumpOnOutOfMemoryError [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[13] -Djava.class.path= [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[14] -Xms256m [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[15] -Xmx512m [2010-03-18 10:11:16] [error] ( javajni.c:611 ) FindClass org/apache/catalina/startup/Bootstrap failed [2010-03-18 10:11:16] [error] ( prunsrv.c:999 ) Failed loading main org/apache/catalina/startup/Bootstrap class [2010-03-18 10:11:16] [error] ( prunsrv.c:1304) ServiceStart returned 3 [2010-03-18 10:11:16] [info] Run service finished. [2010-03-18 10:11:16] [error] ( prunsrv.c:1477) Commons Daemon procrun failed with exit value: 4 Xms and Xmx are specified twice. There is also no space between Xms 256m and Xmx 512m. was: Command line: "C:\Data\tomcat\bin\tomcat6.exe" //US//Tomcat ^ --Description "Apache Tomcat - Quantel Dino" ^ --StartClass org.apache.catalina.startup.Bootstrap ^ --StopClass org.apache.catalina.startup.Bootstrap ^ --StartParams start ^ --StopParams stop ^ --DependsOn MySQL ^ --StartMode jvm ^ --StopMode jvm ^ --JvmOptions "-Dcatalina.base=C:\Data\tomcat" ^ --JvmOptions "-Dcatalina.home=C:\Data\tomcat" ^ --JvmOptions "-Djava.endorsed.dirs=C:\Data\tomcat\endorsed" ^ --JvmOptions "-Djava.io.tmpdir=C:\Data\tomcat\temp" ^ --JvmOptions "-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" ^ --JvmOptions "-Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties" ^ --JvmOptions "-Dcom.sun.management.jmxremote" ^ --JvmOptions "-Dcom.sun.management.jmxremote.port=8181" ^ --JvmOptions "-Dcom.sun.management.jmxremote.authenticate=false" ^ --JvmOptions "-Dcom.sun.management.jmxremote.ssl=false" ^ --JvmOptions "-XX:+HeapDumpOnOutOfMemoryError" ^ --JvmMs 256 ^ --JvmMx 512 ^ --Jvm c:\data\java\bin\server\jvm.dll ^ --JavaHome c:\data\java ^ --Startup auto Produces debug of: [2010-03-18 10:11:15] [debug] ( prunsrv.c:1412) Commons Daemon p
[jira] Created: (DAEMON-146) -Xms and -Xmx are included twice
-Xms and -Xmx are included twice - Key: DAEMON-146 URL: https://issues.apache.org/jira/browse/DAEMON-146 Project: Commons Daemon Issue Type: Bug Components: Procrun Reporter: David Newcomb Priority: Minor Fix For: 1.0.3 Command line: "C:\Data\tomcat\bin\tomcat6.exe" //US//Tomcat ^ --Description "Apache Tomcat - Quantel Dino" ^ --StartClass org.apache.catalina.startup.Bootstrap ^ --StopClass org.apache.catalina.startup.Bootstrap ^ --StartParams start ^ --StopParams stop ^ --DependsOn MySQL ^ --StartMode jvm ^ --StopMode jvm ^ --JvmOptions "-Dcatalina.base=C:\Data\tomcat" ^ --JvmOptions "-Dcatalina.home=C:\Data\tomcat" ^ --JvmOptions "-Djava.endorsed.dirs=C:\Data\tomcat\endorsed" ^ --JvmOptions "-Djava.io.tmpdir=C:\Data\tomcat\temp" ^ --JvmOptions "-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" ^ --JvmOptions "-Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties" ^ --JvmOptions "-Dcom.sun.management.jmxremote" ^ --JvmOptions "-Dcom.sun.management.jmxremote.port=8181" ^ --JvmOptions "-Dcom.sun.management.jmxremote.authenticate=false" ^ --JvmOptions "-Dcom.sun.management.jmxremote.ssl=false" ^ --JvmOptions "-XX:+HeapDumpOnOutOfMemoryError" ^ --JvmMs 256 ^ --JvmMx 512 ^ --Jvm c:\data\java\bin\server\jvm.dll ^ --JavaHome c:\data\java ^ --Startup auto Produces debug of: [2010-03-18 10:11:15] [debug] ( prunsrv.c:1412) Commons Daemon procrun log initialized [2010-03-18 10:11:15] [info] Commons Daemon procrun (1.0.3.0) started [2010-03-18 10:11:15] [info] Running 'Tomcat' Service... [2010-03-18 10:11:15] [debug] ( prunsrv.c:1189) Inside ServiceMain... [2010-03-18 10:11:15] [info] Starting service... [2010-03-18 10:11:15] [debug] ( javajni.c:441 ) Jvm Option[0] -Xms256m [2010-03-18 10:11:15] [debug] ( javajni.c:447 ) Jvm Option[1] -Xmx512m [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[2] -Dcatalina.base=C:\Data\tomcat [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[3] -Dcatalina.home=C:\Data\tomcat [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[4] -Djava.endorsed.dirs=C:\Data\tomcat\endorsed [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[5] -Djava.io.tmpdir=C:\Data\tomcat\temp [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[6] -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[7] -Djava.util.logging.config.file=C:\Data\tomcat\conf\logging.properties [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[8] -Dcom.sun.management.jmxremote [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[9] -Dcom.sun.management.jmxremote.port=8181 [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[10] -Dcom.sun.management.jmxremote.authenticate=false [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[11] -Dcom.sun.management.jmxremote.ssl=false [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[12] -XX:+HeapDumpOnOutOfMemoryError [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[13] -Djava.class.path= [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[14] -Xms256m [2010-03-18 10:11:15] [debug] ( javajni.c:456 ) Jvm Option[15] -Xmx512m [2010-03-18 10:11:16] [error] ( javajni.c:611 ) FindClass org/apache/catalina/startup/Bootstrap failed [2010-03-18 10:11:16] [error] ( prunsrv.c:999 ) Failed loading main org/apache/catalina/startup/Bootstrap class [2010-03-18 10:11:16] [error] ( prunsrv.c:1304) ServiceStart returned 3 [2010-03-18 10:11:16] [info] Run service finished. [2010-03-18 10:11:16] [error] ( prunsrv.c:1477) Commons Daemon procrun failed with exit value: 4 Xms and Xmx are specified twice. There is also no space between Xms 256m and Xmx 512m. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (DAEMON-145) Incomplete start options causes crash with no error message
Incomplete start options causes crash with no error message --- Key: DAEMON-145 URL: https://issues.apache.org/jira/browse/DAEMON-145 Project: Commons Daemon Issue Type: Bug Components: Procrun Affects Versions: 1.0.3 Reporter: David Newcomb Priority: Minor Fix For: 1.0.3 With options: -Dcatalina.home=C:\Data\tomcat -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8181 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -XX:+HeapDumpOnOutOfMemoryError Debug (all messages): [2010-03-18 09:54:41] [debug] ( prunsrv.c:1412) Commons Daemon procrun log initialized [2010-03-18 09:54:41] [info] Commons Daemon procrun (1.0.3.0) started [2010-03-18 09:54:41] [info] Running 'Tomcat' Service... [2010-03-18 09:54:42] [debug] ( prunsrv.c:1189) Inside ServiceMain... The options may be incomplete, but it shouldn't crash with no message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CONFIGURATION-412) Cannot use DatabaseConfiguration if the datasource has autocommit = false
[
https://issues.apache.org/jira/browse/CONFIGURATION-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846783#action_12846783
]
Oliver Heger commented on CONFIGURATION-412:
Would it be a solution to provide an implementation of {{setProperty()}} that
issues a single UPDATE statement? Or should {{DatabaseConfiguration}} be
extended to perform commits if configured?
> Cannot use DatabaseConfiguration if the datasource has autocommit = false
> -
>
> Key: CONFIGURATION-412
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-412
> Project: Commons Configuration
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows / Linux - Database Oracle 11
>Reporter: Stefano Bertini
>Priority: Critical
>
> If using a DatabaseConfiguration object with a datasource that has
> *autocommit = false*, the setProperty method fails with a *duplicate key*
> error.
> This happens because in the setProperty method the two calls
> _clearProperty(key)_ and _addProperty(key, value)_ can retrieve two different
> connections from the database.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (LANG-609) Support lazy initialization using atomic variables
[
https://issues.apache.org/jira/browse/LANG-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger updated LANG-609:
--
Attachment: AtomicInitializer.patch
The patch contains an implementation of the AtomicInitializer class. A new
interface {{ConcurrentInitializer}} was introduced which is now implemented by
all initializer classes. Also, an abstract base class for testing initializer
implementations was added.
> Support lazy initialization using atomic variables
> --
>
> Key: LANG-609
> URL: https://issues.apache.org/jira/browse/LANG-609
> Project: Commons Lang
> Issue Type: New Feature
> Components: lang.concurrent.*
>Reporter: Oliver Heger
>Priority: Minor
> Fix For: 3.0
>
> Attachments: AtomicInitializer.patch
>
>
> In the new concurrent package there is already the {{LazyInitializer}} class
> implementing the double-check idiom for lazy initialization of instance
> fields. Another way to perform initialization lazily would be the usage of
> atomic variables. This solution would not need synchronization at all. If
> there is low contention (not many threads in parallel), it is more efficient
> than synchronized access. Its drawback is that the initialization may be done
> multiple times if multiple threads access the initializer almost at the same
> time (however, it can be guaranteed that always the same object created by
> the initializer is returned).
> This is a proposal to add an {{AtomicInitializer}} class as an alternative to
> {{LazyInitializer}} that operates on {{AtomicReference}} variables.
> In order to make the initializers smoothly exchangable, it would make sense
> for them to share a common interface. This interface could also be
> implemented by the {{BackgroundInitializer}} class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
