Rt fpga dma timeout not waiting

Hello
I have a Target to Host DMA between. The read function sits in a while loop with a 2000ms timeout. Upon timeout it loops round and recalls the read function. On the second, and subsequent calls, it does not wait for the timeout time. I assume that this is because it was already itemed out. The error is wired to a shift register.
Does the timeout result in an error on the error line?
Is there a way to clear the timeout?
If i change it to an indefinite wait, is there a way to force the read to wake up?
Thanks
Solved!
Go to Solution.

jonnnnnnn wrote:
Hello
I have a Target to Host DMA between. The read function sits in a while loop with a 2000ms timeout. Upon timeout it loops round and recalls the read function. On the second, and subsequent calls, it does not wait for the timeout time. I assume that this is because it was already itemed out. The error is wired to a shift register.
Does the timeout result in an error on the error line?
Is there a way to clear the timeout?
If i change it to an indefinite wait, is there a way to force the read to wake up?
Thanks
Does the timeout result in an error on the error line? Yes, errro -54000 if memory serves correctly. Did you try highlighting execution to see this...
Is there a way to clear the timeout? Don't wire -1, I got burned by this. The DMA actually polls in the background (I think but I never verified) so a negative timeout can slam your processor. You can maybe try interrupts, although I didn't use this method I just threw a not-too-long timeout on there and cleared the error if it was -54000
If i change it to an indefinite wait, is there a way to force the read to wake up? The read will only return when data is there, unless you have a timeout.
CLA, LabVIEW Versions 2010-2013

Similar Messages

  • DMA from host to FPGA target is not supported for this remote system.

    I am trying tocommunicate with my FPGA (on the cRIO 9002) from the RTOS.  I setup up anOpen the correct VI reference with no error but as soon I try to access thefifo I receive error -63001 and the attached message says:
    Error -63001 occurredat Open FPGA VI Reference in target - multi rate - variables - fileIO_old.vi
    Possible reason(s):
    NI-RIO FPGACommunications Framework:  (Hex 0xFFFF09E7) DMA from host to FPGA targetis not supported for this remote system. Use another method for I/O or changethe controller associated with the FPGA target. 
    What other I/O optionsdo I have to move data asynchronously from the RTOS to the FPGA. I triedcreating memory but it appears that I can not write to the memory from the RTOSside.
    We also have a 9012sitting around will using this cRIO instead solve this problem. 
    I am very very greenwhen it comes to LabView so I apologize if this is an easy question. 
    Solved!
    Go to Solution.

    As stated in the NI-RIO driver readme,
    DMA is not supported from the host to the FPGA on the cRIO-900x series.
    The cRIO-901x controller supports DMA transfers from host to FPGA and
    FPGA to host while the cRIO-900x series controllers only support FPGA
    to host DMA transfers. Therefore, LabVIEW returns an error if you try
    to transfer using DMA from the cRIO-900x controller.
    The 9012 looks like the ideal solution, you are very lucky to be having extra hardware laying around 
    Rob K
    Measurements Mechanical Engineer (C-Series, USB X-Series)
    National Instruments
    CompactRIO Developers Guide
    CompactRIO Out of the Box Video

  • FPGA DMA Size Allocation

    Hi all,
    My application involves grabbing images from a 3-taps, 16-bit camera using FlexRIO. The PXI controller I am using is Windows-based while the FlexRIO module that I have is a PXI-7954 + NI 1483 adapter. The size of the image I am grabbing is 2560 x 2160, U16 and the clock cycle is 100 MHz. I've been trying for over a week and up to today, I still am not able to get the image from the camera as I kept on getting the DMA Write Timeout error. Right now, the DMA size in the FPGA is set at 130k but whenever I tried to increase this further, I get a compilation error. I've tried to have the host program to grab 100k data points from the FPGA DMA at every milisecond but it seems that, I am capped at about 10-15ms. Perhaps, Windows has its own limitation...
    Attached is the program that I am using, modified from the LabVIEW shipped example. Please advice, how do move forward from here? or, is it possible to further increase the DMA buffer size up 10x higher than the current limit?
    Attachments:
    1-Tap 10-Bit Camera with Frame Trigger.zip ‏1684 KB

    Hi Shazlan
    Apologies for taking so long to reply to you.
    You are correct in saying that the latest driver is IMAQ 4.6.4 and this can be downloaded from our website if you have not done so already.
    If you have already installed the IMAX 4.6.4 driver, has this managed to resolve your issue?
    Also, have you tried to run the compilation again and obtained a report outlining the problems?
    As a side note - I have been looking into the possibility of downloading some sort of driver for the Samos camera you are using from Andorra.  While National Instruments have not created a driver for this device, Andorra do have a Software Development Kit (SDK) which they say works with LabVIEW.  You may find it useful to have this so that you no longer have to write the driver yourself.  This may then save resources on the FPGA.
    Keep me updated on your progress and I will continue to look into this issue for you.
    Regards
    Marshall B
    Applications Engineer
    National Instruments UK & Ireland

  • 1473R DMA timeout at high speed?

    I'm using a 1473R with a Basler line camera spl2048-140km. I managed to modify the example to run the camera on both 8 tap 8 bit mode and 4 tap 12bit mode. Both run well at low speed. However, there are two issues when I try to run it at high speed.
    If I set the frame trigger at relatively high speed before I start the acquiring (like 30kHz), a DMA timeout error will jump out as soon as I start it (error -8999). If I set it at low speed (like 100Hz), it will run fine as I increase it to 30kHz after it starts.
    Another issue is, when I try to push the speed of the camera to its limit, which is 70kHz for single channel mode and 140kHz for dual channel mode, I will always have the error -8999. It happens when the speed reaches 100kHz in 8 tap 8 bit mode, and 50kHz at 4 tap 12 bit mode. I wonder where the bottle neck is and if there will be a way to solve it.
    Thanks!

    I'm not that familiar with the FPGA code for the 1473R, but I am fairly sure that the DRAM example has been tested with fairy fast cameras. That said, it seems from looking at it that it does not have a good feedback mechanism if PCIe bandwidth is not available. It's only feedback seems to be if the host DMA buffer fills up (e.g. host code doesn't read it fast enough). Since PCIe/memory bandwidth is extremely host-dependent, it is quite possible this example is not well tested with the combination of very fast cameras and some systems that have more jittery PCIe bandwidth. I'm not sure of the specifics of the DMA FIFO behavior, but my assumption is that the number of elements remaining really only concerns itself with host space available. For most situations, the minimal amount of FIFO built into the DMA engine likely makes this work fine.
    First, I'd try instrumenting the code to figure out which specific part in the FPGA code is timing out. The example doesnt seem to track all the error cases well.
    Assuming it is the host DMA that times out AND it always reports that there is free space available, my suggestion would be to modify the code to let the DMA step retry with the same data the next clock cycle on a Timeout and let the data back-up in DRAM as needed.
    Eric

  • BackupExec: A timeout occurred waiting for NDMPD.NLM to init

    "Error: 1004 A timeout occurred waiting for NDMPD.NLM to initialize."
    A very common and well documented issue but every fix I have found has not worked. The list is extensive so I will start by describing the issue, then the environment and finally what I have tried so far.
    The issue
    I can not load BackupExec 9.1 or 9.2 on NetWare 6.5 SP8. The loader starts and when it gets to loading NDMPD.NLM the CPU hits 99% (reported by monitor.nlm) and BackupExec stops loading for about 80-120 seconds. The loader eventually gives up after a non-critical abend. From this point on I can not unload becdm.cdm and I generally reboot the server to clear the abend.
    BackupExec has been working on the server for about 2 years, I can not link any changes to the time it stopped working.
    It used to load reliably every time for about 1.5 years and then it started to exhibit this issue when loading 1 in 10 times. It has gradually gotten worse and now will not load at all.
    Before you say it, yes I know Symantec dropped BackupExec for NetWare years ago.
    It seems to me this can only be a hardware issue now but I'm keen to hear any other ideas?
    The environment
    * The physical server is a HP DL385 G5 (SKU 411360-371), the tape drive is an external half height HP Ultrium 448 LTO 2 (SKU DW086A) using SAS to connect to a HP SC44Ge SAS HBA (SKU 416096-B21). It has 18GB of RAM, Two quad-core AMD Opteron 2352 2.1 GHz CPU's and 5 x direct attached SAS hard drives running on the internal P400 RAID controller configured with RAID 5.
    * I can provide firmware versions if needed, the BIOS is HP A09 2009-07-11. Don't have the tape drive or HBA versions to hand.
    * The server is running VMware ESXi 4.1.0 build 260247, using a free license i.e. stand alone.
    * The VMware server uses about 50% of RAM, 70% of storage and 12% of CPU.
    * The guest is NetWare 6.5 SP8 (overlay) running as a guest with 4GB of vRAM and a single CPU. The tape drive is presented as a generic SCSI device.
    * I'm running BackupExec for NetWare 9.2.1401.5 build 287839 with the NetWare Open File Option and a Windows Remote Agent.
    * I'm running the storage driver LSIMPTNW.HAM version 5.02, 5 Dec 2007, which is default with SP8. BackupExec 9.2 device driver becdm.cdm version 7.50, 7 Feb 2006.
    * The NetWare server sees the tape drive as an "Unbound Device Object" until becdm.cdm is loaded at which point its recognsied as "HP Ultrium 2-SCSI T65D"
    * The tape drive is listed on the BackupExec HCL - "StorageWorks Ultrium 448 LTO2" except mine is SAS not SCSI. Enterprise Support - Symantec Corp. - Symantec Backup Exec for NetWare Servers (tm) 9.x (9.0, 9.1, 9.2) Hardware Compatibility List. Includes HCL information for supported drives, libraries, virtual tape devices, fibre-channel HBAs, switches, and rou
    What have I tried so far?
    * We have a rental tape drive identical to our own as the original one was over-heating, so I have tried two physical tape drives. Both using the same server, HBA and SAS tape drive cable.
    * I have used tcpcon.nlm to check that port 10,000 is unused.
    * I have tried the parameter -!X on the line of bestart.ncf that loads BackupExec to stop it checking if port 10,000 is free.
    * I have added a set statement to c:\nwserver\startup.ncf "set auto load of cdm modules = off" so it will not try to load unwanted CDM's.
    * I have renamed all copies of nwtape.cdm to nwtape.cdx on the C: so they can not be auto loaded.
    * There are no load statements in the startup.ncf for other tape drive device drivers. Just scsihd.cdm and idecd.cdm.
    * There are no tape libraries or robots involved. Its just a basic tape drive.
    * The physical and virtual server have been rebooted numerous times to ensure its not a memory issue etc...
    * I've loaded the server with no other significant modules loaded. Just the basics like eDirectory etc... and the same issue still occurs.
    * In addition to the NW65 SP8 default version of lsimptnw.ham I have tried version 5.03.01, 23 Jan 2008, from the LSI website.
    * I have deleted the original BackupExec folder from the server (sys:\bkupexec) and re-installed BackupExec numerous times.
    * I have powered off the tape drive a number of times
    * I have changed the tape drives virtual SCSI ID, presented by VMware to the NetWare guest, to be a higher number on the same virtual HBA as the virtual disk. I have also tried allocating the tape drive a virtual SCSI ID on a dedicated virtual HBA, SCSI 1:0.
    * I have deleted the SMDR config file (sys:\etc\sms\smdr.cfg) and re-created it using the command "load smdr.nlm new"
    * I have deleted the NetWare servers backup queue and the SMS SMDR Group from eDirectory and re-created the queue using the command "load qman.nlm new". Note: as its NW65SP8 the SMS RPC object does not exist and the SMS SMDR group is not re-created.
    * I have deleted the two BackupExec objects from eDirectory and re-created them by loading BackupExec using "bestart.ncf".
    * I have checked the health of eDirectory.
    * I have tried the LSI SAS and LSI Parallel virtual HBA's in the VMware guest machine.
    * I have tried adding the parameter qtags=off to the load command for lsimptnw.ham in startup.ncf.
    * I have tried the parameter -b on the line of bestart.ncf that loads BackupExec
    * I have tried loading ipxspx.nlm to stop any public symbol error messages when loading BackupExec
    * I have also tried BackupExec version 9.1 build 0306.12 and 9.1.1158.10 build 289707
    * I have built a second NetWare 6.5 SP8 server (SP8 overlay DVD, MD5 verified ISO media) using the Backup server profile during the GUI install stage. I have loaded afreecon.nlm, installed VMware tools (vmwtool.nlm) and BackupExec for NetWare 9.2.1401.5 build 287839. The same issue occurs
    System output
    1) Excerpt from "list storage adapters"
    0x04 [V358-A3] SAS1068:00008 [slot 8]
    0x06 [V358-A3-D0:0] HP Ultrium 2-SCSI T65D
    2) Backup Exec SureStart Console
    Module NETDB.NLM is already loaded
    Module SMDR.NLM is already loaded
    Module TSAFS.NLM is already loaded
    Loading module TSANDS.NLM
    Module BECDM.CDM is already loaded
    Loading module B2D.NLM
    Module NWIDK.NLM is already loaded
    Module NSS.NLM is already loaded
    Loading module OFM.NLM
    Loading module NRLTLI.NLM
    Loading module AD_ASPI.NLM
    Loading module NDMPD.NLM
    Error: 1004
    A timeout occurred waiting for NDMPD.NLM to initialize.
    Press <Alt+Esc> to return to the Server Console. After you resolve
    the error condition(s), re-execute the BESTART command.
    3) Abend log
    Novell Open Enterprise Server, NetWare 6.5
    PVER: 6.50.08
    Server halted Sunday, 6 May 2012 5:38:23.196
    Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)
    Registers:
    CS = 0008 DS = 0010 ES = 0010 FS = 0023 GS = 0023 SS = 0010
    EAX = 00000000 EBX = 00204B58 ECX = 896B77E0 EDX = 8A26157C
    ESI = 00204B58 EDI = 00000F9B EBP = 8A261DD4 ESP = 8A261DA8
    EIP = 8A1E03FD FLAGS = 00010082
    8A1E03FD C680B00E000000 MOV [EAX+00000EB0]=?, 00
    EIP in LSIMPTNW.HAM at code start +000013FDh
    Access Location: 0x00000EB0
    The violation occurred while processing the following instruction:
    8A1E03FD C680B00E000000 MOV [EAX+00000EB0], 00
    8A1E0404 8A45FC MOV AL, [EBP-04]
    8A1E0407 8845F8 MOV [EBP-08], AL
    8A1E040A 8A45F8 MOV AL, [EBP-08]
    8A1E040D 89EC MOV ESP, EBP
    8A1E040F 5D POP EBP
    8A1E0410 5F POP EDI
    8A1E0411 5E POP ESI
    8A1E0412 5B POP EBX
    8A1E0413 C3 RET
    Running process: Server 10 Process
    Thread Owned by NLM: SERVER.NLM
    Stack pointer: 8A261F5C
    OS Stack limit: 8A25A020
    Scheduling priority: 67371008
    Wait state: 50500F0 Waiting for work
    Stack: --8A261E01 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00951740 ?
    8A1E0414 (LSIMPTNW.HAM|(Code Start)+1414)
    --0097BAA0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --01900190 ?
    --157C157C ?
    --0D000001 ?
    --0097BACC ?
    --8A261D01 ?
    --8A261E18 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A1DFD6B (LSIMPTNW.HAM|(Code Start)+D6B)
    --0097BAA0 ?
    --0097BAC0 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --0097BA50 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00F20000 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00200000 ?
    --0097BAA0 ?
    --0097BAC0 ?
    --8A261EB0 ?
    --8A261E44 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A1FAA64 ?
    --0097BA50 ?
    --00000F03 (LOADER.NLM|KernelAddressSpace+F03)
    --00000286 (LOADER.NLM|KernelAddressSpace+286)
    --00951740 ?
    8972FA00 (NWPA.NLM|HAI_Enable_Real_Mode_Access+34)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --8A261E70 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A1FAC47 ?
    --0097BA50 ?
    --00204B58 ?
    --0097BA50 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --01080000 ?
    --01080000 ?
    --8A261E90 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A1FAC95 ?
    --00952180 ?
    --010824A0 ?
    --02058001 ?
    --8A261EB8 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A207658 ?
    --010824A0 ?
    --01091240 ?
    --00951740 ?
    --00008100 (LOADER.NLM|KernelAddressSpace+8100)
    --00008134 (LOADER.NLM|KernelAddressSpace+8134)
    --8A261EEC ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    8A208ED6 ?
    --010824A0 ?
    --00000003 (LOADER.NLM|KernelAddressSpace+3)
    --00000046 (LOADER.NLM|KernelAddressSpace+46)
    --02010002 ?
    --010824A0 ?
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --00951740 ?
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00204B60 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    89729AE5 (NWPA.NLM|NPAThreadRoutine+3D)
    --00010002 ?
    -896E5110 (MM.NLM|PostponeEvent+0)
    8973173F (NWPA.NLM|CDM_MountActivate_Message+EB)
    --00000001 (LOADER.NLM|KernelAddressSpace+1)
    --00000000 (LOADER.NLM|KernelAddressSpace+0)
    --802171E4 ?
    --802171E4 ?
    80327F6B (MM.NLM|RetryPostponedMessages+237)
    --01081A00 ?
    --00204B60 ?
    --00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
    --00204B58 ?
    --00204B58 ?
    003682B2 (SERVER.NLM|CallAESRoutineWithEsiSet+A)
    Additional Information:
    The CPU encountered a problem executing code in LSIMPTNW.HAM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
    Thanks,
    MC

    Well the problem is now resolved. It was either faulty tapes (about 12 of) or two tape drives with faulty heads. We had the heads replaced in one of the drives and tested it with a new tape, it works perfectly again.
    MC

  • Timeout in waiting for IPS service to start. Component: IPS

    Hello
    I have an sa 520 and in logs i see the message
    <Timeout in waiting for IPS service to start.
    Component: IPS>
    i am sure that ips failed to start because although i have enabled ips in lan with
    Signature File SBIPS000019  i do not see any logs for ips events
    firmware version = 2.2.0.7
    the above happened after a facory reset and configuration from scratch

    Well the problem is now resolved. It was either faulty tapes (about 12 of) or two tape drives with faulty heads. We had the heads replaced in one of the drives and tested it with a new tape, it works perfectly again.
    MC

  • DMA Timeout Error

    Changing to XP-64Bit, I installed the software for my HP Scanjet 8270, and haven't been able to scan ever since.  I continuously get a DMA Timeout error.  If I let it sit for a while, eventually I get an HP-CUE Scanning Flow Component error, and then an automatic application/shutdown error window with the AppName: hpqkygrp.exe, AppVer: 9.0.0.257 details.  After 2 solid weeks of back and for with the pathetic HP non-Support, I haven't gotten anywhere.  I have uninstalled/re-installed, downloaded their latest FULL version, this thing just doesn't work.  It doesn't work with the XP scan wizard either.  It gets about a 1/3 of the page and then just hangs in the scanner with a DMA Timeout error.  Please help !!!

    I'm having the same problem. My scanner is a HP ScanJet 8250. I'm using Adobe Pro Extended & Windows Fax & Scan programs. Currently running Windows 7 (64 bit) Professional on an Intel i7-2600 CPU with 4x2.00GB of DDR3-1333 RAM
    When using the feeder tray, it will either feed 3/4 of a page before timing out or it will not scan anything at all. When using the flatbed, the scanning bulb will move down the glass but then stop at the end and timeout.
    I did have this scanner fuctioning properly on another computer using Windows 7 (64 bit) Ultimate but the hardware specs elude me at this point in time. I saw there was a firmware update for previous generations of Windows but nothing for Windows 7.
    So far I have tried uninstalling & reinstalling the driver. Switching through every USB port on the tower. And I've swapped out the USB cable.
    Any help would be greatly appreciated.

  • HOST to FPGA DMA Transfers

    Hi,
    We're having trouble using the Host to FPGA DMA feature available in
    LabVIEW 8.20 with IFRIO. After starting a compile, we get the following
    error message:
    An internal software error has occurred.
    Please contact National Instruments technical support at ni.com/support
    with the following information:
    Error -61048 occurred at This target does not support DMA Output (from the host to the target).
    Possible reason(s):
    LabVIEW FPGA:  This target does not support DMA Output (from the host to the target).
    Any help would be greatly appreciated.
    Thanks.

    Hi Manik:
    We did not support DMA output on the PCI-5640R when we released NI-5640R 1.0. This is why you are getting the error message that you are seeing.
    We plan to add support for DMA output in an upcoming release.
    ----abhay

  • CCP related: A timeout occured waiting for a response from the ECU

    Hello All,
                I had just started using ECU Calibration tool kit software. Iam using USB 8473 for my application.When I tried to run the VI after loading the *.A2L file, I see an error message saying "A timeout occured waiting for a response from the ECU ". Does anyone know how to communicate with the ECU through CCP.
            Iam pretty sure that Iam using the right cable. I also checked the address of the parameters using Get property.vi what iam trying to read, wether they are matching with the address in the *.A2L file or not.They are matching. However I was able to communicate with my ECU when I use the same device to read the data over J1939 data link, based on arbitration ID's, with the Vi's from CAN Frame to Channel Conversion Library.
        Can any pls help me out how to communicate with my ECU using CAN Calibration Toolkit software.
    -Lucky.

    Hello,
              I am sending you an attachment of the manual for the ECU Calibration tool kit . Please go through the manual it will clarify your doubt. Moreover , check for can vi's in the example finder in labVIEW. Those will help ....
    I am sending you a link which gives you some insight about the installation of  CCP command set and the use of the toolkit with the USB CAN hardware.
    http://digital.ni.com/softlib.nsf/websearch/D7DE248D07CAD00086256ED3004BAB8A?opendocument&node=13206...
    Drivers and Updates: ECU Measurement and Calibration Toolkit 2.1
    Attachments:
    can manual.pdf ‏1437 KB

  • Process chain Error: This AND process is not waiting for event RSPROCESS

    Hi All,
    I am facing an error in the process chain in PRD.
    Error message: This AND process is not waiting for event RSPROCESS.
    We had a process chain which had two sub chains which run parallel and below of this we had AND process type and below of the AND process we had 4 more jobs.
    Once the two subchains got successfully loaded, the and process should turn to green and further 4 jobs should start.
    It is a daily load , it worked fine from past years,but suddenly the AND processtype is getting failed.The thing is in the two subchains if one got completed, the AND process process is not waiting for 2nd subchain to get completed.The AND process is turning to RED (status: cancelled) . I tried to repeat the AND process once after above 2 subchains loaded, but it didnt worked.
    And i removed the existing AND process and created a new one and placed it in same place and activated and schedules again.but still it is getting failed with same error.
    Thanks in advance,
    Sai Chand.S

    Hi,
    If you did any transports related to that metachain we face similar kind of issues.
    not only the AND process , we need to remove all the process before executing the AND process and create it again.
    It helps you, you said your in production So you should take the proper approvals and do it.
    Regards,
    Yerrabelli.

  • Client-Auth reports: HTTP4030: Timeout while waiting for client certificate

    Hello,
    I'm having problems with the certificate authentication in my Sun Java System Web Server Enterprise Edition 6.1: I have created an ACL in the SJWS that asks for a client certificate when the user goes to a specific URI:
    acl "uri=/server1/myaction.do";
    authenticate (user) {
    method="ssl";
    deny (all)
    user = "admin";
    It works great and, when the user goes to "/server1/myaction.do" (we are using Internet Explorer 7 as Web browser), the window for selecting the client certificate appears:
    - If the user selects a certificate that doesn't require password, everything works fine.
    - The problem comes when the certificate is configured in Internet Explorer for asking for a password every time it is accessed. Once the user has selected the password protected certificate, the window for typing the password appears, but if the user doesn't type it and click OK IN LESS THAN 5 SECONDS (I've timed it), the following messages appear in the SJWS logs:
    [28/Nov/2007:09:25:05] failure ( 2055): for host 10.0.145.11 trying to GET /server1/myaction.do, Client-Auth reports: HTTP4030: Timeout while waiting for client certificate.
    [28/Nov/2007:09:25:05] security ( 2055): HTTP4290: get_auth_user_ssl: client passed no certificate.
    I tried to add the following two lines to the magnus.conf file of the SJWS, but nothing changed:
    SSLClientAuthTimeout 240
    AcceptTimeout 3600
    Has anyone experienced something similar? Any little piece of advice would be greatly appreciated.
    Thank you very much in advance,
    Carlos.

    This is fixed in Web Server 7.0 update 2. Please migrate/upgrade to Web Server 7.0 update 2. Sorry for the inconvenience.

  • WaitFor() Does not wait for Process

    Experts,
    I have a Process p for a Microsoft Outlook Process OUTLOOK.EXE
    Now if there is an Email file (xyz.msg) opened as this process along with my MS Outlook running then,
    p.waitFor();
    // Where p = runner.exec(shell_command_to_open_msg_file);
    does not wait and move further.
    But if the MS Outlook is not running, then it waits till I manually close the Email msg file.
    How can I handle/overcome the former situation?
    Thanks in advance

    moondra_JavaDev wrote:
    How can I handle/overcome the former situation?
    You can't in java.
    What happens is that when outlook is already running then the new attempt to run does the following
    1. A application starts
    2. It determines that outlook is already running.
    3. It focuses that instance
    4. It exits.
    The last step is what you see. You do not have access to the one that is running because it isn't the same application.
    I would suggest examining the business requirements that are driving this. If you allow the user to already have outlook open then it seems rather odd that you are insisting that they exit it anyways. Instead you can pop a dialog and require that they tell you when they are done. Or don't use outlook and use java mail instead.

  • WORKFLOW PROCESS IS NOT WAITING FOR USER INPUT LIKE RE-ASSIGN FUNCTION

    I am using Stand alone Workflow 2.6, In my workflow process
    which is an Issue tracking system which is working fine. On Enhancement I would like to create my own RE-ASSIGN function which will, Change the ownership of an issue totally to other user.
    For this I Created a package(CHANGE_OWNER.CREATE)which will show list of Users and Comment field(Just like Re-Assign).
    Here user can pick other user, and add comment,
    once submit for that Item key I am updating the workflow notification table so that paritcular issue ownership will be changed.
    In my workflow process I created a lookup code called "Change Owner". On click of Change Owner it will call the Function
    in workflow process which will call CHANGE_OWNER.CREATE, here
    the workflow process supposed to wait and get the User to be
    changed. BUT THE PROCESS IS NOT WAITING, IT JUST DISPLAYED THE
    SCREEN AND CONTINUED THE WORKFLOW PROCESS. I WANT THE MY
    WORKFLOW PROCESS TO BE ACT AS RE-ASSINGN BUTTON WHICH WILL WAIT
    FOR THE USER INPUT.
    HOW TO DO IT.
    Thanks
    Bala.

    Hi Bala
    What enhancements were you adding to the Workflow Reassign/Delegate feature, which included being able to add comments? A good idea is to look for any differences between how workflow implements the reassign feature, and your customization.
    Also, make sure you only use the Public documented PL/SQL APIs and do not update the tables directly to ensure no Support or Upgrade Issues.
    Cheers
    Mark
    I am using Stand alone Workflow 2.6, In my workflow process
    which is an Issue tracking system which is working fine. On Enhancement I would like to create my own RE-ASSIGN function which will, Change the ownership of an issue totally to other user.
    For this I Created a package(CHANGE_OWNER.CREATE)which will show list of Users and Comment field(Just like Re-Assign).
    Here user can pick other user, and add comment,
    once submit for that Item key I am updating the workflow notification table so that paritcular issue ownership will be changed.
    In my workflow process I created a lookup code called "Change Owner". On click of Change Owner it will call the Function
    in workflow process which will call CHANGE_OWNER.CREATE, here
    the workflow process supposed to wait and get the User to be
    changed. BUT THE PROCESS IS NOT WAITING, IT JUST DISPLAYED THE
    SCREEN AND CONTINUED THE WORKFLOW PROCESS. I WANT THE MY
    WORKFLOW PROCESS TO BE ACT AS RE-ASSINGN BUTTON WHICH WILL WAIT
    FOR THE USER INPUT.
    HOW TO DO IT.
    Thanks
    Bala.

  • How can I not wait for a RFC response

    Hi everyone, i want to execute an RFC and not wait for the response, i don´t care, so, is there a way to achieve this ? thanks

    Hello Isaac,
    If you are calling the RFC from WebDynpro then you have to wait for the RFC response. However, there is a way that you can get early response from a RFC.
    Suppose you are using RFC1 in your program and it contains business logic. Now, don't directly call the RFC1, instead, write another RFC2 which calls RFC1 asyncronously. This way, when you call RFC2 it automatically call RFC1 and does not wait for any response for RFC1
    You can call RFC1 from RFC2  asynchronously:
    CALL FUNCTION RFC1 STARTING NEW TASK taskName
    Your WD application will immediately get a response from RFC2 while RFC1 still executing.
    To know more about asynchronous RFC refer [Parallel Processing with Asynchronous RFC  |http://help.sap.com/saphelp_nwpi71/helpdata/en/22/0425c6488911d189490000e829fbbd/content.htm]
    Hope this helps
    Abhinav

  • WaitFor() does not wait!

    Hi, I have a small applet that launches a MS Word app and opens a document. In the code I use the waitFor() process method to wait until the MS Word app closes so I can do some processing to the MS Word file.
    The code looks like this:
    public void openMSWDocument() throws IOException
    Process p = Runtime.getRuntime().exec("cmd /c start " + outfilePath);
    try
    p.waitFor();
    System.out.println("process complete");
    catch (InterruptedException ie)
    System.out.println("Process interrupted: " + ie.toString());
    for some reason, the process does not wait. Is there something that I am not doing that I should be doing?

    Never mind. I found the problem.
    It seems that using 'start' in my command line will cause the waitFor() not to work.
    The process p is dependant on the 'start' process to complete, so when 'start' terminates (after it launches my windows app) then so does the process p. Hence, waitFor() = 0.
    so i used the command line cmd = appFilePath + " " + fileNamePath;
    Its works!

Maybe you are looking for