on 07-28-2008 9:11 PM
hi guys,
I have one more query.
I get an error log "database verify failed" during the report execution but my report appears fine. is this an error with the JRC ?
Also when i pass 'NULL' for the outputstream object in the processRequest() i get response already commited error but when i pass the pageContext.out to that method i am not gettin that error. i have set the Isownpage and isownform as true.
Thanks,
Prem
I'd need more info concerning the context within which the database verify error is displayed.
Are you possibly changing the database location in code? This would trigger a database verify step, to ensure the design schema is compatible to the runtime schema.
Since this is intermittent - not every time - I'm wondering if this is load-related.
As for the output stream exception - the viewer works by postback, where it writes HTML output to the response Writer interface, and binaries (export formats) to the response OutputStream interface. The last argument of the processHttpResquest is used to specify the Writer object. If it's null, then it retrieves the getWriter from the HTTPServletResponse argument.
The exception arises because of this - when you pass in null, then it writes to the Writer, and something else on the page is writing to the OutputStream and colliding, since you can't write to both the response.getWriter() and response.getOutputStream() within the same request.
Sincerely,
Ted Ueda
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The JRC has been known to verify the database when you are changing table location at runtime. It is how the product is designed; it will verify the database connection with null values before setting the connection.
Because the error you are seeing doesn't affect the application in any way, and as long as the report is running as expected you don't need to give it a second thought.
As for your second issue, it may well be that for whatever reason your application server has a problem when you pass null into that method; it isn't a bug, you can resolve it as you are doing by passing the pageContext.out if that works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ted/Enns,
Please calrify my doubt.
thanks,
Prem
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.