Unable to handle fault thrwon by BPEL in ESB

hi ,
my bpel process(syncronous request&reply) is throwing the remote fault and my ESB process is not picking the fault even both fault schema are same.
error message:
<MSG_TEXT>An error occurred for port: BPEL_OC4J_SOAP_Provider: javax.xml.rpc.soap.SOAPFaultException: business exception.</MSG_TEXT>
can any one throw some light on this.
PS:my bpel fault schema is not part of response schema( so cant use reply activity inside fault handling section)
Thanks,
Narasimha.

There is a bug in the ESB, what version are you on. If on 10.1.3.3 you will need to apply the latest MLR patch.
cheers
James

Similar Messages

How to return fault from Async BPEL to ESB

Hi,
I have ESB that has input,output and fault, This ESB calls Async BPEL that takes only input. Now i want to return fault from BPEL to ESB. How do i do it?
Please help.

Hi,
My use case is i am implementing AIA. So my enterprise layer is ESB and my ABCS provider is BPEL. As provider takes lot of time to complete the instance, to avoid timeout issue i just created Async BPEL with two ports one for input another for fault. I am able to send back my fault back to this call back port. But how i can receive the fault to the same ESB which called the BPEL?
I am not able to implement it. I can not go for any workaround like creating one more BPEL and then make it as sync, put pick activity and receive the fault then send back to ESB.
Thats the reason i am very specific. If you find some solution please let me know.

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

Facing issue while handling faults using fault-policies.xml

Hi All,
Scenario: One Asynchronous Bpel is trying invoke the webservice. When the status of the webservice is "Down", the BPEL will throw "System fault : remoteFault"
This fault will be handled by the fault-policies.xml.
CustomFaultHandler.java : basically it will print data to audit-trail and send data to the JMS Queue.
I am facing some issues , when i am trying to handle faults using fault-policies.xml.
Issue1: Display warning message at time of deployment : Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Issue2: CustomFaultHandler.java is able to print data to audit-trail but unable to send data to the Queue. and why the policy file getting executed at time of "Start of Invocation" and then it's showing "Invocation faulted" ?
Audit-Trail Message:
*===========*
Started invocation of operation "process" on partner "RemoteService".Started invocation of operation "process" on partner "RemoteService".
[Fault Recovery] Invoked handleBPELFault on custom java action class "com.CustomFaultHandler".
Invoke1
190002190002
default/TestjavaAction!5.0*soa_fcb2a5dd-06a7-47f9-bb88-cab14d343856/TestBPEL
190002
Faulted while invoking operation "process" on provider "RemoteService". Faulted while invoking operation "process" on provider "RemoteService".
fault-policies.xml:
*==========*
<?xml version="1.0" encoding="UTF-8"?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1" id="ErrorHandlingModelr"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension"
name="bpelx:remoteFault">
<condition>
<action ref="ora-java"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="ora-java">
<javaAction className="com.CustomFaultHandler"
defaultAction="ora-terminate">
<returnValue value="Manual" ref="ora-abort"/>
</javaAction>
</Action>
<Action id="ora-abort">
<abort/>
</Action>
</Actions>
</faultPolicy>
</faultPolicies>
fault-bindings.xml:
*===========*
<?xml version="1.0" encoding="windows-1252" ?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<component faultPolicy="ErrorHandlingModelr">
<name>TestBPEL</name>
</component>
</faultPolicyBindings>
Warning Message when trying to deploy the composite to the server :
=============================================
Warning: Schema validation failed for fault-policies.xmlXML-24506: (Error) Identity constraint validation error: 'Key sequence not found in key reference'
Error Message from server:
*==============*
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
ORABPEL-05002
Message handle error.
error while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the reported exception is: Fault not handled.
failure to handle a fault thrown from a scope, by any blocks in the scope chain.
This exception occurred because the fault thrown in the BPEL flow was not handled by any fault handlers and reached the top-level scope.
A top-level fault handler should be added to the flow to handle faults not caught from within the flow.
This error contained an exception thrown by the message handler.
Check the exception trace in the log (with logging level set to debug mode).
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:205)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at com.collaxa.cube.engine.dispatch.Dispatcher$ContextCapturingThreadFactory$2.run(Dispatcher.java:850)
at java.lang.Thread.run(Thread.java:662)
Please help..
Thanks in Advance
Edited by: Sharmistha Ghosh on May 16, 2012 12:37 PM

My SOA suite version is 11.1.1.7 and i was getting the same warning while compiling the Composite in JDeveloper. To fix it update your fault-policy.xml
Change it to
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <faultPolicy version="0.0.1"
                 id="BPELProcessV1_Faults"
                 xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
                 xmlns:xs="http://www.w3.org/2001/XMLSchema"
                 xmlns="http://schemas.oracle.com/bpel/faultpolicy"
                 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
And it will solve the issue.

Need help: Unable to handle kernel paging request at virtual address; javac

Hi
we're working with apache tomcat under linux mandrake 10. (x86)
when our webapp get recompiled the server stop responding
(web server, telnet, etc... are down, but the server is pingable)
after a hard reboot , we get this message in var/log/messages :
Unable to handle kernel paging request at virtual address 02000064
kernel: printing eip:
kernel: c018e379
kernel: *pde = 00000000
kernel: Oops: 0000 [#1]
kernel: CPU: 1
kernel: EIP: 0060:[proc_pid_stat+137/928] Not tainted VLI
kernel: EIP: 0060:[<c018e379>] Not tainted VLI
kernel: EFLAGS: 00010286
kernel: EIP is at proc_pid_stat+0x89/0x3a0
kernel: eax: 00000000 ebx: 02000000 ecx: d85ac000 edx: 92960700
kernel: esi: d11ea6f0 edi: ded440a0 ebp: cf0ddf44 esp: cf0ddee4
kernel: ds: 007b es: 007b ss: 0068
kernel: Process javac (pid: 2415, threadinfo=cf0dc000 task=d11ea6f0)
kernel: Stack: c0143d5a c1259e78 00000000 c1259e78 c0343980 0000015b 00000000 cf0ddf40
attached ther is kernel messages, pci , dmesg.
Thanks
Massimo TRENTO
Apache Tomcat/4.1.30
j2sdk1.4.2_01
kernel 2.6.3-7mdksmp #1 SMP
--- DMESG ---
00100000 - 000000001f6f0000 (usable)
BIOS-e820: 000000001f6f0000 - 000000001f6fb000 (ACPI data)
BIOS-e820: 000000001f6fb000 - 000000001f700000 (ACPI NVS)
BIOS-e820: 000000001f700000 - 000000001f780000 (usable)
BIOS-e820: 000000001f780000 - 0000000020000000 (reserved)
BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
503MB LOWMEM available.
found SMP MP-table at 000f7920
hm, page 000f7000 reserved twice.
hm, page 000f8000 reserved twice.
hm, page 0009f000 reserved twice.
hm, page 000a0000 reserved twice.
On node 0 totalpages: 128896
DMA zone: 4096 pages, LIFO batch:1
Normal zone: 124800 pages, LIFO batch:16
HighMem zone: 0 pages, LIFO batch:1
DMI present.
ACPI: RSDP (v000 PTLTD ) @ 0x000f7980
ACPI: RSDT (v001 PTLTD RSDT 0x00050000 LTP 0x00000000) @ 0x1f6f74ed
ACPI: FADT (v001 FSC D156x 0x00050000 0x000f4240) @ 0x1f6f751d
ACPI: MADT (v001 FSC APIC 0x00050000 CSF 0x00000000) @ 0x1f6faf76
ACPI: BOOT (v001 PTLTD $SBFTBL$ 0x00050000 LTP 0x00000001) @ 0x1f6fafd8
ACPI: DSDT (v001 FSC D156x 0x00050000 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0xf008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 15:2 APIC version 20
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1 15:2 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
Using ACPI for processor (LAPIC) configuration information
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID: Product ID: APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
Enabling APIC mode: Flat. Using 1 I/O APICs
Processors: 2
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=linux-nonfb ro root=301 noapic devfs=mount acpi=ht resume=/dev/hda5
Initializing CPU#0
PID hash table entries: 2048 (order 11: 16384 bytes)
Detected 2793.223 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Memory: 504916k/515584k available (1920k kernel code, 9820k reserved, 892k data, 288k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay loop... 5537.79 BogoMIPS
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Freeing initrd memory: 225k freed
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU#0: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#0: Thermal monitoring enabled
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
per-CPU timeslice cutoff: 1462.56 usecs.
task migration cache decay timeout: 2 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/1 eip 3000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 5570.56 BogoMIPS
CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000
CPU: After vendor identify, caps: bfebfbff 00000000 00000000 00000000
CPU: Trace cache: 12K uops, L1 D cache: 8K
CPU: L2 cache: 512K
CPU: Physical Processor ID: 0
CPU: After all inits, caps: bfebfbff 00000000 00000000 00000080
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#1.
CPU#1: Intel P4/Xeon Extended MCE MSRs (12) available
CPU#1: Thermal monitoring enabled
CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Total of 2 processors activated (11108.35 BogoMIPS).
cpu_sibling_map[0] = 1
cpu_sibling_map[1] = 0
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 2792.0645 MHz.
..... host bus clock speed is 199.0474 MHz.
checking TSC synchronization across 2 CPUs: passed.
Starting migration thread for cpu 0
Starting migration thread for cpu 1
Brought up 1 CPUs
NET: Registered protocol family 16
EISA bus registered
PCI: PCI BIOS revision 2.10 entry at 0xfd8cb, last bus=3
PCI: Using configuration type 1
mtrr: v2.0 (20020519)
ACPI: Subsystem revision 20040211
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
PnPBIOS: Disabled
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
Transparent bridge - 0000:00:1e.0
PCI: Discovered primary peer bus 01 [IRQ]
PCI: Using IRQ router PIIX/ICH [8086/24d0] at 0000:00:1f.0
PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmask
PCI: Found IRQ 10 for device 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
SBF: Simple Boot Flag extension found and enabled.
SBF: Setting boot flags 0x1
apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16ac)
apm: disabled - APM is not SMP safe.
Starting balanced_irq
ikconfig 0.7 with /proc/config*
VFS: Disk quotas dquot_6.5.1
devfs: 2004-01-31 Richard Gooch ([email protected])
devfs: boot_options: 0x1
Initializing Cryptographic API
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
pty: 1024 Unix98 ptys configured
Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH5: IDE controller at PCI slot 0000:00:1f.1
PCI: Found IRQ 10 for device 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x3000-0x3007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x3008-0x300f, BIOS settings: hdc:DMA, hdd:pio
hda: WDC WD800LB-07DNA2, ATA DISK drive
Using anticipatory io scheduler
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: LITE-ON COMBO LTC-48161H, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
ICH5-SATA: IDE controller at PCI slot 0000:00:1f.2
PCI: Found IRQ 10 for device 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:02:01.0
ICH5-SATA: chipset revision 2
ICH5-SATA: 100% native mode on irq 10
ide2: BM-DMA at 0x3010-0x3017, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x3018-0x301f, BIOS settings: hdg:pio, hdh:pio
hda: max request size: 1024KiB
hda: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 >
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard on isa0060/serio0
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
EISA: Probing bus 0 at eisa0
NET: Registered protocol family 2
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET: Registered protocol family 1
BIOS EDD facility v0.13 2004-Mar-09, 1 devices found
Please report your BIOS at http://linux.dell.com/edd/results.html
PM: Reading pmdisk image.
PM: Resume from disk failed.
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
VFS: Mounted root (ext2 filesystem).
Mounted devfs on /dev
SCSI subsystem initialized
libata version 1.00 loaded.
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: hda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 1038473
ext3_orphan_cleanup: deleting unreferenced inode 1038472
ext3_orphan_cleanup: deleting unreferenced inode 1038471
ext3_orphan_cleanup: deleting unreferenced inode 1038470
ext3_orphan_cleanup: deleting unreferenced inode 1038469
ext3_orphan_cleanup: deleting unreferenced inode 1038467
ext3_orphan_cleanup: deleting unreferenced inode 1038466
ext3_orphan_cleanup: deleting unreferenced inode 1038464
ext3_orphan_cleanup: deleting unreferenced inode 1038463
ext3_orphan_cleanup: deleting unreferenced inode 1038462
ext3_orphan_cleanup: deleting unreferenced inode 1038461
ext3_orphan_cleanup: deleting unreferenced inode 1038460
ext3_orphan_cleanup: deleting unreferenced inode 1038459
ext3_orphan_cleanup: deleting unreferenced inode 1038458
ext3_orphan_cleanup: deleting unreferenced inode 1038457
ext3_orphan_cleanup: deleting unreferenced inode 1038456
ext3_orphan_cleanup: deleting unreferenced inode 1038455
ext3_orphan_cleanup: deleting unreferenced inode 1038454
ext3_orphan_cleanup: deleting unreferenced inode 973782
EXT3-fs: hda1: 19 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Mounted devfs on /dev
Freeing unused kernel memory: 288k freed
Real Time Clock Driver v1.12
drivers/usb/core/usb.c: registered new driver usbfs
drivers/usb/core/usb.c: registered new driver hub
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.1
PCI: Found IRQ 9 for device 0000:00:1d.0
PCI: Sharing IRQ 9 with 0000:00:02.0
PCI: Sharing IRQ 9 with 0000:00:1d.3
uhci_hcd 0000:00:1d.0: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: irq 9, io base 00001400
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Found IRQ 11 for device 0000:00:1d.1
uhci_hcd 0000:00:1d.1: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: irq 11, io base 00001800
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
PCI: Found IRQ 10 for device 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Sharing IRQ 10 with 0000:02:01.0
uhci_hcd 0000:00:1d.2: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: irq 10, io base 00001c00
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
PCI: Found IRQ 9 for device 0000:00:1d.3
PCI: Sharing IRQ 9 with 0000:00:02.0
PCI: Sharing IRQ 9 with 0000:00:1d.0
uhci_hcd 0000:00:1d.3: UHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.3 to 64
uhci_hcd 0000:00:1d.3: irq 9, io base 00002000
uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 4
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
PCI: Found IRQ 9 for device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: EHCI Host Controller
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: irq 9, pci mem e0004000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 5
PCI: cache line size of 128 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 8 ports detected
EXT3 FS on hda1, internal journal
Adding 522072k swap on /dev/hda5. Priority:-1 extents:1
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected an Intel 865 Chipset.
agpgart: Maximum main memory to use for agp memory: 431M
agpgart: Detected 8060K stolen memory.
agpgart: AGP aperture is 128M @ 0xf0000000
Supermount version 2.0.4 for kernel 2.6
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k2
Copyright (c) 1999-2004 Intel Corporation.
PCI: Found IRQ 10 for device 0000:02:01.0
PCI: Sharing IRQ 10 with 0000:00:1d.2
PCI: Sharing IRQ 10 with 0000:00:1f.1
PCI: Sharing IRQ 10 with 0000:00:1f.2
PCI: Setting latency timer of device 0000:02:01.0 to 64
eth0: Intel(R) PRO/1000 Network Connection
inserting floppy driver for 2.6.3-7mdksmp
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
hdc: ATAPI 48X DVD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ide-floppy driver 0.99.newide
drivers/usb/core/usb.c: registered new driver hiddev
drivers/usb/core/usb.c: registered new driver hid
drivers/usb/input/hid-core.c: v2.0:USB HID core driver
NET: Registered protocol family 17
e1000: eth0 NIC Link is Up 100 Mbps Half Duplex
PCI: Found IRQ 5 for device 0000:00:1f.5
PCI: Sharing IRQ 5 with 0000:00:1f.3
PCI: Setting latency timer of device 0000:00:1f.5 to 64
intel8x0_measure_ac97_clock: measured 49851 usecs
intel8x0: clocking to 48000
NET: Registered protocol family 10
Disabled Privacy Extensions on device c037da00(lo)
IPv6 over IPv4 tunneling driver
Installing knfsd (copyright (C) 1996 [email protected]).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
eth0: no IPv6 routers present
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24045 messages suppressed.
Neighbour table overflow.
printk: 24276 messages suppressed.
Neighbour table overflow.
printk: 16555 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24221 messages suppressed.
Neighbour table overflow.
printk: 24272 messages suppressed.
Neighbour table overflow.
printk: 15931 messages suppressed.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
Neighbour table overflow.
printk: 24289 messages suppressed.
Neighbour table overflow.
printk: 21235 messages suppressed.
Neighbour table overflow.
---- LSPCI ---
00:00.0 Host bridge: Intel Corp. 82865G/PE/P Processor to I/O Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02)
00:03.0 PCI bridge: Intel Corp. 82865G/PE/P Processor to PCI to CSA Bridge (rev 02)
00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02)
00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02)
00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02)
00:1f.2 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev 02)
00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Controller (rev 02)
02:01.0 Ethernet controller: Intel Corp.: Unknown device 1019
-- LSMOD --
Module Size Used by
nfsd 175840 8
exportfs 7552 1 nfsd
md5 4864 1
ipv6 251392 29
snd-seq-oss 33568 0
snd-seq-midi-event 8704 1 snd-seq-oss
snd-seq 55696 4 snd-seq-oss,snd-seq-midi-event
snd-pcm-oss 53316 0
snd-mixer-oss 19008 1 snd-pcm-oss
snd-intel8x0 34440 0
snd-ac97-codec 59588 1 snd-intel8x0
snd-pcm 97440 2 snd-pcm-oss,snd-intel8x0
snd-timer 26660 2 snd-seq,snd-pcm
gameport 5664 1 snd-intel8x0
snd-page-alloc 12996 2 snd-intel8x0,snd-pcm
snd-mpu401-uart 8320 1 snd-intel8x0
snd-rawmidi 25248 1 snd-mpu401-uart
snd-seq-device 9032 3 snd-seq-oss,snd-seq,snd-rawmidi
snd 55492 12 snd-seq-oss,snd-seq-midi-event,snd-seq,snd-pcm-oss,snd-mixer-oss,snd-intel8x0,snd-ac97-codec,snd-pcm,snd-timer,snd-mpu401-uart,snd-rawmidi,snd-seq-device
soundcore 10560 1 snd
af_packet 22632 0
hid 55360 0
raw 8640 1
ide-floppy 19776 0
ide-tape 36752 0
ide-cd 41764 0
cdrom 38272 1 ide-cd
floppy 61620 0
e1000 83460 0
supermount 39856 1
intel-agp 18364 1
agpgart 32460 2 intel-agp
ehci-hcd 25572 0
uhci-hcd 31856 0
usbcore 103228 5 hid,ehci-hcd,uhci-hcd
rtc 13640 0
ext3 114216 2
jbd 61976 1 ext3
sd_mod 17696 0
ata_piix 8836 0
libata 40256 1 ata_piix,[permanent]
scsi_mod 117104 2 sd_mod,libata
----- /var/log/kernel/warnings -------
Oct 5 10:16:47 nsilaslin02 kernel: printing eip:
Oct 5 10:16:47 nsilaslin02 kernel: c018e379
Oct 5 10:16:47 nsilaslin02 kernel: Oops: 0000 [#1]
Oct 5 10:16:47 nsilaslin02 kernel: CPU: 1
Oct 5 10:16:47 nsilaslin02 kernel: EIP: 0060:[proc_pid_stat+137/928] Not tainted VLI
Oct 5 10:16:47 nsilaslin02 kernel: EIP: 0060:[<c018e379>] Not tainted VLI
Oct 5 10:16:47 nsilaslin02 kernel: EFLAGS: 00010286
Oct 5 10:16:47 nsilaslin02 kernel: EIP is at proc_pid_stat+0x89/0x3a0
Oct 5 10:16:47 nsilaslin02 kernel: eax: 00000000 ebx: 02000000 ecx: d85ac000 edx: 92960700
Oct 5 10:16:47 nsilaslin02 kernel: esi: d11ea6f0 edi: ded440a0 ebp: cf0ddf44 esp: cf0ddee4
Oct 5 10:16:47 nsilaslin02 kernel: ds: 007b es: 007b ss: 0068
Oct 5 10:16:47 nsilaslin02 kernel: Process javac (pid: 2415, threadinfo=cf0dc000 task=d11ea6f0)
Oct 5 10:16:47 nsilaslin02 kernel: Stack: c0143d5a c1259e78 00000000 c1259e78 c0343980 0000015b 00000000 cf0ddf40
Oct 5 10:16:47 nsilaslin02 kernel: 52143e93 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Oct 5 10:16:47 nsilaslin02 kernel: 00000000 00000000 000000d0 00001000 000000d0 d11ea6f0 00000400 de64f060
Oct 5 10:16:47 nsilaslin02 kernel: Call Trace:
Oct 5 10:16:47 nsilaslin02 kernel: [buffered_rmqueue+234/400] buffered_rmqueue+0xea/0x190
Oct 5 10:16:47 nsilaslin02 kernel: [<c0143d5a>] buffered_rmqueue+0xea/0x190
Oct 5 10:16:47 nsilaslin02 kernel: [proc_info_read+75/320] proc_info_read+0x4b/0x140
Oct 5 10:16:47 nsilaslin02 kernel: [<c018b60b>] proc_info_read+0x4b/0x140
Oct 5 10:16:47 nsilaslin02 kernel: [vfs_read+142/224] vfs_read+0x8e/0xe0
Oct 5 10:16:47 nsilaslin02 kernel: [<c015bf2e>] vfs_read+0x8e/0xe0
Oct 5 10:16:47 nsilaslin02 kernel: [sys_read+46/80] sys_read+0x2e/0x50
Oct 5 10:16:47 nsilaslin02 kernel: [<c015c14e>] sys_read+0x2e/0x50
Oct 5 10:16:47 nsilaslin02 kernel: [sysenter_past_esp+82/121] sysenter_past_esp+0x52/0x79
Oct 5 10:16:47 nsilaslin02 kernel: [<c010b1b9>] sysenter_past_esp+0x52/0x79
Oct 5 10:16:47 nsilaslin02 kernel:
Oct 5 10:16:47 nsilaslin02 kernel: Code: 00 00 8b 7e 68 85 ff 74 09 57 e8 b3 5f f9 ff 59 89 c7 8b 8e 24 03 00 00 85 c9 74 38 8b 81 98 00 00 00 89 45 c8 8b 59 04 8b 51 08 <0f> bf 43 64 0f bf 5b 66 c1 e0 14 09 d8 01 d0 89 c1 c1 e9 14 0f
Oct 5 10:30:32 nsilaslin02 kernel: Linux version 2.6.3-7mdksmp ([email protected]) (gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)) #1 SMP Wed Mar 17 14:24:28 CET 2004
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 0000000000100000 - 000000001f6f0000 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f6f0000 - 000000001f6fb000 (ACPI data)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f6fb000 - 000000001f700000 (ACPI NVS)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f700000 - 000000001f780000 (usable)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 000000001f780000 - 0000000020000000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fec00000 - 00000000fed00400 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fee00000 - 00000000fef00000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000f7000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000f8000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 0009f000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: hm, page 000a0000 reserved twice.
Oct 5 10:30:32 nsilaslin02 kernel: On node 0 totalpages: 128896
Oct 5 10:30:32 nsilaslin02 kernel: DMA zone: 4096 pages, LIFO batch:1
Oct 5 10:30:32 nsilaslin02 kernel: Normal zone: 124800 pages, LIFO batch:16
Oct 5 10:30:32 nsilaslin02 kernel: HighMem zone: 0 pages, LIFO batch:1
Oct 5 10:30:33 nsilaslin02 kernel: Processor #0 15:2 APIC version 20
Oct 5 10:30:33 nsilaslin02 kernel: Processor #1 15:2 APIC version 20
Oct 5 10:30:33 nsilaslin02 kernel: Enabling APIC mode: Flat. Using 1 I/O APICs
Oct 5 10:30:33 nsilaslin02 kernel: Built 1 zonelists
Oct 5 10:30:33 nsilaslin02 kernel: Kernel command line: auto BOOT_IMAGE=linux-nonfb ro root=301 noapic devfs=mount acpi=ht resume=/dev/hda5
Oct 5 10:30:33 nsilaslin02 kernel: PID hash table entries: 2048 (order 11: 16384 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: Detected 2793.223 MHz processor.
Oct 5 10:30:33 nsilaslin02 kernel: Console: colour VGA+ 80x25
Oct 5 10:30:33 nsilaslin02 kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Oct 5 10:30:33 nsilaslin02 kernel: Calibrating delay loop... 5537.79 BogoMIPS
Oct 5 10:30:33 nsilaslin02 kernel: Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Oct 5 10:30:33 nsilaslin02 kernel: POSIX conformance testing by UNIFIX
Oct 5 10:30:33 nsilaslin02 kernel: CPU0: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Oct 5 10:30:33 nsilaslin02 kernel: per-CPU timeslice cutoff: 1462.56 usecs.
Oct 5 10:30:33 nsilaslin02 kernel: task migration cache decay timeout: 2 msecs.
Oct 5 10:30:33 nsilaslin02 kernel: enabled ExtINT on CPU#0
Oct 5 10:30:33 nsilaslin02 kernel: ESR value before enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: ESR value after enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: Booting processor 1/1 eip 3000
Oct 5 10:30:33 nsilaslin02 kernel: masked ExtINT on CPU#1
Oct 5 10:30:33 nsilaslin02 kernel: ESR value before enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: ESR value after enabling vector: 00000000
Oct 5 10:30:33 nsilaslin02 kernel: Calibrating delay loop... 5570.56 BogoMIPS
Oct 5 10:30:33 nsilaslin02 kernel: CPU1: Intel(R) Pentium(R) 4 CPU 2.80GHz stepping 09
Oct 5 10:30:33 nsilaslin02 kernel: cpu_sibling_map[0] = 1
Oct 5 10:30:33 nsilaslin02 kernel: cpu_sibling_map[1] = 0
Oct 5 10:30:33 nsilaslin02 kernel: Using local APIC timer interrupts.
Oct 5 10:30:33 nsilaslin02 kernel: calibrating APIC timer ...
Oct 5 10:30:33 nsilaslin02 kernel: ..... CPU clock speed is 2792.0645 MHz.
Oct 5 10:30:33 nsilaslin02 kernel: ..... host bus clock speed is 199.0474 MHz.
Oct 5 10:30:33 nsilaslin02 kernel: checking TSC synchronization across 2 CPUs: passed.
Oct 5 10:30:33 nsilaslin02 kernel: Starting migration thread for cpu 0
Oct 5 10:30:33 nsilaslin02 kernel: Starting migration thread for cpu 1
Oct 5 10:30:33 nsilaslin02 kernel: Brought up 1 CPUs
Oct 5 10:30:33 nsilaslin02 kernel: PCI: Probing PCI hardware
Oct 5 10:30:33 nsilaslin02 kernel: PCI: Probing PCI hardware (bus 00)
Oct 5 10:30:33 nsilaslin02 kernel: Transparent bridge - 0000:00:1e.0
Oct 5 10:30:33 nsilaslin02 kernel: PCI: IRQ 0 for device 0000:00:1f.1 doesn't match PIRQ mask - try pci=usepirqmask
Oct 5 10:30:33 nsilaslin02 kernel: pty: 1024 Unix98 ptys configured
Oct 5 10:30:33 nsilaslin02 kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Oct 5 10:30:33 nsilaslin02 kernel: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
Oct 5 10:30:33 nsilaslin02 kernel: RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Oct 5 10:30:33 nsilaslin02 kernel: hda: WDC WD800LB-07DNA2, ATA DISK drive
Oct 5 10:30:33 nsilaslin02 kernel: Using anticipatory io scheduler
Oct 5 10:30:33 nsilaslin02 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 5 10:30:33 nsilaslin02 kernel: hdc: LITE-ON COMBO LTC-48161H, ATAPI CD/DVD-ROM drive
Oct 5 10:30:33 nsilaslin02 kernel: ide1 at 0x170-0x177,0x376 on irq 15
Oct 5 10:30:33 nsilaslin02 kernel: hda: max request size: 1024KiB
Oct 5 10:30:33 nsilaslin02 kernel: VFS: Mounted root (ext2 filesystem).
Oct 5 10:30:33 nsilaslin02 kernel: PCI: cache line size of 128 is not supported by device 0000:00:1d.7
Oct 5 10:30:33 nsilaslin02 kernel: hdc: ATAPI 48X DVD-ROM CD-R/RW CD-MRW drive, 2048kB Cache, UDMA(33)
Oct 5 10:30:33 nsilaslin02 kernel: ide-floppy driver 0.99.newide
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
Oct 5 10:30:39 nsilaslin02 kernel: atkbd.c: This is an XFree86 bug. It shouldn't access hardware directly.
Oct 5 10:30:50 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:30:50 nsilaslin02 last message repeated 9 times
Oct 5 10:30:55 nsilaslin02 kernel: printk: 24045 messages suppressed.
Oct 5 10:30:55 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:31:00 nsilaslin02 kernel: printk: 24276 messages suppressed.
Oct 5 10:31:00 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:06 nsilaslin02 kernel: printk: 16555 messages suppressed.
Oct 5 10:36:06 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:06 nsilaslin02 last message repeated 9 times
Oct 5 10:36:11 nsilaslin02 kernel: printk: 24221 messages suppressed.
Oct 5 10:36:11 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:36:16 nsilaslin02 kernel: printk: 24272 messages suppressed.
Oct 5 10:36:16 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:22 nsilaslin02 kernel: printk: 15931 messages suppressed.
Oct 5 10:46:22 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:22 nsilaslin02 last message repeated 9 times
Oct 5 10:46:27 nsilaslin02 kernel: printk: 24289 messages suppressed.
Oct 5 10:46:27 nsilaslin02 kernel: Neighbour table overflow.
Oct 5 10:46:32 nsilaslin02 kernel: printk: 21235 messages suppressed.
Oct 5 10:46:32 nsilaslin02 kernel: Neighbour table overflow.

Java programs are run by a virtual machine which is running in userland. They don't "mess" with the kernel.
OTOH, each userland program interacts with the kernel through system calls, signals, pageing activity, ...
My guess is that it's either broken hardware, or a fault in the linux kernel.
Is the crash reproducible? Does ist always crash with the same error message, at the same "eip" location?
If the crashes are sporadic and non deterministic, with different error messages each time, then I'd say it's
a hardware problem. Otherwise, it could be a linux kernel software problem.

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)

I have just switched over to iCloud and I am now getting an error message in iCal which is the following: The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should con

I have recently switched from MobileMe to iCloud and I now getting an error message in iCal :
"The server is currently unable to handle the connection due to a temporary overloading or maintenance of the server. If this continues you should contact the server administrator.
You may try to connect to the server again or take the account offline."
Since I am working from home and I am not on a server other than iCloud I don't understand why I am getting this message. (for 3 days). How do I fix it?

TomCT60,
Is your MacBook using Mac OS X 10.6.8 as indicated in your post? If so you will not be able to fully integrate with iCloud.
iCloud and Snow Leopard, by Roger Wilmut describes what iCloud options are available for Snow Leopard.
If you are using Lion, go to iCal>Preferences...>Accounts, and delete/re-add your iCloud CalDAV server.

Handling fault messages in BPM

Hi,
I am using BPM for a RFC to SOAP scenario to handle Fault messages. (Please have a look at my previous post also SOAP Fault message )
I have created an exception block in BPM to catch the fault message from SOAP service. Inside the exception block i need to map the fault message to RFC response. But fault message is not accessible in Exception block.
Let me know if you have any idea to solve this.
Thanks,
Uma

Uma:
Let me make clear the requiremt. You have RFC Import(aka Request message) and Export(aka Response + Exception) and you have Web Service with Request, Response, Fault messages. And you want to send the fault messages back to the RFC in addition to the response. I was wondering, If we do the following mapping without BPM, does that fulfill your requirement.
RFC-Import <----
> SOAP Request
RFC-Export <----
> SOAP Response
RFC-Export <----
> SOAP Fault
Can you let me know if you face any problems with this one. I have seen your other thread and was wondering, whats the problem is. May be I didn't understand the requirement properly. Please clarify me

Handling Fault Messages for JDBC Receiver (Syn Inbound)

Dear Freinds,
Can we handle fault messages for JDBC Receiver which is synchronous.
OB Proxy Syn <> IB JDBC Syn
1. How to handle the same ? Please give some examples.
2. Should we use Stored Procedures at Oracle side to handle the fault messages and send back as response to the Proxy Response. Will it work.
Thanks & Regards
K.Ramesh

Dear Friend,
I have 2 interfaces where Proxy is OB & JDBC is IB. In the first interface both sender and Receiver are synchronous and in the second one it is Async.
In the first interface i have to send one field from R/3 table along with Native SQL query string to XI and the response of the SELECT query is sent back to the sender.
Assume if no fields are selected based on the field sent then proper error message has to be sent instead of the response message.
In the second interface i will be using UPDATE query at Asyn JDBC receiver.
How to do this if you are having JDBC Receiver.
I saw in many blogs where they had mentioned that we cannot handle fault messages in the Receiver JDBC.
KIindly explain.
Thanks
K.Ramesh

Is Firefox 3.6.10 technology unable to handle the new youtube?

Youtube made some sort of change(s) 1 day ago. Ever since then numerous links freeze up and firefox loads a "500 internal server error" page. The old youtube user interface was enforced once again. No change after disabling all my extensions. These same sites and new interface load on Chrome, Safari, Firefox4.
Is the current Firefox 3.6.10 technology unable to handle the new youtube?

* "Clear the Cache": Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"
* "Remove the Cookies" from sites that cause problems: Tools > Options > Privacy > Cookies: "Show Cookies"
Start Firefox in [[Safe Mode]] to check if one of your add-ons is causing your problem (switch to the DEFAULT theme: Tools > Add-ons > Themes).
See [[Troubleshooting extensions and themes]] and [[Troubleshooting plugins]]

SJIS- Japan Encoding Issues(*Unable to handle Double Byte Numeric and Spec)

Hi All,
Problem:
Unable to handle Double Byte Numeric and Special Characters(Hypen)
The input
区中央京勝乞田１９４４－２
Output
区中央京勝乞田１９４４?２
We have a write service created based on the JCA (Write File Adapter) with the native schema defined with SJIS Encoding as below.
*<?xml version="1.0" encoding="SJIS"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:tns="http://nike.com/***/***********"
     targetNamespace="http://nike.com/***/*************"
     elementFormDefault="unqualified" attributeFormDefault="unqualified"
     nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="SJIS">*
Do anyone have similar issue? How can we handle the double byte characters while using SJIS encoding? At the least how can we handle double byte hyphen ??
Thanks in Advance

Have modified my schema as shown below and it worked well for me and i am partially successful up to some extent. Yet, not sure the workaround will resolve the issue at the final loading...
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:tns="http://nike.com/***/***********"
targetNamespace="http://nike.com/***/*************"
elementFormDefault="unqualified" attributeFormDefault="unqualified"
nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="UTF-16">*
If anyone has the resolution or have these kind of issues let me know.........

Fault information from bpel process when exception happens

How to extract all the fault information from bpel process when exception happens?
Are there any other methods other than "ora:getFaultName(), ora:getFaultAsString()"
When I use "ora:getFaultName(), ora:getFaultAsString()", I get the below message,so I am wondering whether
I can get any more information about the exception as mentioned below - "detailed root cause described in the exception message" -> how do I get it?
Check the detailed root cause described in the exception message text and verify that the XPath query is correct.

Hi,
As far as I know, it's not possible to get the exception message with a catch all. You need to catch each exception separately, and the you will be able to get each message.
Regards
Gustavo

How to handle faults in JMS Server ?

Hi,
Can any one tell me how to handle faults in jms server. I am new to this environment.
Regards,
Raju.

Hi,
This may be helpful...
http://docs.oracle.com/cd/E23943_01/web.1111/e13738/troubleshoot.htm#g1139030
Cheers,
Vlad

Application Issue - Adobe connect unable to handle "unreachable" responses

Hi,
We've discovered what seems to be a bug with the Adobe Connect application/flash player.
For some reason when you have a proxy in place adobe connect still attempts to establish a direct connection to the adobe servers (for example na7fms2.adobeconnect.com), if these packets get dropped video plays with no issue.
However in our case we have ACL's setup on our Cisco routing core (which do not allow this traffic), which in turn respond with "Destination Unreachable (Communication administratively filtered)".
Adobe Connect seems to be unable to handle these responses and goes into a loop continiously attempting a direct connection (around every 10-12 seconds), therefore causing streaming video's to restart every 10-12 seconds.
Below is a screenshot of the packet capture of the accurance.
Basically we managed to create two of the following scenarios in our network.
Video restarts every 10-12 seconds:
Video plays with no issues:
Now this "Destination Unreachable" response is completely legal in terms of RFC http://www.ietf.org/rfc/rfc792.txt
It would be great if this issue could be raised as a bug and fixed in future versions.
Thanks,
Daniil

Seeing the same issue. Did anyone find any solution?.
Only solution that I could see was opening HTTPS at firewall for only Adobe Connect servers. Wasn't able to locate anything that published the network ranges for the Adobe Connect servers however. Wasn't really a solution that I was happy with anyway.
Only need to do this to allow 1 employee to access a recorded Adobe Connect meeting.
Thanks
Iain.

Unable to handle 64-bit address space

MDS 9216i keeps rebooting and getting the following message:
Starting kernel...
PCI: Unable to handle 64-bit address space for
PCI: Cannot allocate resource region 7 of bridge 02:01.0
PCI: Cannot allocate resource region 0 of device 02:01.0
PCI: Error while updating region
PCI: Failed to allocate resource
PCI: Error while updating region
Any suggestion..?

I don't believe that CDETs is open against the 9216. If you are seeing this error occur on the MDS console, then I suspect a hardware error on the 9216. Software failures would land you at a BIOS prompt, or at a 'LOADER>' prompt. I suggest you contact your 9216 hardware service provider.

Unable to handle fault thrwon by BPEL in ESB

Similar Messages

Maybe you are looking for