single triggered acquisition on scope timeout problems

Similar Questions

• Acquisition of IMAQdx - synchronization problems

  Hi all

  I built a code a VI in which I put in place a camera IMAQdx acquisition in a loop of producer-consumer (see attached VI). The code also controls the camera exposure time.

  I would like to record images at 10 frames per second, the camera is set up to acquire NI Max 10 fps, but surprisingly, the code saves more than 10 frames per second, even if I inserted a synchronization feature in the loop of the producer.

  Any ideas on what does not work?

  Thank you.

  Kind regards

  E.S.

  There are three modes of acquisition of the camera: Snap, sequence and Grab based on parameters that you set:

  Wink (single image acquisition): continuous = 0; Buffer Count = 1

  Sequence (fixed number of frames): continuous = 0; County of buffer > 1

  Enter (Continuous Acquisition): Continuous = 1; County of buffer > 1

  - So I guess you want continuous acquisition, which means that you must set the buffer has more than 1 (usually more than 3) that the driver uses internally to avoid overwriting images.

  -You can check The Grab and configuration example VI attributes that lets the user view the current attributes and settings, update the attribute parameters, acquire images continuously and display images in an image control.

  -From the example above, you can also see the framerate that acquire and then proceed to the backup of images.

  -To access the example help-> find examples--> search for Grab.

• com.adobe.livecycle.generatepdf.client.GeneratePdfServiceClient Timeout problem

  We have an obligation to convert large tiff files full text PDF. I use the following code to convert files of small size, but with a large file, I see a timeout problem.

  ALC-CEO-10010-000: com.adobe.livecycle.generatepdf.client.ConversionException: ALC-CEO-010-010-The conversion has expired.

  User must have administrator privileges. Looks like some privileges are missing.

  -Wasil

• Encoder triggered Acquisition (Single Channel N samples)

  Hello Internets,

  I am an inexperienced user of LabVIEW, I'm trying to set up a system in which blood samples are taken when triggered by a digital pulse.

  I'm sampling using a PCI-6250. I have an updated encoder in place that emits a digital pulse once per turn. I would possibly take about 1000 samples in a very short time triggered by this time by pulse rev.

  The problem I have right now is that I seem to get a lot less reading I expect otherwise, the LabVIEW program, I'm running also takes a long time to stop following my pressing the stop button.

  The table fills also in a way that is strange to me, perhaps someone could it explain?

  Thanks, any help would be greatly appreciated!

  Hi Relaxidermist,

  There are a few things in your current code that seems contrary to your goal:

  "I would possibly take about 1000 samples in a very short time triggered by this time by pulse rev."

  Assuming that you want to read 1000 samples for each received external trigger and you have several triggers coming, I would start by this example:

  Redeclenchables analog input finished using digital triggering

  I'll be the first to admit that he is not the most intuitive - on the M-series (like your 6250), use a meter to output to an acquisition really triggered.  You could rearm task in the software, but this takes time and is prone to triggering signals are missing.

  If you were on a series of X (63xx devices), the code you have is close, but you must make the following changes:

  (1) use the clock embedded to your example of clock instead of the external signal for PPR source.

  (2) make the task finished instead of continuous.

  (3) enable the redeclenchables property - it is not available on your device of the M series (where workaround posted above).

  Best regards

• Gateway Timeout problem

  With the help of a MacBook Pro 13' (mid-2012) El Capitan (Version 10.11.1). running

  Usually living abroad, came home last night and managed to connect my computer to the internet WiFi and my parents very well. Could access any Web site, ran perfectly. This morning I started having a problem where I can open only a small number of websites (Facebook, Youtube, Google, Apple, Wikipedia), another Web site gives me a ' Gateway Timeout: unable to connect to the remote host " message, even large reputable (NYT, etc.)."

  Here are the facts:

  • MacBook connects to the WiFi
  • MacBook restarted, the problem persisted
  • Reset the router (FRITZ!) 6360 Box cable, German provider is Unitymedia)-online everything has worked again for about 2 minutes, and then the problem comes back
  • All other computers/phones in the House has no problem, can access any Web site
  • Connected my MacBook to the Ether, has worked well. Yet once unplugged and tried WiFi problem returned. Ethernet plugged back in (with WiFi off), now, even the ethernet gives me the same problem
  • Software antiVirus Sophos's active and firewall settings and Web Protection were not yet activated (no idea why)
  • First time this question has occurred (connected to this dozens of times network and worked very well, but with the Mavericks) and has produced at night - everything worked fine yesterday and I am not aware of having made changes to anything.

  Found a thread with a person having a similar problem on another forum of support, but in his case, all its devices had the question so that, in our House, everything works but my MacBook. So I doubt that it is a problem with the provider or router.

  Any help would be greatly appreciated!

  AntiVirus software is Sophos.

  Uninstall completely and evaluate the results.

  Use the Remove Sophos Anti-virus program. It will be installed in the folder Applications on your Mac, unless you have moved or deleted. In this case, follow the instructions in uninstalling here: https://www.sophos.com/support/knowledgebase/122710.aspx. Beware that the effectiveness of the uninstall program is poor, a typical feature of garbage software.

• Generation of data and acquisition of high frequency problem

  The fitting requires a fishing signal (32,764 KHz) saw tooth (0.3 Hz) signal output to drive the laser and acquires the signal from the output of the detector. I use the NI USB-6356 data acquisition with the speed limit of 1.25 MECH. / s.

  I put the generation mode like "Samples continues", samples of writing/reading of 1.2 M and 500K (Hz) frequency in the DAQ Assistant. I also tried 500K and 500K.

  The scheme of vi is illustrated in the following figure.

  

  Of the front plate, the generation of signal is normal, which may be seen in the left side of the following figure. But signals a lot of periodic fluctuations that will appear if the right side of the figure. In addition, the siganl acquist go all the time.

  

  I think it's maybe a few errors with my setting of the sampling frequency, I tried a lot of time for a change of pace, but it seems unnecessary.

  These fluctuations exist not only in the growing period but alos can be seen in the declining period, which is shown in the following figure:

  

  I tried to solve this problem for almost a week and try a lot of different rate, but all fail.

  Could someone give me any suggestions please? Thank you very much!!

  Thanks SOSOSO much for your reply immediately every time!

  This is my first time to write the Labview program with data acquisition

  The attachment is the field of Vi.

  I'll read the Web page that you offer, thank you very much once again!

• TCP timeout problems

  Hello

  Request: I'm using LabVIEW 8.2 to connect with a RFID reader.

  I connect to the player via TCP and write (write block TCP) a number of orders (connection, system of game settings, player tags list queries), and my VI works smoothly, with one exception: since I don't know how many tags in advance will be near the read drive ability, I have no method to measure the length of the data back (the block of reading TCP bytes to read).

  To break down the problem, I can either read a very small number of bytes and avoid a time-out error 56, losing some data back in the process, or I can allow the system to timeout, read a large number of bytes and allowing every step of execution take time designated in the time-out period rather than the amount of time it takes indeed for the reader to respond.

  My question, simplified: is there a way I can use the TCP protocol to read only the data that is sent (rather not specify the number of bytes that will be read, which allows the VI to make when no additional data is available)?

  Thank you in advance.

  As far as I know, there is no way to check the amount of data it is in advance. Some protocols have a predefined byte quantity, or send a message by sending the length of the message, for you first read and know how many bytes you need.

  If you can not do that, what you want to do is call reading TCP primitive in a while loop until you get an error in time-out and the warp threads in a tunnel of automatic indexing output. You can then wire the string array resulting 1 d in the string concatenate primitive to convert it to a string. In this way, you can use a short timeout and read a small number of bytes for each reading without loss of information.

• Acquisition of vision create problems with webcam

  Hi, I installed a trial version of the software Vision Acquisition as well as the Vision Assistant. The problem is that after installing NIs USB plug in camera http://zone.ni.com/devzone/cda/epd/p/id/5030 it takes a photo once, but that it does not detect the camera and not only that, the camera is not detected by my laptop. I'm using LabVIEW 8.6 with Windows 7 on a Compaq Presario V3000 laptop.

  wond3rboy wrote:

  Hi, thanks for your response. Can I use Vision Acquisition 2009 with LabVIEW 8.6?

  Yes, seems you can:

  http://digital.NI.com/public.nsf/allkb/6B55FF09D1FBD3108625719600650B7C

  http://digital.NI.com/public.nsf/allkb/244E6DDF9A92A6CD8625730100629047

  Andrey.

• Timeout problems

  Dear friends, I am working on a motor controller application that uses state machines to plan tasks to accomplish. I need to order 2 motors and each is managed by a state machine. These state machines have been transformed into a sub VI, once they have exactly the same functionality. Everything works perfectly, except by the fact that, for some reason I don't understand, a machine behaviors differently from the other folder.

  To make things clearer, we will appoint an engine as the engine of X and the other as an engine of Y.

  I used 'Elapsed time' live to build structures of timeout in the state machine. Motor x laws of State machine as expected, but Y it is unclear just of delays implemented. Two of them being the same under VI, I don't see any way they could present different results when they are subject to the same conditions.

  It is important to say that these screws of State machine share a resource VISA RS232. In VI sup, I used an input and output connector so the line VISA can be connected to the first VI and it will output goes directly to the entrance of the second.

  I noticed that changing the operating system stopped the screws changes witch VI ignores the timeout. The second VI is always the problem. I could clearly understand there's a delay time between the execution of the first machine of the State and the second, once there is a shared resource. But it does not seem normal to have a specific timeout ignored.

  I hope someone could help me with that.

  Thank you very much

  Leonardo

  Is that the Subvi execution is set to 'Reenterant '?  If this is the the second call will wait until the end of the first run.  Go to file-> properties VI, select the performance tab, and check the "re-entrant execution."  This clones different VI instances when it is called

• Internet a serious - unable to connect to any site problems, timeout problem

  Hello

  I am facing a problem when I am trying to connect to the internet, the problem is that I am getting timeout error.
  When I see the State it shows me

  Envoy: 193448 received: 123

  The problem is that I can see the bytes sent fom my computer at the rate so high that it is not allowing me to receive whatever it is... It seems to me is perhaps a kind of Virus that blocks the incoming packets and also stifles internet sending of junk (not sure what). I checked the Task Manager and I see 99% the system idle process.

  Help me what shd I do?

  Hi Abhishek,

  ·         Do you use Internet Explorer to browse the web?

  ·         What is the exact message that you receive?

  Method 1: I see you have another thread posted about the infection by the virus. I suggest that you run the scan as suggested and see if it helps.

  Method 2: Run the Fixit tool in the following article to check the issue.

  Internet Explorer error "connection timed out" when server does not

• EA6900 DHCP timeout problem

  This is by far the stronger and more sophisticated wireless router that I have ever used, but it has a small problem in providing wireless services on my phone.  I looked through all the settings and read all the troubleshooting assistance, and I can't find which could control the router sending a momentary power switch pulse exactly all the 60 minutes that is picked up by one of my Apps (AutomateItPro) phone...

  I have had no problem affecting this router upward, mosty plain vanilla right out of the box.  Because I use a cable broadband ISP (Charter) I use DHCP - so I don't get in other internet protocoal settings that control "Connect on Demand", etc..  Nor was I changed the default maximum, length of lease of customer value in the configuration of the router, it's always 1440 minutes (24 hours).

  This app on my phone has the value triggers a notification when I disconnect all WiFi (this router provides my WiFi at home but I have the app to the WiFi network of any) and activate the mobile data and vice versa with a different tone.  With precision every 60 minutes since I have hard reset the router (with an unplugged power cable), I get a notification of your momentary loss of WiFi follwed in 2 seconds by restoring the WiFi.  I tried a hard reset twice and it is a signal on the router, not the app, or my phone.  The problem is that this continues to happen at night when I am sleeping, and this powerful application overrides my silent nights for the phone settings, so I can still hear him.

  What is the setting that does this on the router, and it is possible to prevent him from doing this (emission of the momentary power pulse of the wireless signal)?  I haven't checked if it is a reassignment of IP addresses at this time also...  I really like this router, but being awake is a pain...  (Yes there are other solutions of circumvention of the APP, but those who are not as reliable I found like stop this problem at the source of the router if possible.)

  Thanks from a newbie!

  Hey Ronald,.

  I used to have the same problem.

  The way I fixed it changed the name of one of my networks.

  This router is dual band and has a band of 5 GHz and 2.4 GHz band.

  I had both my SSID network named the same thing with the same password.  For a reason which is that... my connection would constantly.  After changing the name and password of one of the bands I have over this problem.

  Hope that helps Ronald.

  I know it's really annoying.

• At the request of application scope of problem.

  Hi, I am trying to use the PL/JSON package on my apex application. It has been installed and configured for access public (it may be necessary in different patterns on the DB, in addition to the apex) with this command:

  --types
grant execute on json to public;
create or replace public synonym json for json;
grant execute on json_list to public;
create or replace public synonym json_list for json_list;
grant execute on json_value to public;
create or replace public synonym json_value for json_value;
grant execute on json_value_array to public;
create or replace public synonym json_value_array for json_value_array;
--packages
grant execute on json_ext to public;
create or replace public synonym json_ext for json_ext;
grant execute on json_parser to public;
create or replace public synonym json_parser for json_parser;
grant execute on json_printer to public;
create or replace public synonym json_printer for json_printer;

  And tested with this example from github site:

  declare
  obj json;
begin
  obj := json('{"a": true }');
  obj.print;
  --more complex json:
  obj := json('
{
  "a": null,
  "b": 12.243,
  "c": 2e-3,
  "d": [true, false, "abdc", [1,2,3]],
  "e": [3, {"e2":3}],
  "f": {
  "f2":true
  }
}');
  obj.print;
  obj.print(false); --compact way
end;

  Now, if I run this script on the console to a different schema, it works fine. If I run it from the console SQL Workshop on the apex of the IDE (such as apex_public_user) works fine too, but if I create an Application process run on demand (which runs as apex_public_user), with the same code and then call the process of javascript like this:

  var get = new htmldb_Get(null,$v('pFlowId'),'APPLICATION_PROCESS=P4_JSON_TEST',0); 
  alert(get.get());
  
  

  Just to see the result. And all that I get an exception was thrown:

  ORA-06550: line 19, column 13: 
  PLS-00222: no function with name 'PRINT' exists in this scope 
  ORA-06550: line 19, column 5: 
  PL/SQL: Statement ignored
  
  

  The strange thing is that the exception, it is not been lifted by the declaration of the json object, nor the instantiation, but by printing called function. Which brings back me to my question: who is part of a process of application on request? (or what I'm doing wrong).

  Database version:

  • Oracle Database 11 g Release 11.2.0.4.0 - 64 bit Production

  Apex version:

  • Oracle Application Express 4.2

  Thank you for your time.

  Hi DelayLama,

  DelayLama wrote:

  Hi @Kiran, thanks for the reply, actually I did what recommended you, I copy the example on the web page and I forgot to add the changes, this is the actual code:

  1. declare
  2. JSON obj;
  3. Start
  4. obj: = json ("{"a": true}");
  5. obj. Print;
  6. -more complex json:
  7. obj: = json (')
  8. {
  9. 'a': null,
  10. 'b': 12.243,.
  11. 'c': 2-3.
  12. "d": [true, false, 'abdc', [1,2,3]],.
  13. « e » : [3, {« e2 » : 3}],
  14. "f": {
  15. "f2": true
  16. }
  17. }');
  18. HTP. PRN (obj. Print (false)); -way compact
  19. end;

  Also, I tried what @Edwin suggested, but the problem persists.

  The obj.print returns a string? I doubt it because it is a wrapper for dbms_output. I think that, as obj.print is scheduled to run only in kind of SQL Developer more/SQL environments.

  In the context of Oracle APEX, you write a process on demand Application and he expects you to return a string. Try the simple example to build the string json in a variable and return that, mentioned above and let me know if it works.

  Kind regards

  Kiran

• exercise of the VM session timeout problem

  Hello

  First off all I want to thank all those who contribute on this post, I have a 5.0 vcenter and vmware view running 5 customer, the problem is that on my infrastructure vm´s of users sessions go on the time-out for the most part after 7 or 8 hours of active session is probably for security reasons , I want to turn off this option, but don t know where to find the settings for it on my vcenter, due anyone know how to disable this feature?

  Best regards!

  I am a beginner on vmware view, but I'm trying to help you.

  Most common session is disconnected as a result the VMware View connection Server Session timeout.  This global setting disconnects the sessions after the time-out expires. The default setting is 600 minutes (10 hours).

  To avoid these disconnects, educate users that there is an automatic session expiration time or increase the value of timeout in minutes via the view connection server > view Configuration > global settings and enter the time in the dialog box Session timeout.

  Remember points of certification for responses 'useful' and / or 'correct '.

  -------------

  Bil Bens

• weird http timeout problem

  OK, maybe not weird, but weird. It's WL7sp7.
  
  In the std newspapers in our production environment, we see the following message "the server could not send the HTTP message during the timeout value configured. The socket has been closed. ». You can see this message only to a second interval specific than a minute... that is, in the log below, extract as the second "33" (11: 52:33, 11:55:33, 12:11:33, etc..). After a reboot, we will see only this message to the second "21" (15: 13:21, 3:21:21 PM PST, etc.).
  
  The problem, it is a DOTNET fact http post for this app WL application... If the messages at the wrong time DOTNET application (e.. g, to the second '33' minute) the http post fails. The DOTNET application logs the remote server took of disconnection. If you look at the logs to stdout for the same time, we see the connection timeout message. The post and the response would only last a second or two and little almost always succeeds wait for these applications, which falls on the 'bad' (milli?) second of the minute.
  
  I don't know if I've explained clearly this strange phenomenon. If this is not the case, let me know. An excerpt from our newspapers std:
  
  

  grep /tmp/WLPRODSVR04-stdout.log "the server could not send the HTTP message"

  # < 5 November 2008 11:52:33 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '2' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 11:55:33 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '20' to the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 12:11:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 12:34:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '4' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 12:42:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '2' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 12:53:34 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 12:57:34 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  ....
  [reboot]
  .....
  # < 5 November 2008 3:13:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 3:21:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 3:29:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 3:30:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 3:38:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 5 November 2008 16:30:21 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 16:41:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '27' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 17:56:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 18:01:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 18:08:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 18:55:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 19:11:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 19:50:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 8:00:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 8:07:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 8:20:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 9:15:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '25' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 9:34:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 9:41:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 10:14:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 10:17:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 10:24:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 10:38:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 11:04:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '25' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 11:09:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 11:28:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 11:49:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 12:20:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 12:47:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '20' to the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 12:56:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 1:10:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 1:18:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 3:29:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 6 November 2008 16:19:21 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 5:23:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 17:59:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 18:31:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 6:51:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 19:24:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 19:31:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 19:41:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 8:00:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 8:21:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 8:47:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 9:15:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 9:20:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 9:34:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 10:06:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 10:12:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 10:54:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 11:05:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 11:12:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 11:28:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '27' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  ....
  [reboot]
  .....
  # < 7 November 2008 12:24:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 12:31:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "14" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 12:31:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "14" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 12:35:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '16' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 1:14:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '17' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 1:15:09 pm PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '10' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 1:32:10 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '19' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 2:03:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '15' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 2:12:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '11' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 2:12:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '11' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 2:24:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
  # < 7 November 2008 3:39:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >

  Its a known problem with WLS 7.0 SP7 (CR300032 and CR196369) associated with CompleteHTTPMessageTimeout. WebLogic Server closes a connection intermittently while responding to the slow clients. If you have a support contract, you can open a service request and download the patch and details of the Czech Republic.

• Toshiba 48L1433DB - USB timeout problems

  My USB Ports do not appear on my list of Source and I have a problem of "dead time".

  If I put a stick in the media page loading USB ports and everything works perfectly, but then turns off after an hour or two (the on-screen message shows empty port lit).

  Then I have to unplug the stick and reload until I can start watching again (have to fast forward to place where disconnect happened but have to stop every now and then to avoid time re-product)

  Very curious

  Posted by [email protected]
  

  My USB Ports do not appear on my list of Source and I have a problem of "dead time".

  If I put a stick in the media page loading USB ports and everything works perfectly, but then turns off after an hour or two (the on-screen message shows empty port lit).

  Then I have to unplug the stick and reload until I can start watching again (have to fast forward to place where disconnect happened but have to stop every now and then to avoid time re-product)

  Very curious

  As a first step, you must make sure, that it is not caused by the type format and/or stick file.
  Have you checked with a stick from another provider? Also, does come with any type of file, or related to some formats?