Bruce Schuchardt created GEODE-2254:
---------------------------------------
Summary: SharedConfigurationUsingDirDUnitTest - all tests fail on
Windows with suspect strings
Key: GEODE-2254
URL: https://issues.apache.org/jira/browse/GEODE-2254
Project: Geode
Issue Type: Bug
Components: configuration
Reporter: Bruce Schuchardt
Running with revision 6992fcf3438f0d5de246579400bdf8f44928429e, all of the
tests in this class fail with a suspect string that looks like this
functionality does not work correctly on Windows. It looks like cluster
configuration creates a file name based on java.sql.Timestamp.toString() which
has characters in it that Windows does not like:
{noformat}
[error 2016/12/28 08:17:38.475 PST <Pooled Message Processor 1> tid=0x75]
cluster-config-2016-12-28 08:17:38.474.zip (The filename, directory name, or
volume label syntax is incorrect)
java.io.FileNotFoundException: cluster-config-2016-12-28 08:17:38.474.zip (The
filename, directory name, or volume label syntax is incorrect)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.<init>(FileOutputStream.java:213)
at java.io.FileOutputStream.<init>(FileOutputStream.java:162)
at
org.apache.geode.management.internal.configuration.utils.ZipUtils.zip(ZipUtils.java:48)
at
org.apache.geode.distributed.internal.SharedConfiguration.initSharedConfiguration(SharedConfiguration.java:264)
at
org.apache.geode.distributed.internal.InternalLocator$SharedConfigurationRunnable.run(InternalLocator.java:650)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.geode.distributed.internal.DistributionManager.runUntilShutdown(DistributionManager.java:621)
at
org.apache.geode.distributed.internal.DistributionManager$4$1.run(DistributionManager.java:878)
at java.lang.Thread.run(Thread.java:745)
{noformat}
All of the tests fail with the same symptom. This is likely a product issue
and not a test problem.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
