Web Application - Security Mechanism Selection
by Darran Lofthouse
Firstly my apologies for sending to three lists but this is a topic that
has a lot of interested parties so I wanted to make sure all were covered.
We are currently working on what is needed for Undertow to be integrated
within AS8 - making good progress with the standard mechanisms as
specified by the servlet specification but now reaching the more complex
configuration scenarios which I wanted to discuss in this e-mail.
The core of Undertow supports multiple authentication mechanisms being
active for a given web application concurrently e.g. Client Cert, Digest
and SPNEGO all at the same time. Some of this is enabled for domain
management already but for web app deployments the initial behaviour is
that a single mechanism is associated based on the web.xml.
So the configuration I am now looking at obtaining some feedback for is: -
- Defining new authentication mechanisms.
- Defining a set of these mechanisms.
- Where these definitions should live, webapp? subsystem? both?
Initially the integration will be with the existing JAAS domains as that
is what exists today, once we have PicketLink available in a subsystem
and the work David is working on regarding identity/request association
then we will also migrate to those as well.
For the moment a web application is also associated with a single
security domain - once we migrate to PicketLink it will be associated
with a single defintion there.
* Historic Configuration *
Up until JBoss AS 6 it was possible for single authentication mechanisms
to be defined within the JBoss Web configuration, within the web.xml the
custom auth-method could then be referenced to enable the new mechanism.
From JBoss AS 7 the authentication mechanisms were defined by defining
the mechanism as a valve within the jboss-web.xml - the presence of the
mechanism was then detected during deployment causing the addition of a
mechanism based on the auth-method to be skipped.
In both cases the jboss-web.xml descriptor is used to associate the web
application with the security domain.
* AS8 Configuration *
Users are already used to providing a lot of their configuration within
the deployments - maybe even including PicketLink definitions where they
do not want to use definitions defined within the AS config.
However I have also seen demand from users to be able to take a ready
built war and deploy it to development or production and have
appropriate security settings defined in each environment.
So for this reason I think we should take the approach of allowing full
security configuration within the deployment but allowing for subsystem
defined overrides to override the defined configuration at deployment time.
I think this leads us to three areas of configuration: -
1 - Mechanism Definition
This would be something simple along the lines of: -
<mechanism auth-method="..." module="..." class="...">
2 - Security Compound
This needs a good name to be selected but the idea is the compound is an
ordered set of authentication mechanisms associated with a domain e.g.
<security-compound name="..." domain="...">
<mechanism auth-method="..." />
<mechanism module="..." class="..." />
</security-compound>
These mechanisms can either be a reference to previously defined
mechanisms or can be a new definition that applies only to that compound.
So far #1 and #2 can either be defined in a subsystem to be referenced
subsequently or if these are defined within the jboss-web.xml descriptor
they will apply to the web application being deployed.
For #1 we will have defined internally the set of standard mechanisms
and maybe a couple of additional mechanisms - the configuration can then
be used to completely replace them with alternative implementations.
3 - Security Overrides
This is something I am considering to live just within a subsystem, one
or more fields are defined to match against web applications as they are
being deployed and if there is a match the specified security-compound
is applied to the web application instead of the definition within it's
deployment descriptors.
<security-override auth-method="..." war-name="..."
security-domain="..." security-override="..." />
The idea being if auth-method, war-name or security-domain match the
values currently defined for the web app being deployed then the
security settings are replaced with the specified security-compound.
A couple of areas that I still need to look into in more details are how
is additional configuration passed to the individual mechanisms
including possible service injection and additional areas to override
from the web.xml such as FORM or role mapping definitions but initially
I want to focus on how the mechanisms are specified and associated and
then build from there to add the additional settings.
* Legacy Valve Support *
I am also working on wrapping existing valves so that they can be used
within Undertow when deployments are deployed to AS8 - however I see
this as an alternative to the mechanisms supported by Undertow.
As a valve would be used for legacy compatibility this would mean that
previous functionality can be retained but moving forwards for better
integration the valve would need to be migrated.
Regards,
Darran Lofthouse.
11 years, 4 months
- 3
- 3
On security context and propagation
by David M. Lloyd
The Problem
===========
In order to support all the Java EE 7 requirements, we need to be able
to propagate security context in a predictable and uniform manner.
Unfortunately, we have almost as many security context concepts as we do
projects which support authentication. There is no single way to
execute a task given a security context snapshot from another thread
that will work for all of our projects.
Project-Specific Security Context
---------------------------------
The typical implementation of a project-specific security context is
just a Subject, cached into a ThreadLocal and available via some
accessors. In addition we have the SecurityRolesAssociation concept
from PicketBox, which is meant to encapsulate roles from an EE perspective.
Available Mechanisms
====================
A number of mechanisms are provided by the JDK and the EE SDK
specifically for addressing this problem domain. Here's a quick review
so we are all speaking the same language.
javax.security.auth.Subject
---------------------------
The focal point for security in both SE and EE is the Subject class,
which is an encapsulation of related information for a security entity,
including credentials (passwords, keys, etc.) and identities (user/group
names, roles, etc.). Most (not all) of our security-aware projects
already seem to use Subject, though they may not all be using it in the
same way.
Subject has some utility methods which are intended to allow association
with the current security context. With these methods you can run tasks
as different Subjects. We currently do not support these methods.
java.security.Principal
-----------------------
The base interface for an identity. Though there are no specific
supported implementations for EE use cases, this interface would be the
base for user names, group names, role names, and so on. JDK Principal
implementations do exist for filesystem users and groups, certificate
signers and principals, JMX authenticated identities, etc.
java.security.AccessControlContext ("ACC")
------------------------------------------
This is *the* JDK-provided security context. It represents the
accumulated privileges of "protection domains", which can in turn
correspond to principals, permissions, and/or code sources (i.e. JARs).
A given ACC, in simplified terms, represents the *intersection* of
privileges granted by all the invocations on the call stack.
It gets a bit complex once you plumb the depths but imagine ACC
conceptually like a second execution stack. Every time you call into
another module, you push another layer on the stack which includes that
module's permission set (which is AllPermission by default, but can be
restricted on a per-module basis). This also includes calling into
deployments. You can also push a Subject on to this stack using
Subject.doAs*().
It is worth emphasizing that the effective permission set for an ACC is
the intersection of all of its parts, so the more calls you make, the
more restricted your permissions are. This is why we use
AccessController.doPrivileged*() and/or Subject.doAsPrivileged(): it
"clears" the stack for the duration of the invocation, adding only the
module which hosts the Privileged*Action class being executed (and
optionally the given Subject as well). This becomes important when you
consider that in many cases, you have no idea under what context a given
piece of code will be run, thus you cannot be certain whether a
restricted operation will succeed without using doPrivileged().
Perhaps the canonical case of this is class initialization. Common
sense would seem to imply that classes should always be initialized in a
privileged context, but that does not seem to be the case in reality.
Thus class init is often stuck with awkward doPrivileged constructs,
especially when field init is involved.
A Unified Security Context
==========================
The ACC affords us a uniquely suited mechanism for security association.
Subjects are already designed to be connected into ACCs; in fact, you
can query an ACC for its associated Subject with a simple get. In turn
the Subject can be queried for its Principals and credentials.
This also gives us saner integration with JAAS, to the extent that such
sanity is possible; users can use the returned Subject with
Subject.doAs() and get the results they would expect in any situation.
Finally ACC is in the JDK - any third-party security-aware framework is
much more likely to integrate with ACC and Subject than with some
framework provided by us. And, the JDK security manager framework is
ready to handle it, so a user security policy could for example forbid
certain Subjects from performing operations as an additional security layer.
Getting the Current Subject
---------------------------
To get the current subject you can do something like this:
Subject current = Subject.getSubject(AccessController.getContext());
This will work from any context - though there is a permission check
involved so a security action is in order in this case.
Propagation Within the AS
-------------------------
We need to do in-system propagation of security context in a few
situations. The predominant one (to me) is using JSR-236 thread pools -
tasks submitted by an EE component must run under the same security
context that the submitter holds.
Fortunately propagation of this nature is quite simple: use
AccessController.getContext() to acquire the current security context,
and use AccessController.doPrivileged() to resume.
Propagation to other components (e.g. EJBs) is a little different
though. In this case you do not want the baggage of the caller ACC; you
only need to preserve the caller Subject. In this case, you would
acquire the Subject as above, and the security interceptor would simply
use Subject.doAs() to resume.
Propagation Over the Network
----------------------------
It should be possible to use Principal information stored on the Subject
in combination with private credentials to provide all the information
required for network propagation of security context. This should work
particularly well with the Remoting authentication service in particular.
One Step Farther: ACC-Based Permission Checking
-----------------------------------------------
It is possible to take this idea a little farther and introduce
permission checking for JACC-style permissions based on the ACC. Using
ACC.checkPermission we can do permission checking regardless of the
presence or absence of a SecurityManager. However, it is not clear what
benefits we would derive from this move (if any).
Costs and Alternatives
======================
ACC is not free. It's a fairly heavyweight structure (though it does
make certain optimizations in some cases), and it contains what is
probably more information than is strictly necessary as it is designed
for full-bore SecurityManager sandboxing and permission checking. Thus
it is worth exploring alternatives.
Alternative: Central Security Context
-------------------------------------
Alternative #1 is to support a central security context represented by a
Subject in one place which all frameworks and libraries share.
Pros: lightweight (as much as possible anyway); conceptually simple
Cons: not compatible Subject.doAs or AccessController.doPrivileged;
additional dependency for all security-aware frameworks; third-party
stuff is less likely to just work
Alternative: ???
----------------
Add your ideas here!
Action
======
I think, barring any major dissent, we should make a move towards using
ACC as a unified security context. I think that given the EE 7 security
manager requirements and user requests over time, that standardizing
around ACC makes sense.
Discussion: go!
--
- DML
11 years, 4 months
- 6
- 21
EL 3
by Rémy Maucherat
Hi,
I reviewed EL 3, and I believe the RI looks more than acceptable
(license is GPL+CDDL - as usual, I think -, with good quality).
The new spec sources (
https://java.net/projects/el-spec/sources/source-code/show/trunk/api/src/...
) could be imported in the EE specs repository (there is no other
compatible EL 3 implementation, so no need to edit or change the
ExpressionFactory implementation loading mechanism), while the
implementation could be used directly as an external dependency, at
least for the time being.
Comments ?
Rémy
11 years, 5 months
- 6
- 9
wildfly-master-testsuite-ip6 - Build # 7354 - Failure!
by ci-builds＠redhat.com
wildfly-master-testsuite-ip6 - Build # 7354 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7354
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
1 tests failed.
FAILED: org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase.org.jboss.as.test.integration.jpa.cfgfile.CfgFileTestCase
Error Message:
Cannot deploy: jpa_cfgfile.jar
11 years, 6 months
- 3
- 3
wildfly-master-testsuite-ip6 - Build # 7345 - Failure!
by ci-builds＠redhat.com
wildfly-master-testsuite-ip6 - Build # 7345 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7345
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
1 tests failed.
REGRESSION: org.jboss.as.test.integration.ejb.timerservice.entity.BMPEntityBeanTimerTestCase.testEntityBeanTimerService
Error Message:
null
11 years, 6 months
- 1
- 0
Problem with ejbStore on as7.2 (jboss-eap 6.1)
by Peter Craddock
I have a set of tests that check the CRUD operation of my application and I have found a problem when ejbStore is called where the real Exception is not being wrapped and sent back to the client.
When the test do an instert (ejbCreate) with a Duplicate Name the exception is thrown on the server and is sent back to the client as a RemoteException that contains a TransactionRolledBackException that then contains my exception as expected. In the update test (ejbStore) is called and the DupliacteNameException is thrown but all the client gets is a TransactionRolledBackException with no cause or detail.
This is a EJB2.1 app that uses BMP
Pete.
________________________________
Advanced Computer Software Group plc
Registered in England at Munro House, Portsmouth Road, Cobham, Surrey, KT11 1TF. Registration number 5965280
Please note that Advanced Computer Software Group plc may monitor email traffic data and also the content of email for the purposes of security and staff training.
This message (and any associated files) is intended only for the use of the stated recipient and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error or are not the intended recipient please notify us immediately by replying to the message or calling 08451 60 61 62 and deleting it from your computer. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
We advise that in keeping with good computing practice the recipient of this email should ensure that it is virus free. We do not accept responsibility for any virus that may be transferred by way of this email.
Email may be susceptible to data corruption, interception and unauthorised amendment, and we do not accept liability for any such corruption, interception or amendment or any consequences thereof.
This email has been scanned for all viruses by the MessageLabs SkyScan service.
Please consider the environment before printing this email
________________________________
11 years, 6 months
- 1
- 0
wildfly-master-testsuite-ip6 - Build # 7342 - Failure!
by ci-builds＠redhat.com
wildfly-master-testsuite-ip6 - Build # 7342 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7342
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
377 tests failed.
FAILED: org.jboss.as.test.compat.jpa.hibernate.Dom4jLoadingTestCase.org.jboss.as.test.compat.jpa.hibernate.Dom4jLoadingTestCase
Error Message:
Cannot deploy: hibernate_dom4j.ear
FAILED: org.jboss.as.test.compat.jpa.hibernate.Hibernate3EmbeddedProviderNullDataSourceTestCase.org.jboss.as.test.compat.jpa.hibernate.Hibernate3EmbeddedProviderNullDataSourceTestCase
Error Message:
Cannot deploy: Hibernate3EmbeddedProviderNullDataSourceTestCase.ear
FAILED: org.jboss.as.test.compat.jpa.hibernate.Hibernate3EmbeddedProviderTestCase.org.jboss.as.test.compat.jpa.hibernate.Hibernate3EmbeddedProviderTestCase
Error Message:
Cannot deploy: hibernate3_test.ear
FAILED: org.jboss.as.test.compat.jpa.hibernate.envers.HibernateEnvers3EmbeddedProviderTestCase.org.jboss.as.test.compat.jpa.hibernate.envers.HibernateEnvers3EmbeddedProviderTestCase
Error Message:
Cannot deploy: hibernate3_test.ear
FAILED: org.jboss.as.test.compat.jpa.hibernate.persistencebootstrap.PersistenceBootstrapTestCase.org.jboss.as.test.compat.jpa.hibernate.persistencebootstrap.PersistenceBootstrapTestCase
Error Message:
Cannot deploy: PersistenceBootstrapTestCase_test.ear
REGRESSION: org.jboss.as.test.integration.domain.ExpressionSupportSmokeTestCase.test
Error Message:
Managed servers were not started within [120] seconds
REGRESSION: org.jboss.as.test.integration.domain.management.cli.BasicOpsTestCase.testDomainSetup
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.BasicOpsTestCase.testWalkRemoteHosts
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.BasicOpsTestCase.testConnect
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.BasicOpsTestCase.testWalkLocalHosts
Error Message:
null
FAILED: org.jboss.as.test.integration.domain.management.cli.DeployAllServerGroupsTestCase.org.jboss.as.test.integration.domain.management.cli.DeployAllServerGroupsTestCase
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverrideWithRedeployAffected
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverrideWithRedeployAffected
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testSimpleOverride
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testWildcardOverride
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testMultipleLinks
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.DomainDeploymentOverlayTestCase.testRedeployAffected
Error Message:
The controller is not available at [::1]:9990
FAILED: org.jboss.as.test.integration.domain.management.cli.DeploySingleServerGroupTestCase.org.jboss.as.test.integration.domain.management.cli.DeploySingleServerGroupTestCase
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployCliTestApps
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployCliTestApps
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAps
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAps
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployAllWars
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployAllWars
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAs
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAs
Error Message:
null
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAWARs
Error Message:
The controller is not available at [::1]:9990
REGRESSION: org.jboss.as.test.integration.domain.management.cli.UndeployWildcardDomainTestCase.testUndeployTestAWARs
Error Message:
null
FAILED: org.jboss.as.test.integration.domain.management.cli.JmsTestCase.org.jboss.as.test.integration.domain.management.cli.JmsTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.domain.management.cli.DataSourceTestCase.org.jboss.as.test.integration.domain.management.cli.DataSourceTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase.org.jboss.as.test.integration.domain.management.cli.RolloutPlanTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.ee.injection.resource.basic.ResourceInjectionTestCase.org.jboss.as.test.integration.ee.injection.resource.basic.ResourceInjectionTestCase
Error Message:
Cannot deploy: resource-injection-test.war
FAILED: org.jboss.as.test.integration.ee.injection.resource.enventry.EnvEntryTestCase.org.jboss.as.test.integration.ee.injection.resource.enventry.EnvEntryTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ee.injection.resource.resourceref.ResourceRefTestCase.org.jboss.as.test.integration.ee.injection.resource.resourceref.ResourceRefTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ee.remotelookup.LookupTestCase.org.jboss.as.test.integration.ee.remotelookup.LookupTestCase
Error Message:
Cannot deploy: deploy.jar
FAILED: org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase.org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingInContainerTestCase
Error Message:
Cannot deploy: test.jar
FAILED: org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase.org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase
Error Message:
Cannot deploy: test.jar
FAILED: org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase.org.jboss.as.test.integration.ejb.management.deployments.EjbInvocationStatisticsTestCase
Error Message:
Cannot deploy: ejb-management.jar
FAILED: org.jboss.as.test.integration.ejb.management.deployments.EjbJarInEarRuntimeResourcesTestCase.org.jboss.as.test.integration.ejb.management.deployments.EjbJarInEarRuntimeResourcesTestCase
Error Message:
Cannot deploy: ejb-management.ear
FAILED: org.jboss.as.test.integration.ejb.management.deployments.EjbJarRuntimeResourcesTestCase.org.jboss.as.test.integration.ejb.management.deployments.EjbJarRuntimeResourcesTestCase
Error Message:
Cannot deploy: ejb-management.jar
FAILED: org.jboss.as.test.integration.ejb.mdb.JMSMessageDrivenBeanTestCase.org.jboss.as.test.integration.ejb.mdb.JMSMessageDrivenBeanTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.MDBTestCase.org.jboss.as.test.integration.ejb.mdb.MDBTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.activationconfig.unit.MDBActivationConfigTestCase.org.jboss.as.test.integration.ejb.mdb.activationconfig.unit.MDBActivationConfigTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.cdi.MDBCdiIntegrationTestCase.org.jboss.as.test.integration.ejb.mdb.cdi.MDBCdiIntegrationTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase.org.jboss.as.test.integration.ejb.mdb.containerstart.SendMessagesTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.dynamic.DynamicMessageListenerTestCase.org.jboss.as.test.integration.ejb.mdb.dynamic.DynamicMessageListenerTestCase
Error Message:
Cannot deploy: ear-with-rar.ear
FAILED: org.jboss.as.test.integration.ejb.mdb.messagedestination.MessageDestinationTestCase.org.jboss.as.test.integration.ejb.mdb.messagedestination.MessageDestinationTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.messagedrivencontext.SetMessageDrivenContextInvocationTestCase.org.jboss.as.test.integration.ejb.mdb.messagedrivencontext.SetMessageDrivenContextInvocationTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.messagelistener.MessageListenerInClassHierarchyTestCase.org.jboss.as.test.integration.ejb.mdb.messagelistener.MessageListenerInClassHierarchyTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.objectmessage.unit.ObjectMessageTestCase.org.jboss.as.test.integration.ejb.mdb.objectmessage.unit.ObjectMessageTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.resourceadapter.ConfiguredResourceAdapterNameTestCase.org.jboss.as.test.integration.ejb.mdb.resourceadapter.ConfiguredResourceAdapterNameTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.resourceadapter.DeploymentPackagedRATestCase.org.jboss.as.test.integration.ejb.mdb.resourceadapter.DeploymentPackagedRATestCase
Error Message:
Cannot deploy: ear-containing-rar.ear
FAILED: org.jboss.as.test.integration.ejb.mdb.resourceadapter.ResourceAdapterNameTestCase.org.jboss.as.test.integration.ejb.mdb.resourceadapter.ResourceAdapterNameTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.mdb.timerservice.SimpleTimerMDBTestCase.org.jboss.as.test.integration.ejb.mdb.timerservice.SimpleTimerMDBTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.pool.lifecycle.PooledEJBLifecycleTestCase.org.jboss.as.test.integration.ejb.pool.lifecycle.PooledEJBLifecycleTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.pool.override.PoolOverrideTestCase.org.jboss.as.test.integration.ejb.pool.override.PoolOverrideTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase.org.jboss.as.test.integration.ejb.security.AnnotationAuthorizationTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.AuthenticationTestCase.org.jboss.as.test.integration.ejb.security.AuthenticationTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.EJBSecurityTestCase.org.jboss.as.test.integration.ejb.security.EJBSecurityTestCase
Error Message:
Cannot deploy: ejb-security-test.jar
FAILED: org.jboss.as.test.integration.ejb.security.InherritanceAnnSFSBTestCase.org.jboss.as.test.integration.ejb.security.InherritanceAnnSFSBTestCase
Error Message:
Cannot deploy: inherritanceAnnOnlySFSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.InherritanceAnnSLSBTestCase.org.jboss.as.test.integration.ejb.security.InherritanceAnnSLSBTestCase
Error Message:
Cannot deploy: inherritanceAnnOnlySLSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.InjectionAnnSFSBtoSFSBTestCase.org.jboss.as.test.integration.ejb.security.InjectionAnnSFSBtoSFSBTestCase
Error Message:
Cannot deploy: injectionAnnOnlySFSBtoSFSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.InjectionAnnSFSBtoSLSBTestCase.org.jboss.as.test.integration.ejb.security.InjectionAnnSFSBtoSLSBTestCase
Error Message:
Cannot deploy: injectionAnnOnlySFSBtoSLSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.InjectionAnnSLSBtoSFSBTestCase.org.jboss.as.test.integration.ejb.security.InjectionAnnSLSBtoSFSBTestCase
Error Message:
Cannot deploy: injectionAnnOnlySLSBtoSFSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.InjectionAnnSLSBtoSLSBTestCase.org.jboss.as.test.integration.ejb.security.InjectionAnnSLSBtoSLSBTestCase
Error Message:
Cannot deploy: injectionAnnOnlySLSBtoSLSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.LifecycleTestCase.org.jboss.as.test.integration.ejb.security.LifecycleTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.MDBRoleTestCase.org.jboss.as.test.integration.ejb.security.MDBRoleTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.RunAsPrincipalTestCase.org.jboss.as.test.integration.ejb.security.RunAsPrincipalTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase.org.jboss.as.test.integration.ejb.security.SecurityDDOverrideTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSFSBTestCase.org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSFSBTestCase
Error Message:
Cannot deploy: singleMethodsAnnOnlySFSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSLSBTestCase.org.jboss.as.test.integration.ejb.security.SingleMethodsAnnSLSBTestCase
Error Message:
Cannot deploy: singleMethodsAnnOnlySLSB.jar
FAILED: org.jboss.as.test.integration.ejb.security.asynchronous.AsynchronousSecurityTestCase.org.jboss.as.test.integration.ejb.security.asynchronous.AsynchronousSecurityTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase.org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalWithNoDefaultSecurityDomainTestCase.org.jboss.as.test.integration.ejb.security.callerprincipal.GetCallerPrincipalWithNoDefaultSecurityDomainTestCase
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.jbossappxml.JBossAppXMLSecurityTestCase.org.jboss.as.test.integration.ejb.security.jbossappxml.JBossAppXMLSecurityTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsDefaultAllowedTestCase.org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsDefaultAllowedTestCase
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsTestCase.org.jboss.as.test.integration.ejb.security.missingmethodpermission.MissingMethodPermissionsTestCase
Error Message:
Cannot deploy: missing-method-permissions-test-app.ear
FAILED: org.jboss.as.test.integration.ejb.security.rolelink.SecurityRoleLinkTestCase.org.jboss.as.test.integration.ejb.security.rolelink.SecurityRoleLinkTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.runas.RunAsTestCase.org.jboss.as.test.integration.ejb.security.runas.RunAsTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.runas.mdb.RunAsMDBUnitTestCase.org.jboss.as.test.integration.ejb.security.runas.mdb.RunAsMDBUnitTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.ejb.security.singleton.SingletonSecurityTestCase.org.jboss.as.test.integration.ejb.security.singleton.SingletonSecurityTestCase
Error Message:
Cannot deploy: ejb3-singleton-security.jar
FAILED: org.jboss.as.test.integration.jca.security.DsWithSecurityDomainTestCase.org.jboss.as.test.integration.jca.security.DsWithSecurityDomainTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.jca.security.RaWithSecurityDomainTestCase.org.jboss.as.test.integration.jca.security.RaWithSecurityDomainTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.management.cli.HelpTestCase.org.jboss.as.test.integration.management.cli.HelpTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.management.cli.JmsTestCase.org.jboss.as.test.integration.management.cli.JmsTestCase
Error Message:
null
FAILED: org.jboss.as.test.integration.messaging.mgmt.AddressControlManagementTestCase.org.jboss.as.test.integration.messaging.mgmt.AddressControlManagementTestCase
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.AddressSettingsTestCase.testAddressSettingWrite
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.ConnectionFactoryManagementTestCase.testWriteDiscoveryGroupAttributeWhenConnectorIsAlreadyDefined
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase.org.jboss.as.test.integration.messaging.mgmt.CoreQueueManagementTestCase
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testChangeMessagePriority
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testChangeMessagePriority
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testListAndCountMessages
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testListAndCountMessages
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testAddJndi
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testAddJndi
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageCounters
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageCounters
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageMovement
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageMovement
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageRemoval
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testMessageRemoval
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testListConsumers
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testListConsumers
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testPauseAndResume
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSQueueManagementTestCase.testPauseAndResume
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListAllSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListAllSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testAddJndi
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testAddJndi
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListAllSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListAllSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListNonDurableSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListNonDurableSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListNonDurableSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListNonDurableSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListDurableSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListDurableSubscriptionsAsJSON
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testCountMessagesForSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testCountMessagesForSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListMessagesForSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListMessagesForSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testDropAllSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testDropAllSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testDropDurableSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testDropDurableSubscription
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListDurableSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.mgmt.JMSTopicManagementTestCase.testListDurableSubscriptions
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testFailedAuthenticationBlankUserPass
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testUnsuccessfulAuthorization
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testDefaultClusterUser
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testFailedAuthenticationBadUserPass
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testSuccessfulAuthorization
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
REGRESSION: org.jboss.as.test.integration.messaging.security.SecurityTestCase.testSuccessfulAuthentication
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
FAILED: org.jboss.as.test.integration.messaging.xmldeployment.DeployedXmlJMSManagementTestCase.org.jboss.as.test.integration.messaging.xmldeployment.DeployedXmlJMSManagementTestCase
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.messaging.xmldeployment.DeployedXmlJMSTestCase.org.jboss.as.test.integration.messaging.xmldeployment.DeployedXmlJMSTestCase
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.naming.remote.ejb.RemoteNamingEjbTestCase.org.jboss.as.test.integration.naming.remote.ejb.RemoteNamingEjbTestCase
Error Message:
Cannot deploy: test.jar
FAILED: org.jboss.as.test.integration.naming.remote.multiple.MultipleClientRemoteJndiTestCase.org.jboss.as.test.integration.naming.remote.multiple.MultipleClientRemoteJndiTestCase
Error Message:
Cannot deploy: two.war
FAILED: org.jboss.as.test.integration.naming.remote.multiple.NestedRemoteContextTestCase.org.jboss.as.test.integration.naming.remote.multiple.NestedRemoteContextTestCase
Error Message:
Cannot deploy: ejb.ear
FAILED: org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase.org.jboss.as.test.integration.naming.remote.simple.RemoteNamingTestCase
Error Message:
Cannot deploy: test.jar
FAILED: org.jboss.as.test.integration.web.security.basic.WebSecurityBASICTestCase.org.jboss.as.test.integration.web.security.basic.WebSecurityBASICTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.web.security.cert.WebSecurityCERTTestCase.org.jboss.as.test.integration.web.security.cert.WebSecurityCERTTestCase
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.web.security.form.WebSecurityFORMTestCase.org.jboss.as.test.integration.web.security.form.WebSecurityFORMTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.web.security.form.WebSecurityJBossSimpleRoleMappingTestCase.org.jboss.as.test.integration.web.security.form.WebSecurityJBossSimpleRoleMappingTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.web.security.servlet3.WebSecurityProgrammaticLoginTestCase.org.jboss.as.test.integration.web.security.servlet3.WebSecurityProgrammaticLoginTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.web.security.tg.TransportGuaranteeTestCase.org.jboss.as.test.integration.web.security.tg.TransportGuaranteeTestCase
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.clustering.cluster.ejb2.invalidation.CacheInvalidationTestCase(SYNC-tcp).testCacheInvalidation
Error Message:
The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase(SYNC-tcp).testClusteredStatefulTimeout
Error Message:
Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase(SYNC-tcp).testStatefulTimeout
Error Message:
Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase(SYNC-tcp).testNested
Error Message:
Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.StatefulTimeoutTestCase(SYNC-tcp).testStatefulBeanNotDiscardedWhileInTransaction
Error Message:
null
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase(SYNC-tcp).testAnnotationBasedClusteredBeanDeployment
Error Message:
Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.deployment.ClusteredBeanDeploymentTestCase(SYNC-tcp).testDDBasedClusteredBeanDeployment
Error Message:
Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.descriptor.disable.DisableClusteredTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.descriptor.disable.DisableClusteredTestCase(SYNC-tcp).testStatefulBean
Error Message:
Failed to create proxy
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.descriptor.disable.DisableClusteredTestCase(SYNC-tcp).testStatelessBean
Error Message:
EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:not-creating-cluster-dd, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@355c70
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.security.FailoverWithSecurityTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.security.FailoverWithSecurityTestCase(SYNC-tcp).testDomainSecurityAnnotation
Error Message:
EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:cluster-security-domain-test, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@16fa1ee
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.stateful.remote.failover.dd.RemoteEJBClientDDBasedSFSBFailoverTestCase(SYNC-tcp).testRemoteClientFailoverOnShutdown
Error Message:
Failed to create proxy
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testSecondLevelCache
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@2ef2be
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testBasicXPC
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@db2a1
REGRESSION: org.jboss.as.test.clustering.cluster.ejb3.xpc.StatefulWithXPCFailoverTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@9ad258
REGRESSION: org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@ac78ec
REGRESSION: org.jboss.as.test.clustering.cluster.jsf.JSFFailoverTestCase(SYNC-tcp).testUndeploy
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testStartCacheContainer
Error Message:
null
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testDistributedCache
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1886b5f
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testReplicatedCache
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@18367ac
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testLocalCache
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1244fff
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testInvalidationCache
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1031ba1
REGRESSION: org.jboss.as.test.clustering.cluster.management.CacheTestCase(SYNC-tcp).testStopContainers
Error Message:
null
REGRESSION: org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.singleton.SingletonTestCase(SYNC-tcp).testSingletonService
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@8be055
REGRESSION: org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSerialized
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@145938c
REGRESSION: org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testSessionReplication
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@16903c0
REGRESSION: org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnUndeploy
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@9075a
REGRESSION: org.jboss.as.test.clustering.cluster.web.ClusteredWebSimpleTestCase(SYNC-tcp).testGracefulServeOnShutdown
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@c202ae
REGRESSION: org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1bb66d9
REGRESSION: org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@746115
REGRESSION: org.jboss.as.test.clustering.cluster.web.DistributionWebFailoverTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1e56017
REGRESSION: org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@182f72b
REGRESSION: org.jboss.as.test.clustering.cluster.web.GranularWebFailoverTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.NonHaWebSessionPersistenceTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-single must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.NonHaWebSessionPersistenceTestCase(SYNC-tcp).testSessionPersistence
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@14e97a1
REGRESSION: org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase(SYNC-tcp).testGracefulSimpleFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@6dd488
REGRESSION: org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase(SYNC-tcp).testGracefulUndeployFailover
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@189b0fd
REGRESSION: org.jboss.as.test.clustering.cluster.web.ReplicationWebFailoverTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).test
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1870f8c
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.CoarseSessionExpirationTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).test
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@100936d
REGRESSION: org.jboss.as.test.clustering.cluster.web.expiration.FineSessionExpirationTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).test
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@efdd8b
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.CoarseSessionPassivationTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).testSetup
Error Message:
Deployment with name deployment-0 could not be deployed. Container container-0 must be started first.
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).test
Error Message:
Provider for type class java.net.URL returned a null value: org.jboss.arquillian.container.test.impl.enricher.resource.URLResourceProvider@1190390
REGRESSION: org.jboss.as.test.clustering.cluster.web.passivation.FineSessionPassivationTestCase(SYNC-tcp).testCleanup
Error Message:
Deployment with name deployment-0 could not be undeployed. Container container-0 must be still running.
FAILED: org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase.org.jboss.as.test.iiop.basic.BasicIIOPInvocationTestCase
Error Message:
Arquillian has previously been attempted initialized, but failed. See cause for previous exception
FAILED: org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase.org.jboss.as.test.iiop.security.IIOPSecurityInvocationTestCase
Error Message:
Arquillian has previously been attempted initialized, but failed. See cause for previous exception
FAILED: org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase.org.jboss.as.test.iiop.transaction.TransactionIIOPInvocationTestCase
Error Message:
The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
REGRESSION: org.jboss.as.test.manualmode.ejb.client.cluster.EJBClientClusterConfigurationTestCase.testServerToServerClusterFormation
Error Message:
Cannot deploy: server-to-server-clustered-ejb-invocation.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerRestarts
Error Message:
Cannot deploy: server-two-module.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.client.outbound.connection.RemoteOutboundConnectionReconnectTestCase.testRemoteServerStartsLate
Error Message:
Cannot deploy: server-two-module.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.testReconnection
Error Message:
Cannot deploy: ejbclientreconnection.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.client.reconnect.EJBClientReconnectionTestCase.testReconnectionWithClientAPI
Error Message:
Cannot deploy: ejbclientreconnection.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.shutdown.RemoteCallWhileShuttingDownTestCase.testServerShutdownRemoteCall
Error Message:
Cannot deploy: dep1.jar
REGRESSION: org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase.testStatefulBeanAsync
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase.testStatefulBean
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase.testStatelessBeanAsync
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase.testStatelessBean
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
FAILED: org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase.org.jboss.as.test.manualmode.ejb.ssl.SSLEJBRemoteClientTestCase
Error Message:
newValue is null
REGRESSION: org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredProductVersion
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.layered.LayeredDistributionTestCase.testLayeredDeployment
Error Message:
Cannot deploy: test-deployment.war
REGRESSION: org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase.logAfterReload
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.logging.Log4jAppenderTestCase.logAfterReload
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testActiveBackupReload
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testPassiveBackupReload
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testBackupActivation
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testLiveReload
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.messaging.HornetQBackupActivationTestCase.testBackupFailoverAfterFailback
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://localhost:9990. The connection timed out
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.start
Error Message:
Cannot deploy: bogus.jar
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneFullHaXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test702HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneJtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test701StandaloneHAXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test701StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneFullXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneMinimalisticXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneFullHAXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneJtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneFullHaXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test700StandaloneHAXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneFullHaXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test700HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneFullXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneFullXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneOsgiOnlyXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneFullHaXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneOsgiOnlyXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneJtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test702StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test702StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneJtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneHornetqColocatedXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test701StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneHAXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test702DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneFullXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test701DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testHostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test700StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test701HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test700DomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneHornetQCollocatedXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneJtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneHornetQCollocatedXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testDomainXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710StandaloneMinimalisticXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneMinimalisticXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneMinimalisticXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneMinimalisticXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test710HostXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneOsgiOnlyXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneHornetQCollocatedXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneXtsXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test712StandaloneFullXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test711StandaloneXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneOsgiOnlyXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.testStandaloneOSGiXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test713StandaloneHornetQCollocatedXml
Error Message:
null
REGRESSION: org.jboss.as.test.manualmode.parse.ParseAndMarshalModelsTestCase.test702StandaloneHAXml
Error Message:
null
FAILED: org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase.org.jboss.as.test.multinode.remotecall.RemoteLocalCallTestCase
Error Message:
Arquillian has previously been attempted initialized, but failed. See cause for previous exception
FAILED: org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase.org.jboss.as.test.multinode.remotecall.scoped.context.DynamicJNDIContextEJBInvocationTestCase
Error Message:
The server is already running! Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. Please stop server before running or change to another type of container. To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration
FAILED: org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase.org.jboss.as.test.multinode.transaction.TransactionInvocationTestCase
Error Message:
Arquillian has previously been attempted initialized, but failed. See cause for previous exception
FAILED: org.jboss.as.test.integration.osgi.cdi.ManagedBeansTestCase.org.jboss.as.test.integration.osgi.cdi.ManagedBeansTestCase
Error Message:
Cannot deploy: osgi-cdi-test
FAILED: org.jboss.as.test.integration.osgi.classloading.BundleNestedInEarTestCase.org.jboss.as.test.integration.osgi.classloading.BundleNestedInEarTestCase
Error Message:
Cannot deploy: nested-bundle-as-lib.ear
FAILED: org.jboss.as.test.integration.osgi.classloading.BundleNestedInWarTestCase.org.jboss.as.test.integration.osgi.classloading.BundleNestedInWarTestCase
Error Message:
Cannot deploy: as945.war
FAILED: org.jboss.as.test.integration.osgi.classloading.LogServiceDynamicImportTestCase.org.jboss.as.test.integration.osgi.classloading.LogServiceDynamicImportTestCase
Error Message:
Cannot deploy: dynamic-logservice
FAILED: org.jboss.as.test.integration.osgi.classloading.LogServiceStaticImportTestCase.org.jboss.as.test.integration.osgi.classloading.LogServiceStaticImportTestCase
Error Message:
Cannot deploy: static-logservice
FAILED: org.jboss.as.test.integration.osgi.classloading.ModuleRegistrationTestCase.org.jboss.as.test.integration.osgi.classloading.ModuleRegistrationTestCase
Error Message:
Cannot deploy: example-module-reg
FAILED: org.jboss.as.test.integration.osgi.classloading.OptionalImportTestCase.org.jboss.as.test.integration.osgi.classloading.OptionalImportTestCase
Error Message:
Cannot deploy: optional-import-tests
FAILED: org.jboss.as.test.integration.osgi.classloading.SystemPackagesTestCase.org.jboss.as.test.integration.osgi.classloading.SystemPackagesTestCase
Error Message:
Cannot deploy: test-bundle
FAILED: org.jboss.as.test.integration.osgi.classloading.VersionRangeImportTestCase.org.jboss.as.test.integration.osgi.classloading.VersionRangeImportTestCase
Error Message:
Cannot deploy: version-range-tests
FAILED: org.jboss.as.test.integration.osgi.configadmin.ConfigAdminIntegrationTestCase.org.jboss.as.test.integration.osgi.configadmin.ConfigAdminIntegrationTestCase
Error Message:
Cannot deploy: osgi-configadmin-tests
FAILED: org.jboss.as.test.integration.osgi.configadmin.ConfigAdminTestCase.org.jboss.as.test.integration.osgi.configadmin.ConfigAdminTestCase
Error Message:
Cannot deploy: configadmin.jar
FAILED: org.jboss.as.test.integration.osgi.configadmin.ConfigurationAdminTestCase.org.jboss.as.test.integration.osgi.configadmin.ConfigurationAdminTestCase
Error Message:
Cannot deploy: osgi-configadmin
FAILED: org.jboss.as.test.integration.osgi.core.BundleLifecycleTestCase.org.jboss.as.test.integration.osgi.core.BundleLifecycleTestCase
Error Message:
Cannot deploy: example-bundle
FAILED: org.jboss.as.test.integration.osgi.core.BundleStorageTestCase.org.jboss.as.test.integration.osgi.core.BundleStorageTestCase
Error Message:
Cannot deploy: storage-testcase
FAILED: org.jboss.as.test.integration.osgi.core.StartLevelTestCase.org.jboss.as.test.integration.osgi.core.StartLevelTestCase
Error Message:
Cannot deploy: startlevel-testcase
FAILED: org.jboss.as.test.integration.osgi.deployment.ArquillianDeployerTestCase.org.jboss.as.test.integration.osgi.deployment.ArquillianDeployerTestCase
Error Message:
Cannot deploy: example-arquillian-deployer
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleDeploymentCaseOneTestCase.org.jboss.as.test.integration.osgi.deployment.BundleDeploymentCaseOneTestCase
Error Message:
Cannot deploy: bundle-deployment-case-one
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleDeploymentCaseTwoTestCase.org.jboss.as.test.integration.osgi.deployment.BundleDeploymentCaseTwoTestCase
Error Message:
Cannot deploy: bundle-deployment-casetwo
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleRefreshTestCase.org.jboss.as.test.integration.osgi.deployment.BundleRefreshTestCase
Error Message:
Cannot deploy: deployment-refresh-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleReplaceTestCase.org.jboss.as.test.integration.osgi.deployment.BundleReplaceTestCase
Error Message:
Cannot deploy: deployment-replace-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleUninstallTestCase.org.jboss.as.test.integration.osgi.deployment.BundleUninstallTestCase
Error Message:
Cannot deploy: deployment-uninstall-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.BundleUpdateTestCase.org.jboss.as.test.integration.osgi.deployment.BundleUpdateTestCase
Error Message:
Cannot deploy: deployment-update-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.DeferredResolveTestCase.org.jboss.as.test.integration.osgi.deployment.DeferredResolveTestCase
Error Message:
Cannot deploy: deferred-resolve-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.DeploymentMarkerTestCase.org.jboss.as.test.integration.osgi.deployment.DeploymentMarkerTestCase
Error Message:
Cannot deploy: deploymentmarker-tests
FAILED: org.jboss.as.test.integration.osgi.deployment.LegacyBundleTestCase.org.jboss.as.test.integration.osgi.deployment.LegacyBundleTestCase
Error Message:
Cannot deploy: legacy-bundle
FAILED: org.jboss.as.test.integration.osgi.deployment.ServerDeploymentTestCase.org.jboss.as.test.integration.osgi.deployment.ServerDeploymentTestCase
Error Message:
Cannot deploy: deployment-tests
FAILED: org.jboss.as.test.integration.osgi.ear.CollectionsEnterpriseArchiveTestCase.org.jboss.as.test.integration.osgi.ear.CollectionsEnterpriseArchiveTestCase
Error Message:
Cannot deploy: lib-collections.ear
FAILED: org.jboss.as.test.integration.osgi.ear.EnterpriseArchiveTestCase.org.jboss.as.test.integration.osgi.ear.EnterpriseArchiveTestCase
Error Message:
Cannot deploy: war-structure.ear
FAILED: org.jboss.as.test.integration.osgi.ejb3.EjbBindingsTestCase.org.jboss.as.test.integration.osgi.ejb3.EjbBindingsTestCase
Error Message:
Cannot deploy: osgi-ejb3-test
FAILED: org.jboss.as.test.integration.osgi.ejb3.StatelessBeanTestCase.org.jboss.as.test.integration.osgi.ejb3.StatelessBeanTestCase
Error Message:
Cannot deploy: ejb3-osgi-target
REGRESSION: org.jboss.as.test.integration.osgi.ejb3.client.EJBClientDescriptorTestCase.testEJBClientContextConfigurationInOSGiBundle
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.osgi.http.HttpServiceTestCase.org.jboss.as.test.integration.osgi.http.HttpServiceTestCase
Error Message:
Cannot deploy: http-service-example
FAILED: org.jboss.as.test.integration.osgi.jaxb.XMLBindingTestCase.org.jboss.as.test.integration.osgi.jaxb.XMLBindingTestCase
Error Message:
Cannot deploy: example-jaxb
FAILED: org.jboss.as.test.integration.osgi.jaxrs.RestEndpointTestCase.org.jboss.as.test.integration.osgi.jaxrs.RestEndpointTestCase
Error Message:
Cannot deploy: osgi-rest-test
FAILED: org.jboss.as.test.integration.osgi.jaxws.WebServiceClientTestCase.org.jboss.as.test.integration.osgi.jaxws.WebServiceClientTestCase
Error Message:
Cannot deploy: simple-client.jar
FAILED: org.jboss.as.test.integration.osgi.jaxws.WebServiceEndpointTestCase.org.jboss.as.test.integration.osgi.jaxws.WebServiceEndpointTestCase
Error Message:
Cannot deploy: osgi-ws-test
FAILED: org.jboss.as.test.integration.osgi.jndi.JNDITestCase.org.jboss.as.test.integration.osgi.jndi.JNDITestCase
Error Message:
Cannot deploy: example-jndi
FAILED: org.jboss.as.test.integration.osgi.jpa.PersistenceTestCase.org.jboss.as.test.integration.osgi.jpa.PersistenceTestCase
Error Message:
Cannot deploy: osgi-jpa-test
FAILED: org.jboss.as.test.integration.osgi.jta.TransactionTestCase.org.jboss.as.test.integration.osgi.jta.TransactionTestCase
Error Message:
Cannot deploy: example-jta
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testFrameworkActivation
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testBundleRuntimeOperations
Error Message:
Cannot deploy: test-bundle
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testAddRemoveCapabilities
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testActivationMode
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testFrameworkProperties
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
REGRESSION: org.jboss.as.test.integration.osgi.management.FrameworkManagementTestCase.testStartLevel
Error Message:
java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.integration.osgi.repository.RepositoryTestCase.org.jboss.as.test.integration.osgi.repository.RepositoryTestCase
Error Message:
Cannot deploy: osgi-repository-bundle
FAILED: org.jboss.as.test.integration.osgi.resource.BundleContextInjectionTestCase.org.jboss.as.test.integration.osgi.resource.BundleContextInjectionTestCase
Error Message:
Cannot deploy: managed.ear
FAILED: org.jboss.as.test.integration.osgi.resource.ResourceInjectionTestCase.org.jboss.as.test.integration.osgi.resource.ResourceInjectionTestCase
Error Message:
Cannot deploy: resource-injection.jar
FAILED: org.jboss.as.test.integration.osgi.webapp.WebAppSpecTestCase.org.jboss.as.test.integration.osgi.webapp.WebAppSpecTestCase
Error Message:
Cannot deploy: osgi-webapp-spec-tests
FAILED: org.jboss.as.test.integration.osgi.webapp.WebAppTestCase.org.jboss.as.test.integration.osgi.webapp.WebAppTestCase
Error Message:
Cannot deploy: osgi-webapp-test
FAILED: org.jboss.as.test.integration.osgi.webapp.WebBundleTestCase.org.jboss.as.test.integration.osgi.webapp.WebBundleTestCase
Error Message:
Cannot deploy: webbundle-tests
FAILED: org.jboss.as.test.integration.osgi.xml.DocumentBuilderTestCase.org.jboss.as.test.integration.osgi.xml.DocumentBuilderTestCase
Error Message:
Cannot deploy: dom-parser.jar
FAILED: org.jboss.as.test.integration.osgi.xml.SAXParserTestCase.org.jboss.as.test.integration.osgi.xml.SAXParserTestCase
Error Message:
Cannot deploy: sax-parser.jar
FAILED: org.jboss.as.test.integration.osgi.xml.StreamReaderTestCase.org.jboss.as.test.integration.osgi.xml.StreamReaderTestCase
Error Message:
Cannot deploy: stream-reader.jar
FAILED: org.jboss.as.test.integration.osgi.xml.XPathFactoryTestCase.org.jboss.as.test.integration.osgi.xml.XPathFactoryTestCase
Error Message:
Cannot deploy: xpath-test.jar
FAILED: org.jboss.as.test.integration.osgi.xservice.BundleAccessesModuleServiceTestCase.org.jboss.as.test.integration.osgi.xservice.BundleAccessesModuleServiceTestCase
Error Message:
Cannot deploy: xservice-module-access
FAILED: org.jboss.as.test.integration.osgi.xservice.ModuleAccessesBundleServiceTestCase.org.jboss.as.test.integration.osgi.xservice.ModuleAccessesBundleServiceTestCase
Error Message:
Cannot deploy: xservice-module-access
FAILED: org.wildfly.test.extension.rts.CoordinatorTestCase.org.wildfly.test.extension.rts.CoordinatorTestCase
Error Message:
Cannot deploy: test-deployment.war
FAILED: org.wildfly.test.extension.rts.ParticipantTestCase.org.wildfly.test.extension.rts.ParticipantTestCase
Error Message:
Cannot deploy: test-deployment.war
FAILED: org.wildfly.test.extension.rts.ProvidersTestCase.org.wildfly.test.extension.rts.ProvidersTestCase
Error Message:
Cannot deploy: test-deployment.war
FAILED: org.jboss.as.test.smoke.jms.DefaultJMSConnectionFactoryTest.org.jboss.as.test.smoke.jms.DefaultJMSConnectionFactoryTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.jms.JMSBridgeTest.org.jboss.as.test.smoke.jms.JMSBridgeTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.jms.SendToJMSQueueTest.org.jboss.as.test.smoke.jms.SendToJMSQueueTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.jms.SendToJMSTopicTest.org.jboss.as.test.smoke.jms.SendToJMSTopicTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.jms.SendToQueueFromWithinTransactionTest.org.jboss.as.test.smoke.jms.SendToQueueFromWithinTransactionTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.jms.SendToTopicFromWithinTransactionTest.org.jboss.as.test.smoke.jms.SendToTopicFromWithinTransactionTest
Error Message:
java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to http-remoting://[::1]:9990. The connection timed out
FAILED: org.jboss.as.test.smoke.messaging.MessagingTestCase.org.jboss.as.test.smoke.messaging.MessagingTestCase
Error Message:
Cannot deploy: messaging-example.jar
REGRESSION: org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.testJMSOverHTTPWithServlet
Error Message:
Could not lookup value for field private javax.naming.Context org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.remoteContext
REGRESSION: org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.testJMSOverHTTPWithServlet
Error Message:
null
REGRESSION: org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.testJMSOverTCP
Error Message:
Could not lookup value for field private javax.naming.Context org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.remoteContext
REGRESSION: org.jboss.as.test.smoke.messaging.client.jms.JmsClientTestCase.testJMSOverTCP
Error Message:
null
REGRESSION: org.jboss.as.test.smoke.messaging.client.messaging.MessagingClientTestCase.testMessagingClient
Error Message:
HQ119007: Cannot connect to server(s). Tried with all available servers.
FAILED: org.jboss.as.test.xts.simple.wsat.client.WSATTestCase.org.jboss.as.test.xts.simple.wsat.client.WSATTestCase
Error Message:
Cannot deploy: wsat.war
FAILED: org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase.org.jboss.as.test.xts.simple.wsba.coordinatorcompletion.client.WSBACoordinatorCompletionTestCase
Error Message:
Cannot deploy: wsba-coordinator-completion.war
FAILED: org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase
Error Message:
Cannot deploy: wsba-participant-completion.war
FAILED: org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase.org.jboss.as.test.xts.simple.wsba.participantcompletion.client.WSBAParticipantCompletionTestCase
Error Message:
Failed to remove Byteman script
11 years, 6 months
- 1
- 0
wildfly-master-testsuite-ip6 - Build # 7336 - Failure!
by ci-builds＠redhat.com
wildfly-master-testsuite-ip6 - Build # 7336 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7336
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
2 tests failed.
REGRESSION: org.jboss.as.test.integration.ejb.timerservice.simple.SimpleTimerServiceTestCase.testAnnotationTimeoutMethod
Error Message:
null
REGRESSION: org.jboss.as.test.integration.ejb.timerservice.simple.SimpleTimerServiceTestCase.testTimedObjectTimeoutMethod
Error Message:
null
11 years, 6 months
- 1
- 0
wildfly-master-testsuite-ip6 - Build # 7326 - Failure!
by ci-builds＠redhat.com
wildfly-master-testsuite-ip6 - Build # 7326 - Failure:
Check console output at to view the results.
Public: http://hudson.jboss.org/hudson/job/wildfly-master-testsuite-ip6/7326
Internal: http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/wildfly-master-tes...
Test summary:
5 tests failed.
REGRESSION: org.jboss.as.test.integration.respawn.RespawnTestCase.testDomainRespawn
Error Message:
null
REGRESSION: org.jboss.as.test.integration.respawn.RespawnTestCase.testReloadHc
Error Message:
null
REGRESSION: org.jboss.as.test.integration.respawn.RespawnTestCase.testReloadHcButNotServers
Error Message:
null
REGRESSION: org.jboss.as.test.integration.management.api.web.DeploymentScannerTestCase.testAddRemoveRollbacks
Error Message:
null
REGRESSION: org.jboss.as.test.integration.management.api.web.DeploymentScannerTestCase.testAddRemove
Error Message:
Management operation failed: "JBAS014803: Duplicate resource [ (\"subsystem\" => \"deployment-scanner\"), (\"scanner\" => \"testScanner\") ]"
11 years, 6 months
- 1
- 0
- ← Newer
- 1
- Older →