Import-TIME timeout problem

Similar Questions

• Use several of DV Panasonic NV-DS60 11 imported elements without problems.

  Use several of DV Panasonic NV-DS60 11 imported elements without problems.

  Now using elements 14 but this program does not SEE the camera.

  Why not 14 sees the camera and how can I fix this problem?

  joudar

  It's not Adobe, instead essentially a user to user forum. I saw the first 14 supported Import Formats of video clips list. My first impression is as follows. DV-stream (.dv) here does not refer to the ability of Premiere Elements to capture DV data using a firewire connection in Premiere Elements.

  It is my understanding that the raw DV via firewire can be stored in a file with a .dv file extension. You also have these same raw DV data via firewire can be stored in container (Windows) .avi or .mov (Mac). I'd say that Adobe 'Dv-stream (.dv)' refers to the import of a file DV.dv in a Premiere Elements project with add Media/files and folders.

  However, this interpretation reveals a problem because if I take a known Dv.dv file and try to import in first items 14, 13/13.1 on Windows 10 or 7 64-bit, it will not matter and gives the message saying that the file type is not supported or the codec is missing. This same DV.dv reproduces with the VLC Player.

  The frequency of the presence of Adobe in this forum is not defined. But, perhaps personal Adobe or Premiere elements support Team can clarify the inclusion of 'DV-stream (.dv) in its list of supported import Formats. There is certainly no more DV HDV data capture firewire premiere elements Capture window elements first 13/13.1 and 14.

  Will post more information that it will be available.

  RTA

• 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

• 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

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

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

• import time timestamp with timezone data in sql developer

  Hi all

  I'm trying to import a csv file into a table in sql developer, but cannot be granted. The reason is that a column of the csv file contains temporal data in this kind of format

  "2010-10-20 22:00:00 UTC.  I tried timestamp with or without time zone format in sql developer without success. Can someone please point a way to solve the problem?

  Thank you very much in advance.

  You define the format of stamp on this step:

  http://thatjeffsmith.wpengine.com/wp-content/uploads/2012/04/excel_copy9.PNG

  While respecting the advice to bring data from that date as a varchar2 'string' - Please don't do that. Storing dates as strings of dates (or stamps), as strings.

• 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

• Import of sound problems

  I try to import .aiff (22,050 24 bit) in the casting director and Director (12) crashes when imported. I was initially an import batch, but I'm now import one at a time - a couple were imported, but I'll have to force Director quit and try to re - import several times before that I can import a file. Has anyone else had problems to import its under Director 12?

  24 and 32-bit audio are not supported. Try 16-bit:

  http://helpx.Adobe.com/Director/using/publishing-iOS-devices-using-Director.html

• Import Word doc problems 3

  Hi all

  I need to import a word document into indesign cs3 it's 150 pages of time so I need to see if I can fix this problem automatically.

  the document is a series of interviews, so he's followed by issue of response etc.

  questions are in bold in word but not characters in shape somehow. they just used the bold button. [screegrab of the word below]

  I created a paragraph style in indesign, called 'question' that applies color, bold and one space after the adjustment.

  I want to apply the style to each question, but by clicking on each issue in indesign and using my short comand key to apply it would be torture.

  any advice greatly appreciated.

  Thank you, Graham.

  

  Post edited by: graham

  Wow,

  I can answer my own question!

  I am impressed.

  I must thank Bob Levine to help me take a look to find/replace a little closer.

  in InDesign, you need to click your text box, and then choose file > place and place your Word copy.

  then choose Edition > find/replace in the first text tab down is to find and Format change.

  Find the Format you choose, in my case, at the time and "BOLD".

  Change of Format, where you choose your style of paragraph or character, in my case, 'issues '.

  then just hit everything change.

  can I get 10 points for who or what?

  Kind regards, Graham.

• Import Word doc problems 1

  Hello

  I had a bit of a kick to look on the net but I see not expensive plug-ins for this problem.

  I need to import a word document into indesign cs3 which is 150 pages, so I need to see if indesign can automatically create as many pages as necessary during import.

  the only way I know right now is to click on the small box at the bottom right of a text box [which is more red for some reason any] where I stuck all copy, which loads the overflow to the cursor and then navigate to a new page and click in the empty text box [with an Apple + shift key to unlock it from the masterpage] so that the overflow text enters that area and then repeat, repeat, repeat, etc.

  given this is the first time in 9 years or so to use indesign it's a problem for me I don't want to spend $79 and reduce a gain already small.

  Thank you, Graham.

  Shift + click when you place it.

  Bob

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

• Datasource XA - IllegalStateException timeout problems

  WebLogic 10 using a XA (BEA Oracle Driver (Type 4 XA)) data source I have a long running transaction. When you import data from an excel spreadsheet, I have to perform several select to validate the data, and then enter the number of lines for EACH row in the excel worksheet.
  
  I spend half of the excel lines or better everytime, then get the following error.
  
  
  Message: Exception encountered while marking the transaction rollback status [java.lang.IllegalStateException: can't mark the transaction for rollback xid = BEA1-00125574DC1B83308930, status = Rolled back.] [Reason = weblogic.transaction.internal.TimedOutException: Transaction has expired after 31 seconds]
  BEA1-00125574DC1B83308930]]
  
  I tried to put "Set XA Transaction Timeout" = true and 'XA Transaction Timeout' = 1200 on the console for the data source. This does not change things.
  
  Someone at - he seen this before? The error seems strange to me with the attempt to restore place.

  Hello
  You can also check the setting of JTA on the domain level. Domain-> JTA. Please check the page JTA, including advance setting. Please check the timeout and abandon the time-out properties. What value do you have here?

• Time Capsule - problem with the backup

  Hej!

  I get the message "an error occurred during the file copying. The problem may be temporary. If the problem persists, use disk utility to repair the backup drive. "A bit of research on Google, it seems that to restart the time capsule actually perform a repair disk. So I did it. The problem comes back, and sometimes she disappears, if I restart the backup, which confuses me. Is it possible to view the error logs and check what is the problem? I'm afraid that the backup drive may have hardware problems. I bought time capsule airport little for more than a year (in Sweden).

  Someone else has encountered this, and what was your solution?

  Johannes

  Most of the questions is network... and the error messages may not clearly identify between a network and disk problem problem.

  I bought time capsule airport little for more than a year (in Sweden).

  How long this problem has been going since then?

  In Europe the warranty period may be 2 or 3 years by law.

  Certainly if you have AppleCare on a supported product... computer, ipad, or apple TV the TC will be replaced by Apple under warranty. Just explain your problem to them.

  If you do not have access to the warranty or replacement.

  I highly recommend that you check your drive TC if there is nothing on what you need... then do a single pass low level format. It's utilitarian airport disk tab Archive is here... then the clear operation.

  

  Erase use the single-pass option.

  

  It is a low level disk format. (Don't bother with 7 and never even dream of using 35).

  If the problem persists when you restart the backup I suspect network problems... or the TC is a failure... mine (a 3rd in 3 years) comes from the same way... I pulled the drive and replaced it with a better brand than the basic model known problem seagate used Apple.

• Distnoted and Time Machine problem

  Since the update to El Capitan, I had a real problem with the stability of the iMac.  From time to time - a couple of maybe days, three times a day, maybe - it would just freeze with BBOD on the login screen.  So, in general, after wake from sleep or screen saver.  Execution of SSH on the iMac would show distnoted clocked at > 380%; kill that process would be to release all.  He seemed to be repercussions for this purpose - for example, Time Machine, notifications would stop appearing - backups work (depending on the Console) would simply not be notified.

  Anyway, I actually had my TM drive disconnected for more than a week now, and the problem occurred.  So it seems to be one of the three possibilities:

  • bad interaction between distnoted and TM or processes
  • defective drive.  It's a mobile hard drive from Lacie P9223 (but I also have a second desktop Lacie drive that causes the same behavior).  Disk utility shows no problem with either of the readers.
  • bad driver/firmware.  Maybe... in light of the same manufacturer.  I tried the update of the LaCie firmware but it just does not recognize the plugged into readers - I assume that the update is for one or more different models.

  Short run out and buy another drive from a different manufacturer - and who knows how different the internal components are really - someone has an idea how I could continue this?  Everything was ok before the upgrade; I remember that with a previous version of OSX external drives popular of some manufacturers stopped working, I had this problem at the time.

  Determine if the same problems occur when running in "safe" mode: OS X El Capitan: start in safe mode