- This topic has 3 replies, 2 voices, and was last updated 15 years, 8 months ago by Loyal Water.
-
AuthorPosts
-
ADP-1MemberWhen I start WAS 6.0 from the servers view in “RUN” mode, as opposed to “DEBUG” mode, I get this error when we do some XML processing.
[3/26/09 9:13:16:148 EDT] 0000002f SystemErr R java.lang.RuntimeException: java.lang.NullPointerException at org.apache.xalan.transformer.TransformerImpl.run(TransformerImpl.java:3456) at com.ibm.debug.xdi.jaxp.xalan.interpreted.DebugTransformerImpl.run(DebugTransformerImpl.java:697) at org.apache.xalan.transformer.TransformerHandlerImpl.endDocument(TransformerHandlerImpl.java:389) at com.ibm.debug.xdi.jaxp.xalan.interpreted.DebugTransformerHandler.endDocument(DebugTransformerHandler.java:157) at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at com.ibm.debug.xdi.jaxp.xalan.interpreted.DebugTransformerHandler.endDocument(DebugTransformerHandler.java:221) at org.apache.xerces.parsers.AbstractSAXParser.endDocument(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityManager.endEntity(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.skipSpaces(Unknown Source) at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
I have seen this before when I start the same server at the command line only when I have debugging enabled. Please note the portion of the stack trace where it shows IBM’s DebugTransformerImpl.
I have verified that when starting from Blue’s servers view that the “Debug” checkbox is unchecked in the WAS console, yet this error persists. If I start from the command line (startserver server1) with debugging off, this works fine (no error).
I am evaluating the use of Blue for my team instead of the regular version and this is one of the issues stopping us from moving forward. (I’m also waiting to hear on the system properties post)
Jay
Loyal WaterMemberJay,
I need you to post your installation details (MyEclipse > Installation Summary > Installation Details) here for me.Also, are you seeing the same error when running was outside blue as well
ADP-1MemberI do not see this error when I run WAS outside of blue, unless WAS is in DEBUG mode. I’m pretty sure there is a bug in WebSphere that causes this error when in debug mode. However, this error occurs when I run WAS inside blue in RUN mode (not debug). Here are the installation details:
*** Date:
Friday, March 27, 2009 1:04:27 PM EDT** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11*** MyEclipse details:
MyEclipse Blue Edition
Version: 7.1.1 Blue
Build id: 7.1.1-Blue-20090310*** Eclipse details:
MyEclipse Blue EditionVersion: 7.1.1 Blue
Build id: 7.1.1-Blue-20090310Eclipse Platform
Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700Eclipse Java Development Tools
Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800Eclipse Graphical Editing Framework GEF
Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400Eclipse RCP
Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800Eclipse Plug-in Development Environment
Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files\Genuitec\MyEclipse 7.1 Blue Edition\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\Program Files\Genuitec\MyEclipse 7.1 Blue Edition\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files\Genuitec\MyEclipse 7.1 Blue Edition\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
C:\Program Files\Genuitec\MyEclipse 7.1 Blue Edition\configuration
-vm
C:\Program Files\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll
Loyal WaterMemberIt’s really hard to say what the problem is, I’d be leaning towards a bug with WebSphere that is effecting startup in different modes.
-
AuthorPosts