Show me the code! – By Davanum Srinivas

April 27, 2009

Crash Analysis/Diagnostics of IBM SDKs for WAS Webcast on May 13, 2009

Filed under: Uncategorized — Davanum Srinivas @ 9:49 am

Invite posted on WAS forum:
http://www.ibm.com/developerworks/forums/thread.jspa?threadID=260362&tstart=0

On 13 May 2009 at 11:00 AM EDT, a WebSphere Support Technical Exchange presentation on Crash Analysis/Diagnostics of IBM SDKs (1.5 & 1.6) for WebSphere Application Server will be delivered by Giribabu Paramkusham, Ajay Bhalodia & Daniel Julin, subject matter experts. An open question and answer session will follow the presentation.

This exchange will include topics on setting up system to gather data required for debugging and analyzing the crash, common crash scenarios, analysis of javacore/system core file, and a review of DumpAnalyzer features to analyze the core file. Presentation will be limited to IBM Java on AIX, Linux and Windows.

Level of Difficulty: Intermediate

Plan to join the meeting 10 minutes early. Presentations typically last for 30-45 minutes followed by a question and answer session. For more information and details on how to participate in this and other free WebSphere Support Technical Exchanges click here.

Date: May 13, 2009

Time: 11:00 AM EDT

For dial-in numbers and web conferencing information, please visit:
[http://www.ibm.com/software/websphere/support/TE/techex_K449908F79981V00.html]

We look forward to seeing you on the webcast.

Leave a Comment »

No comments yet.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Create a free website or blog at WordPress.com.

%d bloggers like this: