BPMN Business Management CMMN Presentations Process Management Service Oriented Architecture (SOA)

Ibm bpm problem determination


ibm bpm problem determination


IBM BPM Problem
Websphere application server architecture
Network deployment concepts
Runtime Flow
Administration flow
Clustered application servers
IBM BPM key databases
o BPEL instances
o BPD instances
● The CMNDB and BPMDB are the runtime databases, which store
process instances information for BPD and BPEL
● The default configuration when creating the BPE container through the
administrative console is CMNDB, but can be changed
More details: https://www.evernote.com/shard/s210/sh/70704404-0d24-42f0-9e1a-
Tuning method
Tuning considerations
Problem determination
Problem analysis
1. review the log file (SystemOut.log, ffdc logs, jvm
2. check product version, search message code with
the product version
3. ibm support assistant, forum, bpm community , tech
notes, …
Reference link: http://www-
Log files and locations
Log or trace file format
– Useful data such as software levels for the WebSphere
Application Server binary files and the IBM Business
Process Manager binary files
– A mix of informational, warning, and error messages
SystemOut.log examples
FFDC (first-failure data capture)
file naming convention:
<server name>_<thread ID>_yy.MM.dd_HH.mm.ss_<unique ID>.txt
and contains information that is relative to the value of
the ffdcRun.properties Level property value
ffdc in logs folder example
ffdc content example
High Performance Extensible Logging (HPEL)
• Performance
– Log and trace events are stored as binary data so performance is substantially
faster than default log and trace framework (basic mode)
– Less impact to systems when trace is enabled
• Extensions
– HPEL includes information about which application each log or trace record is
– When used with cross-component trace, HPEL includes information about which
request each log or trace record is from
– Developers can add their own log or trace record extensions
– HPEL logViewer command enables filtering logs or trace data by extension
name and value
• Filtering
– HPEL logViewer command helps you filter logs and trace data by date, time,
level, and thread ID
High Performance Extensible Logging
HPEL on developerworks:
Problem diagnostic tips
– understanding the system architecture
– timestamp in the log files (eg:
ttps://docs.google.com/spreadsheets/d/1c65eHb8mZTBeva2HOvmyuHv5ksl7UiEW-MLq3LTgzXE/pubhtml )
– count occurrence times of error message
– guest in which context may cause the errors
Kind of data should be collect for
performance-related problem
– Thread dumps
– Heap dumps
– Java gc logging
– Event manager and process monitor
– Custom solution code logging
– Instrumentation logging
Troubleshooting JVM problems
Problem Determination – collect log files
1. verbose gc log, heap memory dump
2. java core files
Troubleshooting JVM problems
Symptoms analysis
1. server crashes
– application server stop or exit unexpectedly
1. hung process
– verify that app server process is running
– threads might be deadlocked
– looping in code
1. out of memory
– errors and exceptions that are logged without process exit
– at times, can process in unexpected process exit
4. performance degradation
– app server might crash and the nodeagent restarts it
– check to see whether the process ID is continually changing
Troubleshooting JVM problems
garbage collection logs
● verbosegc is written to native_stderr.log (ibm jdk), native_stdout.log (sun
solaris, hp-ux java package)
● to enable verbosegc log (http://www-
01.ibm.com/support/docview.wss?uid=swg21114927 )
● tool to visualize http://www.ibm.com/developerworks/java/jdk/tools/gcmv/
Troubleshooting JVM problems
heapdumps and javacores (javadumps, threaddumps)
● heapdumps is dump of all the live objects that are on the java heap
● heapdumps file (phd portable heap dump) – OutOfMemory error located in <profile root> dir
javacore ( javadump, threadump)
● all about java thread present, classes loaded, heap statistics
● javacore is generated automatically by event of java crash or OutOfMemory error
● manually:
o – kill -3 on unix or wsadmin
o cmd>wsadmin
wasdmin>set jvm [$AdminControl completeObjectName type=JVM,process=%1,*] >
wsadmin>$AdminControl invoke $jvm dumpThreads >> %FILENAME%
● <profile root> for ibm jdk
● native_sdout.log solaris and hp-ux native_stdout.log
Troubleshooting JVM problems
root profile location
Troubleshooting JVM problems
memory and heap analysis
● memory analyzer tool
● memory dump diagnostic for java
● ibm heapanalyzer
verbosegc log analysis
● ibm garbage collection and memory visualizer
● ibm pattern modeling and analysis tool for java garbage collector
javacore analysis
● ibm thread and monitor dump analyzer for java
Troubleshooting JVM problems
jvm documents
demo: java -jar
Problem prevention and best practices
– set up monitoring and detect problems
– create and maintain system architecture
– establish baselines (system load time,
response time)
– define a diagnostic collection plan
– create maintenance plan
course materials
ibm knowledge center for trouble shooting http://www-
ibm wait
ibm developer works
analyze java thread dumps

Leave a Comment

Get the BPI Web Feed

Using the HTML code below, you can display this Business Process Incubator page content with the current filter and sorting inside your web site for FREE.

Copy/Paste this code in your website html code:

<iframe src="https://www.businessprocessincubator.com/content/ibm-bpm-problem-determination/?feed=html" frameborder="0" scrolling="auto" width="100%" height="700">

Customizing your BPI Web Feed

You can click on the Get the BPI Web Feed link on any of our page to create the best possible feed for your site. Here are a few tips to customize your BPI Web Feed.

Customizing the Content Filter
On any page, you can add filter criteria using the MORE FILTERS interface:

Customizing the Content Filter

Customizing the Content Sorting
Clicking on the sorting options will also change the way your BPI Web Feed will be ordered on your site:

Get the BPI Web Feed

Some integration examples