[infinispan-issues] [JBoss JIRA] (ISPN-4110) A Custom-store should be able to set dependencies to external resources like datasource-subsystem to prevent from startup problems in server mode

[Wolf-Dieter Fink (JIRA)]

Wolf-Dieter Fink created ISPN-4110:
--------------------------------------

             Summary: A Custom-store should be able to set dependencies to external resources like datasource-subsystem to prevent from startup problems in server mode
                 Key: ISPN-4110
                 URL: https://issues.jboss.org/browse/ISPN-4110
             Project: Infinispan
          Issue Type: Enhancement
    Affects Versions: 7.0.0.Alpha1, 6.0.1.Final, 6.0.0.Final
            Reporter: Wolf-Dieter Fink
            Assignee: Tristan Tarrant


If a custom store is configured like shown below the infinispan system does not know which dependency to set as this is done if a standard *keyed-jdbc-store is used.

So the cache-store implementation class need to take care of the the dependencies during startup.
Also it is possible that the MSC threads are blocked by such initializations and other subsystems are not started until the cache initialization fails.

It should be possible to set a dependency with the store configuration.


Example configuration:
        <replicated-cache name="cache" mode="ASYNC" start="EAGER">
          <expiration interval = "300000" lifespan="525600000000"/>
          <locking isolation="REPEATABLE_READ" acquire-timeout="20000" concurrency-level="500" striping="false"/>
          <transaction mode="NONE"/>
          <store class="org.jboss.loaders.jdbc.stringbased.CustomJdbcStringBasedCacheStore" passivation="false" preload="true" purge="false" shared="true">
            <property name="connectionFactoryClass">org.infinispan.loaders.jdbc.connectionfactory.ManagedConnectionFactory</property>
            <property name="datasourceJndiLocation">java:jboss/datasources/OracleDS</property>
            <property name="databaseType">ORACLE</property>
        ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira