• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • Ron McLeod
  • paul wheaton
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Devaka Cooray
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
  • Himai Minh
Bartenders:

Pls Help !! Debugging Error Message "Error within Debug UI"

 
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
I am very new to WSAD. I was trying debug a web application. After creating a new "Websphere application server debug" configuration from debug secondary window, when I tried to start debugging I am getting following message

"Error Within Debug UI:"


The log file shows following exception. Please help

!ENTRY org.eclipse.debug.ui 4 120 Mar 14, 2006 15:49:38.240
!MESSAGE Error logged from Debug UI:
!STACK 0
java.lang.reflect.InvocationTargetException: java.lang.NullPointerException
at java.lang.Throwable.<init>(Throwable.java)
at java.lang.Throwable.<init>(Throwable.java)
at java.lang.NullPointerException.<init>(NullPointerException.java:63)
at com.ibm.debug.wsa.internal.core.WSAJavaDebugTarget.createWSAJavaDebugTarget(WSAJavaDebugTarget.java:280)
at com.ibm.debug.wsa.WSADebugPlugin.createWSADebugTarget(WSADebugPlugin.java:171)
at com.ibm.debug.wsa.internal.launcher.WSAAttachLaunchConfigurationDelegate.launch(WSAAttachLaunchConfigurationDelegate.java:137)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:156)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:676)
at org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITools.java:538)
at org.eclipse.debug.ui.DebugUITools$2.run(DebugUITools.java:487)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:101)
[ March 15, 2006: Message edited by: PRK ]
 
pie sneak
Posts: 4727
Mac VI Editor Ruby
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"PRK", we don't have many rules around here but our naming policy is one of them. Not complying with the policy will lead to your account becoming locked. This warning hopefully will prevent that from happening, but some action is required on your part.

Please review the policy here and you can change your Publicly Displayed Name here.
 
Ranch Hand
Posts: 173
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
"PRK", you need to do step-by-step debugging to see what the last command executed successfully was and which command breaks. I have gotten this extremely clueless message for several things (and it doesn't say why). You will get it if you try to pass a null value to a putString, so you need to code for that:
String name = {get the name here};
if (name == null)
name = ""; // or something to that effect
request.putString("appName", name);

I've also gotten the message when my poral is expecting a certain number of objects based on the number of items supposedly loaded but no one thought to ensure that one of the values was not null before handing the process over to me.

And in case you don't know, step-by-step mode is automatic when you first start debug. Take advantage of it. It may be painstaking, but it's a heck of a lot easier hitting F5 thru everything than sitting and staring at code trying to figure out which line in the thousands is causing the problem. It takes a lot less time, too.

Good luck.
 
Rajkishore Pujari
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for replying "Pat Flickner".

I got that error message when I tried to start debugging. Debugger failed to launch after that exception.

Thanks,
 
reply
    Bookmark Topic Watch Topic
  • New Topic