Modifying *.ds.xml in JBoss produces null ManagedConnectionF

[nivek]

I get the following error when a change is made to my *-ds.xml in JBoss V4 while my Spring app is deployed:

org.springframework.transaction.CannotCreateTransa ctionException: Could not open JDBC Connection for transaction

org.jboss.util.NestedSQLException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null

This error does not occur in other non-spring applications. If I redeploy the application, the problem is resolved.

Is there a way to correct this w/o redeploying?

[nivek]

Please let me know if I can provide any more information. I can't belive that I'm the only one with this problem.

How do I re-enlist my JndiObjectFactoryBean with the newly generated ConnectionFactory once a change is made to the *.ds.xml file while the server is running and the application is deployed?

Any feedback would be greatly appreciated..

[alesj]

How exactly do you use JndiObjectFactoryBean in this case?

[nivek]

Thank you for the repsponse. Here are my config settings.

JndiObjectFactoryBean
<bean id=dataSource class=org.springframework.jndi.JndiObjectFactoryBean>
<property name=jndiName value=java:/OracleDS>


Transaction Manager
<bean id=transactionManager class=org.springframework.transaction.jta.JtaTransactionManager/>

oracle-ds.xml
<local-tx-datasource>
<jndi-name>OracleDS</jndi-name>
<connection-url>jdbc:oracle:thin:@...</connection-url>
<driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
<user-name>user</user-name>
password
<min-pool-size>0</min-pool-size>
<max-pool-size>100</max-pool-size>
<blocking-timeout-millis>5000</blocking-timeout-millis>
<idle-timeout-minutes>15</idle-timeout-minutes>
</local-tx-datasource>

Using Spring 1.2.6 and JBoss 4.0.2 and IBatis in my DAO layer

[alesj]

Hmm .. I believe something similar happened to me also.
Couldn't quite figure it out why this is happening. But I must say I didn't look too hard.

But this is more of "JBoss.com -> JBoss User -> JCA/JBoss" topic.

One would think that when pulling out object from JNDI should have dealt with this.
Is the JOFB caching it?

If you get some positive reply, please let me know.

Sorry couldn't be more helpful.

[nivek]

Boy that sure wasn't the responce I was hoping to get. I can already see Adrian's post in the JCA forum reading "This isn't a %^$# JBoss issue, it's a Spring issue".

What are your thoughts of possibly using a ConnectionFactory proxy to interogate the factory and reinitialize it if lost?

I'm about to say screw it all and just use DBCP and not JBoss connection pooling. :(

[alesj]

I don't think Spring is an issue here.
You could do that with plain JNDI stuff.

[nivek]

I found the solution to my problem. Here is what I had to do to get hot deployment of JNDI objects working in Spring with JBoss:

Add this to the JndiObjectFactoryBean bean
property name="cache" value="false"
property name="proxyInterface" value="javax.sql.DataSource"

[alesj]

Yep, just like I thought.
See my second post: Is the JOFB caching it?

Rgds, Ales

[bluesky1861]

heya, but, how u config the jboss-service.xml file ?

can u give me an example plz :D

[bluesky1861]

my email: [e-mail]

:D :D

[alesj]

Which jboss-service.xml file are we talkin' about?

[bluesky1861]

thx for ur reply :D

default\deploy\application.war\META-INF\jboss-service.xml

i am doing the project with myfaces1.1.1, spring1.2.6 and hibernate3 these days.

thx a lot :D

[alesj]

What has this xml got to do with JBoss/Spring integration?

[bluesky1861]

yeah... it's a deploy problem i think

BTW, where can i find the jboss deployment solution for such a myfaces+spring+hibernate3 based project?

cheers~ :D