APEX Listener - Browse File Issue - ORDS, SODA & JSON in the Database

Hi guys,
I have a strange Issue on new Apex Listener and APEX4:
My arch is: Oracle 11g - APEX4 - Apex Listener - Oracle Glassfish 3.1
When i try to upload a file with a "Browse File" item, I can do this only if the local path of my file is less than 80 char, this problem appear only on IE, on FF all work right!
For Example, using IE, if i try to upload a file located on my pc in "C:\Documents and Settings\MYUSERNAMEDIRECTORYMYUSERNAMEDIRECTORY\Documenti\Immagini\Immagine.JPG" (note the full path lenght is more than 80 chars ), the system don't upload my file.
Using FF, the same file is uploaded correctly.
If I try to upload a file located in "C:\immagine.JPG" (note the full path length is less than 80chars ) , using FF or IE, everything work correctly.
I found another user with the same problem on APEX Forum, this is the link -> Re: APEX Listener Feedback - File Upload Issue
but I didn't found any solution or workaround.....
Is this a bug?Is it a problem only with new Apex Listener? or this issue is only with Apex Listener with GlassFish ?
I test it without Apex Listener and this problem don't appear!
Best Regards,
Emilio 

I have the SAME problem......................any solution? 

Hi guys,
no solution but a comment on testing. I work with oracle 11g, apex 3.2, I.)mod plslq Gateway IIa) Tomcat IIb)OC4j & APEX Listener
FF an IE comparision:
1. mod pl/sql Gateway + long filename/path
FF works fine, IE works fine
2. mod pl/sql Gateway + short filename/path
FF works fine, IE works fine
3. OC4j & APEX Listener + long filename/path
FF dont works, IE dont works
4. OC4j & APEX Listener + short filename/path
FF dont works, IE dont works
ps
for Tomcat same results with file Browse, but there is no support for issues, so OC4j is doing the same.
Any help welcome, thanks
Thomas 

I confirm, I have the same problem. 

Is there any information in the log files?
-kris 

Kris,
In my testing - No "web server" events are generated.
Is there a particular log you are intersetd in?
Using the listenerAdmin - With all logging and Errors on...
Errors - None
Logging
A bunch of this...
08/05/10 16:00:11 Procedure apex_util.get_blob_file FOUND Args 11 DBTime 42 ms ProcessingTime 84 ms
I am very willing to work with you on this subject.
-- Tim St. Hilaire 

Regarding Testing - I will echo Thomas's findings.
The now released version of Apex Listener - the uploads don't work with LONG or SHORT path names when using IE.
The previous "Early Adopter" version did work with "short" paths when using IE. The released version (apex_listener.1.10.179.10.43) seems to have an issue with IE in general. (testing with IE8 currently)
--Tim                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            

Kris,
Some data for you - Hopefully it helps.
When files are being uploaded via IE through the listener, they are coming in with FULL PATHS from their source.
Example from the DEBUG log on a simple application that allows image uploads.
<pre>
IE8 – Upload with Listener : 0.28: ...Session State: Saved Item "P1_IMAGE" New Value="F1346299084/C:\TJSH\danger_512.gif"
IE8 – Upload with mod_plsql : 0.29: ...Session State: Saved Item "P1_IMAGE" New Value="F16253/danger_512.gif"
FF – Upload with Listener : 0.12: ...Session State: Save Item "P1_IMAGE" newValue="F158067855/danger_512.gif" "escape_on_input="N"
FF – Upload with mod_plsql : 0.23: ...Session State: Save Item "P1_IMAGE" newValue="F10898/danger_512.gif" "escape_on_input="N"
</pre>
This shows that IE uploads - through the listener include the c:\ path to the file.
Once upon a time - this was an issue with the standard APEX upload in the APEX builder (like application imports and static files) - this is no longer the case - Images and files can be uploaded through the APEX builder just fine.
Now seeing that file uploads work in the builder - uploads of static files - file names still INCLUDE the full path, but the process works as expected.
I would guess the conflict is in the field code / built in within APEX that is not liking the extra characters.
In my example - the P1_IMAGE field is defined using Source Type of Database Column: IMAGE:MIMETYPE:FILENAME:UPDATED_ON::inline:Download Me
I wanted to share this observation in the hope that it will help expedite a possible solution.
--Tim St.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

Here's what I'm thinking and checking on...
wwv_flow_file_objects$.filename is a varchar2(400). This is where the limit is getting hit. mod_plsql must have mangled the name down to fit in that. I'm not. I'm checking still....
-kris 

Problem Solved in new Listener version (1.0.2)
thank you!

Related

Getting ORA-06508 in APEX Listener Configuration

Hi,
I'm trying to configure the Apex Listener. After entering all required fields and clicking on "Apply" I'm getting the error messages listed below. This happens when trying both Basic and TNS Connection types.
ORA-06508: PL/SQL: could not find program unit being called
Unable to run page sentry in application 4500.
Thanks in advance for your help.
Edited by: user3654649 on Jun 14, 2011 11:32 AM
Edited by: user3654649 on Jun 14, 2011 11:33 AM 
Hi,
it seems the APEX Listener can connect to your database, so the error must be somewhere in your APEX configuration.
Could you please provide some additional information on your setup, e.g.
- Which database user did you configure your APEX Listener to use? Usually you would choose APEX_PUBLIC_USER.
- Which database version are you using?
- Which APEX version does your database have?
- Did you use some other web server before using APEX Listener? (Embedded PL/SQL Gateway or Oracle HTTP Server)
-Udo 
Hi,
Thanks for your answer.
The database user that I'm truing to configure the listener to use is APEX_PUBLIC_USER. the database version is 10.2.0.4. The APEX version is 4.0.2.00.07 and for this database I did not use Embedded PL/SQL Gateway or Oracle HTTP Server.
thanks. 
So, everything up to now seems to be correct. Now, second line questions:
- Did you encounter any problem in your APEX installation?
- Could you check if there is any invalid object in your APEX schema? (run apexvalidate.sql from your APEX installation package connected to that instance as sys)
- Which JEE container do you use?
- Did you deploy the images for APEX yet? And did you deploy it to the context you've configured as images prefix during your APEX installation?
-Udo 
I did not encounter errors in the APEX installation. I don't have any invalid objects in apex_040000 or flows_files schemas (I did select * from dba_objects where owner='APEX_040000' and status='INVALID').
I ran the apexvalidate.sql procedure and now when doing "select * from dba_registry;" I see APEX status as INVALID - however there are no invalid objects in apex_040000 or flows_files schemas.
When doing the installation I followed the Application Express installation guide Release 4 - specifically "Scenario 1: Downloading from OTN and Configuring the Oracle Application Express
Listener" and I ran the installation script as "#apexins APEXTBS APEXTBS TEMP /i/"
The images directory is under apex (apex/images) while apex is the root directory of the installation.
Is there anything that I should have done differently with the /i/ ? Should it be the physical location for the images (something like /oradata/apex/images) ? Another thing - I just noticed that APEX_040000 and FLOWS_FILES are both locked - can this have to do anything with the error I'm getting ?
Waht does it mean "configured as images prefix " ? Is there anything that should be done that is not listed in the installation guide ? Regarding the "JEE container " I don't know.
thanks. 
One more thing - When doing the configuration it prompts me to enter the images directory and to this I reply with the exact physical location.
Enter the path to the directory containing the APEX static resources
Example: /Users/myuser/apex/images
or press Enter to skip:
thanks. 
Hello Sue,
I ran the apexvalidate.sql procedure and now when doing "select * from dba_registry;" I see APEX status as INVALID - however there are no invalid objects in apex_040000 or flows_files schemas.I'm sorry, I forgot to mention that you have to add some parameters to the apexvalidate-Call. In the APEX 4.0.x-case, this would be
#apexvalidate.sql x x APEX_040000I guess this will either bring up errors or put the APEX entry in the dba_registry back to VALID.
In addition to checking for invalid objects and trying to recompile/... them in case there are hits, the validation routine also checks if all vital objects are really there. I'd expect some error should have been raised if you didn't call the procedure as noted above.
I ran the installation script as "#apexins APEXTBS APEXTBS TEMP /i/"That's correct. Are the tablespace APEXTBS and TEMP present and below their size limit?
Is there anything that I should have done differently with the /i/ ?No, that's the default value and fits perfectly in most cases.
Another thing - I just noticed that APEX_040000 and FLOWS_FILES are both locked - can this have to do anything with the error I'm getting ?No, that's the way it should be. These two schemas should never be active database users. When using APEX Listener, you use APEX_PUBLIC_USER to connect to the database.
Waht does it mean "configured as images prefix " ?+/i/+ is the images prefix in your case. As I see in your following post, you are running APEX Listener in standalone mode, so you don't have to care - it has unchangeable contexts +/apex/+ and +/i/+ which fits to your APEX installation.
To explain my question:
You can deploy the APEX Listener to a "full blown" application server (which I referred to as JEE-Container) instead of running in standalone mode.
In that case you have to provide a context containing your images that fits to that prefix.
- When doing the configuration it prompts me to enter the images directory and to this I reply with the exact physical location.That's where the context +/i/+ is mapped to in standalone mode. Everything's correct here as well.
So, after all, everything looks great. If there really hasn't been any error during the installation and the validation routine doesn't throw any error as well, I'd try a clean uninstall (drop FLOWS_FILES, APEX_040000 and APEX_PUBLIC_USER) and rerun the installation routine.
If that doesn't help, could you try to enable the EPG once just to check the APEX installation itself is fine? I really doubt this error is really related to the APEX Listener at the moment...
-Udo 
Hi Udo,
Thanks for your reply.
Running apexvalidate.sql with the suggested parameters did not produce any errors.
SYS#cwsrvsit> #apexvalidate.sql x x APEX_040000
Procedure created.
No errors.
SYS#cwsrvsit> SYS#cwsrvsit> SYS#cwsrvsit>
However the status is still invalid :
SYS#cwsrvsit> select comp_id,comp_name,status from dba_registry where comp_id='APEX';
COMP_ID COMP_NAME STATUS
------------------------------ ----------------------------------- ----------
APEX Oracle Application Express INVALID
Should I try a new installation ? Is it possible that something in the Java insrtallation is wrong ?
thanks again,
Sue 
Hi Sue,
I'm sorry, I just didn't have my APEX troubleshooting notes at hand when posting the previous comments. Now I found them I see I missed some other steps to restart the validation, but I tested the following to work on my testing environment:
set define '^'
set concat on
set concat .
set verify off
#apexvalidate x x APEX_040000
exec validate_apex;Result:
SQL> exec validate_apex
...Database user "SYS", database schema "APEX_040000", user# "46" 23:39:36
...Compiled 0 out of 2721 objects considered, 0 failed compilation 23:39:36
...234 packages
...227 package bodies
...426 tables
...12 functions
...19 procedures
...3 sequences
...439 triggers
...1177 indexes
...176 views
...0 libraries
...4 types
...0 type bodies
...0 operators
...0 index types
...Begin key object existence check 23:39:36
...Completed key object existence check 23:39:36
...Setting DBMS Registry 23:39:36
...Setting DBMS Registry Complete 23:39:36
...Exiting validate 23:39:36
PL/SQL procedure successfully completed.At the end of that block you see that the dbms_registry is set according to the result. So if your query
select comp_id,comp_name,status from dba_registry where comp_id='APEX';still returns "INVALID", I'd recommend to redo the installation.
Is it possible that something in the Java insrtallation is wrong ?I don't think so, as your APEX Listener is able to connect to the database, but the database is not able to produce the APEX workspace login page.
Sorry once more for not providing the correct troubleshooting script at once.
-Udo 
Hi Udo,
Thanks for your reply - it was very helpful. I dropped the AOPEX environment and did a reinstall - now I'm able to do the listener configuration without issues. My next question is - is there a way to do it in the background ? When doing it as "java [options] -jar apex.war" it depends on my session being connected. If I'm doing a CTRL+C the listener goes down. Is there a way to do the configuration in the background and keep it up and running ?
thanks again,
Sue 
Hi Sue,
When doing it as "java [options] -jar apex.war" it depends on my session being connected. If I'm doing a CTRL+C the listener goes down. Is there a way to do the configuration in the background and keep it up and running ?That's actually two different problems of the APEX Listener in standalone mode: One concerning the configuration to be persistent and one to let the APEX Listener run in background.
You can solve both problems by using a "full blown" application server to deploy the APEX Listener. But you can also do this in standalone mode.
Lets start with easier one - the configuration:
The APEX Listener stores its configuration in the "apex.home". By default, this is located in your TEMP-directory. So, depending on your environment, it might be gone after you logged out. You can configure the "apex.home" as a startup parameter and let it point to some directory that is persistent. You could just configure your APEX Listener once, shut it down, and copy the apex-directory to that directory and you'll never have to configure it again.
java -Dapex.home=<Path_to_your_non-temporary_directory> -jar apex.warThe second one might be a little more difficult, depending on your operating system.
If you use a Windows system, you'll find a solution description in the following message: {message:id=9606494}
On Linux systems, a simple solution might be to use a "screen" session. That doesn't really start the APEX Listener as system service, but lives as long as the screen session lives in the background and you can easily do this with a less privleged user. For a neat solution that even start/stop cleanly with your OS, I need to know which one you run your APEX Listener.
-Udo 
Hi Udo,
Thank you very much for your help - it worked.
After doing :
java -Dapex.home=/orabackup_iris2/export/apex_listener/home -jar apex.war and answereing all the prompts,
I did CTRL+C to stop the listener and then I copied the content (cp -R) of /orabackup_iris2/export/apex_listener/home to /orabackup_iris2/export/apex_listener
and the I ran :
nohup java -Dapex.port=8080 -Dapex.home=/orabackup_iris2/export/apex_listener -Dapex.images=/orabackup_iris2/export/apex/images -jar /orabackup_iris2/export/apex_listener/apex.war &
If you can please go over the steps above and see if it makes sense - I hope it's not just pure luck...
thanks again,
Sue 
Hi Sue,
it's not just luck, it definetly works that way.
Just some final remarks:
- There's no need to change/copy the contents from +/orabackup_iris2/export/apex_listener/home+ to +/orabackup_iris2/export/apex_listener+ in your case, as the first directory doesn't seem to be a temporary one.
- I'd recommend to put the java-call including parameters into a shell script and call that instead.
- nohup works fine for on-demand background processes. As you probably know it's not providing a "system service"-like functionality.
- nohup creates a default file for console output of the job it started. I'd recommend to redirect it to a named file and append all output.
So, your final setup would look as follows
start_apex_listener.sh
#!/bin/sh
java -Dapex.port=8080 -Dapex.home=/orabackup_iris2/export/apex_listener -Dapex.images=/orabackup_iris2/export/apex/images -jar /orabackup_iris2/export/apex_listener/apex.warnohup call
nohup /orabackup_iris2/export/apex_listener/start_apex_listener.sh >> /orabackup_iris2/export/apex_listener/apex_listener.log 2>&1 &If your question is answered, please mark this thread and any helpful or correct answer post accordingly.
-Udo 
Udo,
Thank you very much for all your help - my question is definiteley answer
All the best,
Sue
Edited by: Sue on Jun 19, 2011 6:25 AM 
Hi Sue,
I'm glad I could help you.
If you don't mind, you can mark "helpful" and "correct" answers in this thread. Especially in longer threads, this makes it easier for other people to find relevant posts.
Thanks,
Udo

Oracle APEX Listener 1.1.1 Released

Oracle APEX Listener 1.1.1 is now available on OTN.
This release addresses the following issues:
- Fixed a problem with second and subsequent deployments of the Listener using the configuration of the first Listener deployment.
- Reduced the default value of apex.jdbc.MaxConnectionReuseCount from 50000 to 1000. This may address issues with the database temp segment being exhausted (Error ORA-01652).
- Fixed a problem with character encoding when consuming HTML forms submitted using the multipart/form-data content-type.
- Fixed a problem with an IllegalStateException being thrown when the path /apex (instead of /apex/) was accessed on the standalone Listener.
- Fixed a problem where stored procedures defined by the database user which the listener connects as, could not be invoked without prefixing with the schema name.
- Fixed a problem with some JDBC settings in apex-config.xml not actually being used to configure the connection pool.
- Fixed flexible parameter support to handle POSTs without requiring a query string to be present in the submitted URI
Edited by: Colm Divilly on Apr 18, 2011 9:51 AM
Edited by: Colm Divilly on Apr 20, 2011 10:17 AM 
Thanks for the release Colm,
Great to see issues raised here being actively worked on. 
Hello Colm,
at first, I have to join mwrf: It's great to see that APEX Listener is being updated more frequently these days and that topics discussed here make it to the release plan.
I have two issues that are still not fixed in this release:
- Reduced the default value of apex.jdbc.MaxConnectionReuseCount from 50000 to 1000. This may address issues with the database temp segment being exhausted (Error ORA-01652).This is not true for the standalone startup of the apex.war. At least, the console output still states 50000 and as the parameter is not configurable via listenerAdmin, I have to believe in that output.
The second issue concerns the handling of the apex.properties file: The value for apex.images stored there is never overwritten and only effective on the first start.
Reproduction:
First start of the APEX Listener using java -Dapex.images=/home/tomcat/apache-tomcat/webapps/ROOT/i -Dapex.port=8888 -jar apex.war=> adminlistener etc. have to be configured, stored value is apex.images=/home/tomcat/apache-tomcat/webapps/ROOT/i (corresponding timestamp)
=> effective images-directory is +/home/tomcat/apache-tomcat/webapps/ROOT/i+
Second start using java -Dapex.images=/home/tomcat/apache-tomcat/webapps -Dapex.port=8888 -jar apex.war=> stored value is still apex.images=/home/tomcat/apache-tomcat/webapps/ROOT/i (timestamp also unchanged)
=> effective images-directory is +/home/tomcat/apache-tomcat/webapps/ROOT/i+
Third start using java -Dapex.images=/home/tomcat/apache-tomcat/webapps -Dapex.port=8888 -Dapex.erase=true -jar apex.war=> adminlistener etc. have to be configured, stored value is still apex.images=/home/tomcat/apache-tomcat/webapps/ROOT/i (timestamp updated, i.e. correct)
=> effective images-directory is +/home/tomcat/apache-tomcat/webapps/ROOT/i+
Reproduced on Windows XP and Ubuntu.
-Udo
P.S.: If I delete the directory /tmp/apex manually, the file is recreated correctly.
Edited by: Udo on 22.04.2011 23:25
P.P.S.: Checked apex.jdbc.MaxConnectionReuseCount for "regular" deployment: The apex-config.xml created actually still contains the value 50000. (Fresh Appserver installation, first-ever apex.war deployment there).
BTW: There is a version of apex-config.xml with Kris' local config in the download package and an archive called apex_listener.1.1.1.104.21.22.zip which both don't seem to belong into a regular release package.
Edited by: Udo on 23.04.2011 00:05 
I just reproduced a third issue reported by Jeffrey Harris in thread {thread:id=2209368}:
It seems not possible to change the cache.dir used by the APEX Listener.
I tried to change it in both web.xml and apex-config.xml without any success - the caches bdb directory is always created next to the apex-config.xml.
As I tested on that issue I wondered why the same key is configured in both web.xml and apex-config.xml anyway. I suggest there should be only one location, which (if set) should be the apex-config.xml or some place in java.io.tmpdir as (documented) default value.
Please let me know if I'm doing something wrong and changing the cache dir actually works different from what I'm thinking.
Thanks,
Udo 
Just to put the good with the bad:
I've tested flexible parameter passing, and it works great now, thanks! I have a non-Apex, Web PL/SQL application, that includes hand written procedures with the web toolkit, PL/SQL Server Pages, and Web PL/SQL generated from Oracle Designer, and it works beautifully for the first time under Apex Listener. Before this latest update, there were a few things that didn't work.
Only strange thing: The main menu for the system is of course set up as the default page for this deployment. I have to set it up as schemaname.procedurename or I get a not found error, even though there is a public synonym, procedurename. Once the menu runs, other procedures run fine without using a schemaname as a prefix. 
The schemaname.procedurename problem is noted as having been fixed in 1.1.1 as per the release notes,
Are you sure it's not working? I haven't tested myself yet.
Edited by: mwrf on Apr 26, 2011 5:40 AM 
Thanks for the feedback folks, will look into the issues listed above
- Colm 
The bdb folder is used to store the Resource Templates data, it has nothing to do with the cache 
Oops - my bad. I'm pointed at the development database, and it turns out that there WASN'T a public synonym for the menu procedure on that database. (I just checked - there IS one in production - I don't know how these got out of sync.)
Once I added the synonym, and once I stopped and re-started the listener - it all worked. Hooray!
Since this particular application has always relied on Basic Database Authentication in mod_plsql, I wouldn't be able to use Apex Listener in production without changing the authentication methodology. But I have other applications that either have public access, no authentication, or have their own internal authentication scheme for which Apex Listener is now an option. 
Of course! That's my fault. I started testing with the config file location, which was reported not to be handled properly, and used a new (default) config file for these tests. That newly created config file didn't have caching configured despite the path, so it is correct that nothing happens, because there is nothing to be cached. I don't know why I didn't check that again before posting. Probably because I let myself take the (wrong) path to be the one by ignoring the obvious difference.
Sorry for the false report.
Still I'm wondering why the cache.dir is configurable in both apex-config.xml and web.xml. Possibly I missed a point there as well...
-Udo

ERR-7621 Could not determine workspace for application (:)

Hello!,
We have a simple template based report in apex, it has 2 tabs, each displays a very small, static table
(about 30 records, 3 columns each). There is 1 user accessing apex, who is logged into the db server
that has the apex app. We've tried several browsers, all same have behaviour as outlined below;
When selecting either tab, we frequently get this error;
"Error ERR-7621 Could not determine workspace for application (:) on application accept
Expecting p_company or wwv_flow_company cookie to contain security group id of application owner.
OK."
The user clicks "OK" and it takes them back to the tab they were viewing but not the one they selected
OR sometimes it displays the wonderful, "Page Cannot Be Displayed" etc.. Refreshing browser either
then displays the error message (above) or stays with "Page Cannot Be Displayed".
The environment:
Application Express 3.0.1.00.08 using PL/SQL gateway
Oracle db 11.1.0.6
Windows 2003 SP2
Browsers IE(6,7,8), Chrome, FF
Additionally APEX is very, very slow whether it errors or not and in any browser.
We've exhausted looking up "ERR-7621" online and in the application express forum, so
we thought we'd try here at this forum as it seems related.
Any ideas where to start troubleshooting? Thanks in advance, Donald 
I cannot give a proper answer, because I don;t know how you set up your tabs (among others)
I strongly suggest you upgrade to Apex 4 and the apex listener.
regards,
richard 
I'm not sure who moved this thread from {forum:id=251} to this forum. The OP doesn't use APEX Listener, so this thread belongs to {forum:id=137}.
#OP: Please avoid cross postings and only follow the thread you've started here: {thread:id=2363747}
Thanks,
Udo

ERR-7621 Could not determine workspace for application when uploading files

Hello guys,
I am having problem with my apex application.
I get ERR-7621 Could not determine workspace for application (:) on application accept whenever I try to upload any file to wwv_flow_files table. Other things work fine.
Anything larger than 300Kb fails.
This only happens when connected via internet(https), doing it locally works fine.
I am using Apex Listener on Tomcat.
Uploading via Modplsql address works fine so it is something to do with the listener but I can't figure out why and it is driving me nuts...
I have searched the net but found no real solution yet.
These are my settings
Apex Listener instance named "apex" deployed in Tomcat in machine01
Tomcat running on machine01
DB and Apache running on machine02
httpd.conf
ProxyPass /apex http://machine01:443/apex
ProxyPassReverse /apex http://machine01:443/apex
tomcat server.xml file connector setting
<Connector port="443" protocol="HTTP/1.1"
proxyName="machine02"
scheme="https"
proxyPort="443"
secure="true"
URIEncoding="UTF-8"
maxHttpHeaderSize="32767"
connectionTimeout="30000"
redirectPort="443"
compression="force"
compressionMinSize="512"
noCompressionUserAgents="gozilla, traviata"
compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/xml,application/css,application/javascript" />
Can anyone help me please? 
Anyone??
Apex version is 4.1.0.00.32
Tomcat 7.0
Apex Listener 1.1.3
Tried with Apex Listener 1.1.4 but no good... 
Hi,
Anyone??Apex version is 4.1.0.00.32
Tomcat 7.0
Apex Listener 1.1.3
Tried with Apex Listener 1.1.4 but no good...>
I use ApexListener , but not with Tomcat, and have not had any issues with file uploads.
Maybe it is Tomcat issue?
Cheers, 
Hi,
could you specify some more details on your scenario? (versions for DB, APEX, APEX Listener, Tomcat, JDK, OS would have been nice...)
My best guess is that your compression isn't working as expected in your setup. Another option that could be tricky is your "secure" setting, as your HTTPD isn't really using secure requests towards your Tomcat, but is proxying simple HTTP to the backend.
-Udo 
Thank you both for replying.
Ok more information on my setup.
DB version is 11.2.0.1.0 is running on Redhat(machine02).
Tomcat version 7.0 on windows(machine01).
I have tried setting compression="off" and secure="false" but sadly didn't solve the problem..
Just curious if <Location> tag can be used? I got it from dads.conf which I used before moving to listener..
It also didn't work.
<Location /apex/>
SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername APEX_PUBLIC_USER
PlsqlDatabasePassword password
PlsqlDatabaseConnectString dbaddress:111:TNSNAME
PlsqlDefaultPage apex
PlsqlDocumentTablename wwv_flow_file_objects$
PlsqlDocumentPath docs
PlsqlDocumentProcedure wwv_flow_file_manager.process_download
</Location>
Downloading file works fine as well so I am really stuck :( 
Below is the code that gets fired when I click upload button on the page...
declare
l_file_name VARCHAR2(4000);
begin
wwv_flow.debug('>>> ' || :P1_XML_FILE);
select filename
into l_file_name
from apex_application_files
where name = :P1_XML_FILE;
--if l_file_count = 1 then
APEX_COLLECTION.ADD_MEMBER(
p_collection_name => 'XML_UPLOAD_LIST',
p_c001 => l_file_name,
p_c002 => :P1_XML_FILE,
p_generate_md5 => 'NO');
--end if;
end; 
Tomcat version 7.0 on windows(machine01).Which exact versions? JDK?
Do you see anything in your catalina.out or some other log you've mapped output from your APEX Listener deployment to?
Just curious if <Location> tag can be used? I got it from dads.conf which I used before moving to listener..I don't think so. The parameters you can set in dads.conf are related to mod_plsql and are not available when using APEX Listener. Obviously things like DB User and connection string have to be set in APEX Listener as well, but I'm not sure which of these parameters would help you with your file uploads.
How long does it take until you receive the ERR-7621, and how "far" is your client away from your APEX Listener? If you are accessing from a remote site: Did you also try a local upload?
If you think a timeout could be effective, you could try to set disableUploadTimeout for your HTTP Connector. There may be other relevant parameters depending on your scenario, e.g. maxPostSize or maxSavePostSize (see [url http://tomcat.apache.org/tomcat-7.0-doc/config/http.html]Documentation for HTTP Connector Configuration for details).
You've posted the code that should be fired after the upload. Could you also provide information about the page/process that starts the upload?
-Udo 
Hi Udo,
Thanks for your response.
The upload works fine in local environment.
I recieve the error as soon as the file is uploaded.
The code I posted is the process that DOES the upload.
Below is what the whole process looks like.
File Browse button -> select file -> click a button which fires the page process in above post -> branch back to current page.
I have tried disabling the branch back but this is not a issue. Problem still occurred.
I will try the Tomcat setting. 
The upload works fine in local environment.Does this local part include the proxy access or do you bypass it?
The code I posted is the process that DOES the upload.I'd have thought this is the process that "processes" the upload, as it expects the file to be in apex_application_files (which actually is a synonym pointing at wwv_flow_files ) already. But...
Below is what the whole process looks like.
File Browse button -> select file -> click a button which fires the page process in above post -> branch back to current page.... now I know that you use the File Browse item targeting at WWV_FLOW_FILES . Do you have any conditions on that item? Does your button trigger any special request or something? How exactly did you configure your branch? Anything else to happen on your page before or after you've selected a file to be uploaded?
And it would still be interesting to know if you see anything in your Tomcat's logs when you submit the upload page...
-Udo 
Hello Udo,
Thanks for getting back and sorry I didn't come back earlier..
> Does this local part include the proxy access or do you bypass it?
We bypass proxy when we access the page locally. So we use local machine's name to access it.
i.e. http://machine01:8080/apex
Bit more info about stuffs in the page.
File browse item does not have any conditions.
On my previous post which I said
> Below is what the whole process looks like.
> File Browse button -> select file -> click a button which fires the page process in above post -> branch back to current page.
I need to correct this.
File browse button -> select file -> click a button item which has action set as Submit Page -> plsql process in my previous post. This has process point set as "on submit after computation & validation"
and the branch has branch point set as "on submit : after processing (after computaion, validation and processing)"
I couldn't find anything in the Tomcat/Apex listener logs when I do this.....
Really stuck :(
SinK

XLS2COLLECTION Error

I am attempting to get the Excel upload to collection working. Using instructions from Denes Kubucek I had our DBA make the following changes: This application works only with the APEX Listener version 2.0 or higher. Prior to installing the application you need to complete the following tasks: install and configure APEX Listenermake changes in the defaults.xml by adding the following four lines: <entry key="apex.excel2collection">true</entry><entry key="apex.excel2collection.onecollection">true</entry><entry key="apex.excel2collection.name">EXCEL_COLLECTION</entry><entry key="apex.excel2collection.useSheetName">true</entry> restart the APEX Listener When I now attempt to upload an .xls file I get an Oracle REST Data Services  500 – Internal Service Error , Any idea what our problem may be? Thanks, Ed
Got it partially working for a one columns ss with 44 rows. However when I attempt to do a 250 row ss I get his error. Anyone know what needs to be tweaked to allow for a large ss?
You might want to check the logfiles on your TOMCAT / Glassfish.  Might be that you've run into a java heap error or some other memory constraint. CheersFilip

Categories

Resources