Skip to Content

SiePortal

The integrated platform for your product selection, buying and support workflow - bringing together Industry Mall and Online Support.

SiePortalDeutsch

Search

Home
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menu temporary not available
- Menue temporary not available
- {{item.title}}

Products & Services
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Support Support
{{(apiData.Support | filter:{'rank':1}:true)[0].title}} Support
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
MySiePortal MySiePortal
{{(apiData.MySiePortal | filter:{'rank':1}:true)[0].title}} MySiePortal
- Menu temporary not available
- Menue temporary not available
- {{item.title}}
Cart ({{apiData.CartCount}})

Navigation

Is there any way to check the C action queu in runtime?

Created by: Peter at: 5/10/2007 12:35 PM (8 Replies)

Rating (1)

Thanks 0

9 Entries

5/10/2007 12:35 PM	Rate (0)
Peter Posts: 83 Rating: (8)	Hallo Nemo or others expert :D Is there any way to check the C action queu in runtime?
Peter Posts: 83 Rating: (8)	Last edited by: CS Moderator at: 11.05.2007 10:45 new subject after splitting
Suggestion To thank Quote Answer

5/10/2007 1:47 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Hi Peter, I'm not sure what you mean... you can use GSCDiagnostics to check for script errors in runtime, and APDIAG can check for errors while switching between screens.
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

5/10/2007 2:01 PM	Rate (0)
Peter Posts: 83 Rating: (8)	Holla Danielle, I have this 5000 action error thing so I want to control/see how many C action are there in script queu. rgds, Peter
Peter Posts: 83 Rating: (8)
Suggestion To thank Quote Answer

5/10/2007 2:26 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Hi Peter, I don't know any way of checking how many scripts are running. Did you check the links Nemo posted? They list possible causes for your problem, like these ones: Standard triggers are used in these actions. The actions in the Global Script cannot be processed in the time given. Through continuous loops and deadlocks in scripts. The error message often occurs when you archive a large number of tags cyclically selective or acyclically in the Tag Logging. The Start / Stop functions (begin / end archiving) are executed every 500ms. Since this happens for each tags, the "script.exe" application is heavily loaded. Never archive more than 10 tags with this method. So you should work on the cause of the problem, and once you've found it you'll have a normal amount of scripts, and the error will stop happening... so you'll know when you have a normal situation when you log is clear of that error. Try the solutions posted in Nemo's post, and if they don't work tell us. Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

5/10/2007 2:28 PM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	danielle, he means if there is a functionality to see in runtime how many actions are active at any time. In that case he can check how his system is performing. I however don't know of a way to check this during runtime.
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

5/10/2007 2:31 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Thanks Ikkezelf, I understood what he meant a little while ago, as I posted. But I was probably writing my post when you posted yours . As I said, I don't know any way of checking this either... so I suggested that he tried the solutions on Nemo's posts, and check if the log was clear of the error, 'cause that's pretty much the only way I can think of right now to know if the problem is solved.
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

5/10/2007 3:14 PM	Rate (1)
Peter Posts: 83 Rating: (8)	I will answer my own question :D I activated apdiagnose application and there under INFO menu there is sub menu Count of Actions in RequestQueue. And guess what... my bad picture produce entry something like this: Applikation: PDLRuntimeSystem cycle Count of Requests 4013 Applikation: PDLRuntimeSystem cycle Count of Requests 1 Applikation: GSC_RT cycle Count of Requests 0 Applikation: PDLRuntimeSystem cycle Count of Requests 1105 Applikation: PDLRuntimeSystem cycle Count of Requests 0 Applikation: GSC_RT cycle Count of Requests 0 No wonder I got 5000 action warning things. After following Nemo advice I got less than 300. Thanks everyone for helping me. Salute.
Peter Posts: 83 Rating: (8)
Suggestion To thank Quote Answer

5/10/2007 3:42 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	You're welcome! Thank you for posting what you found out, it'll be useful fir sure! Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

5/10/2007 3:56 PM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Never to old to learn something Thanks for posting
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on