Buddy idle times

on my old macbook pro(running osX) I can see buddy idle times in ichat/jabber. My new macbook pro is running Snow Leopard and I can no longer see idle times. Am I missing a setting?

Hi,
There is no setting to specifically view the Idle times.
If you are logged in twice to one Jabber server you may find the one that was logged in last gets the updates where as the other does not.
Jabber servers and specifically Jabber app can be set to have different Priorities.
This way you can set up your home computer with a lower Priority than a work one and both lower than say Phone.
This way when you turn on the Work computer it would get any messages rather than having to turn the Home one Off.
I certainly know that iChat (which has no Priority change setting) is se to the same Priority and logging in to the Google Mail Web Page and it's chat Option.
I would expect other Jabber Log-ins to be similar.
8:08 PM Thursday; July 21, 2011
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb( 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Similar Messages

Unable to capture the Idle time for BSP page

Hi Experts,
I want to capture the Idle time of my BSP page. If that is 5 mins then i have to display the pop up displaying the remaining time.
Please let me know how to capture the IDLE TIME. not the time after the page is loaded.
Any suggestion will be helpful.
Aready checked in SDN but unable to get the solution so posting it.
Thanks in advance.
Sravanthi.V

hi,
After capturing the idle time iam giving the warning popup to user before 5mins of expiry.Now my requirement is if the user clicks on OK button of popup the page should get refresh. i.e.Idle time should of system should break and we have to get one more hour for expiry.
Thanks in advance,
Sravanthi.V

RCA Connection Pool idle Time-Out takes no effect !

My question description goes here.
According to JCA specification, I developed my 'ManagedConnectionImpl' class from the interface 'ManagedConnection'. I realize the 'destroy()' function to send out logout request to the EIS.
Then I deployed the connector in Sun Java System Application Server, I noticed there are two parameters in Connection Pool part, they are:
1. Idle Timeout. It said it's the maximum time that a connection can remain idle in the pool. I assume the connection will be removed after the specific time expired and before it's removed it will call the recallable function, 'destroy()', in my concrete class, 'ManagedConnectionImpl'.
2. Pool Resize Quantity. it said it's number of connections to be removed when pool idle time expired.
I am weird about it. I think EIS had itself session control strategy, if the specific session time-out expired, it will invalidate this session. So I think we will set 'Idle Timeout' in application server to be shorter than the EIS session time-out. If the 'Idle Timeout' in application server expired, it should remove all connections inside otherwise maybe the connection with invalid session will exist! (the background knowledge is our system will return back soap fault when it meets invalid session, so the invalid connections will not be removed by switching on your configuration item, 'On Any Failure')
So I set "inital and minimum pool size" to 8, "maximum pool size" to 32 and "Pool Resize Quantity" to 32. (I expect AS to remove all when pool idle time expired)
After deploying, I send out requests at the first round and wait for the time expired but I can't see the desired logout requests from pool automatically even one. Firstly I guess if my recallable function definition is wrong but when I shut down the Application Server, the desired logout requests are sent out from pool automatically. So I think my recallable function definition is workable.
What's your comments on it?
P.S.
I am using Sun Java System Application Server 8.1.
Thanks in advance!
BRs
/Leo

I have had following test to ensure I sent out notification to listener.
[#|2005-08-23T16:14:25.061+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
It's in managed env!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter matchManagedConnections() !|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
try to find a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.062+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Found a matching and existing one, reuse it!|#]
[#|2005-08-23T16:14:25.495+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
tearDown() is called, the application-level connection is released!|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
enter calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
Start calling close() of managed connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
start to notify the listener the completeness of connection.|#]
[#|2005-08-23T16:14:25.496+0800|INFO|sun-appserver-pe8.1_01|javax.enterprise.system.stream.out|_ThreadID=12;|
notify the listener the completeness of connection successfully.|#]
Whether it's related with the initial and minimum number parameter? Although I found it will not be created during AS start-up and will be created at the first request.
Whether it shall be kept to meet the minimum requirement? I have failed to set it to 0.

Crystal report not shown after application idle time

i have a web page which uses around 10 session variables to store values on a button click.and after assign session values Response.Redirect("~/url",false); to a a page which contains crystal report viewer.and report should show those session values.after keeping the application idle for 45 mins i click on the button which assign session values.then it's redirecting to the report page but the report is not shown.it shows a empty page and no errors shown(only happens application is idle for nearly 45 mins other wise works fine)
i'm using iis 7
in the web.config i have set sessionState timeout="60" and application pool idle time out to 60 mins.
any idea why this happens

Make sure you are on SP 8
Make sure you are using .Close and .Dispose on your report objects as you get done with them.
What OS? (2003, 2008, 2012)
Provide more info on the following:
The problem is that the Crystal Report Viewer does not load after a few hours.
What does that mean? Errors? Warnings? Behavior? Symptoms?
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter

SSRS 2012 report integrated with SharePoint 2013 issue :Report refreshing after some idle time

we have SSRS 2012 report integrated with SharePoint 2013 , when we click on any toggle item after some idle time of 60 secs and try again to expand
another toggle item then complete report is getting refreshed and if we are in child report it is redirecting to parent report. . we didn’t set any refreshing property at report level. I hope there will be some idle time setting at sharepoint site
level.
what we observed.
1. there is no problem when we expand toggle items without any idle time.
2. when we open the report and expand few toggles and keep idle for 60 seconds and try
again to expand another toggle item then complete report is getting refreshed (all toggle items are collapsing).
3. If you keep idle for 60 minutes and if you didn’t do any action like expanding toggle
items it is not refreshing.
why it is happening and how to stop that complete refresh.
Surendra Thota

Hi Surendra,
I have tested on my local environment and the issue can be caused by the session time out ,the time out of the report precessing, database timeout,DataSet query execution timeout and so on.
I would like to confirm that the refresh you have mentioned is the page refresh or the report reloading?
Please reference to the setting below to don't limit the timeout values if you got the report reloading:
Point to a report in the library.
Click the down arrow, and select Manage processing options.
In Processing Time-out, select Do not time out report processing or
Limit report processing in seconds if you want to override that value with no time-out or different time-out values.
If you got the session timeout that refresh the page, please reference to the setting in below article:
http://msdn.microsoft.com/en-us/library/gg492284.aspx#bkmk_session_settings_section
Details information in the article below about the timeout setting for your reference:
Set Processing Options (Reporting Services in SharePoint Integrated Mode)
If you still have any problem, please feel free to ask.
Regards
Vicky Liu
If you have any feedback on our support, please click
here.
Vicky Liu
TechNet Community Support

SSRS sharepoint integrated report refershes after 60 secs of idle time

Hi All
we have SSRS 2012 report integrated with sharepoint 2013 in which when we click on any toggle item after some idle time of 60 secs then it refreshing complete report .
what we observered.
1. there is no problem when we expand toggle items without idle item.
2. when we open the report ond expand few toggles and keep idle for 60 seconds and try to expand another toggle item then complete report refresh is happening with all toggle items are collapsing.
3. If you keep idle for 60 minutes and if you didnt do any action like expanding toggle items it is not refreshing.
why it is happening how to stop that complete refresh.
Surendra Thota

Hi Surendra_Thota,
According to your description, there is SSRS drilldown report of sharepoint integrated mode, when you expand toggle after 60 seconds idle time, the report will be completely refreshed, and all toggle items are collapsed.
The report session keeps alive by pinging the server periodically for every N-1 second, where N being the timeout of the session set within Reporting Service. In this case, the report session has already expired in one minute and hence whenever we access
the page after one minute, the report will be completely refreshed. To solve the problem, we can increase the report session timeout for Reporting service 2012 in SharePoint integrated mode by following steps:
Browse the SharePoint central administration URL and navigate to Application Management -> Manage service applications (Under Service Applications).
Select the Reporting services service application and click on manage.
Click on System Settings.
Locate the Session Timeout setting. We can change it to 1200.
Click on OK.
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
If you have any feedback on our support, please click
here.
Wendy Fu
TechNet Community Support

How to track clients idle time and force to Login View

How can I force clients to the Login View after a period of idle time ( 1 hour). My mobile application consist of many views and need the time out to work from any view. Your assistance is appreciated.Using Flash Builder 4.5 and AS 3.0.
I was able to make it work using FlexEvent.Idle to determine the inactivity. But it only works when I am on the second view, if I go deeper (third view) it fails. Here is the code I am using and the error I get
protected function view1_creationCompleteHandler(event:FlexEvent):void
     this.systemManager.addEventListener(FlexEvent.IDLE, userIdle);
private function userIdle(e:FlexEvent):void
   if(e.currentTarget.mx_internal::idleCounter == 200)
    //do something!
    navigator.popToFirstView();
ERROR MESSAGE
++++++++++++++++++++++++
TypeError: Error #1009: Cannot access a property or method of a null object reference.
at views::MainMenu/userIdle()[C:\Documents and Settings\spences\Adobe Flash Builder 4.5\EmployeeLogin\src\views\MainMenu.mxml:89]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.managers::SystemManager/idleTimer_timerHandler()[E:\dev\4.5.1\frameworks\projects\fram ework\src\mx\managers\SystemManager.as:3292]
at flash.utils::Timer/_timerDispatch()
at flash.utils::Timer/tick()
Message was edited by: Stewart TVDSB

Hi Nadeem,
You can find the max session idle time in table APEX_040000.WWV_FLOWS, attribute MAX_SESSION_IDLE_SEC .
brgds,
Peter
Blog: http://www.oracle-and-apex.com
ApexLib: http://apexlib.oracleapex.info
BuilderPlugin: http://builderplugin.oracleapex.info
Work: http://www.click-click.at

How to handle user idle time in portal?

Hi Gurus,
We want to make the portal and its content area use the same session time-out on client side. When it reaches the maximal user idle time, let's take 30 minutes for example, it will automatically log out the portal.
There is already a wonderful solution to handle portal user idle timeout on client side: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/epSnippet-Portaluseridletimeoutforlogoff-custom+javascript
But it does not meet our requirement exactly.
We want to reset user idle time to zero not only for 'urn:com.sapportals:navigation' event, but also for 'onclick', 'onkeypress' and 'onmousemove' events in portal header/footer and content area.
Is it possible to realize our requirement? Or, is it possible to handle the 'onclick', 'onkeypress' and 'onmousemove' events from portal content area in portal header level(masthead)?
Thanks,
Bobby

Hi Bobby,
We have the same requirement and need to subscribe to button click and other such events as well.
Would you let me know if you have implemented such a solution ?
Regards,
Melwyn

WLS 8.1 SP5 Message bridge doesn't refresh connection after idle time out

Hi,
I am seeing in the log after enabling the debug flags that message bridge intermittently stops refreshing the connection without logging further info and causing a production failure.Bridge is forwarding the message from WLS 8.1..5 DQ to the remote MQ 6.0 queue.
Below is the snippet which doesn't come in the log which suggests that bridge stops refreshing the connection.
<BEA-200027> <Bridge "CASLDNSenderBridge" works in asynchronous mode and has not received messages for the predefined maximum idle time. The connections to the adapters will be interrupted and reestablished.>
The above message does appear everytime but intermittently it stops and the messages put after this leading to the exceptions.The bridge has been configured in asynchronous mode and the idle time out is configured as 60 secs.
Can somebody please let me know if there is any known issue with 8.1 SP5 where message bridge stops refreshing connection intermittently or how to debug this further.

I would normally suggest raising the issue with support, but I recall hearing that 8.1 is nearing the end of its support cycle, so I'm not sure that's an option for you. Other options:
- try upgrading to a newer SP, or better yet, a new version of WebLogic
- try changing to synchronous forwarding
- examine thread dumps from when the bridge appears to be stalled
- post the exception that bridge is throwing when it tries to connect
- try patching MQ (the problem could be on the MQ side, and perhaps an older version of the bridge may not be fully capable of handling all of MQs minor quirks)
- write a program to (A) detect inactivity on the src destination, and (B) somehow restart the bridge and/or all of WL when this occurs
Tom

[ZM] Problem with idle shutdown.(or idle tim

My zen micro's current firmware is ..0
I found this problem months ago, but didn't try to figure it out.
There is centainly problem with idle shutdown timer.
I guess the IDLE SHUTDOWN TIMER SHOULD NOT RUN IF THE PLAYER IS PLAYING.
Idle = player is on, but not playing or not performing any task.
My current setting is
Idle timer = 5 min
Sleep timer = 45 min
This problem occurs,
When the player is turning on from deep sleep mode (after 4 hrs of stand-by mode)
I left my player playing mp3 after turning on.
And eventually the player shuts down itself after about 5 min (which is setted as idle timer)
So I checked the screen when the player shut down itself, and the screen was displaying 'Idle Shutdown'
Once the player shut down, it will not shut down again after turing on.
Summary,
. Turn on player after deep sleep mode(4hr)
2. leave player as playing music
3. after time amount of idle timer, it shuts down itself.
4. the screen displays 'idle shutdown' when it shuts down itself.
anyone noticing this problem?

Jason-CL wrote:mcramen,I tested by taking the battery out(this will simulate as a deep sleep), and also turning on and off the player a few times without taking the batttery out with the same setting. The player are still playing now.Jason
Jason, there is a critical difference your test missed: He turned his player off, let it go into "deep sleep" after 4 hours, then turned it back on and left it playing; it then went into "idle shutdown" after 5 minutes. This can only happen with 4-hour-standby firmwares (..02, 2.20.05, and the deprecated .0.02) turned off while playing, which then go into "deep sleep" after 4 hours; if you "simulate" it by resetting, it won't start playing when you turn it back on. And if you press any button, "idle shutdown" will work normally and the bug won't occur. (Older firmwares will lose your place when entering "deep sleep" after 24 hours, so they won't exhibit the problem.)
Sounds like a firmware bug where it fails to recognize that a player turned on from "deep sleep" doesn't need a button punched to be playing. Get ready for .2 and possibly 2.2 firmwares, maybe?
In the meantime, the workaround would be to press any button (menu, pause/unpause, anything) if it's playing when turning on from "deep sleep". (Much like the previous post, but I suspect any button other than the power switch will work, not just pause. But I could be wrong.)Message Edited by RBBrittain on 0-9-2005 02:4 PM

JDBC initialize failed due to long idling time

Hi gurus
Anyone having similar problem and would like to share their solution for the problem stated below.
Normally the integration for IDOC-XI-JDBC scenarios is working fine, but when the R3 halt sending IDOC to XI, the JDBC connection to MS SQL 2000 server failed to process and initialise due to long idling time. Currently the temporary solution is to go to XI change the Integration Directory : Communication Channel for the JDBC - Activate - Clear Cache. Then go to R3, retrigger the IDOC again. And the above problem will be resolved. But after a while (long idling time again), this problem arise once again.
2008-10-21 15:18:45     Success     Message successfully received by messaging system. Profile: XI URL: http://locahost:50600/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
2008-10-21 15:18:45     Success     Using connection JDBC_http://sap.com/xi/XI/System. Trying to put the message into the receive queue.
2008-10-21 15:18:45     Success     Message successfully put into the queue.
2008-10-21 15:18:45     Success     The message was successfully retrieved from the receive queue.
2008-10-21 15:18:45     Success     The message status set to DLNG.
2008-10-21 15:18:45     Success     Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588
2008-10-21 15:18:45     Success     MP: Entering module processor
2008-10-21 15:18:45     Success     MP: Processing local module localejbs/CallSapAdapter
2008-10-21 15:18:45     Success     Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-10-21 15:18:45     Error     JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null
2008-10-21 15:18:46     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
2008-10-21 15:18:46     Error     Exception caught by adapter framework: JDBC Adapter configuration not initialized: null
2008-10-21 15:18:46     Error     Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.
2008-10-21 15:18:46     Success     The message status set to WAIT.
2008-10-21 15:18:46     Success     The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:23:46 GMT+08:00 2008.
2008-10-21 15:23:46     Success     The message status set to TBDL.
2008-10-21 15:23:46     Success     Retrying to deliver message to the application. Retry: 1
2008-10-21 15:23:46     Success     The message was successfully retrieved from the receive queue.
2008-10-21 15:23:46     Success     The message status set to DLNG.
2008-10-21 15:23:46     Success     Delivering to channel: CC_IDOC_TO_DBMS_ESMS_588
2008-10-21 15:23:46     Success     MP: Entering module processor
2008-10-21 15:23:46     Success     MP: Processing local module localejbs/CallSapAdapter
2008-10-21 15:23:46     Success     Receiver JDBC adapter: processing started; QoS required: ExactlyOnce
2008-10-21 15:23:46     Error     JDBC adapter receiver channel CC_IDOC_TO_DBMS_ESMS_588 not initialized. Unable to proceed due to null
2008-10-21 15:23:46     Error     MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null
2008-10-21 15:23:46     Error     Exception caught by adapter framework: JDBC Adapter configuration not initialized: null
2008-10-21 15:23:46     Error     Delivery of the message to the application using connection JDBC_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: JDBC Adapter configuration not initialized: null.
2008-10-21 15:23:46     Success     The message status set to WAIT.
2008-10-21 15:23:46     Success     The asynchronous message was successfully scheduled to be delivered at Tue Oct 21 15:28:46 GMT+08:00 2008.
2008-10-21 15:28:46     Success     The message status set to TBDL.
Edited by: Malcolm Pang on Oct 23, 2008 11:08 AM

In the JDBC adapter , select option Disconnect From Database after Each message processing.
This will solve the process as your JDBC Database seems to be closing the connection after a particular idle time.
Regards
Bhavesh

0% idle time of cpu states from top command in oracle 8i /solaris 5.9

Hi,
for long time idle time is 0% in top command :
database version:oracle 8.1.7.4.0
operating system : sun solaris 5.9
load averages: 9.32, 5.78, 6.13 15:22:13
404 processes: 387 sleeping, 13 running, 4 on cpu
CPU states: 0.0% idle, 78.2% user, 21.8% kernel, 0.0% iowait, 0.0% swap
Memory: 16G real, 7535M free, 5842M swap in use, 9965M swap free
PID USERNAME THR PRI NICE SIZE RES STATE TIME CPU COMMAND
6928 oracle 11 20 0 0K 0K run 2:20 12.62% oracle
23518 oracle 21 31 0 0K 0K run 24:37 11.69% oracle
9664 oracle 20 30 0 0K 0K run 12:41 10.83% oracle
15764 oracle 12 21 0 0K 0K run 2:18 10.28% oracle
9214 oracle 19 21 0 0K 0K run 5:52 8.58% oracle
13734 oracle 173 21 0 0K 0K cpu/3 311:23 6.11% oracle
19271 oracle 1 59 0 0K 0K cpu/0 726:20 4.45% oracle
10436 oracle 1 59 0 0K 0K sleep 81:41 4.39% oracle
22400 oracle 11 59 0 0K 0K sleep 3:22 4.35% oracle
9297 oracle 20 59 0 0K 0K cpu/2 7:39 3.66% oracle
22175 oracle 19 59 0 0K 0K sleep 6:55 3.41% oracle
9494 oracle 1 30 0 0K 0K run 0:02 2.99% oracle
10719 oracle 1 59 0 0K 0K sleep 132:48 1.55% oracle
210 oracle 1 59 0 0K 0K sleep 86:56 1.04% oracle
22084 oracle 24 59 0 0K 0K sleep 2:50 0.92% oracle
and sometime load average goes to 25-30 and cpu states is 0% idle in that load so how i can tune my database:
Regards
Prakash

Hi,
here 0% idle, 0% iowait
one of the query explain plan i am posting over here:
Operation     Object Name     Rows     Bytes     Cost     TQ     In/Out     PStart     PStop
SELECT STATEMENT Hint=CHOOSE          77 K          11800
COUNT STOPKEY
VIEW          77 K     32 M     11800
SORT UNIQUE STOPKEY          77 K     10 M     8384
HASH JOIN OUTER          77 K     10 M     4968
HASH JOIN          77 K     9 M     4477
HASH JOIN          54 K     2 M     3071
TABLE ACCESS FULL     GA_INSTANCE     10      140      1
HASH JOIN          75 K     2 M     3069
HASH JOIN          75 K     1 M     2351
INDEX FAST FULL SCAN     CUST_ACCT_ADDR_PK     75 K     960 K     282
TABLE ACCESS FULL     ADDRESS     199 K     1 M     1960
TABLE ACCESS FULL     CUST_ACCT     112 K     1 M     593
TABLE ACCESS FULL     IQARA_CNR_ACT_LOG     89 K     6 M     1150
TABLE ACCESS FULL     NI_STATIC_IP_ADDR     21 K     317 K     60
Reagrds
Prakash

Report Server does not respond after certain idle time

We have an oracle 10g application server on solaris 10.
The report server has the defaul settings for time out , callback etc..
After the report server stays idle for 2 or 3 hours and the first report that comes after that takes around 8 to 10 minutes to generate. The report server engine does not seem to be getting active immediately.
Is there any parameter I can change so that the reports do not get effected.
Thanks

I have put the idle time out at 300 minutes and the max idle time as 350 minutes. But that does not seem to have helped.And also I have min engine as 1 , max as 10.
Even with the above settings , When the report engine is idle after 30 minutes the 1st report to generate after 30 minutes takes 9 minutes.
please let me know if there are any other parameters I need to change.
thanks

Scheduled Tasks - System Idle Timer

I recently upgraded to Windows 8.1. Unfortunately, my NIC prevents the system from automatically entering Hibernate (if I disable/unplug it the system sleeps properly). To work around this, I thought I would use a Scheduled Task to run shutdown /h after
x minutes of inactivity (probably an hour).
I set my task's trigger to be an hourly check indefinitely.
I set the action to be shutdown /h
I set the conditions to be:
Start the task only if the computer is idle for: 1 hour (checked)
Wait for idle for: Do not wait
The problem I have found is that the task runs if the computer has been idle for only four minutes as per the Task Idle Conditions states (http://msdn.microsoft.com/en-us/library/windows/desktop/aa383561%28v=vs.85%29.aspx). In my mind I should leave the
computer alone, the hour ticks over and the task is initiated. It should then check to see how long the system has been idle for:
>= 1 hour? Run the task
< 1 hour? Do nothing until the next hour
What seems to be happening is it is checking for an idle state and running the task, even if the computer has only been idle for the minimum four minutes.
Has anyone else found this issue? Are there any ideas on how I can fix this? My next idea is to write a batch file to sleep for an hour and then hibernate and to have the task cancel the batch process when the system is no longer idle. Seems like it could
work.
Thanks in advance.

Hi vdboots. The question is regarding Task Scheduling and the idle timer, not the issues my system has with hibernating automatically.
To answer your query, yes I have disabled all devices from waking the computer. The Microsoft drivers for my NIC for some reason keeps the machine awake. I installed the manufacturer's Windows 7 drivers (of course they didn't release any Windows 8 ones...)
and the machine would sometimes enter hibernation, but mostly would just stay on. The only way I could get the computer to automatically hibernate was to disable the NIC altogether, but that is hardly a solution.
As I said, this question is about why Windows doesn't seem to be waiting for 1 hour idle time before initiating the task. The action of the task is fairly irrelevant, in fact for my testing I just launch cmd and run time /t.

IP device tracking and idle timer problem

Hi,
We are deploying 802.1X in our network and have encountered problem with a type of payment terminal.
The problem is that the terminal do not 'speak' to the network after the first initial DHCP request, the terminal waits for incoming packets from a counter to start the payment process. After the idle-time the MAC is flushed from the switch and the port is not authorized any more.
To solve this we set 'authentication control-direction in' on the port and use 'ip device tracking' to keep the client on the network, ip device tracking sends an arp request every 30 seconds to clients.
Our ISE is sending Radius:Idle-Timeout = 300 and the timer start to count down when the client is authenticated.
In Wireshark, I can see that the ARP request is going out and the ARP reply coming back in but this does not update the inactivity timer for the client. So after 5 minutes the port is gone, and there is no way to get the port up again from the network. Traffic from the client brings up the network.
This looks like a bug to me, anyone seen this, or a similar behaviour?
Running:
ISE 1.2p6
IOS 12.2(55)SE6
From Trustsec 1.99 Wired 802.1X Deployment Guide:
Tip Enable IP Device Tracking with inactivity timers to keep quiet endpoints connected. When IP Device Tracking is enabled, the switch periodically sends ARP probes to endpoints in the IP Device Tracking table (which is initially populated by DHCP requests or ARP from the end point). As long as the endpoint is connected and responds to these probes, the inactivity timer is not triggered and the endpoint is not inadvertently removed from the network.
From CLI output
SW03#sh auth sessions int fa0/4
            Interface: FastEthernet0/4
          MAC Address: xxxx.xxxx.5289
           IP Address: 10.10.10.64
            User-Name: XX-XX-XX-XX-52-89
               Status: Authz Success
               Domain: DATA
       Oper host mode: multi-auth
     Oper control dir: both
        Authorized By: Authentication Server
           Vlan Group: N/A
      Session timeout: N/A
         Idle timeout: 300s (server), Remaining: 2s
    Common Session ID: 0A17BD07000000A925152A7B
      Acct Session ID: 0x00000458
               Handle: 0x090000A9
Runnable methods list:
       Method   State
       dot1x    Failed over
       mab      Authc Success
SW03#
SW03#
SW03#
SW03#sh auth sessions int fa0/4
            Interface: FastEthernet0/4
          MAC Address: Unknown
           IP Address: Unknown
               Status: Running
               Domain: UNKNOWN
       Oper host mode: multi-auth
     Oper control dir: both
      Session timeout: N/A
         Idle timeout: N/A
    Common Session ID: 0A17BD07000000AA251A0019
      Acct Session ID: 0x00000462
               Handle: 0x800000AA
Runnable methods list:
       Method   State
       dot1x    Running
       mab      Not run

Here is the port config.
Just to clarify, everything is working except that the terminal is losing the authentication. The terminal works again if traffic is initiated from the terminals menu, like with ping.
interface FastEthernet0/4
description Standard
switchport access vlan xxx
switchport mode access
switchport block unicast
switchport voice vlan xxx
switchport port-security maximum 2
switchport port-security
switchport port-security aging time 5
switchport port-security violation restrict
priority-queue out
authentication control-direction in
authentication event fail action next-method
authentication event server dead action reinitialize vlan xxx
authentication event server dead action authorize voice
authentication event server alive action reinitialize
authentication host-mode multi-auth
authentication order dot1x mab
authentication priority dot1x mab
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
authentication timer inactivity server
authentication violation restrict
mab
no snmp trap link-status
dot1x pae authenticator
dot1x timeout tx-period 5
storm-control broadcast level pps 100
storm-control multicast level pps 100
storm-control action trap
spanning-tree portfast
service-policy input users

Buddy idle times

Similar Messages

Maybe you are looking for