Lookout 4.5.1 slow

Over the past several days, Lookout 4.5.1 (build 19) started to run very slow. The PC is running fine, any application I open runs normal. Lookout is running about 1/3 to 1/4 speed. It's not using any processor time, and the drive isn't full. Inputs (external pushbuttons) have to be held 3 - 4 times longer to take affect. The process are running, but are slow also. I tried closing the server / client and open the LKS files, but they run the same way. This PC has been running flawless for 8+ yrs with no monitor, KB, or mouse, so there are no bugs to contend with. Any ideas would be helpful. Thanks, Mark

Memory usage for lookout.exe, lkcitdl.exe
CPU Usage seems fine.  I have had issues where the process slow to a crawl when Citadel was loading the database.  Even citadel 5 slows down a bit.
Guess we need Ryan in here
Mike
Mike Crabtree - Lead Developer
Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
(866) 964-6948 / (760) 247-9512

Similar Messages

  • Lookout 6 Slow Response

    We are currently moving our clients to Lookout 6, but have noticed some major issues.
    When the server and client processes are opened on the dev. machine, displays are very unresponsive. Clicks to pots, buttons, etc. and delayed about 1-3 seconds. HyperTrends are shoppy, and take minutes to load (only 9 data points!). Client machines on the network are even worse, taking upwards of 10 minutes to load 1 hour of logged data (.1 resolution, very little fluctuation over 1 hour). Moving a panel via the titlebar causes the machine to slow, windows needing to be redrawn constantly.
    The new SQL/MSDE server for Citadel also causes 90% processor usage with the process idle!
    This appears to be a known problem, any ideas?
    Mike
    Dev. Machine Specs:
    Windows XP Pro
    Athlon 1Ghz, 512MB, 2x60GB RAID, ATI 9600 Video. (Not really that slow!)
    Mike Crabtree - Lead Developer
    Destek of Nevada, Inc. / Digital Telemetry Systems, Inc.
    (866) 964-6948 / (760) 247-9512

    Mike@DTSI and skibum09,
    I am sorry to hear that you are having difficulties with Lookout 6.0. My co-workers and I in no way discount your concerns or doubt their validity. It seems quite obvious to me that both of you are having difficult issues.
    That being said, I want to assure you that getting very good performance from Lookout 6.0 in the types of applications that you are describing is completely possible. I have talked to dozens of people who are doing just that. We have not seen the issues that you are describing in any of our applications here at National Instruments. In my opinion, this most likely points at a difference in style of programming, hardware, peripheral software, or networks.
    That leaves a lot open for investigation. If you would both be willing, I would appreciate it if you could post, 1, a general description of your application, 2, details of the computer(s) having the trouble (HW, OS, and OS ServPack), 3, any peripheral software that is running on the machines (virus scans, firewalls, software updaters, thin clients, etc.), and 4, the details of the networking setup being used.
    I am hopeful that with this information that we may be able to identify some similarities between the machines that you are having trouble with. In addition, if either of you can create a small, hardware-free, application that can duplicate the problems that you are seeing and post it, I would be willing to try running it to see if it is possible for me to duplicate your trouble. I am hopeful that others in this forum might also be willing to do the same.
    So lets track down the problem that you are seeing and get it resolved. I look forward to your responses.
    Regards,
    Jed R.
    Applications Engineer
    National Instruments

  • Lookout 6.0 and Citadel 5 Slow to Connect and Display Data

    Wondering if anyone else is seeing this.
    We had a Lookout 5.1 Citadel 4 database running about 75-100 data points. We use hypertrends for viewing the trended data. In the old version, the hypertrends and historical data would be presented on the screen nearly instantaneously. We recently upgraded to Lookout 6.0 and Citadel 5. The hypertrends now take minutes to display and often times come in choppy. This is VERY inconvenient, especially when we try to connect other clients over our T1 WAN connection.....display time is VERY long.
    I don't want to update our other Lookout system to 6.0 until this issue is resolved, our other system has a database that has somewhere in the realm of 3000+ data points it is tracking, and we can't afford to lose the speed for the trending displays.
    Thanks for any input in advance.

    I complained to ni about the fact that nicitdl5 is using a lot of processor resources on the computer running the server process. As an answer I received the same bla bla ... more robust ... bla bla. The thing is that it is happening only when the client is accessing the server from the network. When they are on the same computer every thing is fine. I think it is more of a communication problem. You can use the performance monitor to graph the network activity of nicitdl5 to see that it is receiving a lot of packets while sending almost nothing. That leads me to the hypothesis that the client is making a lot of useless request (buggy hyper.cbx?) to the citadel server.
    Still, I'm reassured to see that I'm not alone facing that performance issue but I think that we'll have to wait for 6.1!

  • How do I move Lookout 5 w/ Fieldpoint 3 to a new PC

    I want to move my install of Lookout 5 from an old, slow computer to a newer, faster one. Both machines run Windows 2000 SP4. I have a clean install of Lookout 5 and Fieldpoint 3 on the new machine, and the old machine still works and is running on the same network subnet. In addition to lookout.sec (in the Windows system folder), what else do I need to move to bring up my system on the new machine? Are there registry keys that need export/import? Which folders (by default, at least) need to be copied?
    Thanks!!

    Besides .l4p .l4t .lks .lka files, you need to copy the database folder to the new machine. And then create a new database on the new machine with the data.
    Ryan Shi
    National Instruments

  • Lookout "Client" Not Updating with Correct Numbers

    We have Lookout 6.6 processes running on full development servers at separate locations.  At Station  1, Lookout is communicating with plcs collecting data. The data here is updating properly.  At Station 2, we have expressions looking at data on the Lookout process running at Station 1.  At Station 2, our expression might look something like this:
     \\192.168.201.10\processname\modbus1.30001  192.168.201.10 is the static IP address of the Lookout computer at Station 1. 
    If for some reason the computer at Station 2 is restarted, the value of the expression shown above will often times be incorrect when Lookout comes back up.  It will stay incorrect until the actual value of the expression changes at Station 1, or we modify the expression at Station 2 and type it in exactly as it was.  Somehow, this forces the expression to update and the value will be corrected.  This is causing significant problems because we cannot rely on the values shown at Station 2 to be correct on signals that aren't continuously changing. 
    I have installed the latest Logos engine (via a Lookout 6.7.2 install) to try and address this issue, and it does appear to be better, but the problem is still occurring.  The problem is not an inability to communicate between Station 1 and  Station 2, because modifying the expression at Station 2 to be exactly as it was causes the numbers to properly update. 
    Any suggestions to address this problem will be appreciated very much.
    Jeff Miller 

    Thanks for the reply Ryan.
    All updates for 6.0.2 are current.
    I updated the hyper.cbx as noted in your post.
    This did not seem to correct the problem.
    We do not have any of the client laptop firewalls turned on.  If I turn the server firewall on, I can't connect to the client laptops.(Seperate issue that I will deal with in another post.) 
    I turned the firewalls for the client laptops on and added the following exceptions to the the firewall exceptions list.
    C:\Windows\system32\lkads.exe
    C:\Windows\system32\lktsrv.exe
    C:\Windows\system32\nicitdl.exe
    C:\Windows\system32\nicitdl5.exe
    C:\Program Files\National Instruments\Lookout x.x\lookout.exe
    I can now connect and get the Hypertrend to work.
    The first couple of times the trending was slow but by turning the
    trend off, the trend would slowly load.  It is now a lot faster and
    probably is restricted, now by the modem speed.
    Thanks for your help.
    WaterWorks
    http://digital.ni.com/public.nsf/allkb/0D7B86F4B4D19A5E86256F9A006EECB1?OpenDocument
    http://digital.ni.com/public.nsf/websearch/8AE45BBFA1D7025E862570F200642FD8?OpenDocument
    hyper1.zip (89 kb)
    Message Edited by WaterWorks on 06-25-2008 06:23 PM

  • Dreamweaver slow to close

    I'm running Dreamweaver 8 and for the last few months have
    been experiencing very slow change-over when switching from site to
    site. When I click on a another site in the Files drop-down,
    Dreamweaver starts a background file activity which, on the larger
    sites, can take a minute or more. Is there any way to speed this
    up? Its making it a very, very slow job when jumping between sites
    to make adjustments, etc. The strange thing is that I never used to
    have a problem with this and it seems to have started quite
    suddenly, but I can't think what has changed. I'm running a
    dual-Xeon based PC so resources are NOT an issue.
    Thanks in anticipation.

    Hello Sathanas,
    This might be due to a sync in progress while you are trying to quit DW.
    Next time you face this, lookout for the sync settings icon on the top right corner of the DW window.
    If it shows "Syncing...", allow the sync to complete. You should be able to quit DW immediately thereafter.
    Cheers,
    Subhadeep

  • Lookout server process control through modem from remote site

    Hi!
    I want to control the lookout version 5.0 server process from my office by using the simple 56k internal modem and telephone line. I know the congiguration for sever /Client for  Local Area Network (LAN).
    1. I have server process.
    2. I have client process. (I start server process on client computer when server computer fails)
    3. Internal modem (56 k)
    4. Telephone Line.
    Please send me the mateial which can help me in solving this problem.
    Your response is highly appreciated.
    Atif Sarfraz

    Atif,
    A couple of options are discussed in the the following thread:
    http://forums.ni.com/ni/board/message?board.id=190&message.id=73
    That was way back when VPN wasn't as common.  Today... if you can VPN into your Server's network, then it will be a breeze since you are actually on the same network.  But VPN via dial-up will be painfully slow. 
    Hope this at least gives you some ideas. 
    -Khalid

  • Lookout network

    I have a consultation, I have a server with Windows 2003 which runs 6 Lookout and one PC with Windows XP with LK6, but as when loading the PC with Windows XP becomes slow, decidi to leave the one that has the 2003 is the one who keeps the data base, but when wanting to ploting by means of the Hypertrend in the PC with Windows XP does not display nothing, desire to know if somebody can help me in this problem.  Thanks.

    Vlady_1, how are you doing today? I hope all is well. I know that there were some issues with Lookout 6.0 and here is some information that might help.
    http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BE60070823B?opendocument&node=1...
    Also, we did not test Lookout with Windows 2003, so technically we cannot support it if you have major compliance issues. In any case, here is a thread that might also help. A customer said he was using Lookout 6.0.2 and had not experienced and MAJOR problems. So that might be something you want to try.
    http://forums.ni.com/ni/board/message?board.id=190&message.id=3393&requireLogin=False
    Thanks a lot.
    Live, Learn, Love, and Share the knowledge
    Efosa O.

  • Modbus?? Is running to slow to process

    I am running lookout 6.6 on Dell Precision T3600 Windows 7 Pro. 64 bit 8 RAM workstation the problem is on Process_Server\Modbus?? Is running to slow to process it takes mins to load.. Is it the program issue or system?

    I have noticed delays if there is a large amount of dynamic symblic links.  Is this the case?
    Forshock - Consult.Develop.Solve.

  • Lookout 6.2, Citadel Crash

    Ok, beating a dead horse... I think we are definitely getting to the end of our NI lifespan
    Background
    System installed with Lookout 6.1 in 2008, ran well for about 1.5 years.  Random crashes, database corruption, etc. Initially believed to have been the machine (Software RAID 5 sucks).  New machine built in Oct. 2010; no RAID, Intel Core2 machine, XP SP3.  Upgraded to Lookout 6.2.  Could not import the 6.1 database, performance slowed to a crawl, believed to be from a corrupt database.  Created a new database.  
    Today
    Machine is experiencing system failures on Citadel and Lookout. We have nothing but AlarmDialer 4 (custom notification software), RealVNC Enterprise, Lookout 6.2, HP Printer and standard system related tools (TrueImage, AVG, Adobe Reader (Latest version, for manuals)) installed on this machine.  All updates installed.  
    Latest Windows Mini-dumps: http://support.forshock.com/files/MRCWD/Minidump.zip
    Latest (related) error messages:
    Event Type: Error
    Event Source: SQLBrowser
    Event Category: None
    Event ID: 1
    Date: 12/21/2010
    Time: 5:27:46 PM
    User: N/A
    Computer: SCADA
    Description:
    The SQL configuration for SQL is inaccessible or invalid.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 4d 00 53 00 53 00 51 00   M.S.S.Q.
    0008: 4c 00 53 00 65 00 72 00   L.S.e.r.
    0010: 76 00 65 00 72 00 5c 00   v.e.r.\.
    0018: 43 00 75 00 72 00 72 00   C.u.r.r.
    0020: 65 00 6e 00 74 00 56 00   e.n.t.V.
    0028: 65 00 72 00 73 00 69 00   e.r.s.i.
    0030: 6f 00 6e 00 00 00         o.n...  
    Event Type: ErrorEvent Source: SQLBrowserEvent Category: NoneEvent ID: 1Date: 12/21/2010Time: 5:27:46 PMUser: N/AComputer: SCADADescription:The SQL configuration for SQL is inaccessible or invalid.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.Data:0000: 4d 00 53 00 53 00 51 00   M.S.S.Q.0008: 4c 00 53 00 65 00 72 00   L.S.e.r.0010: 76 00 65 00 72 00 5c 00   v.e.r.\.0018: 43 00 75 00 72 00 72 00   C.u.r.r.0020: 65 00 6e 00 74 00 56 00   e.n.t.V.0028: 65 00 72 00 73 00 69 00   e.r.s.i.0030: 6f 00 6e 00 00 00         o.n...  
    Event Type: Information
    Event Source: MSSQL$CITADEL
    Event Category: (2)
    Event ID: 26037
    Date: 12/21/2010
    Time: 10:01:26 AM
    User: N/A
    Computer: SCADA
    Description:
    The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: b5 65 00 00 0a 00 00 00   µe......
    0008: 0e 00 00 00 53 00 43 00   ....S.C.
    0010: 41 00 44 00 41 00 5c 00   A.D.A.\.
    0018: 43 00 49 00 54 00 41 00   C.I.T.A.
    0020: 44 00 45 00 4c 00 00 00   D.E.L...
    0028: 00 00 00 00               ....    
    We get lots of these entries:
    Event Type: Information
    Event Source: MSSQL$CITADEL
    Event Category: (2)
    Event ID: 17401
    Date: 12/21/2010
    Time: 1:44:58 PM
    User: N/A
    Computer: SCADA
    Description:
    Server resumed execution after being idle 10079 seconds: user activity awakened the server. This is an informational message only. No user action is required.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: f9 43 00 00 0a 00 00 00   ùC......
    0008: 0e 00 00 00 53 00 43 00   ....S.C.
    0010: 41 00 44 00 41 00 5c 00   A.D.A.\.
    0018: 43 00 49 00 54 00 41 00   C.I.T.A.
    0020: 44 00 45 00 4c 00 00 00   D.E.L...
    0028: 00 00 00 00               ....    
    Event Type: Error
    Event Source: Application Error
    Event Category: None
    Event ID: 1000
    Date: 12/22/2010
    Time: 7:29:18 AM
    User: N/A
    Computer: SCADA
    Description:
    Faulting application lookout.exe, version 6.2.0.49153, faulting module nicitmid.dll, version 5.6.0.49153, fault address 0x00069ffb.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 70 70 6c 69 63 61 74   Applicat
    0008: 69 6f 6e 20 46 61 69 6c   ion Fail
    0010: 75 72 65 20 20 6c 6f 6f   ure  loo
    0018: 6b 6f 75 74 2e 65 78 65   kout.exe
    0020: 20 36 2e 32 2e 30 2e 34    6.2.0.4
    0028: 39 31 35 33 20 69 6e 20   9153 in 
    0030: 6e 69 63 69 74 6d 69 64   nicitmid
    0038: 2e 64 6c 6c 20 35 2e 36   .dll 5.6
    0040: 2e 30 2e 34 39 31 35 33   .0.49153
    0048: 20 61 74 20 6f 66 66 73    at offs
    0050: 65 74 20 30 30 30 36 39   et 00069
    0058: 66 66 62 0d 0a            ffb..   
    Event Type: Error
    Event Source: System Error
    Event Category: (102)
    Event ID: 1003
    Date: 12/21/2010
    Time: 5:28:15 PM
    User: N/A
    Computer: SCADA
    Description:
    Error code 00000024, parameter1 001902fe, parameter2 b9cebbbc, parameter3 b9ceb8b8, parameter4 b965a667.
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 53 79 73 74 65 6d 20 45   System E
    0008: 72 72 6f 72 20 20 45 72   rror  Er
    0010: 72 6f 72 20 63 6f 64 65   ror code
    0018: 20 30 30 30 30 30 30 32    0000002
    0020: 34 20 20 50 61 72 61 6d   4  Param
    0028: 65 74 65 72 73 20 30 30   eters 00
    0030: 31 39 30 32 66 65 2c 20   1902fe, 
    0038: 62 39 63 65 62 62 62 63   b9cebbbc
    0040: 2c 20 62 39 63 65 62 38   , b9ceb8
    0048: 62 38 2c 20 62 39 36 35   b8, b965
    0050: 61 36 36 37               a667    
    Forshock - Consult.Develop.Solve.

    Year later.  We have a system with approximately 8.05GB in citadel.  System shutdown, restart.  Database is now taking over 1 hour to "rebuild" and is not complete.  Secondary has 7.99GB, same issue.
    Processes will not function, system is sluggish, basically useless.
    Long live Citadel... 
    Forshock - Consult.Develop.Solve.

  • Lookout 6 Hiccups

    Sorry, this is a bit long winded....
    I seem to have found the case of some of our hiccups with Lookout 6.0. We had been having problems with client workstations and extremely slow or now historical data trending on their clients. I had checked many things, including rebuilding the server and client processes, using ActiveX Trend vs. Lookout Trend and visa-versa, we used both an upgraded database and new database from scratch, etc.... I had spoken with support numerous times and they all had me trying different fixes.
    NOTE:
    Client Computers Discussed are Windows XP Professional SP2
    Server Computer is a Windows 2003 Server Machine
    One of our new client computers would not update historical trends at all, live data was fine, it would read that data and you could see it updating, but any historical trending would not work at all. I noticed that there is a new folder structure under the following (this will vary depending on your server computer's name and your server's database you are connecting to) "C:\Program Files\National Instruments\Shared\Citadel\_LocalCache\_monet_\_c__program_files_national_instruments_lookout_6_0_database_". I noticed that on machines that were trending historical data properly (or at least as properly as they could be, still slower then 5.0), there were files in this directory that seemed to be duplicating the database file structure on the server's machine, on the machine not trending, there were no files or just a log file (don't really remember). This raised my question about how the server and client communicate when using trends, I never got a straight answer from support, except to say that they talked to R&D and supposedly this folder has nothing to do with the historical trending on the client computer.
    ***HOWEVER***
    During a recent non-related software upgrade, we found an issue with user rights assignments on Windows XP Professional workstations where for some reason, if a user was part of more then one group and they were a part of the "USERS" group, they would receive restricted access on the local computer even if they were a part of "POWER USERS" or "ADMINISTRATORS". We ended up having to make users part of the "POWER USERS" group only, to solve the unrelated problem. After doing this, the user with the non-functioning client noticed that the trends started updating on his computer.....and low and behold, there is now over 200MB of data in that cache folder, something tells me that the cache folder just might have something to do with the historical trending on 6.0 client computers. Hopefully at some point this post will either give someone some insight to a similar problem or at least any other database related issues they may be having with Lookout 6.0......or at least amuse someone.
    If this all sounds a little sarcastic, it probably is....
    Don't get me too wrong here, I do appreciate the new functionality provided with 6.0 and the new Citadel 5.0 database structure, but I think there are some serious inefficiencies in how the database functions and it seems like there is a major lack in documentation and knowledge on how it operates in the background.

    fixthis,
    I am unclear on what exactly you are seeing.  "hypertrend chart updates, but the signals do not always appear."  Do you mean the chart keeps scrolling, but the signals disappear?  When you say "data window that pops up for the hypertrend does not update the data while moving the cursor across the hypertrend chart." I assume you are referring to the cursor data window -- what method are you using to move the cursor -- by clicking the arrows on the Hypertrend, by clicking on the cursor itself and moving it, by clicking the arrows in the Cursor data window, or by manually changing the time in the Cursor data window, either by using the arrows or typing a new time in?
    Does this happen with both the Lookout Hypertrend and the NI ActiveX Hypertrend object?  Does it happen when only one trace is on the Hypertrend or only with a larger number of traces?
    We are very interested in knowing about Hypertrend/Citadel issues customers are experiencing, but unless we can reproduce the issue or have a very clear understanding of what is going on, it is very difficult to determine what the cause is or any possible fixes -- is it possible for you to post screen shots, and a very simple process file that will reproduce this problem?
    Doug M
    Applications Engineer
    National Instruments
    For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

  • Copying Lookout Objects

    Is there any way to copy Lookout "Expression" and "Average" objects using
    the keyboard shortcuts (i.e. "CTL-C") or with the mouse?. I can
    successfully copy objects such as "Gauges" and "Pots" and Lookout creates a
    new object with a number appended to the end of the original name. If I try
    to do the same thing with the expression it just creates a linked copy of
    the same object. I have many expressions that are practically identical
    except for the name and the source and I have to do "Object >> Create..."
    every time! This is REALLY slowing down my development.
    Geoffrey B. Klotz
    GK Associates, Inc.
    TEL: (805) 523-8700
    FAX: (805) 523-1216
    EMAIL: [email protected]

    Thanks for the suggestions. Editing the .lks file seems to work great. I
    figured out that when you are finished editing the source that you have to
    recompile manually. Maybe on a future release of Lookout, NI can include a
    text editor for manipulating the source code similar to some of the HTML
    editors like MS FrontPage.
    One other suggestion is adding a feature to the "alignment" commands that
    will make all highlighted display boxes equal in dimension. The most time
    consuming part of creating a user panel right now is manually manipulating
    each gauge object with the mouse and trying to match the size of previously
    created display objects.
    All in all, a nice product. Thanks again.
    Geoffrey B. Klotz
    GK Associates, Inc.
    TEL: (805) 523-8700
    FAX: (805) 523-1216
    EMAIL: [email protected]
    Guy McDonnell wrote in message
    news:[email protected]..
    > One approach, though it can be perilous, is to manualy edit the .lks file
    > with a basic text editor that does not force hidden character such as eol.
    > This approach allows the copy paste option you reference. I usually use
    the
    > editor with my C compiler but notepad will also work.
    >
    >
    > "newsgroups.ni.com" wrote in message
    > news:[email protected]..
    > > Is there any way to copy Lookout "Expression" and "Average" objects
    using
    > > the keyboard shortcuts (i.e. "CTL-C") or with the mouse?. I can
    > > successfully copy objects such as "Gauges" and "Pots" and Lookout
    creates
    > a
    > > new object with a number appended to the end of the original name. If I
    > try
    > > to do the same thing with the expression it just creates a linked copy
    of
    > > the same object. I have many expressions that are practically identical
    > > except for the name and the source and I have to do "Object >>
    Create..."
    > > every time! This is REALLY slowing down my development.
    > >
    > > --
    > > Geoffrey B. Klotz
    > > GK Associates, Inc.
    > > TEL: (805) 523-8700
    > > FAX: (805) 523-1216
    > > EMAIL: [email protected]
    > >
    > >
    > >
    >
    >

  • What is causing Lookout to Lock-Up

    I am running Lookout V6.6 on an HP desktop computer with Windows 7 64-bit OS.  Lookout is running in XP mode.  We are experiencing increasing frequency of the Lookout application locking-up.  Yes, not much of a SCADA system when this happens.  The OS System Manager shows Lookout "Not responding" and I have to reboot the computer before Lookout will operate again.
    This is a simple SCADA system controlling two well sites with lead and lag pumps at both sites.  It seems that lockups may occur more frequently when two pumps are being turned off near simultaneously.  The computer uses a serial connection to a Zetron Controller talking to two Zetron RTU's in the field.

    Not running 6.6 here regularly so can only recommend on my own observations.
    Symbolic links that user a dynamic connection can cause a slow down when starting, especially if the link connects to another object that may use a symbolic link itself.
    Customer drivers (CBX) and ActiveX controls can cause issues.
    Forshock - Consult.Develop.Solve.

  • Lookout remote object behavior

    I want to know if there is a better solution to remote an object in a server
    process than the one I had to use. Let's suppose I have a PotA in a server
    process that have his value property connected to an expression or to
    another object (let' say it PotA Input Connection). Also, the value property
    of PotA serves as origin to the value property of another object (PotA
    Output Connection). If I had to control this PotA object from a client
    process with a remote source url, Lookout says "the remote object is not
    writable". This leaves the remote connection as unidirectional.
    To solve this I must to connect the value of the remote pot (RemotePotA) to
    the value of PotA in the server process, but also I had to connect the value
    property of PotA to the value property in the client process, sharing the
    value expression with the one if have previously. At this moment, I have
    lost the client process machine independence, because the server process is
    now locked to an specific client. Wrong way.
    But I have another way to do it, that seems to me a way to fool Lookout
    read-only check of objects. In the server process I create PotA as described
    before, and PotB. I set the remote property of PotA to PotB in the same
    server process. And voil�, I can use the remote property of RemotePotA in
    the client to connect to PotB in the server process.
    I had to do this for a great number of objects in a project (around 100) and
    now I've noticed that this slows the Lookout application a lot, specially
    the screen refresh, but I'm not sure if is this behavior is the origin of
    the decreased speed.
    Well, about this I have three questions:
    1) This way to construct remoted object is correct?. There is no unexpected
    event loopings?
    2) If the contruct is correct, why Lookout not let to remote directly the
    PotA object without all this complications? In fact, I'm modifying a
    property by an indirect method, and if it works why not remove the read-only
    checking?
    3) If the construct generates unexpected events and it's an undesirable way
    to do this, how can I remote a Pot which have a value property connected to
    an expression or another object to control it from a client process?
    Maybe anyone can give me some light about this question...
    Thanks
    Joaquin Villanueva
    T-Systems

    First of all, I am having some trouble following your explanation, but I think I have a general idea. Any time you use a connection it is a one way street as you found out, you should use the URL. Even though both pots are local, you can make pot B the URL in pot A's object properties and leave pot B as local control. This allows two way data transfer. I hope this helps, but if it doesn't let me know.

  • Application running slow in ver 1.5, 1.6 but not in 1.4

    We have a application that was running very slow when we used any version sun java instead of MS java in IE6 SP2.
    I removed MS Java from IE and installed Sun java 1.4.2_16 and the applications starts in under 10sec's.
    But we had to test the other version of java as well, i then installed the other versions from 1.5 update 14 to 1.6 update 4 and the application takes about 30 to 40 sec to load the web page.
    I then looked at the development version of java 1.6 update 10 and version 7. In 1.6 update 10 the application would load but would not refresh the applets it would just hang. In version 7 the application would not start up at all.
    In all the versions i increased the memory parmeters from 128 to 256 and in version 1.6 i changed it to -Xmx300m as well but still the application was slow loading. Removed all the versions and reinstalled 1.4.2_14 and the application works fine and loads up under 10 sec.
    Does any one have any idea why this is happening.
    IE 6 sp2
    XP sp2 been used.

    You should try profiling the startup code.
    As a first go around, you might try getting a stack trace during the startup process and look for locks (see jstack).
    If your application is built on Swing, it's my understanding that the later versions of Java are more strict about use of the Event Dispatch Thread--pay particular attention to activity off the EDT locking the thread.

Maybe you are looking for