Igor Kromin |   Consultant. Coder. Blogger. Tinkerer. Gamer.

NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ for more details.
Recently after installing ADF 12c and extending my domain to support ADF applications, I could no longer start my managed server. The 'Unresolved reference to WseeJaxwsFileStore' error kept on coming up every time I'd try to start the server.
 WebLogic managed server log
<Aug 22, 2014 2:25:16 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141266]Parsing failure in config.xml: The following failures occurred:
-- Unresolved reference to WseeJaxwsFileStore by [my_domain]/JMSServers[WseeJaxwsJmsServer_auto_2]/PersistentStore
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:128)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:895)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:572)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:471)
at weblogic.Server.main(Server.java:74)
Caused by: weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- Unresolved reference to WseeJaxwsFileStore by [my_domain]/JMSServers[WseeJaxwsJmsServer_auto_2]/PersistentStore
at weblogic.descriptor.internal.ReferenceManager.resolveReferences(ReferenceManager.java:324)
at weblogic.descriptor.internal.DescriptorImpl.validate(DescriptorImpl.java:457)
at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:268)
at weblogic.management.provider.internal.DescriptorManagerHelper.loadDescriptor(DescriptorManagerHelper.java:81)
at weblogic.management.provider.internal.RuntimeAccessImpl$IOHelperImpl.parseXML(RuntimeAccessImpl.java:704)
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:249)
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:116)
... 7 more
<Aug 22, 2014 2:25:16 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.>
<Aug 22, 2014 2:25:16 PM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<Aug 22, 2014 2:25:16 PM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>

When I checked the config.xml file for my domain, one of the JMS server configurations was indeed referencing the WseeJaxwsFileStore persistent store, however this store did not exist. Instead, the configuration file had the WseeJaxwsFileStore_auto_2 store defined.

The fix was to update the JMS server configuration to use the other persistent store that was already configured in the file like this:


Skip down to comments...
Hope you found this post useful...

...so please read on! I love writing articles that provide beneficial information, tips and examples to my readers. All information on my blog is provided free of charge and I encourage you to share it as you wish. There is a small favour I ask in return however - engage in comments below, provide feedback, and if you see mistakes let me know.

If you want to show additional support and help me pay for web hosting and domain name registration, donations, no matter how small, are always welcome!

Use of any information contained in this blog post/article is subject to this disclaimer.
comments powered by Disqus
Other posts you may like...