September 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1961) BufferPool platform mbean resources are registered under the wrong parent resource

by Brian Stansberry (JIRA)

BufferPool platform mbean resources are registered under the wrong parent resource ---------------------------------------------------------------------------------- Key: AS7-1961 URL: https://issues.jboss.org/browse/AS7-1961 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.1.0.Beta1 ManagementResourceRegistration bufPool = memPoolRoot.registerSubModel(PathElement.pathElement(NAME), new DescriptionProvider() { ... That "memPoolRoot" should be "bufPoolRoot". -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-3227) Drools is incorrectly expiring events in CLOUD mode

by Edson Tirelli (JIRA)

Drools is incorrectly expiring events in CLOUD mode --------------------------------------------------- Key: JBRULES-3227 URL: https://issues.jboss.org/browse/JBRULES-3227 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.3.0.CR1 Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.2.1.Final, 5.3.0.Final Regression introduced in 5.3.0.CR1. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SECURITY-74) Policy Management Console using JBoss SEAM

by Anil Saldhana (JIRA)

Policy Management Console using JBoss SEAM ------------------------------------------ Key: SECURITY-74 URL: http://jira.jboss.com/jira/browse/SECURITY-74 Project: JBoss Security and Identity Management Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossXACML-Console Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.1 Need for a progressive Policy Management console using JBoss SEAM. The JAXB2 object model provided with JBoss XACML can be used to construct the policies. -- 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

14 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (AS7-1943) HTTP management interface ignores wrong operation in GET request

by Dominik Pospisil (JIRA)

HTTP management interface ignores wrong operation in GET request ---------------------------------------------------------------- Key: AS7-1943 URL: https://issues.jboss.org/browse/AS7-1943 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1 Reporter: Dominik Pospisil Assignee: Brian Stansberry HTTP management interface ignores wrong operation in GET request. I think that ignoring wrong input in public API is wrong idea and should be avoided. Error should be returned instead. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

3
2
0 / 0

[JBoss JIRA] Created: (AS7-1914) Proper description providers for Vault

by Kabir Khan (JIRA)

Proper description providers for Vault -------------------------------------- Key: AS7-1914 URL: https://issues.jboss.org/browse/AS7-1914 Project: Application Server 7 Issue Type: Feature Request Components: Security Reporter: Kabir Khan Assignee: Anil Saldhana Fix For: 7.1.0.Beta1 See https://github.com/jbossas/jboss-as/pull/333 for details. But basically I see some instances where attributes have type=LIST and no value-type -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SECURITY-624) Vault remove method

by Anil Saldhana (JIRA)

Vault remove method ------------------- Key: SECURITY-624 URL: https://issues.jboss.org/browse/SECURITY-624 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: PicketBox Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v4_0_4 My fault. I did not add a remove() method in vault interface. :( -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (AS7-1948) Inconsistent model representation for osgi subsystem

by Thomas Diesler (JIRA)

Inconsistent model representation for osgi subsystem ---------------------------------------------------- Key: AS7-1948 URL: https://issues.jboss.org/browse/AS7-1948 Project: Application Server 7 Issue Type: Bug Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Beta1 There are a number of inconsistencies in the management model {code} [standalone@localhost:9999 /] /subsystem=osgi:read-resource(recursive=true) { "outcome" => "success", "result" => { "activation" => "lazy", "configuration" => {"org.apache.felix.webconsole.internal.servlet.OsgiManager" => {"entries" => {"manager.root" => "jboss-osgi"}}}, "module" => { "org.apache.felix.scr" => { "module" => undefined, "start" => "2" }, "org.apache.felix.log" => { "module" => undefined, "start" => "1" }, "org.jboss.osgi.webapp" => { "module" => undefined, "start" => "3" }, "org.jboss.osgi.http" => { "module" => undefined, "start" => "2" }, "org.apache.felix.metatype" => { "module" => undefined, "start" => "2" }, "org.apache.aries.jmx" => { "module" => undefined, "start" => "2" }, "org.jboss.osgi.blueprint" => { "module" => undefined, "start" => "3" }, "org.apache.aries.util" => {"module" => undefined}, "org.jboss.osgi.logging" => { "module" => undefined, "start" => "1" }, "org.osgi.compendium" => {"module" => undefined}, "org.jboss.osgi.webconsole" => {"module" => undefined}, "org.jboss.logging" => {"module" => undefined}, "org.jboss.as.osgi.configadmin" => { "module" => undefined, "start" => "1" }, "javaee.api" => {"module" => undefined}, "org.jboss.netty" => { "module" => undefined, "start" => "2" }, "org.apache.felix.eventadmin" => { "module" => undefined, "start" => "2" }, "org.jboss.osgi.jmx" => { "module" => undefined, "start" => "2" }, "org.apache.felix.configadmin" => { "module" => undefined, "start" => "1" }, "org.apache.felix.webconsole" => { "module" => undefined, "start" => "2" }, "org.jboss.osgi.xerces" => { "module" => undefined, "start" => "3" }, "org.projectodd.stilts" => { "module" => undefined, "start" => "2" } }, "property" => { "org.osgi.framework.startlevel.beginning" => {"value" => "1"}, "org.osgi.framework.system.packages.extra" => {"value" => "org.apache.commons.logging;version=1.1.1, org.apache.log4j;version=1.2, org.jboss.as.osgi.service;version=7.0, org.jboss.osgi.deployment.interceptor;version=1.0, org.jboss.osgi.spi.capability;version=1.0, org.jboss.osgi.spi.util;version=1.0, org.jboss.osgi.testing;version=1.0, org.jboss.osgi.vfs;version=1.0, org.slf4j;version=1.5.10,"}, "org.jboss.osgi.system.modules" => {"value" => "org.apache.commons.logging, org.apache.log4j, org.jboss.as.osgi, org.slf4j,"} } } } {code} #1 properties should be represented equal for the configuration and framework #2 "module" => undefined does not make sense #3 startlevel should be named 'startlevel' not 'start' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (AS7-1925) Snapshots should not be automatically taken - the current folder already tracks intermediate updates.

by Darran Lofthouse (JIRA)

Snapshots should not be automatically taken - the current folder already tracks intermediate updates. ----------------------------------------------------------------------------------------------------- Key: AS7-1925 URL: https://issues.jboss.org/browse/AS7-1925 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Alpha1, 7.0.2.Final Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 7.1.0.Beta1 For some reason the snapshot folder is being auto populated with snapshots, however the auto backup of config already goes into the current folder which is preserved after each restart. The snapshots should be on-demand when requested and not automatically created. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (AS7-1949) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host.

by u j (JIRA)

JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. ------------------------------------------------------------------------------------------------------------------------------------ Key: AS7-1949 URL: https://issues.jboss.org/browse/AS7-1949 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.2.Final Environment: Windows 7, 64bit Reporter: u j On startup of jboss-as-7.0.2.Final with standalone-preview.xml on Windows 7, many of the following errors ocurr: 07:38:49,167 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. Hence, the startup is very slow. Complete startup log: 07:38:41,173 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA 07:38:41,777 INFO [org.jboss.msc] JBoss MSC version 1.0.1.GA 07:38:41,826 INFO [org.jboss.as] JBoss AS 7.0.2.Final "Arc" starting 07:38:43,876 WARN [org.jboss.as] No security realm defined for native management service, all access will be unrestricted. 07:38:43,948 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) 07:38:43,951 WARN [org.jboss.as] No security realm defined for http management service, all access will be unrestricted. 07:38:43,960 INFO [org.jboss.as.logging] Removing bootstrap log handlers 07:38:43,981 INFO [org.jboss.as.connector.subsystems.datasources] (Controller Boot Thread) Deploying JDBC-compliant driver class org.h2.Driver (version 1.2) 07:38:44,010 INFO [org.jboss.as.clustering.infinispan.subsystem] (Controller Boot Thread) Activating Infinispan subsystem. 07:38:44,061 INFO [org.jboss.as.jacorb] (Controller Boot Thread) Activating JacORB Subsystem 07:38:44,127 INFO [org.jboss.as.naming] (Controller Boot Thread) JBAS011800: Activating Naming Subsystem 07:38:44,138 INFO [org.jboss.as.naming] (MSC service thread 1-9) JBAS011802: Starting Naming Service 07:38:44,144 INFO [org.jboss.as.osgi] (Controller Boot Thread) JBAS011910: Activating OSGi Subsystem 07:38:44,166 INFO [org.jboss.as.security] (Controller Boot Thread) Activating Security Subsystem 07:38:44,172 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.0.Beta2 07:38:44,187 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.0.Beta3 07:38:44,203 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.0.Beta3 07:38:44,455 INFO [org.jboss.as.webservices] (Controller Boot Thread) Activating WebServices Extension 07:38:44,461 INFO [org.apache.catalina.core.AprLifecycleListener] (MSC service thread 1-8) The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\java\jdk1.6.0\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;native 07:38:44,582 INFO [org.jboss.as.ee] (Controller Boot Thread) Activating EE subsystem 07:38:45,342 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.0.Beta3 07:38:46,162 INFO [org.jboss.as.remoting] (MSC service thread 1-8) Listening on /127.0.0.1:9999 07:38:46,165 INFO [org.jboss.as.jmx.JMXConnectorService] (MSC service thread 1-9) Starting remote JMX connector 07:38:46,224 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-16) Starting Coyote HTTP/1.1 on http-127.0.0.1-127.0.0.1-8080 07:38:46,431 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingjournal,bindingsDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingbindings,largeMessagesDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messaginglargemessages,pagingDirectory=C:\java\jboss\jboss-as-7.0.2.Final\standalone\data\messagingpaging) 07:38:46,455 WARNING [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) Security risk! It has been detected that the cluster admin user and password have not been changed from the installation default. Please see the HornetQ user guide, cluster chapter, for instructions on how to do this. 07:38:46,462 INFO [org.jboss.as.connector] (MSC service thread 1-13) Starting JCA Subsystem (JBoss IronJacamar 1.0.3.Final) 07:38:46,505 WARN [jacorb.codeset] (MSC service thread 1-14) Warning - unknown codeset (Cp1252) - defaulting to ISO-8859-1 07:38:46,539 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) Bound data source [java:jboss/datasources/ExampleDS] 07:38:46,556 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) Registered connection factory java:/JmsXA 07:38:46,563 INFO [org.jboss.as.jacorb] (MSC service thread 1-14) CORBA ORB Service Started 07:38:46,567 INFO [org.hornetq.ra.HornetQResourceAdapter] (MSC service thread 1-8) HornetQ resource adaptor started 07:38:46,568 INFO [org.jboss.as.connector.services.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatorhornetq-ra 07:38:46,680 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5455 for CORE protocol 07:38:46,693 INFO [org.hornetq.core.remoting.impl.netty.NettyAcceptor] (MSC service thread 1-7) Started Netty Acceptor version 3.2.3.Final-r${buildNumber} 127.0.0.1:5445 for CORE protocol 07:38:46,695 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) Server is now live 07:38:46,696 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-7) HornetQ Server version 2.2.7.Final (HQ_2_2_7_FINAL_AS7, 121) [1eee8233-e7bc-11e0-aa93-5442495fe54a] started 07:38:46,699 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-15) trying to deploy queue jms.queue.testQueue 07:38:46,711 INFO [org.jboss.as.jacorb] (MSC service thread 1-11) CORBA Naming Service Started 07:38:46,877 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:47,039 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:47,085 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:47,484 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:47,775 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:48,089 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:49,139 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:49,167 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:49,341 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:50,571 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:50,629 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:50,720 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:50,874 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:51,055 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:51,272 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:51,418 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:51,475 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:51,838 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:52,222 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:52,520 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:52,582 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:52,652 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:53,196 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:53,399 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:54,216 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:55,068 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:55,162 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:55,621 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:55,911 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:56,519 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:56,602 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:57,370 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:57,594 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:58,309 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:38:59,792 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:39:00,437 ERROR [org.jboss.remoting.remote] (XNIO NIO Read 1) JBREM00200: Remote connection failed: java.io.IOException: Se ha anulado una conexión establecida por el software en su equipo host. 07:39:00,630 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-15) Bound messaging object to jndi name java:/queue/test 07:39:00,646 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-7) Bound messaging object to jndi name java:/ConnectionFactory 07:39:00,647 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-4) Bound messaging object to jndi name java:/RemoteConnectionFactory 07:39:00,648 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-16) trying to deploy queue jms.topic.testTopic 07:39:00,676 INFO [org.jboss.as.messaging.jms.AS7BindingRegistry] (MSC service thread 1-16) Bound messaging object to jndi name java:/topic/test 07:39:00,694 INFO [org.jboss.as.deployment] (MSC service thread 1-13) Started FileSystemDeploymentService for directory C:\java\jboss\jboss-as-7.0.2.Final\standalone\deployments 07:39:00,772 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 19827ms - Started 126 of 185 services (59 services are passive or on-demand) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-693) Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite

by Richard Achmatowicz (JIRA)

Incorporate MultithreadedTestCase (MTC) usage into JGroups testsuite -------------------------------------------------------------------- Key: JGRP-693 URL: http://jira.jboss.com/jira/browse/JGRP-693 Project: JGroups Issue Type: Task Environment: JGroups testsuite test cases Reporter: Richard Achmatowicz Assigned To: Bela Ban Fix For: 2.7 MultithreadedTestCase (MTC) is an open-source testing framework which supports the writing of multithreaded test cases. It introduces a global tick-counter which provides a deterministic form of thread synchronization, based on the number of times all threads in a test case are blocked. The tool works well ina debugger, unlike other approximate forms of synchronization (e.g. sleep()) This issue concerns using MTC in order to simplify and improve test cases in the JGroups test suite in which concurrency and blocking are at issue. -- 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

14 years, 7 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2011