Virtual address location in process WSDL

Hi,
now we use following approach:
We refer to default WSDL at http://<server>:<port>/orabpel/<domain>/<process name>/<process name>?wsdl
Where address location is the default revision of the process: http://<server>:<port>/orabpel/<domain>/<process name>/<revision>
Is there any possibility to refer to WSDL with 'virtual address location' that always refers to default revision?
We want that our partner has one WSDL with address location
and we can transparently change process revisions without notifying our partner to clear wsdl caches and refresh address location?
Are there any possibilities?
(we use BPEL 10.1.2.0.0 )
Thank You and Reagrds
Karel

Hi,
To always use the latest revision of a process you need to exclude the <revision> part of the Location url. To dynamically set the url's at runtime you can use the following in a assign activity:
<copy>
<from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:location'))"/>
<to partnerLink="RunUcmJasperReport" bpelx:property="location"/>
</copy>
<copy>
<from expression="string(bpws:getVariableData('urlVariable','/ns1:ParameterCollection/ns1:wsdlLocation'))"/>
<to partnerLink="RunUcmJasperReport" bpelx:property="wsdlRuntimeLocation"/>
</copy>
Make sure you assign both wsdlLocation and Location and that the <from> part explicitly is a string. This works in 10.1.3 but i do not know if it also was available in 10.1.2
Kind Regards,
Andre

Similar Messages

  • Change SOAP Address Location in the WSDL

    When deploying a BPEL service the SOAP Address location is automatically generated to have the
    http://{SERVER}:{PORT} of the SOA server where you are deploying the service but i need to have a different address location.
    I basically needs this because we have a load balancer and firewall restrictions for any external third party that want to invoke our service.
    So the WSDL URL we give to the third party who want to invoke our service will be
    https://loadbalancer/orabpel/default/TestService/1.0/TestService?wsdl
    instead of
    http://soasever:soaserveport/orabpel/default/TestService/1.0/TestService?wsdl
    The loadbalancer will then strip of the https connection and send it as http request to the SOA server.
    So the third party is now able to access the WSDL but he is having issues while invoking the service as the SOAP address location is still having our SOA server name
    Any ideas?

    This can be achieved through dynamic partner linking.
    http://download.oracle.com/docs/cd/E19509-01/821-0017/cnfg_bpel-se-dynamic-ptnrlink_c/index.html
    HTH
    -ND

  • Webservices soap address location url update

    Hi,
    Is there any way to change the soap address location in the wsdl?
    I tried by changing the frontendport and host,But I don't have any option for updating the protocol(http/https) option in weblogic.
    advance thanks

    Thank you very much,
    I followed the same document for updation of endpoint,these settings only updating the host and port ,not the frontend access protocol. End points are generated properly if both the proxy and internal app server mapping uses the same protocol.
    Weblogic always using the application server protocol instead of proxy protocol.
    Example:wsdl accessed from proxy with https and the internal mapping is http.
    https://proxy:443/xxx/xxx?wsdl--->http://appserver:7001/xxx/xxx?wsdl--->web servies end point is http://proxy:80/xxx/xxx?wsdl but the expected endpoint is
    https://proxy/xxx/xxx?wsdl.
    thanks for providing any other advices

  • Disable the soap address location

    Hi,
    I wonder if it’s possible to disable the soap:address location in the WSDL?
    My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
    WebService.
    When I ask the WSDL through my proxy, it’s work well. But the next call, the client
    goes directly to the WebLogic and does not use anymore the proxy. I think the
    problem comes from the soap:address location.
    Thanks for your help.
    Charles

    Hi Charles,
    You could post your own WSDL, see the docs [1] for details, or you could
    use a dynamic client without the WSDL; there are a number of examples of
    how to do this such as Manoj's [2].
    Regards,
    Bruce
    [1]
    http://edocs.bea.com/wls/docs81/webserv/webxml.html#1007638
    [2]
    http://manojc.com/?sample25
    Charles Desmoulins wrote:
    >
    Hi,
    I wonder if it’s possible to disable the soap:address location in the WSDL?
    My problem is that I use a proxy (SOAP) between my WebService Client and the WebLogic
    WebService.
    When I ask the WSDL through my proxy, it’s work well. But the next call, the client
    goes directly to the WebLogic and does not use anymore the proxy. I think the
    problem comes from the soap:address location.
    Thanks for your help.
    Charles

  • EndpointURI property is not overriding WSDL address location

    Hi all.
    We're running into an issue regarding a reference component configured in a composite SOa app:
    <reference name="AutenticarUsuarioExternoFSGuev1"
    ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
    <interface.wsdl
    interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
    <binding.ws
    port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
    noFSGuev1PortSOA)"
    location="AutenticarUsuarioExternoFSGuev1.wsdl"
    soapVersion="1.1">
    <property name="weblogic.wsee.wsat.transaction.flowOption"
    type="xs:string" many="false">WSDLDriven</property>
    <property
    name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
    operty>
    </binding.ws>
    </reference>
    As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
    assume it should override any endpoint configuration in the reference's WSDL.
    The WSDL of the reference component mentioned above has an adress location property configured inside it:
         <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
              <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
    binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
                   <soap:*address*
    location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
              </wsdl:port>
         </wsdl:service>
    The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
    reason, the WSDL address location is used as a second try (kind of failover mechanism).
    What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
    defined by the endpointURI property should be used, that is, it should override any other endpoint.
    I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
    but it continues to use both endpoints.
    Any point on this will be appreciated.
    Regards.
    Denis

    Hi all.
    We're running into an issue regarding a reference component configured in a composite SOa app:
    <reference name="AutenticarUsuarioExternoFSGuev1"
    ui:wsdlLocation="AutenticarUsuarioExternoFSGuev1.wsdl">
    <interface.wsdl
    interface="http://www.claro.com.br/EBS/Claro/v1#wsdl.interface(AutenticarUsuarioExternoFSGuev1PortType)"/>
    <binding.ws
    port="http://www.claro.com.br/EBS/Claro/v1#wsdl.endpoint(AutenticarUsuarioExternoFSGuev1/AutenticarUsuarioExter
    noFSGuev1PortSOA)"
    location="AutenticarUsuarioExternoFSGuev1.wsdl"
    soapVersion="1.1">
    <property name="weblogic.wsee.wsat.transaction.flowOption"
    type="xs:string" many="false">WSDLDriven</property>
    <property
    name="*endpointURI*">http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1</pr
    operty>
    </binding.ws>
    </reference>
    As we see above, we have an endpointURI property configured, which according to my experience in 10g version, I
    assume it should override any endpoint configuration in the reference's WSDL.
    The WSDL of the reference component mentioned above has an adress location property configured inside it:
         <wsdl:service name="AutenticarUsuarioExternoFSGuev1">
              <wsdl:port name="AutenticarUsuarioExternoFSGuev1PortSOA"
    binding="tns:AutenticarUsuarioExternoFSGuev1PortTypeSOAP">
                   <soap:*address*
    location="http://fachadasoague.claro.com.br/FachadaSoaGue/services/AutenticarUsuarioExternoFSGuev1" />
              </wsdl:port>
         </wsdl:service>
    The problem is: When service endpoint defined by the endpointURI property is called and it fails for some
    reason, the WSDL address location is used as a second try (kind of failover mechanism).
    What I expected: There should not be a failover process here, It´s not supposed to happen. Only the endpoint
    defined by the endpointURI property should be used, that is, it should override any other endpoint.
    I tried to work around the problem by removing the location property, according to the SOA Suite documentation,
    but it continues to use both endpoints.
    Any point on this will be appreciated.
    Regards.
    Denis

  • The AQ Service Bus showme a bad wsdl ( soap:address location )from internet

    Hi,
    first of all, excuse my bad english :-)
    I've a problem when I tray to get a wsdl file from Internet.
    In Aqualogic I've configured a wsdl file with the next content:
    <wsdl:service name="EmailValidation">
    <wsdl:port binding="tns:EmailValidationSoap" name="EmailValidation">
    <soap:address location="http://www.axonaxis.cl:7001/email"/>
    </wsdl:port>
    </wsdl:service>
    This file is reference from a proxy service.
    when I try to get the wsdl file from a browser, showme this:
    <service name="EmailValidation">
    <port binding="s0:EmailValidationSoap" name="EmailValidation">
    <s1:address location="http://server2005:7001/email"/>
    </port>
    </service>
    From a browser, put in "location" the server name (of course, if I try to execute the proxy service, the server not found).
    Why is doing this? How can I solve this problem?
    I don't have much experience in this so try to help me.
    Thank you very much (Muchas gracias!)

    ARCHIVO HOST!!!!

  • WSDL soap:address location

    Having developed/tested my soap services they are almost ready for shipping as a product.
    However, in the WSDL the <soap:address location=""> tag is set to my server - as used in development.
    So when I deploy this EAR file from JDev (9.0.5.2) this value is fixed, and will not work for customers.
    Is there anyway to make this value dynamic on deployment by customers or am I stuck with having to find out in advance customers server/port settings and then creating individual release per customer?
    I have tried using a relative url but this doesnt always work for clients trying to connect, e.g.:
    <soap:address location="/webservices/booking"/>
    Thanks in advance for any assistance.

    For now I have written a program, that is run after deployment. This program edits the web.xml and allows customers to specify the server name and port they are using.
    Anyone else have any solutions to this?

  • How to control the location of the SOAP:address element in the WSDL

    I have an EJB exposed as webservice in WebLogic 10.3. Further, the EJB has been annotated with the WebService annotation as in:
    @WebService(name = "S_CALCULATORname", serviceName = "S_CALCULATORserviceName",
    targetNamespace = "http://tempuri.org/SCalculator/")
    @Stateless(name = "S_CALCULATOR")
    public class S_CALCULATOR_Beanxxxxxx
    The location attribute of the SOAP:address element in the WSDL document generated by the Test Client facility is of the form
    http://host:port/ejb-java-class-name/service-name-attribute-value as in:
    <soap:address location="http://123.4.5.678:1234/S_CALCULATOR_Beanxxxxxx/S_CALCULATORserviceName" />
    Is there a way to control the value of the context root portion of the URL, ejb-java-class-name in this case, either using annotations or deployment descriptor files?
    thanks in advance for any replies,
    octavio

    Hi,
    While building the WebService Application you can use the following ANT task...
    <target name="build-service4">
    <jwsc
    srcdir="src"
    destdir="output/TestEar">
    <jws file="examples/webservices/jwsc/TestServiceImpl.java">
    <WLHttpTransport contextPath ="TestContext" serviceUri="TestServiceUri" portName="TestServicePortHTTP"/>
    </jws>
    </jwsc>
    </target>
    Or if you are developing JAXRPC EJB based WebService in that case you can even define the Context root using *@weblogic.jws.WLHttpTransport* annotation....
    @WLHttpTransport(contextPath="simple", serviceUri="SimpleService", portName="SimpleServicePort")
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
    Edited by: Jay SenSharma on Feb 4, 2010 10:22 PM

  • 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.

  • How to start BPM process WSDL from WDA

    Hello,
    I need to start BPM Process from SRM ECC with WDA; i have been through this link ;
    http://forums.sdn.sap.com/thread.jspa?threadID=1643425
    also followed the pdf named 'Triggering NetWeaver BPM Process from ABAP' provided from SAP but still stuck on some issues;
    - I have a WSDL in order to start BPM process and works fine as i successfully call it from EP Java AS with WDJ..
    - What i need to do is to trigg it from SRM Screens so i need to call this WSD from ECC, so;
        When i try to create a consumer proxy using external wsdl option, after putting in WSDL Url it throws an error;
    Exception occurred in communication framework:Error in HTTP Framework:405 Method Not Allowed http://xxx.local:50000/bpm/de
    mosapcom/dccategoryappbpm/StartCatAppSI
    Exception of class CX_SLIB_HTTP_FAIL
    And this is error from BPM Logs for the same action;
    process()
    [EXCEPTION]
    com.sap.engine.interfaces.webservices.runtime.RuntimeProcessException: com.sap.engine.services.webservices.espbase.server.additions.wsa.WSAddressingException: com.sap.SOA.wsr.030104 - Expected request method POST. Found GET.
    at com.sap.engine.services.webservices.espbase.server.additions.SOAPHTTPTransportBinding.getAction(SOAPHTTPTransportBinding.java:581)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.overwriteConfiguration(RuntimeProcessingEnvironment.java:894)
    at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:469)
    Also i found this link : http://wiki.sdn.sap.com/wiki/display/TechTSG/(WSR)Problems-P06/
    But no help so far,
    So, is there anyone faced similar or the same issue? Any suggestion will be appreciated.
    Regards,
    Yasin

    Hi soujanya,
    BPM server is not open to the internet but only intranet, so i will copy the WSDL code for you,
    will be glad if you can help;
    - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.koczer.com/StartCatAppSI/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="StartCatAppSI" targetNamespace="http://www.koczer.com/StartCatAppSI/">
    - <wsdl:types>
    - <xsd:schema targetNamespace="http://www.koczer.com/StartCatAppSI/">
    - <xsd:complexType name="DetailsType">
    - <xsd:sequence>
      <xsd:element name="Category_ID" type="xsd:int" />
      <xsd:element name="Category_Text" type="xsd:string" />
      <xsd:element name="User" type="xsd:string" />
      <xsd:element name="Manager" type="xsd:string" />
      </xsd:sequence>
      </xsd:complexType>
    - <xsd:element name="NewOperation">
    - <xsd:complexType>
    - <xsd:sequence>
      <xsd:element name="Details" type="tns:DetailsType" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:schema>
      </wsdl:types>
    - <wsdl:message name="NewOperationRequest">
      <wsdl:part element="tns:NewOperation" name="parameters" />
      </wsdl:message>
    - <wsdl:portType name="StartCatAppSI">
    - <wsdl:operation name="NewOperation">
      <wsdl:input message="tns:NewOperationRequest" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="StartCatAppSISOAP" type="tns:StartCatAppSI">
      <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
    - <wsdl:operation name="NewOperation">
      <soap:operation soapAction="http://www.koczer.com/StartCatAppSI/NewOperation" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="StartCatAppSI">
    - <wsdl:port binding="tns:StartCatAppSISOAP" name="StartCatAppSISOAP">
      <soap:address location="http://zerbpmts.koczer.local:50000/bpm/demosapcom/dccategoryappbpm/StartCatAppSI" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>

  • SOAP Address Location

    Is there any way to tell what the SOAP Address Location on our Netweaver is? 
    I'm being told by the queryview web service WSDL call that it is
    http://<server>:<port>/sap/bw/xml/soap/queryview?sap-client=100
    I'm not sure if this is correct, because I can't get the queryview webservice to work correctly with adobe flex and that is the URL string it is balking at.
    Any help is greatly appreciated!

    when you simply call this url from browser you would get the following messages
    - <soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
    - <soap-env:Body>
    - <soap-env:Fault>
      <faultcode>soap-env:Server</faultcode>
      <faultstring xml:lang="en">SOAP processing failure, error id = 112</faultstring>
      </soap-env:Fault>
      </soap-env:Body>
      </soap-env:Envelope>
    Regards
    Raja
    Consider rewarding points to helpful answers and mark it answered once you question is answered.

  • JMS transport - weblogic changes soap:address location="jms:.. to http

    Hi,
    Please help me to configure web service to use only jms transport.
    I try to create web service that uses JMS transport.
    I started from WSDL where I placed two elements:
    <soap:binding style="document"
                   transport="http://www.openuri.org/2002/04/soap/jms" />
    and
    <soap:address location="jms://host:7041/contextPathName/serviceUriName?URI=queueName" />
    Then in web service implementation I placed following annotation:
    @WLJmsTransport(contextPath = "contextPathName", serviceUri = "serviceUriName", portName = "portName", queue = "queueName", connectionFactory = "connectionFactoryName")
    Deployment is successful but when I look at generated WSDL (Admin console) I see that weblogic has changed <soap:address location="jms:.. to <soap:address location="http....
    And when I look at monitoring I see that port is using JMS transport.
    When I try to test my service using Admin console Test client I see that the queue is not used (Admin console/monitoring/Messages total is still 0) and service uses (I suppose) http transport.

    Hi,
    Please change "http://www.openuri.org/2002/04/soap/jms" to http://www.openuri.org/2002/04/soap/jms/ for soap1.1 or http://www.openuri.org/2002/04/soap12/jms/ for soap1.2.
    There must be some mismatch between edoc and implementation.
    -LJ

  • How does OpenSPARC translate Virtual Address to Physical Address or Vice V

    The i386 page address system has three levels: dir, page, offset. The 32 bits virtual address consists of dir, page, offset. When the process releases a virtual address to read a memory content, the MMU of i386 will translate the virtual address to physical address as follows:1,Based on the value of CR3 register and dir of virtual address, MMU returns the base address of page.2, Based on the the base address of page and value of page of virtual address, MMU returns the base address of physical page.3, Based on the base address of physical page and value of offset of virtual address, MMU returns physical memory address. 4, Read the content of physical memory address.
    However, when I read the source code of the bw_r_tlb of OpenSPARC�s MMU, I am puzzled. I am not clear how is the page address system of OpenSPARC implement.
    Will you offer me some hints about it ? And are there any documents about it?
    Thanks a lot!

    It would be good to add the definition of Hypervisor in the wikipedia.
    Thanks
    [email protected] wrote:
    > I have downloaded the source code of linux-2.6.17.9 version. In the arch directory of linux-2.6.17.9, I
    find the Hypervisor API (such as sun4v_intr_setstate, sun4v_intr_gettarget) has been
    integrated with Linux kernel. In other words, it is implemented in Linux kernel. All the time, I think
    Hypervisor API is an independent layer which provides an easy way to switch among all kinds of OS. But now,
    I find it is a part of Linux. If so, what a role does Hypervisor API take? Why do we name it Hypervisor API
    rather than a part of Linux? It do puzzle me, am I wrong?
    The Hypervisor API ("application programming interface") is fully described in the UltraSPARC T1 Hypervisor API Specification, which is downloadable from page http://opensparc-t1.sunsource.net/index.html .
    As a brief digression ... the term "Hypervisor API" has always seemed a bit oxymoronic to me -- given the historic equivalency of "application" to "nonprivileged". After all, isn't it more of an "SPI" (supervisor programming interface) because it services privileged supervisor (operating system) software, not nonprivileged (application) software? But if you think of a guest OS as an "application" (in the general sense of the word) supported by the Hypervisor, then "Hypervisor API" makes some sense.
    Now, regarding Hypervisor API and Linux. If you read the UltraSPARC T1 Hypervisor API Specification, you'll find that Hypervisor API calls are defined (appropriately enough) in terms of native SPARC assembly language. I haven't looked at the Linux source code, but I'd bet a considerable sum of money that the Linux sun4v_intr_gettarget() function is a C-language wrapper around a SPARC assemly-language routine that sets up arguments, performs a trap to the Hypervisor intr_gettarget function, and returns the result(s) to the caller.
    In any case, all actual Hypervisor code is fully implemented in the Hypervisor, not in Linux or Solaris or FreeBSD or Wind River Linux or any other OS running on top of the Hypervisor. Each OS may implement some "wrapper" code around Hypervisor calls, but no actual Hypervisor functionality actually resides in a guest OS. In fact, it can't reside in a guest OS because it must run in hyperprivileged mode and guest operating systems run in "merely" Privileged mode.
    To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]
    Shrenik Mehta               Tel: 408-774-8580
    Sr. Director, Frontend Technologies & OpenSPARC Program
    System Group               Fax: 408-774-8154
    Sun Microsystems          http://www.opensparc.net
    NOTICE: This email message is for the sole use of the intended
    recipient(s) and may contain confidential and privileged
    information. Any unauthorized review, use, disclosure or
    distribution is prohibited. If you are not the intended
    recipient, please contact the sender by reply email and destroy
    all copies of the original message.
    To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]

  • Virtual address to physical address

    Hi,
    How do i convert kernel virtual address to physical address.... do we have
    any DDI function for this.?.. i am writing a driver for a pci card... my
    card needs the physical address of the memory location so that it can dump
    data to this location..
    OS: SOlaris 7 on intel pc..
    gurus any idea how to do this stuff???....
    TIA
    azad

    The recommended way to do this is by using the ddi_dma* functions. I would suggest reading the entire "Writing Device Drivers", but pay particular attention to the chapters on DMA and the section in the chapter on character drivers that deals with DMA.

  • New development - need new roads added and 33 lot address locations corrected

    Hello, I am in the new homes and residential development business. I just developed a new residential development and I need to get Bing to update their roads and addresses. The addresses and roads have been in existence since about August 2014. I would have
    expected them to be updated by now but the roads are missing and the address locations are incorrect. 
    I have figured out how to get in touch with and submit bulk data to Google (Map Content Partners), but I cannot find an access point to Bing. I have gone the route of reporting mapping errors via Bing Maps, but I
    was wondering if their is a way to give Bing bulk mapping data to update new addresses and roads. I have shape files that include parcel boundaries, road centerlines, address blocks, and address points. I have also included the lot address and correct location
    coordinates below.
    Any help appreciated. 
    12306 186TH ST E  Puyallup, WA 98374 (-122.26914, 47.08904)
    12310 186TH ST E  Puyallup, WA 98374 (-122.26883, 47.08905)
    12314 186TH ST E  Puyallup, WA 98374 (-122.26853, 47.08906)
    12302 186TH ST E  Puyallup, WA 98374 (-122.26948, 47.08903)
    12318 186TH ST E  Puyallup, WA 98374 (-122.26819, 47.08906)
    12228 186TH ST E  Puyallup, WA 98374 (-122.26979, 47.0891)
    18509 124TH AV E  Puyallup, WA 98374 (-122.26786, 47.08912)
    18413 124TH AV E  Puyallup, WA 98374 (-122.26744, 47.08947)
    18510 124TH AV E  Puyallup, WA 98374 (-122.26832, 47.08954)
    18517 123RD AV E  Puyallup, WA 98374 (-122.26887, 47.08956)
    18520 123RD AV E  Puyallup, WA 98374 (-122.26955, 47.08958)
    18407 124TH AV E  Puyallup, WA 98374 (-122.26725, 47.08963)
    18502 124TH AV E  Puyallup, WA 98374 (-122.26811, 47.08969)
    18511 123RD AV E  Puyallup, WA 98374 (-122.26869, 47.08974)
    18401 124TH AV E  Puyallup, WA 98374 (-122.26703, 47.08979)
    18516 123RD AV E  Puyallup, WA 98374 (-122.26941, 47.08978)
    18412 124TH AV E  Puyallup, WA 98374 (-122.26792, 47.08985)
    18507 123RD AV E  Puyallup, WA 98374 (-122.26847, 47.0899)
    12317 184TH ST CT E  Puyallup, WA 98374
    (-122.26683, 47.08997)
    18512 123RD AV E  Puyallup, WA 98374 (-122.26924, 47.08995)
    18406 124TH AV E  Puyallup, WA 98374 (-122.26772, 47.09001)
    18415 123RD AV E  Puyallup, WA 98374 (-122.26827, 47.09005)
    18508 123RD AV E  Puyallup, WA 98374 (-122.26904, 47.09012)
    12313 184TH ST CT E  Puyallup, WA 98374
    (-122.26707, 47.09019)
    18405 123RD AV E  Puyallup, WA 98374 (-122.26805, 47.09021)
    18416 123RD AV E  Puyallup, WA 98374 (-122.26884, 47.09027)
    12309 184TH ST CT E  Puyallup, WA 98374
    (-122.26732, 47.09033)
    18410 123RD AV E  Puyallup, WA 98374 (-122.26864, 47.09042)
    12305 184TH ST CT E  Puyallup, WA 98374
    (-122.26754, 47.09046)
    18404 123RD AV E  Puyallup, WA 98374 (-122.26842, 47.09059)
    12301 184TH ST CT E  Puyallup, WA 98374
    (-122.26776, 47.09061)
    12227 184TH ST CT E  Puyallup, WA 98374
    (-122.26811, 47.09079)
    18503 124TH AV E  Puyallup, WA 98374 (-122.26763, 47.0893)

    It doesn't look like our data provider has this data yet. Note that in order for new addresses and roads to be added our data provider usually needs to drive to correctly capture all required information. I'll pass this information on to them so they can
    get this updated.
    http://rbrundritt.wordpress.com

Maybe you are looking for