s:graphicImage and images being shared by users!

[sradford]

Hi,

I'm sure you won't believe me but...

In our Seam 1.2.1 application we are observing that images belonging to 'User A' are being rendered via the DynamicImageStore by 'User B'.

We are only able to replicate on Solaris and Ubuntu, and not Windows.

On trying to debug (over the last 5days!) we note that when things go wrong, the number of images stored in the internal Map of DynamicImageStore is wrong. For instance it may be 9 when there are only 2 images being rendered for the current user. The other 7 being images of other users.

From our investigation we can only assume that the DynamicImageStore (or its internal Map) we retrieve is not being confined to a particular user, and neither is it being cleaned-up correctly after use.

Has anyone ANY idea why?

- The nearest forum posting we can see in anyway related to this is http://www.jboss.com/index.html?module=bb&op=viewtopic&t=110988

Thanks in advance.

[pmuir]

Sorry about the late reply. I don't know why this is happening. I hope to include a version of s:graphicImage in in Seam 2.0.0.GA that doesn't rely on session maps to store this information - that should help you :)

[jgblanco]

Hi,

We're developing a Seam application for a community (similar, in some aspects, to MySpace).
The application renders lots of images using s:graphicImage, among them face photos of supporting members. The problem is that, sometimes, in the place of a face, appears another.
I saw the posts above and I'm a bit worried now, because the site must be available by this month.
We can't use JSF's h:graphicImage because of the way we store the images (in a remote file system). The only way we found to get them is by means of byte arrays, using s:graphicImage.
Can you help us with a workaround for this?
Thanks in advance.

[pmuir]

I need a bug report in JIRA with reproduction instructions against an example or a runnable app.

[shane.bryzak]

I had the same issue in one of the Seam examples, however I've fixed the problem in CVS so if you could try the latest version it might fix your problem.

[jgblanco]

Thanks, Shane. I will try from CVS.