SOA+OSB in same JVM, continued

Thanks to Manoj for this overview on how to run the osb and soa suite in one jvm.
My machine was almost dying when i wanted to run both the osb server and the soa suite server.
For development this solution is great and it will save you some resources.

After creating the domain and starting up the admin server i faced the next stacktrace and the adminserver won’t start up.

####<Jun 14, 2010 9:28:40 AM CEST> <Critical> <WebLogicServer> <multimedia> <AdminServer> <Main Thread> <<WLS Kernel>> <> <> <1276500520469> <BEA-000386> <Server subsystem failed. Reason: weblogic.descriptor.DescriptorValidateException: The following failures occurred:
-- JMS server or SAF agent UMSJMSServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent UMSJMSServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent wlsbJMSServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent SOAJMSServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent BPMJMSServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent WseeJmsServer is not targeted to the same target as its persistent store
-- JMS server or SAF agent WseeJaxwsJmsServer_auto_2 is not targeted to the same target as its persistent store

Guess the installation mixed up the targets of the jms stores. In my case most of the failed jms stores where targeted to the AdminServer instead of the soa_server1.

I assume this can also be fixed in ‘Select Optional Configuration’ step of the wizard, where we can select the JMS File Store option to modify.
Or edit the file ‘config.xml’ (what i did) located at

<MIDDLEWARE_HOME>\user_projects\domains\soa_osb_domain\config\config.xml

Find the named jms servers, and check the related filestore. They will have different targets. Fix them so they both target the soa_server1 and start the AdminServer again.

Popularity: 9% [?]