Skip to Content
avatar image
Former Member

Netweaver Environment Is Dead

Our netweaver environment (v6.40 on Sun) is seriously broken. The system fails to close down cleanly after stopsap leaving several vserver, kernal J2E, niserver processes running. When these are killed itÂ’s possible to bring up the config tool but any changes are greeted with a log dialogue which has no buttons. The tool will only come up again once the above sequence is repeated.

In the default.0.trc file is the logging related error below. I believe this is the source of the problem but I have no idea what the source of the error is or how to correct the error. Does any one have an idea how to get out of this deep dark hole?

Thanks

Paul

<! LOGHEADER[END]/ >

#1.5#00144F7A2D20000B000000470000179B00043D4C33A6F467#1193297400228#com.sap.engine.services.log_configurator.admin.LogXMLParser##com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(.,.,.,.)#######SAPEngine_System_Thread[impl:5]_23##0#0#Error##Java###Unable to extract the log configuration for component service_webservices_

[EXCEPTION]

#1#com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3) -> com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)

at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:140)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:130)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.processData(LogXMLParser.java:943)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:918)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:897)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.activateLogger(LogConfiguratorServiceFrameImpl.java:249)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:165)

at com.sap.engine.services.log_configurator.LogConfiguratorApplicationServiceFrame.start(LogConfiguratorApplicationServiceFrame.java:55)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

-


at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)

at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:140)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:130)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.processData(LogXMLParser.java:943)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:918)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:897)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.activateLogger(LogConfiguratorServiceFrameImpl.java:249)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:165)

at com.sap.engine.services.log_configurator.LogConfiguratorApplicationServiceFrame.start(LogConfiguratorApplicationServiceFrame.java:55)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)

at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

... 14 more

-


at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:144)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:130)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.processData(LogXMLParser.java:943)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:918)

at com.sap.engine.services.log_configurator.admin.LogXMLParser.extractConfiguration(LogXMLParser.java:897)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.activateLogger(LogConfiguratorServiceFrameImpl.java:249)

at com.sap.engine.services.log_configurator.LogConfiguratorServiceFrameImpl.init(LogConfiguratorServiceFrameImpl.java:165)

at com.sap.engine.services.log_configurator.LogConfiguratorApplicationServiceFrame.start(LogConfiguratorApplicationServiceFrame.java:55)

at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:79)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:150)

Caused by: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)(:main:, row=1, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:139)

at com.sap.engine.lib.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:127)

at com.sap.engine.lib.xml.StandardDOMParser.parse(StandardDOMParser.java:140)

... 12 more

Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 3f, 3f, 3f(:main:, row:1, col:3)

at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2785)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2830)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:229)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342)

at com.sap.engine.lib.xml.parser.DOMParser.parse(DOMParser.java:101)

... 14 more

#

....

MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###31 services have timed out.#

#1.5#00144F7A2D2000000000001900002DEC00043D4E5796111D#1193306593038#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service ssl has timed out > hard reference to service keystore.#

#1.5#00144F7A2D2000000000001B00002DEC00043D4E57961379#1193306593039#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tc.monitoring.logviewer has timed out > hard reference to service jmx.#

#1.5#00144F7A2D2000000000001D00002DEC00043D4E579615D3#1193306593039#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service keystore has timed out > hard reference to service security.#

#1.5#00144F7A2D2000000000001F00002DEC00043D4E57961E46#1193306593041#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service shell has timed out > hard reference to interface security.#

#1.5#00144F7A2D2000000000002100002DEC00043D4E5796210C#1193306593042#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service webdynpro has timed out > hard reference to interface shell.#

#1.5#00144F7A2D2000000000002300002DEC00043D4E5796249E#1193306593043#com.sap.engine.core.service630.container.MemoryContainer##com.sap.engine.core.service630.container.MemoryContainer#######Thread[Thread-1,5,main]##0#0#Error#1#/System/Server#Plain###Service tclmctcculservice_sda has timed out > hard reference to service jmx.#

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 30, 2007 at 12:06 PM

    Sorry mate missed that bit at the top.

    Either your database is broken or some config files are corrupted.

    Most config is stored in the DB, hence the use of config tool to change stuff.

    Try rolling the DB back to just before the problem started.

    Config Tool is the lowest common denominator for connectivity so if it don't work through that, then it's more than likely the DB.

    See if you have you had any recent SAN issues or entries in lost+found etc.

    Might be a case of disk corruption or something.

    Darryl

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 26, 2007 at 10:08 PM

    Hi,

    Try to kill all the processess running using kill -9... reboot the system. startsap and let me know what is doing?

    thanks,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 29, 2007 at 08:28 AM

    Hi Afi C

    Thanks for feedback but unfortunately I've tried the reboot and the log is as above. My impression is that a logging configuration common to all processes is incorrect but identifying the cause is the problem.

    Does any one know how I find out the logging configuration for component 'service_webservices_' ?

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 29, 2007 at 08:31 PM

    Hi,

    Restore your data at this point.

    thanks,

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 30, 2007 at 11:51 AM

    Hi,

    You should use the config tool to view the logging settings for the service.

    Config tool can be started as the <sid>adm in /usr/sap/<SID>/DVEBMGS<SYS#>/j2ee/configtool/configtool.sh

    Best of luck,

    Darryl

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Oct 30, 2007 at 11:55 AM

    The configtool will only come up once and errors when trying to alter any settings.

    The error is in the form of an empty dialog window with the title Log, its not possible to close this window.

    Add comment
    10|10000 characters needed characters exceeded