How to debug workflow

hi Experts,
I am using wcc11.1.1.7, I know there is a way for debugging service as adding a parameter of &IsPageDebug=1 in url, debug menu will show on the right down of IE, the question is for js log, how to produce js log? is it a log4javascript or idoc sript log? if it's latter one, I can't find doc for this function.
BTW, for workflow debugging, is there anyother way for debugging, since wf could be running in background, wonder if &IsPageDebug=1 could help in this case.
Best regards

"I would like to view the value of a variable in idoc script, in the middle of the process, how to output the value by using js log?"
IdocScript is server-side, JavaScript is client-side. You will not be able to write Idoc run-time variables to a .js log if the IdocScript produces no viewable output - which happens more often than not.
You should be looking at the <$trace$> function in the IdocScript manual. You can use it to write the variable to the system console or to the system log to see the value of the Idoc variables. I covered the trace function quite extensively over on the Sena blog. http://senasystems.blogspot.com/2012/06/debugging-pages-in-content-server-11g.html

Similar Messages

Plz help me how to debug workflow

hi one and all,
plz help me how to debug workflow .
thanking u every body.

Hi
first save and activate then press ctrl+shift F9 then goto F8 and press F5 and F6(function) and output for F7......
Rewards If useful,
Thanks & regards,
S.Suresh

How to debug the workflow

dear friends,
please tell me how to debug the workflow, if you have time then you just see the workflow WS99900212 . in this i have done Leave Approver Notification . but i want to debug on that how to flow step by step .
please you tell me on same workflow , where i am going to take breakpoint.
Thanks in Advance for help.
Cheers.
Puneet.

You can try first of all to enable more logging. (I assume you are running release ERP 2005 since you are not saying what your release is.)
In the workflow builder, select menu item "Goto", "Basic data"
Select the "Version-dependent (current workflow version)" tab
Select the "Control" tab within the version-dependent subscreen
Select the "Performance optimization" tab within the control subscreen
Change the "Settings" drop-down value to "No restrictions on logging".
That will give you much more information in the workflow log. The description of this choice says "All the messages are logged. All runtime operations can be traced." As also noted: don't keep this setting in a production system.

How to debug Sequential workflow and state machine workflow?

Hi All,
How to debug Sequential workflow and state machine workflow?
Thanks in Advance!

check this
http://msdn.microsoft.com/en-IN/library/bb386166(v=vs.90).aspx
http://msdn.microsoft.com/en-us/library/vstudio/ee231573(v=vs.100).aspx

How to debug a program exit in a Workflow ?

Hi experts,
                  How to debug a program exit in a workflow when the workflow is triggered ?
thanks in advance
regards
Ashwin

In 4.6c I did this by creating a function module and a table (zsm50_debug). In the table are just two fields: User name (key), and a flag (yes/no).
The function module:
FUNCTION zsm50_debug.
*"*"Local interface:
*" IMPORTING
*"     REFERENCE(Z_DEBUG_USER) LIKE SY-UNAME
DATA: z_exit,
        z_debug.
CLEAR: z_debug.
DATA: starttime   TYPE t,
        currenttime TYPE t,
        time_passed TYPE i.
starttime = sy-uzeit.
* Check if debugging is switched on
SELECT SINGLE debug FROM zsm50_debug
                      INTO z_debug
                      WHERE uname = z_debug_user.
* Debugging is switched on:
IF z_debug = 'X'.
*   Not an endless loop, but it will continue after approx. 1 minute...
*   Plenty of time to go to SM50 to debug the program and continue!
    DO.
*     Change the value of z_exit to 'X' to exit the loop an stay in
*     debug mode.
      IF z_exit = 'X'.
        EXIT.
      ENDIF.
*     To prevent an endless loop (if the user forgot that debugging was
*     switched on in ZSM50_DEBUG, time is measured to allow the program
*     to continue after 2 minutes
      GET TIME FIELD currenttime.
      time_passed = currenttime - starttime.
      IF time_passed > 120.
        WRITE: / '!!!==========================================!!!'.
        WRITE: / '!!!DEBUGGING STILL SWITCHED ON IN ZSM50_DEBUG!!!'.
        WRITE: / '!!!    Program was delayed by two minutes    !!!'.
        WRITE: / '!!!==========================================!!!'.
        EXIT.
      ENDIF.
    ENDDO.
ENDIF.
ENDFUNCTION.
This FM reads the table and checks if the flag is switched on. If so, it loops for two minutes. After that, it continues regardless. If not flagged, it continues immediately.
This way, you can debug any program that is running in the background.
In every method I program I add this FM right in the beginning. With authorization for SM50, I can then debug the program (in production it may be difficult to get the correct server, if there are more).

How to debug a sandboxed workflow action

hi,
I want to create a sandboxed work flow action.
how to Debug the sandboxed work flow action So,I can find Errors in code.
Thanks in advance.
Anwar

Hello,
The TechNet Sandbox forum is designed for users to try out the new forums functionality. Please be respectful of others, and do not expect replies to questions asked here.
Since your post is off-topic, I am moving it to the
off topic forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book:
Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C406F75746C6F6F6B2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Is it possible to debug workflows deployed using Workflow Manager in VS 2013?

I know and I have debugged workflows in VS 2012 as described here: http://msdn.microsoft.com/en-us/library/jj658563%28v=azure.10%29.aspx
But I am unable to debug in VS 2013 Update 2.
Also, many activities like HttpSend are not displaying after updating to VS 2013 Update 2.
Is there any fix available for this?

You can't step through a SharePoint Designer Workflow. The normal workaround is to Log messages to the History list with the values you want to look at where you would normally put breakpoints. Then run the workflow and examine the history
list to see how the values changed as you went through your workflow.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Debug Workflow in SM50

Hello,
We created a workflow to create the new material . To create Material we use the BDC MM01. but we encounter an error in this step. We would like to debug at this point . ( Set break-point after CALL TRANSACTION) . To do this we use a commande :
DATA: wl_test(1).
wl_test = 'X'.
WHILE NOT wl_test IS INITIAL.
ENDWHILE.
Our purpose is to make the program run in the process list SM50 so that we can go to the debug at this point.
However When we execute Workflow, The process does not exist in SM50 but when we see in SM04, The user WF-BATCH is still connected, This means that It's still running ?
Please help us how to debug this point ( BDC in WF)
Thanks

Hi Prabu,
If you want to use workflow to release POs, you must make the standard and basic settings for workflow (Basis -> Business Management -> SAP Business Workflow).
·     In the case of a release procedure linked to workflow, you must have previously created the user names, positions, jobs, etc. that you here assign to the release code in the organizational plan and must have linked them to the relevant standard tasks in task-specific Customizing (Basis -> Business Management -> Business Workflow -> Perform Task-Specific Customizing).
·     You must assign the authorization M_EINK_FRG to the persons who are to be involved in the release procedure ( Authorization Management -> Create Authorization Profiles and Assign to Users).
If a release code is to be used in workflow, indicate this accordingly in the Workflow field
The Workflow indicator is also used to control role resolution:
·     "1 - Role Resolution with Group, Code and Plant (T16FW)"
Here you use a role resolution that is supplied in the standard system. To do so, you must assign the release point in the section Workflow (see below).
·     "9 - Role Resolution via User Exit"
Here you use the customer exit M06E0005 to define a role resolution of your own.
Regards
Sanjay L

How to debug for inbound mail in SAPconnect - ERMS

Hi,
How to debug from the point of receipt of an inbound mail in SAPconnect so that we can see the data being passed to the ERMS Workflow WS00200001.
Regards,
Deepak

Hi Ashish,
Thanks for your prompt reply. Let me explain the scenario in little bit details. If you want I can post the screen shots at flickr etc. for better understanding.
In transaction SWI1: we are getting Error at Invoking Service Manager for Workflow WS00200001. The error is "ERMS support object: Could not find DOCUMENT - Message no. CRM_ERMS020.
In transaction CRM_ERMS_LOGGING: We are getting error "Exception in method constructor (CL_CRM_ERMS_XPATH_TAG): Service CL_CRM_ERMS_ADD2FB_DOCUMENT failed. Cannot read email".
On providing valid email document id or work item id in transaction CRM_ERMS_LOGGING the required action is executed and everything is ok.
We tried to debug in SCOT by DBG+ but on receipt of inbound mail debug session does not start.
Actually we want to understand, on receipt of email what data is passed to the workflow as method call CL_CRM_ERMS_CONVERTER->CONVERT_DOCUMENT does not return XSL content and the error message is raised. It is possible that the previous method call SERVICE_MANAGER->GET_EMAIL_ID() does not retrieve a value for doc_id, but we are not sure without being able to debug through from the SAP connect process.
Regards,
Deepak

How to debug in SAP Netweaver Developers Studio?

Hi there,
I am trying to debug and slove my error in SAP NWDS.
I am building portal application->JSPDynPage
I am trying to debug the jsp code behind page, it doesn't realli give error message like the java beans does.
I am quite new to this and do not know how to set the function to test and debug this page can anyone provide any solution ?
I have have this prob pls refer to this link
<a href="https://www.sdn.sap.com/irj/sdn/thread?threadID=192104">https://www.sdn.sap.com/irj/sdn/thread?threadID=192104</a>
Thanks loads
Quatre

Hi Quatre ,
-Select the breakpoints in your Dynpages /beans in ur project
-To debug u have to change the prespective to debug which u can find in
window/open prespective /Debug in NWDS
-Select the Run/Debug or the Debug icon in the toolbar.
-Fill the project name ,application name in the in the wizard opnend .
- Follow the debugging using the next step over F6 ,step return F7 keys .
These link may be helpful:
http://help.sap.com/saphelp_nw2004s/helpdata/en/66/547f09281d464b951c9a3a6b06a12d/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/def86ab54da5418a3575373934ca00/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d4/31e24044b80b06e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/be/cffcb407c67842b122bd1296dc810f/frameset.htm
U can always find out the way in the PDK development /how to debug/
ie in NWDS /HELP /SAP WAS AS Documentation /SAP J2ee Enterprise Java Beans/Java development User Guide /Running and Debugging
Cheers,
Swathi Rao
Do offer pts:-)

How to debug web app with weblogic?

I wrote a web app that includes jsp files and some javabeans, then I put the jsp files to directory
mydomain\applications\DefaultWebApp
then I complied javabeans and put those classes to
mydomain\applications\DefaultWebApp\WEB-INF\classes
Then I start the weblogic,it runs very well.
I modified some javabean, complie them and put classes override the old classes,
but the web app can not find the new classes.
Any one know How to debug web app(with javabeans) in weblogic?
thanks!

how to config the hot deploy?
thxSorry, for this delay in responding. I had set notify me with email option in Watch This topic; but I never did get any email notification.
I use wls6.1; I think the process may be very similar to this in wls8.x. In wls6.1 (sp5), this is done via the -
Dweblogic.ProductionModeEnabled=False or
Dweblogic.ProductionModeEnabled=True
in the startup cmd/sh script. Out of the box, wls6.1 is set to Dweblogic.ProductionModeEnabled=False which automatically enables hot deploys.

How To: Debug missing Drivers in MDT

The definitive post on missing drivers in MDT (most comprehensive list I've done so far)…
Please to NOT post questions from this thread, instead create a new thread.
How to debug Network Driver Problems
One of the earliest hurdles an MDT administrator will come across is the management of device drivers, specifically networking drivers. With most other drivers, like Audio, printer, and video drivers, a quick call to Windows Update or install over the network
will resolve the Installation. However unless the Network (and storage) Drivers are installed into Windows from the start, it will be much more difficult to install the rest of the system.
This post should help you get started if you find a machine that did not install a device driver properly, and you want to know how to find and import the correct drivers.
Installing network drivers in the
full OS
Step 1 - Try network connection again
It's possible that you might get a DHCP error from MDT, but when you try again later to connect the Deployment Share it works! This may be caused by a slow or malfunctioning DHCP server in your network. Re-check your DHCP servers, ensure that PortFast is enabled
on your routers. If all else fails get your network administrators to document the DHCP delay. A long delay in modern networks is unnecessary.
Step 2 - Verify connectivity
You may not have a driver problem but a network problem. Check the physical connection on the computer (Network installs on MDT *REQUIRE* a wired network connection, no Wi-Fi). Open a web browser. Check the IP Address (ipconfig.exe /all). Ping the Deployment
Server, manually connect to the Deployment Share. IF you can't connect to the Deployment Share, neither can MDT.
Step 3 - Find the Correct Driver Package
Before you load the driver into MDT, first verify that you have the correct driver. There are scenarios where you may *think* you have the correct driver, but the driver will never run because the package is designed for a different OS/SKU/Platform/whatever.
Install the driver package by:
  ○ Open the Device Manager (devmgmt.msc).
  ○ Find the network device in the list (ensure this is the wired device, not the wireless device)
  ○ Right click on "Properties" and click on the "Details" tab.
  ○ From the "Details" tab, select the property "Hardware Ids" select all the values, and copy to the clipboard, it would be a good idea to save for later. Should look something like:
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA&REV_04
      PCI\VEN_8086&DEV_1502&SUBSYS_21F317AA
      PCI\VEN_8086&DEV_1502&CC_020000
      PCI\VEN_8086&DEV_1502&CC_0200
  ○ From the "Driver" tab, click on "Update Driver…", click on "Browse my computer for driver software" locate the driver package on the local machine or USB Drive, and install the package.
  ○ You should get a confirmation that the driver package was installed.
  ○ IF you do not get confirmation, MDT driver installation may not work.
Windows will install the driver starting with the *.inf install package, and will typically include a *.sys (binary) and a *.cat (digital Signature). If the driver package has been re-packaged into a *.cab, *.zip, or other compressed *.exe file, the
package must be extracted first. This is a hard requirement for any driver used by MDT and/or SCCM. All driver packages that are signed by Microsoft (WHQL) will be installed from the *.inf file, and you should only use devices that have the Microsoft WHQL
Logo as a sign of quality.
If you need a help on where to find driver packages for your devices, the 3 largest Computer OEM manufacturers supply drivers grouped by Make and Model that are easily imported into MDT and SCCM. See:
http://deploymentbunny.com/2014/07/08/back-to-basicwhere-to-find-drivers-for-servers-and-clients/
Step 4 - Load driver into MDT
If you have more than 20 driver packages, or if you anticipate you will have more than 20 drivers, you should start grouping your drivers in sub-folders for organization. One popular method is to group by Computer Make and Model. Ensure that you are using the
correct Driver Selection Profile in your task sequence. If you are unsure, disable any selection profile(s) to ensure the driver is installed correctly.
Step 5 - Run the full MDT installation
During installation MDT will perform the following:
  ○ Run the PNPEnum.exe utility and capture output to PnPEnum.xml. The VEN_Xxxx and DEV_Yyyy from the "HardwareIDs" property above must be present in this list. Otherwise we won't have a match.
  ○ Search through the %DeployRoot%\control\drivers.xml file looking for a match for the HardwareID. MDT may filter the search based on the folder search type.
  ○ MDT will copy each matching driver to the local c:\drivers directory using the xcopy.exe command. You can search (grep) for the string "xcopy" in the ZTIDrivers.log file, that will get you list of all driver packages matched by MDT.
  ○ MDT will allow the machine to boot into the NEW OS, and Driver Installation will begin in the OS. IF there are multiple drivers found and copied locally, the Windows (not MDT) will determine the best one. The c:\windows\inf\SetupAPI.*.log files
will detail which drivers copied locally were installed (or *not* installed).
Installing Network Drivers in
WinPE
Step 6 - Try the network connection again
(See above
Step 7 - Verify Connectivity from within WinPE
Verifying network connectivity will be a bit more difficult in WinPE, since we have a limited User Interface, so all investigation must be done in the debugging mode (Press F8) cmd.exe
  ○ Try connecting to the Deployment Share:
  c:\> net use * \\MDT\DeploymentShare$ /u:UserDomain\UserName *
  ○ Try pinging the Deployment Server:
  c:\> Ping.exe MDT.Corp.contoso.com
  ○ Verify that you have an IP address ( ipconfig /all ) If you have an AutoConfiguration address - Driver OK - WinPE can't reach the DHCP server. If you have "Media Disconnected" - Driver OK - Physical adapter not plugged to network. If
no devices are listed - Driver bad - Driver not installed.
  ○ Check the x:\windows\system32\WpeInit.log - This log will show the network driver (if found) being installed.
Step 8 - Verify driver packages are getting included into WinPE
Firstly, verify the correct driver package from within the full OS above. By default MDT will import *all* Storage and Networking drivers into your WinPE image. However it is possible to change the subset of files copied via "Selection Profile" or
other method. Cross check your WinPE Driver Settings.
  ○ From within the MDT console, right click on the root of your Deployment Share and select properties.
  ○ Click on the "Windows PE" tab, and the "Drivers and Patches" sub tab for both x86 and x64.
  ○ Your Network Drivers package must be in the "Selection Profile" if enabled.
Finally verify that the correct Network Driver package is being copied to WinPE. If necessary this may include setting up a debugger to watch the MDT Provider build the WinPE Image from scratch. My preference is to use the SysInternals
http://live.sysinternals.com/Dbgview.exe tool.
  ○ Open up the MDT console.
  ○ Download and run the DbgView.exe tool.
  ○ Update the deployment share in question.
  ○ The DbgView tool should show what drivers were copied to each WinPE Image.
Other
Whenever you add a driver into the MDT console, you must update the deployment share for that drivers to be added to your WinPE Image. If you are unsure, select "Completely regenerate the boot images." to ensure the drivers is imported. Additionally,
you must copy the updated LitetouchPE_x??.wim and *.iso files to the other consumers of the WinPE image like WDS/PXE and or any USB offline media.
Note that some Broadcom NetXtreme class of drivers have a multi-function driver architecture that may have difficulty loading in WinPE. Ensure that you load the "RIS" class of drivers from Broadcom in your MDT environment.
Note that by default MDT does *NOT* support the installation of Windows over Wireless network devices (Wi-Fi). The MDT installation sources must either be available through wired networking, or offline (USB Flash) media.
This post does not discuss origination of drivers within MDT ( Chaos vs. Total Control ), that is a different topic.
http://www.deploymentresearch.com/Research/tabid/62/EntryId/112/MDT-2013-Lite-Touch-Driver-Management.aspx
Further Help
If you are still having problems with drivers in via MDT, ask the experts in the MDT Technet Forum:
Include a short description of the problem. Including the Make/Mode if necessary.
Include the HardwareIDs from the Device Manager (Devmgmt.msc) into the post (from above).
Copy your known good driver package (step 3 above) to OneDrive.
Copy the following log files to a public site like OneDrive and include the link:
  ○ PnpEnum.xml (from Client)
  ○ Bdd.log (From Client) - or at least the ZTIDrivers.log file.
  ○ c:\windows\inf\SetupAPI.*.log (from client)
  ○ %DeployRoot%\control\Driver*.xml
  ○ %DeployRoot%\control\SelectionProfile*.xml
  ○ %DeployRoot%\control\settings.xml (if problems in WinPE)
  ○ x:\windows\System32\WpeInit.log (if problems in WinPE)
  ○ If the MDT server is not including your driver package in WinPE include the DBGView log.
This post is by Keith Garner - Keith was a developer on the MDT team where he developed the ZTIDrivers.wsf script, he also worked for the Windows Hardware Quality Labs as a technical PM on Driver Quality, and developed samples for the
Microsoft Device Driver Kit (DDK) specifically around the area of Device Driver installation in the OS (Windows NT 5.0, 2000 and Windows XP). (So yes, I know drivers :^).
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

OK. I have redone the drivers for WinPE which has reduced the image size by about 200MB. Unfortunately the problem persists.
Is there anyway to turn on some sort of boot logging so I can see what driver it is failing on?
I am also still seeing the weird behavior of it working over PXE but blue screens when booting from USB. Can anyone explain that?
JJ

How to debug when you can't recreate error consistently

I have a simple illustrator-type application in which I draw rounded rectangles to a JPanel and then the user is able to move them around (the position and repaint is done in via the mouseDragged interface.
Sometimes, the application shuts down when I am dragging a box with this message:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
# An error report file with more information is saved as hs_err_pid3400.log
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
I checked the error report and it suggests the problem is within the PathFiller.WriteAlpha. The entire report is below. The problem I have is that if I restart the application and place boxes in the exact same locations as before, and try moving the one that caused the error, the error is not thrown.
I have no idea how to debug this as I can't even consistently reproduce. I just upgraded to the newest JDK (I think it was 7).
Thanks for any insight and help you can offer.
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d236a0c, pid=3400, tid=2716
# Java VM: Java HotSpot(TM) Client VM (1.5.0_07-b03 mixed mode, sharing)
# Problematic frame:
# C [dcpr.dll+0x6a0c]
--------------- T H R E A D ---------------
Current thread (0x00acae38): JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
siginfo: ExceptionCode=0xc0000005, reading address 0x00000007
Registers:
EAX=0x00a9c6b8, EBX=0x02e33930, ECX=0x00a9c6a4, EDX=0x00000001
ESP=0x0303f314, EBP=0x0303f328, ESI=0x00a35f1c, EDI=0xffffffff
EIP=0x6d236a0c, EFLAGS=0x00010286
Top of Stack: (sp=0x0303f314)
0x0303f314: 02e2865c 00a35f1c 02e33930 ffffffff
0x0303f324: 02e2865c 0303f34c 6d236ce8 02e33930
0x0303f334: 00a35f1c 02e33930 02e2865c 02e33930
0x0303f344: 00acaef8 02e34774 0303f378 6d2326be
0x0303f354: 02e33930 00a35f1c 02f13380 00000001
0x0303f364: 00000020 00000000 22fb02e8 22fad0d0
0x0303f374: 00acae38 0303f3a0 00b6a767 02f13380
0x0303f384: 0303f3b8 0303f3b4 00000001 00000020
Instructions: (pc=0x6d236a0c)
0x6d2369fc: 85 ff 89 7d f8 0f 84 16 01 00 00 eb 03 8b 7d f8
0x6d236a0c: d9 47 08 d8 15 50 c0 23 6d 8b 47 04 d9 55 fc 89
Stack: [0x03000000,0x03040000), sp=0x0303f314, free space=252k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [dcpr.dll+0x6a0c]
C [dcpr.dll+0x6ce8]
C [dcpr.dll+0x26be]
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
V [jvm.dll+0x86401]
V [jvm.dll+0xdb172]
V [jvm.dll+0x862d2]
V [jvm.dll+0x8602f]
V [jvm.dll+0xa0bcb]
V [jvm.dll+0x10bdad]
V [jvm.dll+0x10bd7b]
C [MSVCRT.dll+0x2a3b0]
C [kernel32.dll+0xb50b]
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J sun.dc.pr.PathFiller.writeAlpha8([BIII)V
J sun.java2d.pipe.DuctusRenderer.getAlpha(Lsun/dc/pr/Rasterizer;[BIII)V
J sun.java2d.pipe.DuctusShapeRenderer.renderPath(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;Ljava/awt/BasicStroke;)V
J sun.java2d.pipe.DuctusShapeRenderer.fill(Lsun/java2d/SunGraphics2D;Ljava/awt/Shape;)V
J sun.java2d.pipe.PixelToShapeConverter.fillRoundRect(Lsun/java2d/SunGraphics2D;IIIIII)V
J sun.java2d.SunGraphics2D.fillRoundRect(IIIIII)V
J writingplatform.PlatformNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.TextNode.paintComponent(Ljava/awt/Graphics;)V
J writingplatform.PlatformPanel.paintComponent(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paint(Ljava/awt/Graphics;)V
J javax.swing.JComponent.paintWithOffscreenBuffer(Ljavax/swing/JComponent;Ljava/awt/Graphics;IIIILjava/awt/Image;)V
J javax.swing.JComponent.paintDoubleBuffered(Ljavax/swing/JComponent;Ljava/awt/Component;Ljava/awt/Graphics;IIII)Z
J javax.swing.JComponent._paintImmediately(IIII)V
J javax.swing.JComponent.paintImmediately(IIII)V
J javax.swing.RepaintManager.paintDirtyRegions()V
J javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run()V
J java.awt.event.InvocationEvent.dispatch()V
J java.awt.EventQueue.dispatchEvent(Ljava/awt/AWTEvent;)V
J java.awt.EventDispatchThread.pumpOneEventForHierarchy(ILjava/awt/Component;)Z
v ~RuntimeStub::alignment_frame_return Runtime1 stub
j java.awt.EventDispatchThread.pumpEventsForHierarchy(ILjava/awt/Conditional;Ljava/awt/Component;)V+26
j java.awt.EventDispatchThread.pumpEvents(ILjava/awt/Conditional;)V+4
j java.awt.EventDispatchThread.pumpEvents(Ljava/awt/Conditional;)V+3
j java.awt.EventDispatchThread.run()V+9
v ~StubRoutines::call_stub
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x000360c0 JavaThread "DestroyJavaVM" [_thread_blocked, id=696]
=>0x00acae38 JavaThread "AWT-EventQueue-0" [_thread_in_native, id=2716]
0x00ac5530 JavaThread "AWT-Windows" daemon [_thread_in_native, id=3396]
0x00ac50b0 JavaThread "AWT-Shutdown" [_thread_blocked, id=2656]
0x00ac3eb8 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1644]
0x00a6ef28 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=408]
0x00a6dc28 JavaThread "CompilerThread0" daemon [_thread_blocked, id=992]
0x0003fda0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=1756]
0x00a42240 JavaThread "Finalizer" daemon [_thread_blocked, id=2156]
0x00a40d58 JavaThread "Reference Handler" daemon [_thread_blocked, id=328]
Other Threads:
0x00a3e460 VMThread [id=3024]
0x00a702a8 WatcherThread [id=1740]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
def new generation total 576K, used 20K [0x22a70000, 0x22b10000, 0x22f50000)
eden space 512K, 2% used [0x22a70000, 0x22a73220, 0x22af0000)
from space 64K, 12% used [0x22af0000, 0x22af2128, 0x22b00000)
to space 64K, 0% used [0x22b00000, 0x22b00000, 0x22b10000)
tenured generation total 1408K, used 435K [0x22f50000, 0x230b0000, 0x26a70000)
the space 1408K, 30% used [0x22f50000, 0x22fbcd10, 0x22fbce00, 0x230b0000)
compacting perm gen total 8192K, used 388K [0x26a70000, 0x27270000, 0x2aa70000)
the space 8192K, 4% used [0x26a70000, 0x26ad1170, 0x26ad1200, 0x27270000)
ro space 8192K, 67% used [0x2aa70000, 0x2afcd9f8, 0x2afcda00, 0x2b270000)
rw space 12288K, 46% used [0x2b270000, 0x2b813808, 0x2b813a00, 0x2be70000)
Dynamic libraries:
0x00400000 - 0x0040d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.exe
0x7c900000 - 0x7c9b0000      C:\WINDOWS\system32\ntdll.dll
0x7c800000 - 0x7c8f4000      C:\WINDOWS\system32\kernel32.dll
0x77dd0000 - 0x77e6b000      C:\WINDOWS\system32\ADVAPI32.dll
0x77e70000 - 0x77f01000      C:\WINDOWS\system32\RPCRT4.dll
0x77c10000 - 0x77c68000      C:\WINDOWS\system32\MSVCRT.dll
0x6d730000 - 0x6d8c7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\client\jvm.dll
0x77d40000 - 0x77dd0000      C:\WINDOWS\system32\USER32.dll
0x77f10000 - 0x77f57000      C:\WINDOWS\system32\GDI32.dll
0x76b40000 - 0x76b6d000      C:\WINDOWS\system32\WINMM.dll
0x6d2f0000 - 0x6d2f8000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\hpi.dll
0x76bf0000 - 0x76bfb000      C:\WINDOWS\system32\PSAPI.DLL
0x6d700000 - 0x6d70c000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\verify.dll
0x6d370000 - 0x6d38d000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\java.dll
0x6d720000 - 0x6d72f000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\zip.dll
0x6d070000 - 0x6d1d7000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\awt.dll
0x73000000 - 0x73026000      C:\WINDOWS\system32\WINSPOOL.DRV
0x76390000 - 0x763ad000      C:\WINDOWS\system32\IMM32.dll
0x774e0000 - 0x7761d000      C:\WINDOWS\system32\ole32.dll
0x5ad70000 - 0x5ada8000      C:\WINDOWS\system32\uxtheme.dll
0x73760000 - 0x737a9000      C:\WINDOWS\system32\ddraw.dll
0x73bc0000 - 0x73bc6000      C:\WINDOWS\system32\DCIMAN32.dll
0x73940000 - 0x73a10000      C:\WINDOWS\system32\D3DIM700.DLL
0x6d2b0000 - 0x6d2ef000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\fontmanager.dll
0x74720000 - 0x7476b000      C:\WINDOWS\system32\MSCTF.dll
0x7c9c0000 - 0x7d1d5000      C:\WINDOWS\system32\shell32.dll
0x77f60000 - 0x77fd6000      C:\WINDOWS\system32\SHLWAPI.dll
0x773d0000 - 0x774d2000      C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
0x5d090000 - 0x5d127000      C:\WINDOWS\system32\comctl32.dll
0x605d0000 - 0x605d9000      C:\WINDOWS\system32\mslbui.dll
0x77120000 - 0x771ac000      C:\WINDOWS\system32\OLEAUT32.DLL
0x6d530000 - 0x6d543000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\net.dll
0x71ab0000 - 0x71ac7000      C:\WINDOWS\system32\WS2_32.dll
0x71aa0000 - 0x71aa8000      C:\WINDOWS\system32\WS2HELP.dll
0x6d550000 - 0x6d559000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\nio.dll
0x6d230000 - 0x6d253000      C:\Program Files\Java\jdk1.5.0_07\jre\bin\dcpr.dll
VM Arguments:
java_command: writingplatform.Main
Launcher Type: SUN_STANDARD
Environment Variables:
CLASSPATH=C:\Program Files\Java\jre1.5.0_05\lib\ext\QTJava.zip
PATH=C:\Program Files\Microsoft DirectX 9.0 SDK (August 2005)\Utilities\Bin\x86;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\SSH Communications Security\SSH Secure Shell
USERNAME=Wanderer
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 2 Stepping 9, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows XP Build 2600 Service Pack 2
CPU:total 2 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 1047764k(366012k free), swap 2518724k(2059484k free)
vm_info: Java HotSpot(TM) Client VM (1.5.0_07-b03) for windows-x86, built on May 3 2006 01:04:38 by "java_re" with MS VC++ 6.0

This is not your bug, it's Sun's. All you can do is to:
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
On the other hand, if you cannot afford to wait and just
want to find a quick workaround, you will at least need
to find a way to reproduce the bug with a reasonable
frequency. If you are absolutely unable to reproduce it,
just forget it, but still report it to Sun.

How to configure Workflow Notification Mailer for oracle alert in R12

Hi all....,
How to configure Workflow Notfication mailer for oracle Alert in R12. Please provide the complete steps.. Its urgent.. Plz help me..
Regards ,
Madhan

Duplicate thread (please post only once)
plz help me...!!!! Workflow Notification Mailer
plz help me...!!!! Workflow Notification Mailer

How to change workflow for expired qualification in HR Module

Hi,
My question how to change workflow for expired qualification in HR Module.We need to when date is expired tcode OOQA that system will check and that time workflow should be triggred.
I have serached sap help but i am not understand please below mention URL for SAP help
Link: [http://help.sap.com/saphelp_47x200/helpdata/en/ee/f4c9cafbab11d29ea40000e8215202/frameset.htm]
Please explain step by step how to trigrred workflow for expired qualification?
Please this problem is high and try to solve it.
Thx!
Sachin

Hi,
Why do you want to trigger a wflow and what do you want to do with this trigger. Can you give more details of your exact requirements.
But, if you are looking for how to trigger, you can write a small ABAP pgm and schedule it as a job every night. THis job basically reads the table P1000-ENDDA for expiry date and if it reached today, then you can either trigger the wflow with SAP_WAPI_START_WORKFLOW or use SAP_WAPI_CREATE_EVENT to raise your custom event(for Business Obj. BUS7018, i think this is your BO and there are no std events right now, so you will ahve to add your custom event by extending BUS7018 to ZBUS7018).
Hope I am clear and this helps and if you need more details, reply.
venu

How to debug workflow

Similar Messages

Maybe you are looking for