[Messaging, JMS & JBossMQ] - Re: Looking for help with: Error getting JMSServer member in
by sil
Since I cannot seem to edit, posting a few after thoughts here. After a bit of pondering and playing I am leaning towards the problem area being the connection factory. I have tried a few of the ones provided by default. All are in the global JNDI namespace. If I get no additional error if I use either:
ConnectionFactory (class: org.jboss.mq.SpyConnectionFactory)
XAConnectionFactory (class: org.jboss.mq.SpyXAConnectionFactory)
Then I noticed the this JmsXA. I turned it global by adding the tag <use-java-context>false</use-java-context>. I think, hey, it has JMS in the name, maybe it is important:
JmsXA (class: org.jboss.resource.adapter.jms.JmsConnectionFactoryImpl)
I've had it used in an example that runs entirely on JBoss with success, however, Weblogic gives me the error:
javax.naming.NameNotFoundException: JNDI object with [solr/JmsXA] not found:
| JNDI implementation returned null
| at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:125)
| at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
| at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
| at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
| at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:93)
|
It is bound, exists, and names all match correctly, and the jbossall-client.jar is only included once in the classpath. Once again, any direction, help, thoughts, suggestions will be appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160048#4160048
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160048
17 years, 10 months
[JCA/JBoss] - Turning off CachedConnectionManager
by aggarwald
Hi,
I had been getting IllegalStateException when doing Jboss TM suspend and begin, ie, suspend an outer transaction and start a new inner transaction. Exception was:
| [STDERR] java.lang.IllegalStateException: Trying to change transaction TransactionImple < ac, BasicAction: a0359b1:4e3:4734f5c7:fc status: ActionStatus.RUNNING > in enlist!
|
| [STDERR] at org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener.enli
| st(TxConnectionManager.java:525)
|
| [STDERR] at org.jboss.resource.connectionmanager.TxConnectionManager.transactionStarted(TxConnectio
| nManager.java:328)
|
I had posted this question earlier on Jboss Transactions forum but later on I found that this is a JCA issue. Refer to:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=137565
As this is due to "Lazy JCA Enlistment" feature of CachedConnectionManager, can I disable it? If I disable it, can I still do <track-connection-by-tx>? I am willing to pay the cost of losing optimization, provided I don't loose any transaction correctness. If this is something which is already in the documentation out there (checked the jboss jca wiki but couldn't find much), I'll appreciate it if you can point me to it.
Thanks.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4160030#4160030
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4160030
17 years, 10 months