This content has been marked as final. Show 4 replies
I've managed to implement a workaround for the second problem using a branch back to my upload page.
Still, why should I need this under APEX Listener but not under EPG??
it sounds like you have both EPG and APEX Listener running on the same machine, so your problem might result from a port conflict. Note that both services use TCP port 8080 as default.
At least a port conflict would explain the strange behaviour in your case, some things working on one web server and some on the other.
Some parts of your initial post hint to that direction, e.g.
However, just installing APEX Listener but not configuring it (yet) has meant that my image display in a report using a procedure based on >wpg_docload.download_file( l_ordimage_image.source.localData ) no longer works in EPG - the images are not displayed.... because the APEX Listener only interfere with the EPG if it is at least running on the same machine as your database and furthermore, if it is unconfigured in terms of ist database connection, a port conflict might be the only way it could cause anything like that.
However, if you are sure that's not the issue, please check if you see any error in the APEX Listener's log for the following action you performed:
My application also allows users to upload images from APEX_APPLICATION_FILES using standard code. Under APEX Listener after uploading, I'm left with a blank >page with a wwv_flow.accept URL although the image does indeed uploadIf you actually see just a blank screen, something very bad must have happened and you should see some kind of stack trace there.
For further investigations, if necessary, it would be helpful to know how you deployed or started your APEX Listener and which JDK version you use.
For the moment, I still think the port conflict is my best guess.
You could avoid it by either changing the port for EPG (I'd not recommend that if you have other users still using it) or by changing the port for your APEX Listener.
Thanks for this
EPG is using port 8080 and APEX Listener is using 8585
This may seem a dumb question but where can I find the APEX Listener logs?
that's unexpected. Are you sure you already used this port for APEX Listener at the first start when the mysterious side effects occured? Because that part is really odd and I'd like to separate the two issues...
This may seem a dumb question but where can I find the APEX Listener logs?It doesn't to me. The answer depends on how you deployed your APEX Listener. I assume you currently use the standalone mode. In that case, there is no actual log file, but the output produced on the console where you started the APEX Listener. Additionally, there is an error log in the "Status"-Tab of "/apex/listenerAdmin" or directly in "/apex/listenerStatus".
Please also post which JDK version you use to run the APEX Listener.