[JBoss JIRA] Created: (JGRP-270) can't get correct values when using jmx.JChannel
by Ivan Martinez (JIRA)
can't get correct values when using jmx.JChannel
------------------------------------------------
Key: JGRP-270
URL: http://jira.jboss.com/jira/browse/JGRP-270
Project: JGroups
Issue Type: Bug
Affects Versions: 2.3 SP1
Reporter: Ivan Martinez
Assigned To: Bela Ban
Attachments: jgroups_jmx_gets.patch
I'm looking at jmx.JChannel class and I found this atributes :
private boolean receive_blocks=false;
private boolean receive_local_msgs=true;
private boolean auto_reconnect=false;
private boolean auto_getstate=false;
String group_name="TestGroup";
The problem when using the object using the constructor jmx.JChannel(JChannel) :
when the object is initialized the values are not initialized using the real channel options.
The get methods use this values instead of using channel.getOpt
The values will be correct only after the set** methodas are called on jmx object.
when the bean is created using jmx.JChannel() constructor and the create() method called then it will works fine, because the real channel will be created inside the bean with the current values.
--
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
19 years, 11 months
[JBoss JIRA] Resolved: (JGRP-171) Dist Lock Manager -- doesnt release locks when a node dies
by Bela Ban (JIRA)
[ http://jira.jboss.com/jira/browse/JGRP-171?page=all ]
Bela Ban resolved JGRP-171.
---------------------------
Resolution: Done
done by releasing locks for crashed members. However, the "owner" argument for lock() needs to be a org.jgroups.Address, otherwise the matching of failed members against lock holders fails !
> Dist Lock Manager -- doesnt release locks when a node dies
> ----------------------------------------------------------
>
> Key: JGRP-171
> URL: http://jira.jboss.com/jira/browse/JGRP-171
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.2.9.1, 2.2.9, 2.2.8
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Priority: Minor
> Fix For: 2.4
>
> Attachments: DistLockTest.java
>
>
> Jgroups Version: 2.2.8
> I wrote a simple test program to acquire a lock on one
> object and release it after a second.
> When I run this program on 2 systems, and kill one
> system immediately after acquiring the lock, the other
> system cannot get a lock on that object and don?t have
> a mechanism to unlock it.
> Please Compile the attached DistLockTest program and
> run on 2 systems, and then kill one system immediately
> after it acquires the lock. The other system cannot
> acquire the lock on that object at all.
--
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
19 years, 11 months
[JBoss JIRA] Closed: (JBMESSAGING-428) Stress tests fail
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-428?page=all ]
Clebert Suconic closed JBMESSAGING-428.
---------------------------------------
Resolution: Done
> Stress tests fail
> -----------------
>
> Key: JBMESSAGING-428
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-428
> Project: JBoss Messaging
> Issue Type: Bug
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.0.1.CR5
>
>
> [junit] main 18:46:45,187 INFO [StressTest] ####################################################### Start IN-VM test: testTopicMultipleReceivers
> [junit] main 18:46:45,187 INFO [ServerManagement] IN-VM TEST
> [junit] main 18:46:45,250 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' to JNDI name 'java:/DefaultDS'
> [junit] main 18:46:45,281 INFO [ServiceContainer] remoting = "socket", serialization = "jboss", database = "mysql"
> [junit] main 18:46:45,593 INFO [ServerPeer] JBoss Messaging 1.0.1.CR3 server [server.0] started
> [junit] main 18:46:45,593 INFO [ConnectionFactory] Connector has leasing enabled, lease period 20000 milliseconds
> [junit] main 18:46:45,593 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] deployed
> [junit] main 18:46:45,609 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' to JNDI name 'java:/JCAConnectionFactory'
> [junit] main 18:46:45,609 INFO [LocalTestServer] server started
> [junit] main 18:46:45,609 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,640 INFO [Queue] Queue[/queue/Queue1] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,640 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,671 INFO [Queue] Queue[/queue/Queue2] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,671 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,687 INFO [Queue] Queue[/queue/Queue3] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,687 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,703 INFO [Queue] Queue[/queue/Queue4] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,703 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,718 INFO [Topic] Topic[/topic/Topic1] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,718 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,734 INFO [Topic] Topic[/topic/Topic2] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,734 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,750 INFO [Topic] Topic[/topic/Topic3] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,750 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,765 INFO [Topic] Topic[/topic/Topic4] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] Thread-90 18:49:42,609 ERROR [TransactionalReceiver] Message is null
> [junit] Thread-82 18:49:47,765 ERROR [Receiver] Message is null
> [junit] Thread-86 18:50:02,140 ERROR [RecoveringReceiver] Message is null
> [junit] Thread-96 18:50:09,000 ERROR [Transactional2PCReceiver] Message is null
> [junit] Thread-94 18:50:32,015 ERROR [Transactional2PCReceiver] Message is null (rollback)
> [junit] Thread-88 18:50:33,937 ERROR [RecoveringReceiver] Message is null
> [junit] Thread-92 18:50:37,828 ERROR [TransactionalReceiver] Message is null
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue1] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue2] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue3] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue4] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic1] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic2] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic3] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic4] stopped
> [junit] main 18:50:37,828 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' from JNDI name 'java:/JCAConnectionFactory'
> [junit] main 18:50:37,828 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] undeployed
> [junit] main 18:50:37,843 INFO [ServerPeer] JMS ServerPeer [server.0] stopped
> [junit] main 18:50:37,843 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' from JNDI name 'java:/DefaultDS'
> [junit] main 18:50:37,843 INFO [LocalTestServer] server stopped
> [junit] main 18:50:37,843 INFO [StressTest] ####################################################### Stop IN-VM test: testTopicMultipleReceivers
> No exception in logs.
--
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
19 years, 11 months
[JBoss JIRA] Updated: (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 updated JBMESSAGING-410:
----------------------------------------
Assignee: Clebert Suconic (was: Ovidiu Feodorov)
> 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: Clebert Suconic
> 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
19 years, 11 months
[JBoss JIRA] Assigned: (JBMESSAGING-428) Stress tests fail
by Clebert Suconic (JIRA)
[ http://jira.jboss.com/jira/browse/JBMESSAGING-428?page=all ]
Clebert Suconic reassigned JBMESSAGING-428:
-------------------------------------------
Assignee: Clebert Suconic (was: Ovidiu Feodorov)
> Stress tests fail
> -----------------
>
> Key: JBMESSAGING-428
> URL: http://jira.jboss.com/jira/browse/JBMESSAGING-428
> Project: JBoss Messaging
> Issue Type: Bug
> Reporter: Ovidiu Feodorov
> Assigned To: Clebert Suconic
> Fix For: 1.0.1.CR5
>
>
> [junit] main 18:46:45,187 INFO [StressTest] ####################################################### Start IN-VM test: testTopicMultipleReceivers
> [junit] main 18:46:45,187 INFO [ServerManagement] IN-VM TEST
> [junit] main 18:46:45,250 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' to JNDI name 'java:/DefaultDS'
> [junit] main 18:46:45,281 INFO [ServiceContainer] remoting = "socket", serialization = "jboss", database = "mysql"
> [junit] main 18:46:45,593 INFO [ServerPeer] JBoss Messaging 1.0.1.CR3 server [server.0] started
> [junit] main 18:46:45,593 INFO [ConnectionFactory] Connector has leasing enabled, lease period 20000 milliseconds
> [junit] main 18:46:45,593 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] deployed
> [junit] main 18:46:45,609 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' to JNDI name 'java:/JCAConnectionFactory'
> [junit] main 18:46:45,609 INFO [LocalTestServer] server started
> [junit] main 18:46:45,609 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,640 INFO [Queue] Queue[/queue/Queue1] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,640 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,671 INFO [Queue] Queue[/queue/Queue2] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,671 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,687 INFO [Queue] Queue[/queue/Queue3] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,687 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,703 INFO [Queue] Queue[/queue/Queue4] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,703 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,718 INFO [Topic] Topic[/topic/Topic1] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,718 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,734 INFO [Topic] Topic[/topic/Topic2] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,734 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,750 INFO [Topic] Topic[/topic/Topic3] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] main 18:46:45,750 INFO [LocalTestServer] deploying queue, fullsize:3000, ps:1000 dc size:1000
> [junit] main 18:46:45,765 INFO [Topic] Topic[/topic/Topic4] started, fullSize=3000, pageSize=1000, downCacheSize=1000
> [junit] Thread-90 18:49:42,609 ERROR [TransactionalReceiver] Message is null
> [junit] Thread-82 18:49:47,765 ERROR [Receiver] Message is null
> [junit] Thread-86 18:50:02,140 ERROR [RecoveringReceiver] Message is null
> [junit] Thread-96 18:50:09,000 ERROR [Transactional2PCReceiver] Message is null
> [junit] Thread-94 18:50:32,015 ERROR [Transactional2PCReceiver] Message is null (rollback)
> [junit] Thread-88 18:50:33,937 ERROR [RecoveringReceiver] Message is null
> [junit] Thread-92 18:50:37,828 ERROR [TransactionalReceiver] Message is null
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue1] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue2] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue3] stopped
> [junit] main 18:50:37,828 INFO [Queue] Queue[/queue/Queue4] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic1] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic2] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic3] stopped
> [junit] main 18:50:37,828 INFO [Topic] Topic[/topic/Topic4] stopped
> [junit] main 18:50:37,828 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=JCAConnectionFactory,service=ConnectionFactoryBinding' from JNDI name 'java:/JCAConnectionFactory'
> [junit] main 18:50:37,828 INFO [ConnectionFactory] [/ConnectionFactory, /XAConnectionFactory, java:/ConnectionFactory, java:/XAConnectionFactory] undeployed
> [junit] main 18:50:37,843 INFO [ServerPeer] JMS ServerPeer [server.0] stopped
> [junit] main 18:50:37,843 INFO [ConnectionFactoryBindingService] Unbound ConnectionManager 'jboss.jca:name=DefaultDS,service=DataSourceBinding' from JNDI name 'java:/DefaultDS'
> [junit] main 18:50:37,843 INFO [LocalTestServer] server stopped
> [junit] main 18:50:37,843 INFO [StressTest] ####################################################### Stop IN-VM test: testTopicMultipleReceivers
> No exception in logs.
--
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
19 years, 11 months
[JBoss JIRA] Assigned: (JBMICROCONT-6) Virtual Deployment Framework
by Scott M Stark (JIRA)
[ http://jira.jboss.com/jira/browse/JBMICROCONT-6?page=all ]
Scott M Stark reassigned JBMICROCONT-6:
---------------------------------------
Assignee: Scott M Stark (was: Dimitris Andreadis)
> Virtual Deployment Framework
> ----------------------------
>
> Key: JBMICROCONT-6
> URL: http://jira.jboss.com/jira/browse/JBMICROCONT-6
> Project: JBoss MicroContainer
> Issue Type: Task
> Components: Deployment
> Reporter: Adrian Brock
> Assigned To: Scott M Stark
> Fix For: JBossMC_2_0_0RC1
>
>
> VDF - Virtual Deployment Framework
> ----------------------------------
> VDF registry
> The VDF registry acts as a helper/registry of the VDF contexts.
> Each deployment is made up a top level VDF context
> which might contain sub VDF contexts.
> It does:
> 1) Unpack subdeployments
> 2) Download remote deployments
> 3) Abstract packed/unpacked
> 4) Allow config/registration of url handlers for things like webdav
> 5) Supplying "directory" lists, cf (3) and (4)
> VDF Context
> The VDF context is a replacement for the DeploymentInfo
> of current JBoss it holds the following information:
> name - a name probably a shorted version of the url
> deployer - the identified structural deployer
> logicalURL - the url presented to the user
> physicalURL - the url where it is really located
> parentVDFContext - any parent VDF context (null when top level)
> subVDFContexts - any subdeployments
> classpath - the urls where classes are located
> metainf - the location of any meta data
> manifest - any manifest information
> classloader - constructed by the classloading deployer
> stats/state - e.g. when deployed, the state of the deployment, any errors, etc
> There will be a set of utility methods that provide
> other access, e.g. get me the metadata url for "ejb-jar.xml"
> VDF Context - extensions
> Each structural component can extend the VDF context
> to add more information
> There will also be a "slot" available for each
> deployment component to associate some data with the deployment.
> Context identification
> ----------------------
> A top level deployment must have a structure deployer
> subdeployments that are not explcitly identifed
> (cf Default SubContext processing) that don't have
> deployers are ignored.
> Explicity identified subdeployments must have a
> structure deployer
> Default SubContext processing
> -----------------------------
> All files in the root of the deployment
> are treated as possible subcontexts
--
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
19 years, 11 months