Syslogd daemon take lot of cpu time arounf 50% of cpu utilization.

syslogd daemon problem it take lot of cpu time arounf 50% of cpu utilization. How do i solve this issue without reboot.

You can try then a "/etc/init.d/syslog stop" and "/etc/init.d/syslog start"
This is only a solution which perhaps will solve your load problem. But obviously
you should investigate why you have this strange behavior.
Grouch_fr
Edited by: Groucho_fr on Mar 17, 2009 2:19 AM

Similar Messages

Airport daemon takes over 95% CPU?

I think this started after applying the OS X 10.4.8 update.
When I turn on Airport in certain areas, the 'airport' daemon consumes 95-99% of CPU. Essentially it's spinning madly on one CPU core, sending the fans running at high speed to keep the machine cool.
If I turn Airport off, it doesn't stop. I end up quitting the process from Activity Monitor, or 'kill -HUP'ing it from Terminal. The next time I turn Airport on, the 'airport' daemon is restarted, which is fine... and within a minute or so it goes mad again. The machine quite often locks up solid for a couple minutes at that point, but comes back to a useful state eventually.
The strange thing is that this doesn't happen when I connect to my home WLAN. That's an old 802.11b network, however I can see 802.11g networks there. It happens at work, and I've seen it happen in one other place. (These are the only three locations which I've tried to use Airport since the 10.4.8 update.) So in two of three locations, airport goes nutty.
Any ideas? Thanks.
MacBook Mac OS X (10.4.8)

I don't want to introduce a duplicate thread. Please see http://discussions.apple.com/thread.jspa?messageID=3327038

[Solved] embedded videos in firefox take a lot of CPU time

Playing embeded videos in Firefox take a lot of CPU time. Actually my old computer is not able to play these videos correctly if they are in HD. The problem appears with flash videos (not so surprising, flash sucks...) but also with html5 videos (there is an option in youtube to turn that on). However if I succeed to have the direct URL, these videos play perfecrtlky fine in mplayer using not more than 10-20% of CPU time. Is there a solution to that? Is there any possibility to use an external player to play HTML5 videos in firefox? If anybody knows, Why this problem, are the mozilla folk aware of this problem? (Note that I posted a thread a long time ago for this problem but concerning flash only)
Last edited by olive (2012-04-27 20:33:59)

There's not much you can do to make HTML5 videos as fast as Xv, see http://swfdec.freedesktop.org/wiki/FAQ. They are slow for the same basic reason as Flash... the video overlay cannot be used because the standard allows for controls and CSS to be rendered on top of the video.
As for redirecting to an external player... this is not as easy as it could be. If the videos appeared in <embed> tags or <object> tags, one could use Mozplugger, Media Player Connectivity and other programs, but I don't think one has been written to handle the <video> tag. An upcoming update to firefox will make it use gstreamer, however. If this still results in slow playback, it will at least make it easier to use an external player. I imagine you would have to patch firefox to make it use a port on the localhost as the video sink instead of the screen. Then you would run gst-launch to receive that RTP stream.

Thread.sleep takes a lot of CPU time!

Hi,
I have the run method like this:
public void run()
while(true)
//some set of operations
Thread.sleep(5*1000*60);
The above code's performance was measured under stress test. . The sleep operation seems to take a lot of CPU time
though ideally sleep is like a no-operation mode, meaning since no operation
is done when a thread sleeps, it should not use any/minimal CPU time.
But it seems to take over 30% of CPU time!
Any ideas on why such a weird thing's happening?
In fact, in one more similar method also, sleep is taking similar CPU
time.

A sleeping thread uses no CPU. Try the following, both with and without the for loop. If you see a constant high CPU usage, even when the thread is sleeping, it's probably that the CPU usage is measured as an average over the last second or several seconds, so when the tasks you're performing are intense and take a significant fraction of the time you're sleeping, the average CPU usage doesn't go down that much.
public class Sleeper {
 public static void main(String[] args) throws Exception {
 while(true) {
 for (int ix = 0; ix < 100000000; ix++) {
 int jx = ix * 2;
 ix = --jx;
 Thread.sleep(5 * 1000* 60);
}

Helpd takes a lot of CPU

What is this process ?
It's spawned quite often, and uses a lot of CPU & memory.

Helpd updates all of the Application help files on your Mac.
However, I hate having helpd launching repeatedly and seemingly randomly, taking up 1 gig of RAM, and using so much CPU time that the fans go loudly full blast on my MacBook Pro. I prefer having my MacBook Pro be quiet.
Upon investigation, I found that helpd is controlled by a System LaunchAgent plist which is run on startup:
/System/LaunchAgents/com.apple.helpd.plist
When examining the contents of this plist using XCode, what you find is that:
1. helpd is run when it is loaded by the system at startup or login
2. helpd is run on every Sunday at 2:30 AM
3. the launch agent watches the following folders and runs helpd whenever the folders change:
 /Applications/
 /Applications/Utilities/
The biggest problem is the watch folders. They change whenever you open them (i.e. their modified date changes when opened). They change when you install a new application. Many applications change their Application folder content when run. etc. etc.
(Lingon is a simplified launch agent and launch daemon editor. Lingon 3, by the way, cannot manage anything other than your own user's launch agents and launch daemons. It is limited by Apple's new App Store rules. Lingon 2 can open up system launch agetns and launch daemons. But it is missing many of the plist fields revealed by using XCode. For example, it will show the /Applications/ watch folder. But there are TWO watch folders - the second one is /Applications/Utilities/ Thus, Lingon may cause problems by modifying the system launch agents and daemon plists by missing several fields. I don't recommend Lingon other than to create your own user launch agents and daemons - with Lingon 2 being a much more capable version)
The easiest solution is to use Xcode or another plist editor to modify the com.apple.helpd.plist to change the watch folders.
I changed /Applications/ to /Applications/Utilities/ and left the second watch folder /Applications/Utilities/
Since I seldom open /Applications/Utilities/ this causes helpd to launch far less often.
You can also just simpliy eliminate the watch folders. This keeps helpd running on Sundays at 2:30 AM or on startup or login.
When users get rid of many older applications, they see helpd launch less often since these older applications may be the ones modifying the /Applications/ folder.
If you have only newer applications or few applications, you don't run into the helpd problem as often or at all. This is why few people complain about helpd. Only the users who have numerous applications (particularly older ones or ones not bought from the App Store) run into this problem.
Here are the contents of the com.apple.helpd.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
 <key>EnableTransactions</key>
 <true/>
 <key>EnvironmentVariables</key>
 <dict>
 <key>NSRunningFromLaunchd</key>
 <string>1</string>
 </dict>
 <key>Label</key>
 <string>com.apple.helpd</string>
 <key>LimitLoadToSessionType</key>
 <array>
 <string>Aqua</string>
 <string>LoginWindow</string>
 </array>
 <key>MachServices</key>
 <dict>
 <key>com.apple.helpd</key>
 <true/>
 </dict>
 <key>OnDemand</key>
 <true/>
 <key>Program</key>
 <string>/System/Library/PrivateFrameworks/HelpData.framework/Versions/A/Resourc es/helpd</string>
 <key>RunAtLoad</key>
 <true/>
 <key>StartCalendarInterval</key>
 <dict>
 <key>Hour</key>
 <integer>2</integer>
 <key>Minute</key>
 <integer>30</integer>
 <key>Weekday</key>
 <integer>7</integer>
 </dict>
 <key>WatchPaths</key>
 <array>
 <string>/Applications/</string>
 <string>/Applications/Utilities/</string>
 </array>
</dict>
</plist>

Loading into the Infipackages takes lot of time

Hi Friends,
When i schedule and activate the process chain everyday, it takes lot of time to get loaded in the infopackages, around 5 to 6 hours.
in st13 when i click on the Log id name to see the process chain.
in the LOAD DATA infopackage it shows green, after double clicking on that, process moniter
i see request still running and its yellow but 0 from 0 records.
and this will be the same for hours
Its very slow.
need your guidence on this
Thanks for your help.

Hi,
What are you trying to load using this process chain? If it is cube, are you deleting the indexes on the cube before starting the load. If not, include that step as well in the process chain. This will help in getting improved performance.
Ideally it is always a good practice to delete the indexes before loading.
Regards,
Yogesh

Loading in infopackage takes lot of time

Hi Friends,
When i schedule and activate the process chain everyday, it takes lot of time to get loaded in the infopackages, around 5 to 6 hours.
in st13 when i click on the Log id name to see the process chain.
in the LOAD DATA infopackage it shows green, after double clicking on that, process moniter
i see request still running and its yellow but 0 from 0 records.
and this will be the same for hours
Its very slow.
need your guidence on this
Thanks for your help.

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
Also see if there is any 'sysfail' for any datapacket in SM37.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
5) Check in SM58 and BD87 for pending tRFCs and IDOCS.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the data tables.
SM21 - System log can also be helpful.
Regards,
Habeeb

BO Report in 4.0 takes lot of time to open

Hi We are having BO 4.0 environment.
The underline database is SAP BW and BO reports are built on top of Bex queries.
We found that it takes HELL a lot of time sometimes to open in BI launch pad/Infoview.
Just for opening it takes lot of time we cound found that actually it is not running anything in BW or else .
Could you tell us better integartion or alternate solution even for integartion of BI/BO or may be there would be some problem with interface betwwe BO and BW .
eg Tomcat server slow etc ..
Thanks
Gaurav.

Hi Denis,
Extremely Sorry for not providing enough information.
Business Objects is of BO 4.0 FP3 SP12.
BI is 7.10 Support Package 10 and Revision 627.
The point is While Opening Report In BO 4.0,it takes lot of time to open.
This generally happens whenever we have to open report for the first time in laptop/Desktop machine.
This always happens whenever we open the report for first time. (Generally when we have demo team metting to show our reports to management level and we face it takes lot of time )
Could you let us know for the same if someone else has also received this.
Please let me know if any other details is required.
Regards
Gaurav.

Inserting into a base table of a materialized view takes lot of time.......

Dear All,
I have created a materialized view which refreshes on commit.materialized view is enabled query rewrite.I have created a materialized view log on the base table also While inserting into the base table it takes lot of time................Can u please tell me why?

Dear Rahul,
Here is my materialized view..........
create materialized view mv_test on prebuilt table refresh force on commit
enable query rewrite as
SELECT P.PID,
SUM(HH_REGD) AS HH_REGD,
SUM(INPRO_WORKS) AS INPRO_WORKS,
SUM(COMP_WORKS) AS COMP_WORKS,
SUM(SKILL_WAGE) AS SKILL_WAGE,
SUM(UN_SKILL_WAGE) AS UN_SKILL_WAGE,
SUM(WAGE_ADVANCE) AS WAGE_ADVANCE,
SUM(MAT_AMT) AS MAT_AMT,
SUM(DAYS) AS DAYS,
P.INYYYYMM,P.FIN_YEAR
FROM PROG_MONTHLY P
WHERE SUBSTR(PID,5,2)<>'PP'
GROUP BY PID,P.INYYYYMM,P.FIN_YEAR;
Please help me if query enable rewrite does any performance degradation......
Thanks & Regards
Kris

Execution of first request takes lot of time with JDBC OCI

Hi,
We are having an application which connects to Oracle server(10g Enterprise Edition Release 10.2.0.4.0 64bit) using Oracle JDBC OCI driver(10.2.0.1.0 production (10g R2)).
Everything works fine.
But what we observed is randomly the first request to the server vai JDBC driver in a day takes lot of time, varies from 5-15 minutes.
If we execute the request again it executed immediately
What we observed while debugging is preparedStatement.executeQuery() is taking time.
We enabled logging at the JDBC driver layer and a snapshot isgiven below. Between T2CPreparedStatement.doDefineExecuteFetch () and T2CPreparedStatement.execute_for_rows () it takes 5 minutes. Any idea why it takes this much time and reason for it? Oracle driver is not throwing any exceptions
*4-apr-2011 4:00:01* oracle.jdbc.driver.T2CPreparedStatement doDefineExecuteFetch
FINE: T2CPreparedStatement.doDefineExecuteFetch ()
*4-apr-2011 4:05:12* oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows () returns: void
Detailed jdbc log is below
-apr-2011 4:00:01 oracle.jdbc.driver.OracleStatement doExecuteWithTimeout
FINE: OracleStatement.doExecuteWithTimeout() needToPrepareDefineBuffer = false
4-apr-2011 4:00:01 oracle.jdbc.driver.PhysicalConnection needLine
FINE: PhysicalConnection.needLine()--no return
4-apr-2011 4:00:01 oracle.jdbc.driver.PhysicalConnection registerHeartbeat
FINE: PhysicalConnection.registerHeartbeat()
4-apr-2011 4:00:01 oracle.jdbc.driver.OracleStatement executeMaybeDescribe
FINE: OracleStatement.execute_maybe_describe() rowPrefetchChanged = false, needToParse = false, needToPrepareDefineBuffer = false, columnsDefinedByUser = false
4-apr-2011 4:00:01 oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows (executed_for_describe = false)
4-apr-2011 4:00:01 oracle.jdbc.driver.T2CPreparedStatement doDefineExecuteFetch
FINE: T2CPreparedStatement.doDefineExecuteFetch ()
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement executeForRows
FINE: T2CPreparedStatement.execute_for_rows () returns: void
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleStatement executeMaybeDescribe
FINE: OracleStatement.execute_maybe_describe():return validRows = 1, needToPrepareDefineBuffer = false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleStatement doExecuteWithTimeout
FINE: OracleStatement.doExecuteWithTimeout():return validRows = 1, needToPrepareDefineBuffer = false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINE: OracleResultSetImpl.next(): closed=false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINER: closed=false, statement.currentRow=-1, statement.totalRowsVisited=0, statement.maxRows=0, statement.validRows=1, statement.gotLastBatch=true
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=1)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=2)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getString
INFO: OracleResultSetImpl.getString(columnIndex=3)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl getTimestamp
INFO: OracleResultSetImpl.getTimestamp(columnIndex=4)
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl wasNull
INFO: OracleResultSetImpl.wasNull()
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINE: OracleResultSetImpl.next(): closed=false
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl next
FINER: closed=false, statement.currentRow=0, statement.totalRowsVisited=1, statement.maxRows=0, statement.validRows=1, statement.gotLastBatch=true
4-apr-2011 4:05:12 oracle.jdbc.driver.PhysicalConnection needLine
FINE: PhysicalConnection.needLine()--no return
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement closeQuery
FINE: T2CPreparedStatement.closeQuery ()
4-apr-2011 4:05:12 oracle.jdbc.driver.T2CPreparedStatement closeQuery
FINE: T2CPreparedStatement.closeQuery () returns: void
4-apr-2011 4:05:12 oracle.jdbc.driver.OracleResultSetImpl close
INFO: OracleResultSetImpl.close()
Regards
Sunil

Hi,
Thanks for the reply
- SQL may vary. Its not the same query which takes time always. The same query executed immediately(using another connection from pool) works perfectly
- If there is a failover or stale connection getting closed or timeout, will JDBC driver thhrows exdeption? I didn't see any exceptions in the driver logs. Is there anyway to identify whether failover or timeout is happening?
Some other points
- The application uses connection pooling. This means that connections are created in the beginning and kept in the pool. And it may be in the pool for 72 hours or , before this issue happens
- Application uses prepared statements and the statements are preapred and kept and re used later. So the query which take s more time might be prepared before 48 hours or so.
- This is not happening every day. Many times the pattern is , it happens after 60-72 hours after application is started.
Sunil

Read cluster PCL4 .. takes lot of time

Hi guys,
Though I Know this is a functional related forum, i would want to post techincal question related HR ABAP.
I have a report that needs to read data from PCL4 cluster and display master data changes for an employee. Developed a big program to simulate "RPUAUD00" that displays the logged data.
My concenr is the program that i developed is taking minutes to execute. I am using the 2 function modules "HR_INFOTYPE_LOG_GET_LIST" and "HR_INFOTYPE_LOG_GET_DETAIL" for this purpose.
The function module "HR_INFOTYPE_LOG_GET_LIST" takes lot of time to get executed as it checks all the personnel number with hanges even if there was only one personnel number that was changed. Assuming that my personnel area and personnel sub area has 2000 employees, even if one employee's data is changed, the function module reads the cluster for all the employee and takes a few minutes to comeback, before the function module "HR_INFOTYPE_LOG_GET_DETAIL" is executed to get the exact details changerd. This is irritating the client. Any idea how to reduce the time as i am severely short of ideas as how to.
regards
Sam

Unless you pass the exact pernr, the function cannot determine without looking at all the pernrs for changes..If your program tied to PNP, you can improve the run time passing the pernr list to the function call HR_INFOTYPE_LOG_GET_LIST..
~Suresh

Importing SLD content takes lot of time in Solman 4.0

Hi Folks,
Importing SLD content takes lot of time while installing Solution Manager 4.0. Its in the 42nd phase of 45...SQL 2005 DB.
Its stuck in Configuring system landscape directory....and NOT thrown any error as of now...touch wood.
Can anyone tell me how much time does it take OR is it gone in a loop?

HI All,
Finally I have received an error during the above mentionde phase....
sapinst.log -
>>>
Import Status: PREPARING
Import Status: PREPARING
Import Status: PREPARING
ERROR: CIM_ERR_FAILED: IO error: Read timed out
 CONFIGURATION=
ERROR 2007-10-22 15:55:34
CJS-30059 J2EE Engine configuration error. DIAGNOSIS: Error when configuring J2EE Engine. See output of logfile java.log: 'JSE'.
java.exe.log -
>>>
Import Status: PREPARING
TYPE=A STATE= INFO_SHORT=com.sap.sld.api.wbem.exception.CIMCommunicationException: com.sap.sld.api.wbem.exception.CIMCommunicationException: CIM_ERR_FAILED: IO error: Read timed out
 at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:158)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:720)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:694)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:638)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.referencesImpl(WBEMRemoteClient.java:375)
 at com.sap.sld.api.wbem.client.WBEMClient.references(WBEMClient.java:1773)
 at com.sap.sld.api.wbem.client.WBEMClientUtil.referencesComplete(WBEMClientUtil.java:490)
 at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.collectAssociationsForRestoration(SAPCRUpgrade.java:700)
 at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.delete(SAPCRUpgrade.java:355)
 at com.sap.lcr.pers.delta.importing.ImportHandler.loadFullImport(ImportHandler.java:1765)
 at com.sap.lcr.pers.delta.importing.ImportHandler.loadImpl(ImportHandler.java:1605)
 at com.sap.lcr.pers.delta.importing.ImportHandler.load(ImportHandler.java:1573)
 at com.sap.ctc.util.SLDConfig.importSldContent(SLDConfig.java:812)
 at com.sap.ctc.util.SLDConfig.performFunction(SLDConfig.java:154)
 at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:69)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.net.SocketTimeoutException: Read timed out
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at java.net.SocketInputStream.read(SocketInputStream.java:182)
 at com.tssap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:323)
 at com.tssap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:271)
 at com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:476)
 at com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2604)
 at com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578)
 at com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427)
 at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:142)
 ... 30 more
caused by:
java.net.SocketTimeoutException: Read timed out
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:129)
 at java.net.SocketInputStream.read(SocketInputStream.java:182)
 at com.tssap.dtr.client.lib.protocol.streams.ChunkedInputStream.readLine(ChunkedInputStream.java:323)
 at com.tssap.dtr.client.lib.protocol.streams.ResponseStream.readLine(ResponseStream.java:271)
 at com.tssap.dtr.client.lib.protocol.impl.Response.initialize(Response.java:476)
 at com.tssap.dtr.client.lib.protocol.Connection.getResponse(Connection.java:2604)
 at com.tssap.dtr.client.lib.protocol.Connection.sendInternal(Connection.java:1578)
 at com.tssap.dtr.client.lib.protocol.Connection.send(Connection.java:1427)
 at com.sap.sld.api.wbem.client.WBEMHttpRequestSender.send(WBEMHttpRequestSender.java:142)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:720)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:694)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.send(WBEMRemoteClient.java:638)
 at com.sap.sld.api.wbem.client.WBEMRemoteClient.referencesImpl(WBEMRemoteClient.java:375)
 at com.sap.sld.api.wbem.client.WBEMClient.references(WBEMClient.java:1773)
 at com.sap.sld.api.wbem.client.WBEMClientUtil.referencesComplete(WBEMClientUtil.java:490)
 at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.collectAssociationsForRestoration(SAPCRUpgrade.java:700)
 at com.sap.lcr.pers.delta.importing.SAPCRUpgrade.delete(SAPCRUpgrade.java:355)
 at com.sap.lcr.pers.delta.importing.ImportHandler.loadFullImport(ImportHandler.java:1765)
 at com.sap.lcr.pers.delta.importing.ImportHandler.loadImpl(ImportHandler.java:1605)
 at com.sap.lcr.pers.delta.importing.ImportHandler.load(ImportHandler.java:1573)
 at com.sap.ctc.util.SLDConfig.importSldContent(SLDConfig.java:812)
 at com.sap.ctc.util.SLDConfig.performFunction(SLDConfig.java:154)
 at com.sap.ctc.util.ConfigServlet.doGet(ConfigServlet.java:69)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
// => Importing Data : E:/usr/sap/SOL/SYS/global/sld/model/CR_Content.zip URL=http://devsrv:50100 USER=J2EE_ADMIN ...
Import Status: PREPARING
ERROR: CIM_ERR_FAILED: IO error: Read timed out
 CONFIGURATION=

Dock uses lots of CPU time

I find Dock uses ~140% CPU time sometimes, I can't see a cause for it to do so. It usually stops of its own accord after a random amount of time. Killing it doesn't help, launchd restarts it and it goes back to using lots of CPU.
I have parallels install and I have the version which has the fix (6.0.12106) and I have also tried the work around (no luck obviously).

Never mind, I figured it out by myself. On this particular machine I had a 3rd party plug-in installed (SRS iWow 1.1.8). Removing that brought the CPU usage down to 0.1%. Usually I don't install 3rd party add-ons. This would seem to be a good policy.
Steve

Query from source table takes lots of time

I have to load data from an Oracle table which has millions of records. The loading knowledge module I am using is 'lkm sql to oracle'.
I see that the query from the source database takes lot of time and doing a full table scan where as it supposed to be using an index.
I dont have any lkm with 'lkm oracle to oracle'. Some how I need to add a hint to this source query. How I can do this?

This LKM is not indicated to large volume of data, try to use LKM Oracle to Oracle (DBLINK), see ODI KMs documentation for more information.
Related to HINTS you can add this with KM options, see that some Oracle ODI11g new KMs already have some options to do it, so you can put the hint on interface options of KM or define the temp index on the interface

Infoobject F4 help in the Query takes lot of time and hangs

Hi All,
I have 0Material in the query and the F4 help for selection takes lot of time and hangs after some time.
The 0Material has 2 million records the Infoobject properties for Bex are as below:
Selection:No selection restriction
Query Def. Filter Value Selection: Values in Master Data Table
Query Execution Filter Val.Selectn:Only Posted Values for Navigation
We tried to alter some of the Properties but we have the same issue.
Suggest other options that can be be looked into to get the F4 help in the Query .
Thanks,
Mike

hi Mike,
check if helps
Note 817335 - Performance in F4 Help
Note 748623 - Input help (F4) has a very long runtime - recommendations
Note 581802 - Variable dialog boxes: performance of the F4 help
search oss note for f4 performance ......

Syslogd daemon take lot of cpu time arounf 50% of cpu utilization.

Similar Messages

Maybe you are looking for