[JBoss JIRA] Assigned: (JBMESSAGING-410) java:/JmsXA in no-tx context does not work the same way as JBossMQ
by Ovidiu Feodorov (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-410?page=all ]
Ovidiu Feodorov reassigned JBMESSAGING-410:
-------------------------------------------
Assignee: Ovidiu Feodorov (was: Clebert Suconic)
> java:/JmsXA in no-tx context does not work the same way as JBossMQ
> ------------------------------------------------------------------
>
> Key: JBMESSAGING-410
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-410
> Project: JBoss Messaging
> Issue Type: Bug
> Components: Configuration and Management
> Affects Versions: 1.0.1.CR2
> Reporter: Elias Ross
> Assigned To: Ovidiu Feodorov
> Priority: Critical
> Fix For: 1.0.1.CR5
>
>
> The same code I wrote that uses java:/JmsXA in a non-transacted environment with JBossMQ does not work with JBoss Messaging. And actually the same code does work correctly with SonicMQ as well, using the JCA adaptor with the Sonic XA connection factory.
> Why allow the use java:/JmsXA without transactions? It makes sense to use a cached connection manager anyway, like you would with a database. And anyway, should be addressed for compatibility.
> The following code *should* successfully send a message to a queue running without a transaction. Currently, it doesn't seem to do anything and no usage warnings are produced.
> QueueConnectionFactory queueCF = (QueueConnectionFactory)new InitialContext.lookup("java:/JmsXA");
> ...
> QueueConnection queueConnection = queueCF.createQueueConnection();
> QueueSession queueSession =
> queueConnection.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
> QueueSender queueSender = queueSession.createSender(queue);
> ObjectMessage om = queueSession.createObjectMessage();
> queueSender.send(om);
> queueSender.close();
> queueSession.close();
> queueConnection.close();
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Created: (JGRP-289) Optimize stacks.xml
by Bela Ban (JIRA)
Optimize stacks.xml
-------------------
Key: JGRP-289
URL: http://jira.jboss.com/jira/browse/JGRP-289
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.3 SP1
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.4
We decided we want 4 configurations in stacks.xml:
1. fc-fast-minimalthreads
2. tcp (copy of the above, with TCP/TCPPING as transport)
3. fc-fast-minimalthreads-sync: alternative to #1, without FC and with message bundling disabled
4. tcp-sync: copy of #2, without FC and with message bundling disabled
* The default stacks (fc-fast and tcp) have FC and message bundling is enabled
* All stacks have FLUSH: because we use the Multiplexer, state transfer requires FLUSH
* VIEW_SYNC will be removed (because we use FLUSH, this is redundant)
* STREAMING_STATE_TRANSFER will be the default state transfer protocol
o STATE_TRANSFER is there, but commented
o According to Vladimir, these 2 protocols can be used interchangeably, the correct setState() and getState() methods will always be called
* For the TCP-based stack
o we use TCP_NIO as transport
o Discovery is TCPPING: we pass the list of hosts as a system property, default is localhost
* Vladimir and I will look at the resulting stacks.xml, and once it is correct, pass it on to Brian and Manik, so it can be tested with clustering and JBossCache
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months
[JBoss JIRA] Created: (JGRP-295) DistributedHashtable and ChannelFactory with XML config file
by Stefan Kassal (JIRA)
DistributedHashtable and ChannelFactory with XML config file
------------------------------------------------------------
Key: JGRP-295
URL: http://jira.jboss.com/jira/browse/JGRP-295
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4
Reporter: Stefan Kassal
Assigned To: Bela Ban
I think I have found an issue with DistributedHashtables (jgroups 2.4CR2)
I have a XML file containing the protocol stack and create a ChannelFactory with that file.
ChannelFactory factory=new JChannelFactory(new File(configFilePathM));
The DistributedHashtable is created with
DistributedHashtable distHashM = new DistributedHashtable(distChannelNameM,factory,channelProps,true,TIMEOUT);
The problem is that the constructor of the DistributedHashtable class which I want to use uses the following:
channel=factory != null ? factory.createChannel(properties) : new JChannel(properties);
That means it always tries to uses the properties to create the channel and you cannot force it to use the configuration of the factory.
This could be solved in a way that you check if the properties is null and if it is you call factory.createChannel()
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
18 years, 4 months