[JBoss Messaging] - Re: Lookup for JmsXA returning null
by mskonda
And this is my tx-connection-factory definition:
<!-- JMS XA Resource adapter, use this to get transacted JMS in beans -->
| <tx-connection-factory>
| <jndi-name>JmsXA</jndi-name>
| <use-java-context>false</use-java-context>
| <xa-transaction/>
| <rar-name>jms-ra.rar</rar-name>
| <connection-definition>org.jboss.resource.adapter.jms.JmsConnectionFactory</connection-definition>
| <config-property name="SessionDefaultType" type="java.lang.String">javax.jms.Topic</config-property>
| <config-property name="JmsProviderAdapterJNDI" type="java.lang.String">java:/DefaultJMSProvider</config-property>
| <max-pool-size>20</max-pool-size>
| <security-domain-and-application>JmsXARealm</security-domain-and-application>
| <depends>jboss.messaging:service=ServerPeer</depends>
| </tx-connection-factory>
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056319#4056319
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056319
18Â years, 10Â months
[JBoss Messaging] - Lookup for JmsXA returning null
by mskonda
Probably a silly question, but couldn't figure out why - I've configured JmsXA to be enlisted in Global Name Space and deployed (see below)
20070621 09:00:32.333 INFO [main] ConnectionFactoryBindingService.Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'JmsXA'(): Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'JmsXA'
However, when I do the lookup for publishing a message, I get the CF as null.
| public void publish3() throws Exception
| {
| Connection conn = null;
| try
| {
| ConnectionFactory fac = (ConnectionFactory) initialContext.lookup("JmsXA");
| logger.info("-->got xa conn fact" + fac);
| conn = fac.createConnection();
| logger.info("-->created conns");
| Session xaSession = conn.createSession(false,
| Session.AUTO_ACKNOWLEDGE);
| logger.info("-->created sessions");
| MessageProducer publisher = xaSession.createProducer(XATEST_QUEUE_1_DEST);
| logger.info("-->created pubishers");
| TextMessage message = xaSession.createTextMessage("Hello!");
| logger.info("-->created txtmsgs");
| publisher.send(message);
| }
| catch (Exception e)
| {
| logger.info("Exception in onMessage() " + e.getMessage());
| }
| finally
| {
| closeConnection(conn);
| }
| }
|
I can see the JmsXA bound happily in JNDI View, but can't access though. I'm not sure how and why this happens? Any help appreciated!
/Madhu
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056318#4056318
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056318
18Â years, 10Â months
[JBoss Messaging] - Re: issue with bridge while JBoss starting
by timfox
"JasonHsu" wrote : The most confusing part is the attribute name "SourceProviderLoader" in bridge configuration file.
|
You don't want to touch the SourceProviderLoader dependency in the bridge config. I only used that as an example of something else that uses dendendencies
anonymous wrote :
| I have no idea what attribute name I can use to set the dependancy to a destination. Finally, I found an old post in 2004. It shows the exact answer. Then I add
| <depends>jboss.messaging.destination:service=Queue,name=QueueA</depends>
| | <depends>jboss.messaging.destination:service=Queue,name=QueueB</depends>
| |
|
The thing in the depends is just the service name of the service you want to wait for.
You can find the service names of the services by looking in the service's MBean config file (or looking at the jmx-console).
The service name of queuB (as you discovered) is "jboss.messaging.destination:service=Queue,name=QueueB" - (look in destinations-service.xml)
It's very simple.
anonymous wrote :
| It works fine now if both of the source and target destinations and the bridge are on the same JBoss. However, what I real want to know is that can one or both destinations are on the JBoss other than the bridge and how to config it?
|
AFAIK you can't do remote dependencies
.
Currently the bridge, once started, will retry if the connection goes down. But the connection must be up at the begining.
I can change the code slightly so it retries at startup too.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056311#4056311
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056311
18Â years, 10Â months
[Tomcat, HTTPD, Servlets & JSP] - Code too large for try Statement + JBoss 4.0.1 + Struts
by JbossUserNew786
Hello All,
I have a very Big page with lots of control on it. I am not using any scriplets on JSP page. My whole page consists of struts tags. Just a Presentation logic using struts.
I want to add some more functionality to it. But it gives me error "code too large for try statement ....". If I removed some other part of code from page then it works.
So I come to conclusion that there is some limit on page size.
I have heard that the method cant be more than 64K. As I have one JSP page it automatically gets converted into JSP_Service which in my case may be more than 64K.
To solve this
1] I have divided the JSP code and then used jsp:include But of no use. as finally it would be converted into single service Method.
2] I have put the following line of code into web.xml and also tried to put in Jboss-web.xml. But this also does not work for me.
<jsp-descriptor>
<jsp-param>
<param-name>noTryBlocks</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
Is there any solution for above?
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056310#4056310
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056310
18Â years, 10Â months