Error: Failed to find the Connection Factory with JNDI name

[shiloh.jordan]

I randomly get this error when restarting my application server "WFLYCTL0186:   Services which failed to start:      service jboss.ra.deployment."org.jboss.teiid.resource-adapter.file:main_Polls_0008": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.teiid.resource-adapter.file:main_Polls_0008": WFLYJCA0046: Failed to start RA deployment [Polls_0008]"

Sometimes, I can stop and start my application server perfectly fine and then sometimes I receive this error.

Any suggestions?

All help appreciated

[shawkins]

Is there more to the message or preceding messages related to the file resource adapter?

[shiloh.jordan]

2017-10-27 13:37:09,243 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 60)  MSC000001: Failed to start service jboss.ra.deployment."org.jboss.teiid.resource-adapter.file:main_Polls_0008": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.teiid.resource-adapter.file:main_Polls_0008": WFLYJCA0046: Failed to start RA deployment [Polls_0008]

at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$1.run(AbstractResourceAdapterDeploymentService.java:311)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

at org.jboss.threads.JBossThread.run(JBossThread.java:320)

Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Teiid/teiid-9.0.6/modules/system/layers/dv/org/jboss/teiid/resource-adapter/file/main/

at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2019)

at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$AS7RaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)

at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)

at java.lang.Thread.run(Thread.java:748)

Caused by: javax.resource.spi.InvalidPropertyException: ParentDirectory is not set

at org.teiid.resource.adapter.file.FileManagedConnectionFactory.createConnectionFactory(FileManagedConnectionFactory.java:47)

at org.teiid.resource.spi.BasicManagedConnectionFactory.createConnectionFactory(BasicManagedConnectionFactory.java:57)

at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1746)

... 7 more

[rareddy]

Caused by: javax.resource.spi.InvalidPropertyException: ParentDirectory is not set

Check your configuration for File resource adapter and set the above property to an existing location that is reachable from the "SERVER" machine. Sometimes when Designer and Server are not co-located, users try to list their local directory, that WILL NOT work.

[shiloh.jordan]

Hi rareddy,

In my standalone-teiid.xml file, I see the ParentDirectory is set to an existing location that is reachable from the SERVER machine.  I have it set to C:\Users\Administrator\Desktop.   Should it not be set to this?  This is the directory where my text files are stored. 

My other source models that use the same driver class (org.teiid.resource.adapter.file.FileManagedConnectionFactory), have the ParentDirectory set to the same location. Why would it work for those and not the other?

When doing some research, I see a post on this website (https://developer.jboss.org/thread/241099) that states that this might be a bug.  Do you agree?

Thanks,
Shiloh

[rareddy]

use unix style path and see if that goes away.