Manually Added Server in Existing ALSB/OSB Cluster is Not Starting
(Doc ID 947613.1)
Last updated on NOVEMBER 16, 2023
Applies to:
Oracle Service Bus - Version 2.1 and laterInformation in this document applies to any platform.
Symptoms
After adding a managed server manually into existing ALSB cluster, the below Exception is thrown at server start-up and managed server doesn't start.
ERROR in the server log:
<Oct 2, 2009 2:55:22 PM CDT> <Error> <Deployer> <BEA-149205> <Failed to
initialize the application 'XBus Kernel' due to error java.lang.NullPointerException.
java.lang.NullPointerException
at com.bea.wli.sb.resources.archive.ArchiveResourceConfigManager.initType(ArchiveResourceConfigManager.java:42)
at com.bea.wli.sb.ALSBConfigService.initTypes(ALSBConfigService.java:107)
at com.bea.wli.sb.init.AppListener.__preStart(AppListener.java:129)
at com.bea.wli.sb.init.AppListener.access$000(AppListener.java:73)
at com.bea.wli.sb.init.AppListener$1.run(AppListener.java:102)
Truncated. see log file for complete stacktrace
initialize the application 'XBus Kernel' due to error java.lang.NullPointerException.
java.lang.NullPointerException
at com.bea.wli.sb.resources.archive.ArchiveResourceConfigManager.initType(ArchiveResourceConfigManager.java:42)
at com.bea.wli.sb.ALSBConfigService.initTypes(ALSBConfigService.java:107)
at com.bea.wli.sb.init.AppListener.__preStart(AppListener.java:129)
at com.bea.wli.sb.init.AppListener.access$000(AppListener.java:73)
at com.bea.wli.sb.init.AppListener$1.run(AppListener.java:102)
Truncated. see log file for complete stacktrace
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |