Exception not caught bug?

Hi
I get the following results from running the code below
CC: Sun C++ 5.9 Linux_i386 Build35_2 2006/12/04
Hello
argh
c++ (GCC) 3.4.6
Hello
Caught it
No problem
Systems I tested it on
Whitebox WBRL4 ( Redhat RHEL 4 clone )
Gentoo x86_64
#include <iostream>
#include <stdexcept>
using namespace std;
class ex
        void    test()
                throw runtime_error( "argh" );
public:
        ex()
                try
                        test();
                catch( exception & exc )
                        cout << "Caught it" << endl;
int main()
        try
                throw runtime_error( "Hello" );
                cout << "No error?" << endl;
        catch( exception & ex )
                cout << ex.what() << endl;
        try
                ex      test;
                cout << "No problem" << endl;
        catch( exception & exc )
                cout << exc.what() << endl;
        return 0;
};

You have found a known bug in the release you are using. The bug has been fixed in the EA (early access) release.

Similar Messages

Resteasy in-built exceptions not caught in the exception mapper

Hi friends,
I have written some exception mappers to catch and handle the in-built rest easy exceptions like NotFoundException,MethodNotAllowedException, etc., Sample code as shown:
@Provider
public class NotFoundExceptionMapper implements ExceptionMapper<org.jboss.resteasy.spi.NotFoundExc eption>
@Override
Response toResponse(org.jboss.resteasy.spi.NotFoundExceptio n exception) {
return Response.status(500).build();
I have also written a try catch block in my web filter class. Whenever a NotFoundException occurs, it is not caught in the mapper, but it goes to the catch block in the Filter.
Whereas I have tried another exception mapper class to handle JsonParsingException. This is working correctly and giving a proper response from the mapper whenever a Json Parse exception occurs.
The issue is only with the case of resteasy inbuilt exceptions.
Also, the Provider has been registered in the application context using the include-filter tag inside component scan.
Is there any additional configuration to be done for this?
Please guide me as to what needs to be done to catch rest easy in-built exceptions in the mapper class itself.
Regards,
RM

Cross posted
http://stackoverflow.com/questions/10251640/resteasy-in-built-exceptions-not-caught-in-the-exception-mapper
http://www.java-forums.org/advanced-java/58655-resteasy-built-exceptions-not-caught-exception-mapper.html
db

Exception not caught in BPM

Hi all,
I am doing a scenario using BPM.In which I called SAP and several webservices synchronously.I also define Fault messages in the abstract synchronous message inetrface and
used those message interface to send message synchronously to SAP and webservices in blocks. In those blocks I insert exception branches and attach those exception branches to synchronous steps for both system error and fault message.
Now while executing scenario some times system error and application exception are caught properly in BPM, but sometimes it doesn't catch exceptions for system error and application exception.
Please, can anyone give me a valid reason for this behaviour.
Thanks in advance
Regards,
Sami

Hi,
Some of the suggestions for exception handling-
1) non availability of the Webservice, connection problem etc. For this either you can acheieve Send Step with Acknowledgement mode or Alerts configured for Adapters
2) Application Acknowledgement-Webservice is given any error for the data. You can handle that thru email from XI etc
3) Error in updating the R/3 system
4) Timeout delay while calling Webservice
So for these you can configure Alerts.
Alert management is required to notify runtime errors/abnormal errors during runtime. SO it will notify the user/admin person as per the requierements so that you can avoid some of the delay in the process etc..
About Alert Management-
http://help.sap.com/saphelp_nw2004s/helpdata/en/93/40a442b024b211e10000000a155106/content.htm
Please check the links below:
This will help you
http://help.sap.com/saphelp_nw04/helpdata/en/16/62073ced568e59e10000000a114084/frameset.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/1b9259fb002be8e10000000a11466f/frameset.htm
/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Re: alert monitoring
Re: Alert not working?
Alerts in MS Inbox
Use of Exception Handling is a very essential step inside your BPM and the best thing to do would be to wrap each of your Send / Transformation inside a Exception Handling block.
You can use Moorthy's blog on Reocnilation as well as trigger alerts.
/people/krishna.moorthyp/blog/2006/04/08/reconciliation-of-messages-in-bpm
hope this will help you, For further queries you can revert back.
Plz reward with point sin case you are satisfied.
Regards,
Sushama

Exception not caught

Hi all.
At my new customer, I have to implement webdynpro applications. The problem is that when I want to test the application, IE displays a message like this:
"The following error text was processed in the system EPB : An exception occurred that was not caught.
"The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
I have no idea what the problem is. All the necessary services are activated in SICF.
Thanks for your help
Nicolas

Hi,
it's about the fully qualified domain name (FQDN), see the <a href="http://help.sap.com/saphelp_nw70/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm">documentation</a>
Regards, Heidi

Exception not caught while executing web dynpro application

Hello all,
I'm getting run time error exception CX_WDR_RR_EXCEPTION not caught when running web dynpro application
The error analysis shows the custom component is locked by the user and cannot be regenerated. But I checked in SM12 for locked entries and component was not listed there.
The program terminated in the include LWDR_RUNTIME_REPOSITORYF12
Please suggest how to resolve the isse?
Regards,
anil

sorry...posted in wrong forum...

Exceptions not caught in shared library when compiled under Sun Studio 9

I realize it's a fairly old version of Sun Studio, however if at all possibly we'd like to avoid updating to the latest.
Sun Studio 9, version reports
version of "/opt/SUNWspro/bin/../prod/bin/../../bin/cc": Sun C 5.6 2004/07/15
version of "/opt/SUNWspro/bin/../prod/bin/../../bin/CC": Sun C++ 5.6 2004/07/15
uname -a
SunOS sunblade 5.9 Generic_118558-27 sun4u sparc SUNW,Sun-Blade-100
The problem is within our shared library a function calls another method within a try/catch block. This method then sometimes throws an exception which does have a matching catch block. On all other systems (Windows, AIX, HP-UX, Linux) the code works, the exception is caught and handled. On Solaris with Sun Studio 9 though, the exception is ignored and instead triggers an abort and core dump.
Stack Trace:
ffffffff7daa871c lwpkill (6, 0, ffffffff7fffd9c0, ffffffff7d3064d4, 2, ffffffff7fffd9ec) + 8
ffffffff7da3e4b8 abort (ffffffff7d40dac8, ffffffff7d40cc38, ffffffff7d411e78, 10604c, 2, ffffffff7d40dac8) + 100
ffffffff7d3064d4 __1cH__CimplRdefault_terminate6F_v_ (ffffffff7d40dac8, ffffffff7d40cc38, ffffffff7d411e78, 10604c, 104e40, ffffffff7d3064d0) + 4
ffffffff7d3062b4 __1cH__CimplMex_terminate6F_v_ (ffffffff7d40de40, 0, 0, ffffffff7d40de40, ffffffff7d40c978, 1) + 24
ffffffff7d306f04 exthrow_body (ffffffff7d40de40, 0, 0, 105af4, 52, ffffffff7d40e2e8) + 84
ffffffff7d306e58 __1cG__CrunIex_throw6Fpvpkn0AQstatic_type_info_pF1_v_v_ (ffffffff7d40dec8, ffffffff7f0dea78, ffffffff7ecb6b28, ffffffff7d40de40, 0, ffffffff7d40de40) + 3c
ffffffff7ecb6d90 __1cLIGExceptionFThrow6FnQenumIGErrorCodes_pkcxxp2x_v_ (fffffffffffff3e3, 0, 0, 0, ffffffff7f1187da, a0) + 80
ffffffff7ecb6e78 __1cOThrowException6FnQenumIGErrorCodes_pkcxxp1x_v_ (fffffffffffff3e3, 0, 0, 0, ffffffff7f1187da, a0) + 30
ffffffff7f083304 __1cSIGRasterProcessingNVerifyPalette6FpnMIGRasterPage_nTenumIGContrastModes__v_ (1001f3c10, 0, 0, 0, 0, 0) + b4
ffffffff7f083760 __1cSIGRasterProcessingOInvertContrast6FpnMIGRasterPage_nTenumIGContrastModes_nTenumIGColorChannels_pnPtagAT_RECTANGLE__v_ (1001f3c10, 0, 0, ffffffff7fffe1a8, 0, 0) + 20
ffffffff7f039a2c iIG_IP_contrast_invert (1001f3c10, 100162b10, 0, 0, 0, 0) + 104
ffffffff7f039ba0 iIG_IP_contrast_invert_masked (1001f3c10, 100162b10, 0, 0, 0, 0) + 80
000000010000b4e0 ipcontrast_invert_notify (10014d000, 10014d, 0, 100000, 100162000, 100162) + 48
Try/catch block:
     try
          <Triggering function>
     catch(const IGException& ige)
          <Handling Code>
The code which throws the exception is a static method of IGException which has a basic throw line:
     throw IGException(...);
Source code is compiled with the following flags, none of which I could find any info to suggest affect this:
CC -c -Xt -xCC -misalign -xarch=v9 -O
Linking of the shared object is then done via the following, again nothing obvious that could cause issues. mapfile is an empty file.
ld -o <outputfilename> -G -z textoff -M mapfile -z noversion -64 -h <outputfilename> <object files> -L/opt/SUNWspro/lib/v9 -lCrun -lX11 -lc -lm
I did read somewhere mentioning to make sure to use RTLD_GLOBAL if using dlopen on the .so, but the test app is using ld to link the library.
Does anyone have any ideas why with the Sun Studio 9 compiler these exceptions are not being caught? Based on the fact they are caught on all other compilers, i'm guessing this issue is with the compiler.
Also, as a test it seems that if the shared object is not built as a 64-bit object, then everything works. The issue only seems to occur when it is a 64-bit object. Likely an issue with the 64-bit compiling?
Edited by: 837682 on Feb 17, 2011 9:23 AM

As the other poster pointed out, you need to link the shared library using CC, not ld. I should have noticed that error in the original post.
Try using CC instead of ld in your link command. The CC command causes additional files to be linked into the shared library that are required for proper operation, and particularly for exception handling. I think that is the actual source of your problem.
You should not use -L options that point into the compiler installation area, and when you use CC to link, you don't need to.
I'm surprised that you seem to have a copy of libCrun.so.1 in the compiler installation area -- that should not be the case. The the only versions of libCrun should be static libraries libCrun.a. You almost never want to link with a static version of a system library, and absolutely never when building a shared library. The file /opt/SUNWspro/lib/libCrun.so.1 ought to be a symbolic link pointing to /usr/lib/libCrun.so.1, but if that were the case, the version command would have the same output.
By any chance, did you install your compiler by copying it from another installation? If you do that, you need to use tar, not cp, to ensure that symbolic links are preserved.

Pl/sql exception not caught.

This program should give me an error "table or view does not exist" caught by the pl/sql exception, as dba_data_file1 table does not exist.
However all that it returns is Input truncated to 3 characters
Q1. Why?
Q2. How can I remove this message "Input truncated to 3 characters. Where is this message comming from?
#!/bin/ksh
sqlplus -s << EOF
abc/[email protected]
set pages 0
SET SERVEROUTPUT ON BUFFER 100000000
BEGIN
dbms_output.ENABLE(1000000);
SELECT
round(sum(bytes)/1024/1024/1024),
round(sum(free_bytes)/1024/1024/1024),
TRUNC(SYSDATE)
from
(SELECT tablespace_name, BYTES, 0 FREE_BYTES FROM dba_data_files1
UNION ALL
SELECT tablespace_name, 0, BYTES FROM dba_free_space
union all
SELECT tablespace_name, BYTES, 0 FROM dba_temp_files
union all
SELECT 'REDO-LOGS', b.BYTES, 0
FROM v\\$logfile a, v\\$log b
WHERE
a.GROUP# = b.GROUP#);
dbms_output.put_line("ok ");
EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line("Error "||SQLERRCODE ||":"|| SQLERRM);
exit 1
END;
exit 0
EOF
$> tstrun.ksh
Input truncated to 3 characters

EXCEPTION
WHEN OTHERS THEN
dbms_output.put_line("Error "||SQLERRCODE ||":"|| SQLERRM);
exit 1
END;
if you catch exception, process it then you must reraise it. its a general mistake found when you are using others instead of name exception, so remember whenever you use others you must reraise the exception

Database adapter exception not caught

Hello,
I am testing a BPEL orchestration that was running overnight. This process was handling a lot of database transactions that would take quite some time to run. Sometime during the run the database adapter could not connect and an exception was thrown causing the instance to go into an open.faulted state. In the BPEL orchestration I have a Catch-All at the global scope to handle all uncaught exceptions, but apparently this one exception did not get caught. I have had database exceptions thrown and caught previously in other runs, but I am concerned why this one was not handled. Can anyone provide some insight on why this happened and how this can be prevented. I am using 10.1.3.4
Thanks,
Jim

What was the fault. Have you any faults / configuration defined in the BPEL fault framework?
cheers
James

Exception not caught soalris 8

hi,
I am building my executable on following platform
SunOS 5.8 Generic sun4u sparc SUNW,Ultra-Enterprise
using following compiler
CC: WorkShop Compilers 5.0 98/12/15 C++ 5.0
The problem is when I build the excutable in debug mode i.e by giving -g option the exception which i throw is caught in the catch statement.
But when its a non debug build i.e removing -g the exceptions dont get caught instead i get something like
Terminating<E0> E0
Same code with same compiler works proper on soalris 6.
When used dbx on non debug build , it says that the class which i throw is never caught. How is it possible when its getting caught in debug build?
I searched the forums database and found some similar queries ,but no answers to them
Can anybody help me in this matter.
Any patch which i need to install , as my m/c doesnt have any patches installed as of yet
Thanks and Regards
Amol

Does the bug 4400676 relate to whatever i am talking . If it is so then what patch no shd I use.

Agregation exception not working - bug or normal behaviour

We want to define a key figure with an exception agregation to count a number of invoices of a selection.
We decided to create a specific Key figure with the following properties :
Type : Integer / Cumulative values
Exception agregation : Minimum or Maximum
Agregation Sum
It doesn't work as we want and I'm sure I already did it in the pas on another project. Please let me know if it's a bug or a normal behaviour.
With the following data set :
Day | Invoice | Invoice Item | KF
D1 |INV1     | ITM1         | 1
D1 |INV1     | ITM2         | 1
D1 |INV1     | ITM3         | 1
D1 |INV2     | ITM1         | 1-
D1 |INV2     | ITM2         | 1-
D1 |INV2     | ITM3         | 1-
D1 |INV3     | ITM1         | 1
D1 |INV3     | ITM2         | 1
D1 |INV4     | ITM1         | 1
D1 |INV4     | ITM2         | 1
We expect to have the following aggregation behaviour :
Without Invoice Item display :
Day | Invoice | KF
D1 |INV1     | 1
D1 |INV2     | 1-
D1 |INV3     | 1
D1 |INV4     | 1
With neither Invoice nor Invoice Item :
Day | KF
D1 | 2
Instead we have :
Without Invoice Item :
Day | Invoice | KF
D1 |INV1     | 3
D1 |INV2     | 3-
D1 |INV3     | 2
D1 |INV3     | 2
Day | KF
D1 | 4

Hi,
App user is string so try
<script>
alert("&APP_USER.")
</script>Regards,
Jari

Exception not always caught in Sun Studio 12

Hi,
We're using Sun Studio 12 (Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25) on a Solaris 10 SPARC machine. In our applications an exception thrown is sometimes not caught in the try/catch statement and the program continues at an outer catch statement (which usually leads to the program exiting). So far I've not been able to reduce the code down to a simple example and I don't yet know what conditions causes this behaviour.
In general the code has a big try/catch statement in main. Somewhere deep in the code there is a second try/catch statement which protects against a piece of code which we know may throw an exception. This is usually a smart pointer being dereferenced. The act of dereferencing the smart pointer in turn causes an exception to be thrown which is caught internally in a third try/catch inside the dereference code. The exception is successfully caught and some clean up is done. Then the exception is re-thrown by either using a throw; statement or a new throw xmsg("...");. All our exceptions are always of type xmsg which simply takes a string argument.
When the problem manifests itself the second try/catch is ignored and the re-thrown exception is instead caught in the outer catch statement in main which causes the program to log an error and exit.
We have lots of code which is structured the same way and the same style of code works in many cases only to fail in some specific case. It's an elusive problem because the problem moves around and it also depends on how the program is compiled. It only seems to happen when compiled in debug mode. If I compile with -xO4 the problem seems to go away.
The problem also goes away or moves to a different place if the code has changed somewhere between compiles, i.e. some other developer has modified some code, not necessarily in the same are where the problem originally happened.
One thing we have is a function we call DoThrow (used to suppress a warning on an older compiler) defined like this:
void DoThrow(const std::string& msg)
throw xmsg(msg);
}As an experiment I replaced the call to DoThrow with a straight throw xmsg(...) at a place where the first exception was thrown and the problem went away. I'm not sure if removing the call to DoThrow fixed the problem or if the minor restructuring of the code was enough to move the problem elsewhere.
For production releases we still use WorkShop 6, update 2 which does not have any problems like this. We really would like to upgrade to Sun Studio 12 because it's a much better compiler over all. We can't upgrade until we feel confident we have a workaround.
Does anyone have any thoughts on what might be wrong or any ideas on what I can do to narrow down the problem?
Thanks,
Krister

Many thanks. You've given me a few areas to focus on and I'll bring my house in order.
The only external C++ library we depend on is STLport 5.0.2 which we compile ourselves. It's currently compiled with 5.3 on Solaris 8 and I will recompile it with 5.9 on Solaris 10. All other external libraries are C libraries. Our own code is put in static libraries and linked statically. I've read that exceptions thrown in shared libraries can be problematic.
Your comment about complex conditional expressions (a ? f() : g()) is interesting. We've been bitten before by compiler bugs affecting those types of expressions. Destructors called twice or destructors called for temporaries never created. We may still have some conditional expressions like that.
The exception is of type xmsg, defined this way:
class xmsg
public:
    xmsg(const char* s) : _msg(s) {}
    xmsg(const std::string& s) : _msg(s) {}
    const std::string& why() const { return _msg; }
private:
    const std::string _msg;
};There are three catch blocks involved and all the try/catch statement look like this:
try
catch(const xmsg& msg)
}Here is a stack trace from dbx at the point where the exception is thrown the first time.
[1] __exdbg_notify_of_throw(0xffbf4ae8, 0xffbf4ad0, 0x959b292c, 0xffff0000, 0x0, 0xfc00), at 0xfb6549b4
[2] _ex_debug_handshake1(0x0, 0x101cb84, 0x1, 0x14ffc, 0xfb66a67c, 0xfb66ad38), at 0xfb655728
[3] _ex_throw_body(0xfb66af80, 0x80b2ac, 0xfb66a67c, 0x14d9c, 0x0, 0xfb66af80), at 0xfb655934
[4] __Crun::ex_throw(0xfb66afd0, 0x1460bf8, 0x7ead20, 0x0, 0x16538, 0x1), at 0xfb6558bc
=>[5] TransportSource<User>::Activate(this = 0x1624810, r = CLASS, _ARG3 = CLASS), line 39 in "TransportSource.H"
[6] Source<User>::DoActivate(this = 0x162486c, r = CLASS, e = CLASS), line 272 in "Factory.H"
[7] BaseFactory::Load(this = 0x16020a8, e = CLASS), line 2799 in "BaseFactory.C"
[8] GPAuthorizationSource::Load(this = 0x15d2440), line 110 in "GPAuthorization.C"
[9] ExchangeServer::ExchangeServer(this = 0xffbfa95c, argc = 8, argv = 0xffbfbaec), line 380 in "exchangeServer.C"
[10] main(argc = 8, argv = 0xffbfbaec), line 1525 in "exchangeServer.C"Here is the code for the Activate function in stack frame 5. The exception thrown is the second one.
    virtual T& Activate(const Reference& r, Exemplar<T>&)
      _transport->In().Write(r);
      DemarshallStream out;
      _transport->Method(Process::Activate, out);
      if(!out.Data())
     throw xmsg("Failed to call Activate on server " + _transport->Name());
      if(!out.GetBool())
     throw xmsg("Server returned error: " + out.GetString());
      const ClassHandle& h = out.GetClassHandle(&_connection);
      // don't need to pass refresh flag here because a call to Activate
      // means the object is being loaded for the first time.
      BaseExemplar* x = _handle.GetFactory().Demarshall(h, out, false,
     &_connection, this);
      BaseTransportSource::DoActivate(out);
      if(!x)
     throw xmsg("Failed to activate ref: " + r.ExternalValue());
      return static_cast<T&>(*x->GetInstance());
    }The exception is caught (frame 7 in the stack trace above) and re-thrown in the below code, at the last throw statement.
void BaseFactory::Load(BaseExemplar& e)
SourceMap::iterator p = _sources.find(&e._key->Type());
if(p == _sources.end())
    throw xmsg("Factory<" + _handle.Name() + ">::Load - no source for: "
      + e._key->ExternalValue());
AutoPointer<BaseGuard> g(Guard());
std::list<BaseSource*>::iterator i = p->second.begin();
while(true)
    try
      (*i)->_currentExemplar = &e;
      BO& x = (*i)->DoActivate(*e._key, e);
      (*i)->_currentExemplar = 0;
      if(!e._instance)
     e._instance = &x;
     Activate(e, ActivatedOld, 0);
      return;
    catch(const xmsg& msg)
      (*i)->_currentExemplar = 0;
      ++i;
      if(i == p->second.end())
     throw;
}There is a second try/catch one level up (stack frame 8, the call to GPAuthorizationSource::Load). Here's a snippet of that piece of code.
    try
      const Exemplar<User>& user = UserFactory::Instance().CreateExemplar(
     *new UserReference(authorizationTable._login.Value()));
      *user;
    catch(const xmsg& msg)
      Logger::Instance() << LogHeader << MsgClass(MsgClass::Error)
     << "Error PMAutorizationSource: " << msg.why() << EndMsg;
    // ...I put a break-point in the catch block in the above code but I never hit the break point and the exception is caught in an outer try/catch, an error is printed and the program exits.
try
catch(const xmsg& msg)
    std::cerr << "ERROR: " << msg.why() << std::endl;
}I'm sorry I have not yet been able to produce a smaller example that can be compiled and tested in isolation. I know that's important in order to track down the problem. It seems like the smallest change in seemingly unrelated parts of the code makes the problem come or go.

Cfajax Exception thrown not caught

I'm trying to use the new coldfusion 8 ajax features, but I
receive this error in the Ajax debug window: "window:global:
Exception thrown and not caught"
The result of the ajax cfc call shows correctly in the debug
window, but never makes it back to my code because of this error.
sample code:
<javascript>
function getUserName(userId) {
var myTest = new myTestCFC();
var thisUserName = myTest.getName(userId);
alert(thisUserName);
<in body of html>
<cfajaxproxy cfc="myTestCFC" />
Any ideas?

Yes, I have encountered this. What I found out is that if I
have content in my application.cfc page the results for cfselect
will not make it back to the dropdowns even though the debug window
shows that the values are there. I had my footer info in the
application.cfc. Once I removed that I did not receive the
exception. I found this from
Ben
Forta's blog toward the bottom of the page in the comments
section.
Now that I have taken that out when I go to my form the
dropdowns work correctly but when I select anything from the
dropdowns I can't reference them. Such as #form.cfselected_value#.
So I'm going to go back to my application.cfc and start stripping
items out again to see if there is something there causing the
issuse. If anyone has an answer for this please let me know.
Thanks
Lisa

Exception thrown and not caught

I am testing out Ben Forta's tutorial 2 on ajax dropdown
menus and I am getting the following error...
Line: 787
Char: 1
Error: Exception thrown and not caught
WTH????

Hi,
Check for any html comments placed either in your
Application.cfm file (or) the page which you are experiencing the
error. If anything exists remove those comments and try running the
page again..
HTH

'exception thrown but not caught' error on the url iview

Hi,
EP6, we have url iview that is working fine for displaying a web application. but the problem is some of the link on the web application throws 'exception thrown but not caught' error. it happens to some of the users though.

Hi Mokone
I agree with Raghvendranath statement.
This is not portal side problem.U just using URL of that application
Also do this
Open the URLiView editor and check the Fetch Mode property value.
    Launch the same URL in a new browser window (not in the portal).
    Change the URLiView Fetch Mode property from Server-Side to Client-Side.
    The iView is using the Server-side fetching mode but no proxy is defined for the portal
Hope this info help you
Regards
Ruturaj

Dynamic Actions & Cascading List of Values (Exception thrown and not caught

I am having a really strange issue within my Apex 4.0 environment where I am trying to build dynamic actions and cascading list of values.
I am trying to develop new functionality in an existing application, (original application developed using HTMLdb 1.6 and gradually updated to Apex 4.0.1), to add a dynamic action that sets a value of another field, using SQL. The dynamic action is failing with 'Exception thrown and not caught - jquery-1.4.2.min.js Line: 28 Char: 162'. However, when I create a new application within the same workspace and develop the same functionality is works without a problem.
I have ensured the templates for each page/region are an exact copy of each other.
<b>When I run the application in Firebug I get the following information:</b>
Date     Fri, 31 Dec 2010 14:20:03 GMT
Server     Oracle-Application-Server-11g
X-DB-Content-length     87
Set-Cookie     HTMLDB_IDLE_SESSION=31-DEC-2010 23:20:03;path=/
Content-Length     87
Keep-Alive     timeout=5, max=99
Connection     Keep-Alive
Content-Type     text/html; charset=UTF-8
Content-Language     en
<b>For the application that is working I get slightly different response headers.</b>
Date     Fri, 31 Dec 2010 14:20:37 GMT
Server     Oracle-Application-Server-11g
Cache-Control     no-cache
Pragma     no-cache
X-DB-Content-length     14
Content-Length     14
Keep-Alive     timeout=5, max=94
Connection     Keep-Alive
Content-Type     application/json
Content-Language     en
<b>Notice the Content-Type for the version that doesn't work is using "text/html", while the working version uses "application/json"
Firebug also provides the following error:</b>
uncaught exception: Invalid JSON: Content-type: application/json Cache-Control: no-cache Pragma: no-cache {"value":"1"}
<b>Does anyone have any idea what is going on??
Thanks.
Jon</b>

Patrick,
Thanks my session verify function was causing the problem and I have removed it temporarily from my authentication scheme.
I am using the "check_timeout" function that was developed a number of years ago as part of a "How To" section in the old HTMLdb days. I knew there was an issue with this routine as the newer versions of the browsers handle cookies differently and I was going to redevelop it at some point. Do you know which part of the function causes the issue?
Many Thanks,
Jon
FUNCTION check_timeout
RETURN BOOLEAN
AS
l_session_expire VARCHAR2(256) := NULL;
l_cookie_exists BOOLEAN := TRUE;
BEGIN
IF htmldb_custom_auth.get_user IS NULL THEN
RETURN TRUE;
END IF;
BEGIN
l_session_expire := owa_cookie.get('HTMLDB_IDLE_SESSION').vals(1);
EXCEPTION WHEN NO_DATA_FOUND THEN
l_cookie_exists := FALSE; -- no cookie set, assume first page visit after login
END;
IF l_cookie_exists
AND TO_DATE(l_session_expire,'DD-MON-YYYY HH24:MI:SS') < SYSDATE
THEN
wwv_flow.g_unrecoverable_error := TRUE;
owa_util.redirect_url('f?p='||'500:101'); -- Note hard-coded login application and page ID 500:101
RETURN FALSE;
ELSIF NOT g_cookie_already_sent THEN
owa_util.mime_header('text/html', FALSE);
owa_cookie.send ( NAME => 'HTMLDB_IDLE_SESSION',
VALUE => TO_CHAR(SYSDATE+(c_max_idle_minutes/1440),'DD-MON-YYYY HH24:MI:SS'),
expires => NULL,
path => '/',
domain => NULL );
owa_util.http_header_close;
g_cookie_already_sent := TRUE;
END IF;
RETURN TRUE;
END check_timeout;

Exception not caught bug?

Similar Messages

Maybe you are looking for