WLS 10.3.3 - BEA-280061 The persistent store could not be deployed

Question

Hi,
We have an application which is using WLS 10.3.3. After installing, whenever we start a managed server, it fails with:
<BEA-280061> <The persistent store "XYZ" could not be deployed: java.io.IOException: [Store:280044]The file store directory "/<PATH TO STORE>/XYZ" does not exist
java.io.IOException: [Store:280044]The file store directory "/<PATH TO STORE>/XYZ" does not exist
     at weblogic.store.io.file.StoreDir.throwIOException(StoreDir.java:173)
     at weblogic.store.io.file.StoreDir.createDirectory(StoreDir.java:226)
     at weblogic.store.admin.FileAdminHandler.prepareCommon(FileAdminHandler.java:158)
     at weblogic.store.admin.FileAdminHandler.prepare(FileAdminHandler.java:104)
     at weblogic.management.utils.GenericManagedService.prepareDeployment(GenericManagedService.java:204)
     at weblogic.management.utils.GenericServiceManager.prepareDeployment(GenericServiceManager.java:121)
     at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:628)
     at weblogic.management.internal.DeploymentHandlerHome.prepareInitialDeployments(DeploymentHandlerHome.java:408)
     at weblogic.management.deploy.internal.DeploymentAdapter$2.doPrepare(DeploymentAdapter.java:98)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:22)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:166)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
On investigation, the data/store directory does exist and the path is correct, but the store name directory does not - so for example if the store is called XYZ, there is no folder XYZ in data/store.
There are no errors in the managed server log at all up until this point.
We can get this working by:
* Starting the Managed server
* It fails
* ShutDown the Managed Server
* Create the folder XYZ using mkdir
* Start the Managed Server (this works)
This is the associated section from the config.xml:
<file-store>
<name>XYZ</name>
<target>manserv-1</target>
</file-store>
This is a four node cluster and this store is deployed to all of the nodes - all four nodes have the same issue.
Obviously I'd like to know why this is happening so we can correct it. I have looked round the web but can't see this particular error anywhere.
Thanks in advance for any help
Edited by: 843385 on Mar 10, 2011 6:03 AM

Answer 1

Make sure the directory to which the file store points in available.
- Target attribute of the file store (The server instances or migratable targets defined in the current domain that are candidates for hosting the
file store. In a clustered environment, a recommended best practice is to target a custom file store to the same migratable target as the migratable
JMS service, so that a member server will not be a single point of failure. A file store can also be configured to automatically migrate from an
unhealthy server instance to a healthy server instance with the help of the server health monitoring services.)
- Directory attribute of the file store (The path name to the file system directory where the file store maintains its data files. When targeting a
file store to a migratable target, the store directory must be accessible from all candidate server members in the migratable target. For highest
availability, you can use a SAN (Storage Area Network) disk.)
Note that a filestore is a singleton service and is targetted to one server in the cluster at a time, in your case manserv-1.
So on the machine where manserv-1 runs you must make sure the directory "/<PATH TO STORE>/XYZ exists.