Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 323332

Summary: Java exception/image handling
Product: [Eclipse Project] Platform Reporter: pjs38
Component: IDEAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: P3 CC: francisu, pjs38, remy.suen
Version: 3.6   
Target Milestone: ---   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description pjs38 CLA 2010-08-22 16:12:52 EDT
Build Identifier: 20100218-1602

javax.imageio.IIOException: Can't create output stream!

The exception started popping up out of nowhere.  As a result, I am unable to use Eclipse's instance of Tomcat to manipulate images with the web app.  This looks like a permission issue, but I have no idea how to resolve it, or what caused it (I didn't alter the configuration manually or via the webapp).  

Reproducible: Sometimes
Comment 1 Francis Upton IV CLA 2010-08-22 16:14:06 EDT
Can you see anything in the log? <workspace>/.metadata/.log
Comment 2 pjs38 CLA 2010-08-22 17:03:41 EDT
(In reply to comment #1)
> Can you see anything in the log? <workspace>/.metadata/.log

 .log has content, but none pertaining to this issue.  the original tomcat installation doesn't have this problem, incidentally.  my guess is that the temp directory value, or permissions for the temp directory, got modified somewhere, but i have no idea where or how -- though nothing in the work directory seems off.  for what it's worth, i am finding that the config files (e.g., server.xml) get rewritten unexpectedly (i have to keep adjusting the context entry, for instance), so maybe this is related to that behavior?  thanks.
Comment 3 pjs38 CLA 2010-08-22 17:36:36 EDT
just a little more detail--
Comment 4 pjs38 CLA 2010-08-22 18:06:25 EDT
(In reply to comment #3)
> just a little more detail--

i am pulling binary from database, then resizing the bytes with java's image libraries, which requires temporary output--so, reading is not an issue--it's the temporary output that seems to be causing the issue (as the exception suggests)

also, i upgraded to build 20100617-1415 just now, but i have the same problem still.  

i never encountered this issue on either of my linux boxes, btw. 

thanks.
Comment 5 pjs38 CLA 2010-08-22 20:33:50 EDT
this is going beyond the scope of the original report, but these may very well be connected: 

1. server.xml is rewritten every time i restart the server now, and two <context> tags are added, so i have to remove one manually.  this is also a new behavior that i did not manually specify.  
2. after restart, the server often rejects http requests, and i am forced to restart eclipse altogether.
Comment 6 pjs38 CLA 2010-08-22 22:27:04 EDT
Just FYI, I fired up the project (literally the same instance of it) in Helios on my Linux box, and so far I haven't gotten the exception.  Thanks.
Comment 7 Eric Moffatt CLA 2010-08-24 14:10:55 EDT
Since it's working in Helios do you have any issue with me closing this defect as WORKSFORME ?
Comment 8 pjs38 CLA 2010-08-24 14:20:41 EDT
(In reply to comment #7)
> Since it's working in Helios do you have any issue with me closing this defect
> as WORKSFORME ?

it's forking in Helios on Linux, but still no go on my Mac box.  let me know if i can provide more info.  thanks.
Comment 9 pjs38 CLA 2010-08-29 16:13:29 EDT
is there anything i can do to help with this? thanks.
Comment 10 Eric Moffatt CLA 2010-09-13 16:24:46 EDT
I'm just having trouble figuring out to whom I should send the defect. It doesn't appear to be a Platform issue but whether to direct you towards a Mac expert (if it's a setup/permissions issue or over to the tomcat folks.

If I can get it in front of the right folks they'll know what extra info they need..;-).
Comment 11 pjs38 CLA 2010-09-13 17:22:52 EDT
(In reply to comment #10)
> I'm just having trouble figuring out to whom I should send the defect. It
> doesn't appear to be a Platform issue but whether to direct you towards a Mac
> expert (if it's a setup/permissions issue or over to the tomcat folks.
> 
> If I can get it in front of the right folks they'll know what extra info they
> need..;-).

hey, eric, i deleted and recreated the java.io temp directory, and that fixed the problem.  i kept ownership and permissions the same, so it looks like something in the temp files, rather than permission settings, was causing the problem.  so, it was a file system issue, but i don't think it was a permission issue.  

unless you think this is a useful test case that could yield some interesting data (i'm guessing that's unlikely, especially since i wiped out the offending directory content), i'm happy to close it with a WORKSFORME tag.  

thanks for your help,
paul
Comment 12 Francis Upton IV CLA 2010-10-11 13:22:56 EDT
Per originator