Have you installed or recently upgraded to Oracle APEX Listener 2.0? Have you used SQL Developer 3.2 to manage APEX Listener settings? If you answered yes to both questions then you are in for an unwelcome surprise.
The surprise is that you’ll get a “500 – Internal Server Error” whenever you upload a file via any of your APEX apps or import files via the APEX Application Builder.
Kris Rice responded to my tweet almost immediately.
The problem was a bug in the way SQL Developer uploads APEX Listener settings to the server.
This Oracle forum post describes how to reproduce the bug and the workaround to fix it.
Kris quickly put a fix together and checked it in for the next patch.
@eddieawad Fixed checked in for the patch.In the meantime, just remove that line in the config— krisrice (@krisrice) December 27, 2012
@eddieawad Now it’ll just put a log entry saying bad config param for anything non-numeric in that spot and ignore empty values— krisrice (@krisrice) December 27, 2012
If you are still hesitant to join Twitter, I hope that this post has given you an incentive to join this growing social network. Many Oracle employees, like Kris, are active on Twitter and listening to people like you and me who use their products on a daily basis.