Details
-
Type: Bug
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 1.7
-
Fix Version/s: 1.7.2
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
-
Hide
- Bug4805Example.zip
- 19 kB
- Arran McCullough
-
- Bug4805Example/build.xml 3 kB
- Bug4805Example/nbproject/ant-deploy.xml 2 kB
- Bug4805Example/nbproject/build-impl.xml 53 kB
- Bug4805Example/.../faces-config.NavData 0.3 kB
- Bug4805Example/.../genfiles.properties 0.4 kB
- Bug4805Example/.../private.properties 6 kB
- Bug4805Example/nbproject/.../private.xml 0.2 kB
- Bug4805Example/.../project.properties 6 kB
- Bug4805Example/nbproject/project.xml 7 kB
- Bug4805Example/src/conf/MANIFEST.MF 0.0 kB
- Bug4805Example/src/.../example/TestBean.java 7 kB
- Bug4805Example/web/index.jsp 0.1 kB
- Bug4805Example/web/main.jspx 3 kB
- Bug4805Example/web/META-INF/context.xml 0.1 kB
- Bug4805Example/web/.../faces-config.xml 0.5 kB
- Bug4805Example/web/WEB-INF/web.xml 4 kB
-
- afterTest2.JPG
- 82 kB
-
- beforeTest2.JPG
- 102 kB
-
- screenshot-1.jpg
- 196 kB
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Shows the second chart duplicated in the spot where the third chart should be. Also shows the duplicate src path for both charts.
NetBeans developed test case used to duplicate the reported issue.
I have tested the attached test case with the trunk, and not able to reproduce the problem. Sam can you please verify it?
Problem reproducible with the attached application.
perhaps the latest 1.7.1 code resolves the issue.
Please try to reproduce this issue, Arran claims he can consistently, if necessary go see Arran.
Can't reproduce problem, no matter how many times I reload the page or press the reset button. See screenshot-1.
With the exact same war file, the problem occurs on Arran's machine but not mine. We have the same versions of JDK and Tomcat. The only thing different is the OS. Strange!
I think the problem is in com.icesoft.faces.component.outputchart.ChartResource#calculateDigest. It is using System.currentTimeMillis() to try to generate a unique number. The resource registry must be using this number to generate the resource name. The problem is that System.currentTimeMillis() can potentially generate duplicate numbers if the machine system time doesn't have enough granularity. Need to find another way to generate a unique number.
Here is what the Java API doc has to say about currentTimeMillis():
Note that while the unit of time of the return value is a millisecond, the granularity of the value depends on the underlying operating system and may be larger. For example, many operating systems measure time in units of tens of milliseconds.
Shows the charts displayed in the proper order with different src paths