[jira] [Commented] (EMAIL-112) DataSourceFileResolverTest fails under IBM JDK 1.4 and 1.6 running on Windows
[
https://issues.apache.org/jira/browse/EMAIL-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184308#comment-13184308
]
Peter Kofler commented on EMAIL-112:
changed the name of the non existing test file. this is no fix of the problem?
in IBM JDK, but the tests succeed now, so it's ok.
> DataSourceFileResolverTest fails under IBM JDK 1.4 and 1.6 running on Windows
> -
>
> Key: EMAIL-112
> URL: https://issues.apache.org/jira/browse/EMAIL-112
> Project: Commons Email
> Issue Type: Bug
>Affects Versions: 1.3
> Environment: Windows 7x64,
> java version "1.7.0"
> Java(TM) SE Runtime Environment (build pwi3270-20110906_01)
> IBM J9 VM (build 2.6, JRE 1.7.0 Windows 7 x86-32 20110810_88604 (JIT enabled,
> AOT enabled)
> J9VM - R26_Java726_GA_20110810_1208_B88592
>Reporter: Peter Kofler
>Priority: Minor
> Labels: test
> Attachments: EMAIL-112.patch
>
>
>
> assertNull(toByteArray(dataSourceResolver.resolve("/images/does-not-exist.gif")));
> fails because IBM JDK under Windows assumes "/xxx" NOT to be absolute.
--
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] [Commented] (EXEC-56) CommandLine toString() might be confusing for troubleshooting purposes
[
https://issues.apache.org/jira/browse/EXEC-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13144804#comment-13144804
]
Peter Kofler commented on EXEC-56:
--
Sorry, somehow my version was old, although I did several times svn up...
Forget the patch!
> CommandLine toString() might be confusing for troubleshooting purposes
> --
>
> Key: EXEC-56
> URL: https://issues.apache.org/jira/browse/EXEC-56
> Project: Commons Exec
> Issue Type: Improvement
>Affects Versions: 1.1
>Reporter: Nickolay Martinov
>Assignee: Siegfried Goeschl
>Priority: Minor
> Labels: patch
> Attachments: EXEC-56-tests.patch,
> EXEC-XXX.toString-troubleshooting.patch
>
>
> CommandLine.toString() produces same output for different command lines. This
> may be very confusing during troubleshooting and may lead to incorrect
> assumptions. For example, if actual command to invoke was sh -c "echo 1" it
> might be displayed (in debug output for example) as sh -c echo 1 (that will
> work incorrectly) and incorrect assumption might be made.
> Proposal is to make it clear what every parameter actually is. For example,
> following code
> CommandLine cmd1 = new
> CommandLine("sh").addArgument("-c").addArgument("echo 1", false);
> CommandLine cmd2 = new
> CommandLine("sh").addArgument("-c").addArgument("echo").addArgument("1");
> System.out.println("cmd1: " + cmd1.toString());
> System.out.println("cmd2: " + cmd2.toString());
> will produce confusing output
> cmd1: sh -c echo 1
> cmd2: sh -c echo 1
> Same time, following output might be more helpful to figure out cause of some
> problem or to prove that there are no problems with how parameters are set:
> cmd1: [sh, -c, echo 1]
> cmd2: [sh, -c, echo, 1]
--
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] [Commented] (EXEC-60) Possible deadlock when a process is terminating at the same time its timing out
[ https://issues.apache.org/jira/browse/EXEC-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120451#comment-13120451 ] Peter Kofler commented on EXEC-60: -- I created a test that reproduces the deadlock (from time to time ;-) ExecuteWatchdogTest.java If you have a fast machine then you need to update the "start" and the end of range of the time slice. --- Case of the deadlock was the synchronized call stack in Watchdog#run. > Possible deadlock when a process is terminating at the same time its timing > out > --- > > Key: EXEC-60 > URL: https://issues.apache.org/jira/browse/EXEC-60 > Project: Commons Exec > Issue Type: Bug >Affects Versions: 1.0.1, 1.1 >Reporter: Gui Forget >Priority: Minor > Attachments: commons-exec-1.1-deadlock.txt, deadlock.txt, exec-60.diff > > > I ran into a deadlock when executing a process monitored by ExecuteWatchDog. > This happened in 1.0.1 for me but looking at the code in 1.1 it seems to me > that this could happen in this version as well. -- 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
