Bug in error handling.

I found something wich seems a bug in error handling.
I created a JClient application and I declared my error handler using JUMetaObjectManager.setBaseErrorHandler.
It works normaly.
I created a method wich I connected to the WindowClosing event.
In that method I throw a JBOException in order to inform the user the operation can't be executed.
However I see that message only into the console and my error handler (wich shows a Dialog) is not used.
What's the problem ?
Tks
Tullio

Repost

Similar Messages

Flex bug in global error handling

My application's global error handler (uncaught error handler) works mostly, but I found a case where it doesn't work, but should. Before I filed an official bug report I wanted to post the issue here.
Here is the issue: in a module, ErrorEvents that are not listened for and are dispatched by a Flex component are never caught in the application's uncaught error handler.
I have a sample project that demonstrates this. Here is the module in my test case:
<?xml version="1.0" encoding="utf-8"?>
<s:Module xmlns:fx="http://ns.adobe.com/mxml/2009"
             xmlns:s="library://ns.adobe.com/flex/spark"
             xmlns:mx="library://ns.adobe.com/flex/mx">
<fx:Script>
    <![CDATA[
        private function onClickSparkDispatch():void {
            dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) );   // this isn't caught in the uncaught error handler
        private function onClickNonSparkDispatch():void {
            var nonSparkDispatcher:EventDispatcher = new EventDispatcher();
            nonSparkDispatcher.dispatchEvent( new ErrorEvent( ErrorEvent.ERROR, false, false, "test" ) ); // this is caught in the uncaught error handler
    ]]>
</fx:Script>
    <s:HGroup>
        <s:Button label="Module Spark Dispatch (broken)" click="onClickSparkDispatch()" />
        <s:Button label="Module Non-Spark Dispatch" click="onClickNonSparkDispatch()" />
    </s:HGroup>
</s:Module>
Using Flex 4.6
My application statically links in the Flex SDK ("merged into code" in Flash Builder).
My applications works around these two exsiting bugs:
     https://bugs.adobe.com/jira/browse/SDK-28018
     http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html
Is this a bug?
Thanks,
Rick

It’s been reported. Here is more information and a workaround. http://blogs.adobe.com/aharui/2011/04/catching-uncaughterror-in-flex-modules.html

IE / Spry Bug with custom error handler

Ok, as I was looking through SpryData.js I noticed these
wonderful lines:
Spry.Utils.loadURL.callback = function(req)
if (!req || req.xhRequest.readyState != 4)
return;
if (req.successCallback && (req.xhRequest.status ==
200 || req.xhRequest.status == 0))
req.successCallback(req);
else if (req.errorCallback)
req.errorCallback(req);
In particular the "errorCallback()" method interested me as I
wanted to introduce my own error handler. As I went about testing
this I came up with a quick try of:
var url = "/cfcs/mycfc.cfc?method=IsValidPath&path=" +
encodeURIComponent(sl.value + sd.value);
var optionsObj = new Object();
optionsObj.errorCallback = ShowError;
Spry.Utils.loadURL("GET", url, false, ValidateForm,
optionsObj);
And this works great in FF, but not IE. When I cause an error
to occur from ColdFusion I pass a status code of "500". In FF the
error code causes my "ShowError" function to fire, but not in IE. I
tracked it to this bit of code in SpryData.js:
Spry.Utils.loadURL = function(method, url, async, callback,
opts)
var req = new Spry.Utils.loadURL.Request();
req.method = method;
req.url = url;
req.async = async;
req.successCallback = callback;
Spry.Utils.setOptions(req, opts);
try
req.xhRequest = Spry.Utils.createXMLHttpRequest();
if (!req.xhRequest)
return null;
if (req.async)
req.xhRequest.onreadystatechange = function() {
Spry.Utils.loadURL.callback(req); };
req.xhRequest.open(req.method, req.url, req.async,
req.username, req.password);
if (req.headers)
for (var name in req.headers)
req.xhRequest.setRequestHeader(name, req.headers[name]);
req.xhRequest.send(req.postData);
if (!req.async)
Spry.Utils.loadURL.callback(req);
catch(e) { req = null; Spry.Debug.reportError("Exception
caught while loading " + url + ": " + e.message); }
return req;
Apparently running (req.xhRequest.send(req.postData);) in IE
will throw an error if the requested page throws an error status
code. This causes the try/catch in the Spry function to catch the
IE error and never allows my own error handler to run. Hopefully a
fix for this will be in the works because I really like the idea of
being able to use my own error handler.
--------Edited after initial post.--------
Ok, I figured out another item of interest. My requests
earlier were set to "async = false". If I set "async = true" then
it does work. I realized that because I was using sychronous mode
and IE was throwing the error, it was preventing the call to the
"Spry.Utils.loadURL.callback" method from occuring, while asynch
mode uses the onreadystatechange to call the function and thus
causes my own error handler to function. I am still interested to
know if there is a bug here somewhere and if it is just IE or Spry
or both. Looking forward to reading any posts.

Hi WraithBudde,
Thanks for all the details. In my opinion this is indeed a
bug in Spry for the synchronous case. I'll file a bug and fix it.
> You know you love me.
Heh, yeah, I love anybody who takes the time to report bugs
... especially when they've narrowed it down to the exact set of
lines in the source.
Once again ... THANKS!
--== Kin ==--

Error handling function: ORA-20001: get_dbms_sql_cursor error:ORA-00942: table or view does not exist is not trapped. Why?

Why APEX 4.1 Error handling function does not trap the error of missing table?
Say, I create simple application with single IR report page and I also assign standard simple error handling function.
Function works perfectly, except but this case:
If I just drop a table used by report page and then refresh the page I am getting usual APEX error message:
ORA-20001: get_dbms_sql_cursor error ORA-00942: table or view does not exist
and error handling function is not invoked at all.
Is this a feature or a bug?

Hi,
Check the corrections given in the note 990764:
Reason and Prerequisites
Up to now, using a characteristic with its own master data read class as the InfoProvider was not supported. This is now released but it is not available for all modelings. Using the attributes in the query is not supported for characteristics that have their own master data read class. Using the attributes in the query causes a termination. The following errors may occur in this case:
ORA-00942: table or view does not exist
Fehler in CL_SQL_RESULT_SET Include NEXT_PACKAGE
RAISE_READ_ERROR in CL_RSDRV_VPROV_BASE
Solution
SAP NetWeaver 2004s BI
Import Support Package 11 for SAP NetWeaver 2004s BI (BI Patch 11 or SAPKW70011) into your BI system. The Support Package is available once Note 0914305 "SAPBINews BI 7.0 Support Package 11", which describes this Support Package in more detail, has been released for customers.
In urgent cases you can implement the correction instructions.
The correction instructions contain the tightened inspection for characteristics.
Regards,
Anil Kumar Sharma .P

Owb process flow error handling

Hi,
I am using OWB 10gR2.
I have 2 process flows that each call a series of mappings. Then I have one "master" process flow that calls the two aforementioned proecess flows. When a mapping errors, I want my whole master process flow to abort. I put error handling in, but it doesn't seem to work. For example, if I get an error in the first process flow, I get my email notification that something is wrong. The process ends. However, the master process flow continues to go. I want it to stop. It continues to go because there wasn't an error in the first process flow. The error was handled, and the process flow ended successfully. Does anyone have any tips or tricks on how to handle this type of situation? I'm not doing anything revolutionary. I'm just new to these process flows.
Thanks,
Tim

hmm ok this sounds a bit weird to me.
I've created similar processflows with customers and never had similar problems like you describe.
Just to verify your design, here is how I would solve your master1 processflow.
_______________________END_WARNING
w w
start----PF1----------s---------------PF2------s---- END_SUCCESS
e e
\___________________\____END_WARNING
where the conditions for the transitions is indicated with w for warning, s for success and e for error.
Some poorly made ascii art there but hopefully you get the idea...:p
This also sounds like what you've done already and with extra email functionality.
Are you sure that pf2 starts after pf1? Or can it actually run in parallel with pf1 but just finishes after pf1 so it seems like it its done afterwards? The reason I ask is that I experienced that in one of my processflows with around 30+ mappings, one of the mappings that was supposed to be executed almost at the end, executed before everything else and messed everything up. It was quite the annoying little bug and took a long time for me to discover. If you have noticed on the transitions, there is a little number next to the line on the canvas, indicating in which order the operators are to be executed. In my case, two transitions had the same number and that caused one of the mappings to just start as soon as the processflow was told to start. If this is the case there is a way to set these, but I don't remember right now. Delete and recreate the transitions also do the trick I think.
Hope you figure it out!
Ragnar
edit: seems like my ascii art got a bit messed up... :(
Message was edited by:
rhaug

Using AIA for Error Handling. Logging and Notification Services

hi,
In our project we usie OSB and BPEL for integrating different applications.
There is a suggestion that we should use AIA to just use the Error Handling, Logging and Notification services from AIA. I am not sure about this use case, as most of these services mentioned can be replicated in BPEL. Except for the AIAAsyncExceptionHandling BPEL process, i guess all other functionalties provided by AIA can be easily developed in BPEL or OSB alone.
However, would like to hear from you guys about this particular use case. Is it advisable?

Hi,
It's an issue with 10.1.3.4 OBIEE. (whem using IBM LDAP)
References
BUG:7363517 - INTERNAL BI FAILURE ON STARTUP
They issue can be resolved by setting LD_PRELOAD=/path/libibmldap.so
Here are the steps:
. sa-init.sh
export LD_PRELOAD=/path/libibmldap.so

Using code interface node with dll crashes LV 2011 but not LV 8.6... using max error handling does nothing

Hi all,
I'm having a peculiar problem.
I inherited a project saved in LabVIEW 8.6. The project must use of particular dll that was built a few years ago. The original developer and source code for this .dll are long gone. The very core logic exists, in the form of embedded C code, and that's it. The .dll is called through a Code Interface Node in LV 8.6 and this setup manages to "work". Howver, running the VI that calls this .dll in LV 2011 causes an "insta crash", as in, no "program has stopped responding". Error message pops up, then all LV windows close.
It's very similar to that described in here:
http://digital.ni.com/public.nsf/allkb/D84C9775ABD921CF8625772A005CA50C
but this KB says to try putting the amount of error handling to maximum. I tried that, but it didn't help.
Using the "Debug" option allows me to run the just-in-time debugger with CVI 2010, which then proceeds to say this:
Finally, I manage to get this out of it:
FATAL RUN-TIME ERROR: Unknown source position, thread id 0x000012D4: A non-debuggable thread caused a 'General Protection' fault at address 0x00000000.
I don't think that really helps at all, but it's there.
Here is the function prototype of the .dll:
void _inputPM@224(uint8_t arg1, uint16_t arg2, uint8_t arg3, float arg4, float arg5, float arg6, float arg7, float arg8, float arg9, float arg10, float arg11, float arg12, float arg13, float arg14, float arg15, float arg16, float arg17, uint16_t arg18, uint16_t arg19, uint16_t arg20, uint16_t arg21, uint16_t arg22, uint16_t arg23, uint16_t arg24, uint16_t arg25, uint16_t arg26, float arg27, float arg28, float arg29, float arg30, float arg31, float arg32, float arg33, float arg34, float arg35, float arg36, float arg37, float arg38, float arg39, float arg40, float arg41, float arg42, float arg43, float arg44, float arg45, float arg46, float arg47, uint16_t arg48, uint16_t arg49, uint16_t arg50, uint16_t arg51, uint16_t arg52, float arg53, float arg54, float arg55, float arg56);
(never seen a function take 50 input params like that (wouldn't you use a struct? array? something? But I digress, and I don't know anything about .dlls...))
I do have a ".lib" and a ".cdb" file with the same name as the .dll, but those also looks like some kind of compiled file.
I'm sure the answer I'm going to get is that there is no way of telling what's really going on without .dll source code. I'm hoping against hope that there may be another way or hack.
Any ideas? Thank you for you help.
Regards,
Mark G
Solved!
Go to Solution.

MarkCG wrote:
Changing the call library node to stdcall (WINAPI) did the trick! No more crash. Thank you very much!
I haven't run LV2011 on windows XP, only on windows 7, so I don't know if that makes a dfference. But The call type makes no difference when using LV 8.6 on the same machine, however.
Now I've got to make the .DLL run corretly on a compact fieldpoint.... and avoid crashing IT.
Thank you for the help all!
Well, the DLL did work fine in LabVIEW 8.6 because earlier versions of LabVIEW automatically proceeded to change the calling convention to stdcall, if they noticed a function name decoration of @# (# = number of bytes passed on the stack) appended to the name. This is the default naming decoration for stdcall functions used by VisualC. However this decoration can be overwritten with linker switches, other compilers don't use them always in the same way, and most likely there are in the mean time compilers out there that can produce such decorations also for non stdcall calling convention. So this automagic trickery was removed from newer LabVIEW versions.
I do think it could be considered a bug in the code that upgrades LabVIEW VIs, that it uses the calling convention that is configuerd in the dialog, instead of the calling convention earlier LabVIEW versions used automagically, but it is an esoteric corner case.
What Compact Fieldpoint controller do you have? If it's anything newer than 20xx or 21xx forget it. The 22xx controllers use a PPC CPU and VxWorks operating system and can never get a Windows DLL to operate properly. If it is a 20xx controller it's still highly likely that DLL can not even get loaded into LabVIEW as it likely relies on other runtime libraries and possibly Win32 APIs not present in the Pharlap ETS runtime kernel used on those controllers.
There is a tool to check a DLL for incompatible imports that are not present on specific ETS RT systems. And this list summarizes the RT system used on the various NI controllers.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Bug in authorization handling: server refused the given info 10 times

I am getting the following error when trying to connect to a server through httpclient via NTLM authentication.
"Bug in authorization handling: server refused the given info 10 times"
Any help to solve the issue will really appreciated.
LINK to NTLM authentication source code
http://www.luigidragone.com/networking/ntlm.html

Thank you for your replies. Allow me to clarify.
1) I can override initSession, but how do I trap a failed login without implementing my own custom basic authentication? And isn't this something which is (should?) be handled by the supplied oracle classes? I've attached my provider.xml below, the only code outside this I am using is my custom filter.
2) I am being prompted for a password not by the SSO server, but by netstorage (Basic Authentication prompt). I presume basic authentication uses cookies? There cookies aren't getting passed through correctly?
<provider class="oracle.portal.provider.v2.http.URLProviderDefinition">
<providerInstanceClass>oracle.portal.provider.v2.http.URLProviderInstance</providerInstanceClass>
<session>true</session>
<authentication class="oracle.portal.provider.v2.security.Authentication">
<authType>basic</authType>
</authentication>
<passAllUrlParams>false</passAllUrlParams>
<portlet class="oracle.portal.provider.v2.http.URLPortletDefinition">
<id>1</id>
<name>NetStorage</name>
<title>NetStorage</title>
<description>NetStorage</description>
<timeout>40</timeout>
<showEditToPublic>false</showEditToPublic>
<hasAbout>false</hasAbout>
<showEdit>false</showEdit>
<hasHelp>false</hasHelp>
<showEditDefault>false</showEditDefault>
<showDetails>false</showDetails>
<renderer class="oracle.portal.provider.v2.render.RenderManager">
     <showPage class="oracle.portal.provider.v2.render.http.URLRenderer">
          <contentType>text/html</contentType>
          <charSet>UTF-8</charSet>
          <pageUrl>https://domain/oneNet/netstorage/</pageUrl>
          <filter class="portal.netstorage.NetStorageFilter"></filter>
     </showPage>
     </renderer>
</portlet>
</provider>

Uncaught error handler (global error handling) not working in Chrome FP 10.1.103.22

A few days ago I very happily discovered the new global error handling available in flash-player (FP) 10.1
Now while all works well in Firefox (using Adobe's FP 10.1.102.64), nothing happens in Chrome (using Google's FP 10.1.103.22).
I can disable Google's FP using the "about:plugins" page in Chrome, restart the browser, and then everything works since the browser falls back to the other flash plugin installed, which is again Adobe's FP 10.1.102.64.
Is this a known bug?

Don't tell me the uncaught error handler only works for a debugger version....??
The documentation, which I read quite carefully, doesn't have a word on this. It suggests rather the opposite:
"When content is running in a debugger version of the runtime, such as the debugger version of Flash Player or the AIR Debug Launcher (ADL), an uncaught error dialog appears when an uncaught error happens. For those runtime versions, the error dialog appears even when a listener is registered for the uncaughtError event. To prevent the dialog from appearing in that situation, call the UncaughtErrorEvent object's preventDefault() method."

BUG: unable to handle kernel NULL pointer dereference at 0000000000000

5月 18 18:18:55 thinkman kernel: [<ffffffff81077683>] do_exit+0x3b3/0xbb0
5月 18 18:18:55 thinkman systemd[1]: Stopping Create Volatile Files and Directories...
5月 18 18:18:55 thinkman systemd[1]: Stopped target Local File Systems.
5月 18 18:18:55 thinkman systemd[1]: Stopping Local File Systems.
5月 18 18:18:55 thinkman systemd[1]: Unmounting Temporary Directory...
5月 18 18:18:55 thinkman systemd[1]: Unmounting /boot...
5月 18 18:18:55 thinkman kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000418
5月 18 18:18:55 thinkman kernel: IP: [<ffffffffa04d293f>] pppoe_release+0x15f/0x1d0 [pppoe]
5月 18 18:18:55 thinkman kernel: PGD 0
5月 18 18:18:55 thinkman kernel: Oops: 0000 [#1] PREEMPT SMP
5月 18 18:18:55 thinkman kernel: Modules linked in: veth xt_addrtype xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 n月 18 18:18:55 thinkman kernel: rtl_pci rtlwifi crct10dif_pclmul crc32_pclmul mac80211 crc32c_intel ghash_clmulni_intel aesni_intel i915 aes_x86_64 l月 18 18:18:55 thinkman kernel: CPU: 0 PID: 637 Comm: pppd Tainted: G O 4.0.2-1-ARCH #1
5月 18 18:18:55 thinkman kernel: Hardware name: LENOVO 20EH0001CD/20EH0001CD, BIOS J5ET42WW (1.13 ) 01/22/2015
5月 18 18:18:55 thinkman kernel: task: ffff8800ab4d1440 ti: ffff8800a7a00000 task.ti: ffff8800a7a00000
5月 18 18:18:55 thinkman kernel: RIP: 0010:[<ffffffffa04d293f>] [<ffffffffa04d293f>] pppoe_release+0x15f/0x1d0 [pppoe]
5月 18 18:18:55 thinkman kernel: RSP: 0018:ffff8800a7a03be8 EFLAGS: 00010202
5月 18 18:18:55 thinkman kernel: RAX: 0000000000000000 RBX: ffff8802404a9000 RCX: 000000000000002c
5月 18 18:18:55 thinkman kernel: RDX: ffff880244e67810 RSI: 0000000000000200 RDI: ffffffff8145ce02
5月 18 18:18:55 thinkman kernel: RBP: ffff8800a7a03c28 R08: 0000000000000000 R09: 0000000000000000
5月 18 18:18:55 thinkman kernel: R10: ffff880244e67810 R11: 0000000000000001 R12: ffffffffa04d4280
5月 18 18:18:55 thinkman kernel: R13: ffff8800a7e50000 R14: ffff88024596a920 R15: ffff88024215ce40
5月 18 18:18:55 thinkman kernel: FS: 0000000000000000(0000) GS:ffff88024f200000(0000) knlGS:0000000000000000
5月 18 18:18:55 thinkman kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
5月 18 18:18:55 thinkman kernel: CR2: 0000000000000418 CR3: 000000000180b000 CR4: 00000000001407f0
5月 18 18:18:55 thinkman kernel: Stack:
5月 18 18:18:55 thinkman kernel: ffff8800a7e50030 0000000000000008 ffff88024596a920 ffff8800a7e50000
5月 18 18:18:55 thinkman kernel: ffffffffa04d4280 ffff8800a7e50030 ffff88024596a920 ffff88024215ce40
5月 18 18:18:55 thinkman kernel: ffff8800a7a03c48 ffffffff81458c6f ffff880244e67800 0000000000000008
5月 18 18:18:55 thinkman kernel: Call Trace:
5月 18 18:18:55 thinkman kernel: [<ffffffff81458c6f>] sock_release+0x1f/0x90
5月 18 18:18:55 thinkman kernel: [<ffffffff81458cf2>] sock_close+0x12/0x20
5月 18 18:18:55 thinkman kernel: [<ffffffff811da04f>] __fput+0x9f/0x200
5月 18 18:18:55 thinkman kernel: [<ffffffff811da1fe>] ____fput+0xe/0x10
5月 18 18:18:55 thinkman kernel: [<ffffffff810917b4>] task_work_run+0xd4/0xf0
5月 18 18:18:55 thinkman kernel: [<ffffffff81077683>] do_exit+0x3b3/0xbb0
5月 18 18:18:55 thinkman kernel: [<ffffffff81077f0b>] do_group_exit+0x3b/0xb0
5月 18 18:18:55 thinkman kernel: [<ffffffff81083966>] get_signal+0x246/0x670
5月 18 18:18:55 thinkman kernel: [<ffffffff812c1c65>] ? kobject_put+0xc5/0x210
5月 18 18:18:55 thinkman kernel: [<ffffffff810155a7>] do_signal+0x37/0x750
5月 18 18:18:55 thinkman kernel: [<ffffffff811f9110>] ? mntput_no_expire+0x30/0x1d0
5月 18 18:18:55 thinkman kernel: [<ffffffff811f92d4>] ? mntput+0x24/0x40
5月 18 18:18:55 thinkman kernel: [<ffffffff811da0ed>] ? __fput+0x13d/0x200
5月 18 18:18:55 thinkman kernel: [<ffffffff81015d20>] do_notify_resume+0x60/0x80
5月 18 18:18:55 thinkman kernel: [<ffffffff81577763>] int_signal+0x12/0x17
5月 18 18:18:55 thinkman kernel: Code: 89 df e8 15 ab f8 e0 f0 ff 4b 6c 74 3f 31 c0 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 66 0f 1f 44 00 00 48 8
5月 18 18:18:55 thinkman kernel: RIP [<ffffffffa04d293f>] pppoe_release+0x15f/0x1d0 [pppoe]
5月 18 18:18:55 thinkman kernel: RSP <ffff8800a7a03be8>
5月 18 18:18:55 thinkman kernel: CR2: 0000000000000418
5月 18 18:18:55 thinkman kernel: ---[ end trace d82e11cf3d48de5d ]---
5月 18 18:18:55 thinkman kernel: Fixing recursive fault but reboot is needed!
5月 18 18:18:55 thinkman systemd[1]: Unmounted Temporary Directory.
5月 18 18:18:55 thinkman systemd[1]: Unmounted /boot.
5月 18 18:18:55 thinkman systemd[1]: Reached target Unmount All Filesystems.
5月 18 18:18:55 thinkman systemd[1]: Starting Unmount All Filesystems.
5月 18 18:18:55 thinkman systemd[1]: Stopped target Local File Systems (Pre).
5月 18 18:18:55 thinkman systemd[1]: Stopping Local File Systems (Pre).
5月 18 18:18:55 thinkman systemd[1]: Stopped Create Static Device Nodes in /dev.
5月 18 18:18:55 thinkman systemd[1]: Stopping Create Static Device Nodes in /dev...
5月 18 18:18:55 thinkman systemd[1]: Stopped Remount Root and Kernel File Systems.
5月 18 18:18:55 thinkman systemd[1]: Stopping Remount Root and Kernel File Systems...
5月 18 18:18:55 thinkman systemd[1]: Reached target Shutdown.
5月 18 18:18:55 thinkman systemd[1]: Starting Shutdown.
5月 18 18:18:55 thinkman systemd[1]: Reached target Final Step.
5月 18 18:18:55 thinkman systemd[1]: Starting Final Step.
5月 18 18:18:55 thinkman systemd[1]: Starting Power-Off...
5月 18 18:18:55 thinkman systemd[1]: Shutting down.
5月 18 18:18:55 thinkman systemd-shutdown[1]: Sending SIGTERM to remaining processes...
5月 18 18:18:55 thinkman systemd-journal[138]: Journal stopped

Head_on_a_Stick wrote:
https://bbs.archlinux.org/viewtopic.php?id=189808 (different error though)
Could be a memory error -- run a memtest.
cxh116 wrote:5月 18 18:18:55 thinkman kernel: Fixing recursive fault but reboot is needed!
Does it reboot successfully?
Also, you really need to read this:
http://www.catb.org/esr/faqs/smart-questions.html
reboot is success.
use pppoe,switch to wifi, has this issue.
hardware: thnkpad e450c 20EH0001CD
$lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Haswell-ULT DRAM Controller [8086:0a04] (rev 0b)
00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b)
00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio Controller [8086:0a0c] (rev 0b)
00:14.0 USB controller [0c03]: Intel Corporation 8 Series USB xHCI HC [8086:9c31] (rev 04)
00:16.0 Communication controller [0780]: Intel Corporation 8 Series HECI #0 [8086:9c3a] (rev 04)
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-V [8086:1559] (rev 04)
00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller [8086:9c20] (rev 04)
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 1 [8086:9c10] (rev e4)
00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 3 [8086:9c14] (rev e4)
00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 5 [8086:9c18] (rev e4)
00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series PCI Express Root Port 6 [8086:9c1a] (rev e4)
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series USB EHCI #1 [8086:9c26] (rev 04)
00:1f.0 ISA bridge [0601]: Intel Corporation 8 Series LPC Controller [8086:9c43] (rev 04)
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] [8086:9c03] (rev 04)
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series SMBus Controller [8086:9c22] (rev 04)
00:1f.6 Signal processing controller [1180]: Intel Corporation 8 Series Thermal [8086:9c24] (rev 04)
04:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723]
05:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265] [1002:6900]
06:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader [10ec:5227] (rev 01)

ADF11g+ Custom error handler

Hello,
I am using Build JDEVADF_11.1.1.2.0_GENERIC_091029.2229.5536
I defined the custom error handler as mentioned in the ADF development guide.Facing weired issue when AM method is called from task flow.
e.g,
AM method
public showSuccessMessage(){
this.getDBTransaction().addWarning(new JboWarning("Hello Sample message from AM"));
Above method is called from taskflow and corresponding action is specified in the page.I have task flow ErrorHander activity defined for the task flow also.When I click the button to call the AM method,Jbo warning raised in AM and catched by the task flow error handler and after this control is passed to CustomErrorHandler and message shows properly.But this happens only first time.After that control never goes to custom error handler. Am I missing some thing??
Any idea why??
Thanks
RB

Hi Frank,
Thanks
What I noticed is,
Case:1
when warning is raised using the addWarning api from AM, binding layer throws exception of type Warning,catches in task flow error handler and directly goes to get getDisplay message method of the custom error handler which is defined in databinding.cpx only once.After that it catches in taskflow error handler and never goes to custom error handler defined in data binding.cpx
Case2:
When I raised it as throw new JboException flow goes reportException of custom error handler and which calls the getDisplay message.In this it even not going to task flow error handler.
If you can confirm this is expected behavior or it is bug that would be great,it helps us define the exception handling framework.
Thanks
RB

Detaul Error handling page

Ok I had my cfm server hacked last week. They used a sql
injection. The think that is driving me nuts is I can not set up a
"Detaul Error handling page" in my cfm server. my other older
version 5 works fine. Why have they never fixed this bug.
I looked up the issue and found a fix it did not worked. Does
anyone hae a sugggestion on how I can fix this so an intruder can
not ready ever bit of code on the error page to help fine tune
there attacks.

user3935812 wrote:
I have the same question.No kidding, seeing as you are the exact same user...
This is all Myfaces specific. The best you can do in a standard web environment is to use the error handling built into the server, which basically means catching specific HTTP error codes. Here is an example:
http://www.java2s.com/Tutorial/Java/0400__Servlet/ServletErrorPage.htm

Arch Setup: mkinitcpio error handling

I just did an install and accidentally put lvm - rather than lvm2 - in the HOOKS array. Not surprisingly, this caused the mkinitcpio process at the end of Configure System to fail. However, I didn't see the mkinitcpio 'window' at all; there was just a brief flash of text at the bottom of the screen that didn't last long enough to read. I would have had no idea that it had failed if I wasn't so familiar with the install process. Furthermore, there wasn't anything on tty7 or the live logs either (I didn't think to check the installed system's logs), so had no idea why it failed. I had to chroot into the install and run mkinitcpio there to find out.
So, this is just a suggestion that there should be some kind of error handling for mkinitcpio in the installer.

Done: https://bugs.archlinux.org/task/25322
I have never posted a bug report before, so if you have any criticism or suggestions please let me know.

General purpose Error Handler Routines

While developing various applications we found out that error handling is one of the most important(at the same time one of the most ignored) task. so we decided to develop some modules which will allow us to configure the handling methods
after develoment we think that this library can be useful to everyone, hence we are making it public
please feel free to give your feedback, bug report, improvement ideas etc...
you can also mail me at [email protected]
Tushar Jambhekar
[email protected]
Jambhekar Automation Solutions
LabVIEW Consultancy, LabVIEW Training
Rent a LabVIEW Developer, My Blog
Attachments:
Error Handler.zip ‏367 KB

Hello Tushar,
Thanks for sharing your work on the forum. We really appreciate it.
Regards,
Chetan K
Application Engineer
National Instruments

Advanced Error handling

Hi all,
I am developing an error handling system for an extensive LabView application, unfortunately I can't call it's purpose due to confidentiality.
I just graduated for my university degree in Applied Physics, and therefore I am pretty experienced with LabVIEW (got core 1,2 and 3).
The used synchonization technique is a queue-operated producer/consumer handler. The testing set-up consists out of the following hardware:
- Keithley 2700 multimeter
- A Stanford SR830 Lock-in
- PI-Mercury 863 (Z-stage controller, for moving up and down)
- NI DAQ 6244
My Question is:
How can you make sure that you cover most errors with your error handling application? What would be a correct approach to find all possible errors that could occur during a measurement?
For example: I could disconnect the K2700 and start the application, then a VISA error is most likely to occur. Besides that I could disconnect the power supply of the hardware and start the application and see which error would occur then.
Is there some general kind of rule of thumb to find the possible errors which could occur in the set-up?
Thanks for your reply in advance.
Cheers,
San
Solved!
Go to Solution.

Aha! Found it: https://decibel.ni.com/content/docs/DOC-20726
I think that was the presentation that I was trying to find earlier as it gives some information about actual strategies for dealing with errors and reporting them versus just how to wire up error wires and the general error handler.
As for your reply, you need to think about grouping sections of code and say to yourself "what should happen if an error occurs here?". You will probably end up identifying gating points in your code (e.g. at the end of a case)
As a couple of examples:
- During initialisation, if a device fails to initialise, should you retry and if so, how many times before giving up? Should you let the user attempt to reconfigure the device
- If you're using a queue based architecture and the reference gets destroyed
You end up having to analyse your code and saying "What if....?" a lot!
I think the errors boil down to something like the following:
- Critical application errors: A terminal error caused by a software bug such as accidentally releasing a reference to a main message queue. In this case you have to shut-down the software but you should report or log some information to help you debug the issue remotely!
- Device errors: Failed to initialise, device not present, lost connection, incorrect configuration - the software can't operate normally but maybe you could keep trying to re-initialise or allow the user to try to change settings rather than exit the application.
- User errors: User has misconfigured something such as entered an invalid path or selecting an incorrect file (type, format etc.) - in this case you should probably notify the user and let them try again.
- Known errors: errors that you expect might occur such as creating a folder that already exists - these would usually be ignored or handled in a case structure. Another example of this is errors out of 'close' subVIs in your exit case (the device might never have initialised or may have already shut down)
You'll never be able to catch every single error (and it's not possible to see all errors a VI might produce and you may want to generate your own errors) but you should try to properly handle (& rectify) errors that are more likely to occur (such as lost connection to a device because someone tripped over a serial cable) and leave the other errors to your general handler.
You also want to think about the experience for the end user of your software - something that the presentation linked above mentions. Chances are that the average user isn't going to be able to understand LabVIEW error codes and will be disappointed if the software just shuts down on launch because a device is missing.
There is no holy grail of error handling/reporting - it's something I'm always reading/learning about and try to apply that as much as I can in my applications!
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Bug in error handling.

Similar Messages

Maybe you are looking for