Changes to .jsp in an exploded deployment no longer picked up?
by Jaikiran Pai
One of the very useful features in previous JBoss AS versions was the
ability of the server to identify and pick up changes to a .jsp page in
an exploded deployment and serve the updated content on next request.
Trying this out in JBoss AS 7.0.0.Beta3, I see that this no longer works:
1) Create and deploy a test.war (along with a test.war.dodeploy) in the
standalone/deployments.
2) test.war contains a test.jsp with an intentional syntax error in it
3) Access the jsp via browser and see the (expected) compilation error.
Now open the test.jsp file in a text editor, from the exploded test.war
deployment, and edit it to fix the error
4) Access the jsp via browser again. Tried it more than once. I still
see the compilation failure i.e. the jsp changes aren't being picked up
anymore. I had to undeploy and redeploy the exploded deployment for the
changes to be picked up.
I remember that in previous versions of AS there were some parameters
for the jsp compiler/executor which by default enabled this check for
jsp changes. Has this changed in AS7? Where and what values are set
currently? Or has this got something to do with the way we handle
exploded deployment in AS7?
-Jaikiran
13 years, 6 months
AS7-431: unmanaged content
by Brian Stansberry
Switching to the main as7 dev list as when this is ready it's going to
require some coordination. But first some comments on the patch:
1) Looks like there's a problem with the "relativeTo" handling in
FileSystemDeploymentScannerService:
http://pastebin.com/3PhN3VLg
2) DeploymentFullReplaceHandler in domain-controller needs conversion as
well.
3) ServerDeploymentRepository.addExternalFileReference can disappear. :)
Now the coordination part:
This work will break the existing console and the CLI, so before merging
it we'll need a coordinated change to those (cli is easier since it's
the same code base).
The change this introduces can be conceptualized by looking at the xml
in the JIRA description at [1]
a) the content of a deployment is now represented via a child element,
instead of just the attribute on the <deployment/> element.
b) we support "unmanaged" content, where the child element points to an
archive or exploded directory on the filesystem. Unmanaged means we
haven't slurped the deployment bits into our content repository from
which we will deploy them (and replicate them around the domain if
domain mode is used.) Instead it's the user's responsibility to put the
files where they say they are.
c) the eventual aim is to support associating multiple pieces of content
with a deployment, although this is not currently implemented.
Effect of this is in the configuration model on Carlo's branch, a
resource representing a deployment no longer has a "hash" attribute.
Instead it has a "content" attribute of type ModelType.LIST. Each
element in that list has these attributes:
"hash" -- the sha1 hash for managed content
OR, if "hash" is undefined, meaning content is unmanaged"
"archive" -- ModelType.BOOLEAN indicating whether the unmanaged content
is a zip
"path" -- absolute or relative filesystem path
"relative-to" -- (optional if "path is absolute) name of a system path
against which "path" should be resolved
The "add" and "full-replace" operations for a deployment have analogous
changes. Instead of root level parameters describing the content (e.g.
"hash" or "input-stream-index" or "url") they take a root level
"content" parameter of ModelType.LIST. The elements in the list describe
the content.
We need to decide what to do with the <deployment> element under
<server-group>. I don't see any reason to duplicate all the content
stuff. Simpler is just listing the unique name and whether the
deployment is enabled:
<domain>
<deployments>
<deployment name="foo.ear" runtime-name="foo.ear">
<content id="d37ede977b022a1456ec5e7a5eee07549cb1c414"/>
</deployment>
</deployments>
<server-groups>
<server-group ...>
<deployments>
<deployment name="foo.ear" enabled="true"/>
</deployments>
</server-group>
</server-groups>
</domain>
[1] https://issues.jboss.org/browse/AS7-431
On 4/28/11 10:16 PM, Brian Stansberry wrote:
> My system has been screwed up all afternoon/evening. I'm going to have
> to look at this in the morning. :(
>
> On 4/28/11 3:31 PM, Carlo de Wolf wrote:
>> Test is passing now.
>>
>> https://github.com/jbossas/jboss-as/pull/32 is amended.
>>
>> Carlo
>>
>> On 04/27/2011 06:28 AM, Brian Stansberry wrote:
>>> On 4/26/11 5:07 PM, Brian Stansberry wrote:
>>>> I tested the former using the domain.interactive demo. That's not
>>>> adequate of course. We need to solve knowing when a HostController and
>>>> all its servers are fully up so we can execute proper tests without
>>>> getting spurious failures due to timing.
>>>>
>>>> For the exploded thing, I'll add a variant of
>>>> ServerInModuleStartupTestCase.testFilesystemDeployment(), hopefully
>>>> tonight.
>>>>
>>>
>>> Test added to upstream:
>>> http://github.com/jbossas/jboss-as/compare/54d4c17...b8eb339
>>>
>>>> On 4/26/11 4:24 PM, Carlo de Wolf wrote:
>>>>> Do we have test cases for those things?
>>>>>
>>>>> Carlo
>>>>>
>>>>> On 04/26/2011 10:58 PM, Brian Stansberry wrote:
>>>>>> See https://github.com/bstansberry/jboss-as/commits/AS7-431 for the
>>>>>> small things.
>>>>>>
>>>>>> Before we can merge this though, we need:
>>>>>>
>>>>>> 1) the DeploymentFullReplaceHandlers to work
>>>>>> 2) exploded deployment from the deployments/ dir is broken. We should
>>>>>> convert the FS scanner to add unmanaged content.
>>>>>>
>>>>>> If it's not implemented before this is merged, we need to have a JIRA
>>>>>> for the TODO in domain mode DeploymentAddHandler to deal with
>>>>>> unmanaged
>>>>>> content.
>>>>>>
>>>>>> On 4/26/11 1:46 PM, Brian Stansberry wrote:
>>>>>>> I'm testing this out; have a few comments, but I think the easiest
>>>>>>> way
>>>>>>> to make them is to put them on a branch.
>>>>>>>
>>>>>>> One thing to discuss is the name of this "content" dir. I don't much
>>>>>>> like that name since 1) it's so vague 2) we use the same name in
>>>>>>> other
>>>>>>> places in the dist for the dir where we store managed content. The
>>>>>>> old
>>>>>>> "system-content" in Alpha1 somewhat indicated that it was our
>>>>>>> stuff, not
>>>>>>> theirs. If we're not concerned about that "ours vs. theirs"
>>>>>>> distinction
>>>>>>> and are just trying to create a well-known location for sticking
>>>>>>> unmanaged content, then perhaps "unmanaged-content" ? (I hope someone
>>>>>>> has a better suggestion.)
>>>>>>>
>>>>>>> On 4/26/11 10:21 AM, Carlo de Wolf wrote:
>>>>>>>> Now with domain working.
>>>>>>>>
>>>>>>>> Carlo
>>>>>>>>
>>>>>>>> On 04/26/2011 01:53 PM, Carlo de Wolf wrote:
>>>>>>>>> As Kabir spotted, the domain-controller bits are not working. I'm
>>>>>>>>> working on those now.
>>>>>>>>>
>>>>>>>>> Carlo
>>>>>>>>>
>>>>>>>>> On 04/26/2011 10:15 AM, Carlo de Wolf wrote:
>>>>>>>>>> Please review or pull https://github.com/jbossas/jboss-as/pull/32.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>>
>>>>>>>>>> Carlo
>>>>>>>>>> _______________________________________________
>>>>>>>>>> jbossas-pull-requests mailing list
>>>>>>>>>> jbossas-pull-requests(a)lists.jboss.org
>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests
>>>>>>>>> _______________________________________________
>>>>>>>>> jbossas-pull-requests mailing list
>>>>>>>>> jbossas-pull-requests(a)lists.jboss.org
>>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests
>>>>>>>> _______________________________________________
>>>>>>>> jbossas-pull-requests mailing list
>>>>>>>> jbossas-pull-requests(a)lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jbossas-pull-requests
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
13 years, 7 months
simple H2DS using web app
by Ales Justin
The test/example app using H2DS with JPA is here:
* https://github.com/alesj/hib-in-war/tree/as7
I'm getting this when deploying
Caused by: java.lang.NullPointerException
at org.jboss.as.ejb3.deployment.processors.TransactionAttributeAnnotationProcessor.processClassAnnotations(TransactionAttributeAnnotationProcessor.java:85)
Let me check what the problem might be ...
On Apr 29, 2011, at 8:04 PM, Scott Marlow wrote:
> Also, I think changing the jdbc url to the following might disable their shutdownhook:
>
> connection-url>jdbc:h2:mem:test;DB_CLOSE_ON_EXIT=FALSE,DB_CLOSE_DELAY=-1</connection-url>
>
>
>
> On 04/29/2011 01:58 PM, Scott Marlow wrote:
>> From what I can tell, using MySQL might help but some other ideas.
>>
>> I looked at http://www.h2database.com/html/features.html and it seems
>> that the jdbc url should be okay. We currently have:
>>
>> connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1</connection-url>
>>
>> That should keep the H2 database open until its no longer needed. I
>> wonder if H2 has a "on shutdown hook" being invoked too early.
>>
>> I verified that we have proper dependencies (at least for my test app):
>> http://pastebin.com/DDFEks1u
>>
>>
>> On 04/29/2011 01:01 PM, Scott Marlow wrote:
>>> On 04/29/2011 12:21 PM, Scott Marlow wrote:
>>>> If you run a local database server, that might be a workaround.
>>>
>>> Or maybe not, if its the database pool that is getting closed, too
>>> early, it won't help to use an external server.
>>>
>>
>
13 years, 8 months
Deployment descriptors?
by denstar
Hi!
I'm wondering a couple things here:
1) Is there something like jboss-web.xml as far as configuring context
paths and whatnot? I don't recall seeing anything like that when I
was looking at the DTD for jboss-deployment-structure.xml, though it
seems a logical place, so I wouldn't be surprised if I missed it.
2) Are we at a point where I can add a context for serving static
content from some arbitrary location on disk? If so, I'm thinking it
ties in with #1, so maybe this is more like one and a half questions.
:Den
--
We must welcome the future, remembering that soon it will be the past;
and we must respect the past, remembering that it was once all that
was humanly possible.
George Santayana
13 years, 8 months
server-config "group" attribute not writeable
by Heiko Braun
any reason for this?
[localhost:9999 /] /host=local/server-config=test-server:write-attribute(name=group,value=main-server-group)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" => "Attribute group is not writeable"}
}
Ike
13 years, 8 months
DOCS: Researching details for standalone clustering
by Darrin Mison
Hi, I'm chasing down details about the "standalone clustering" (as included in Beta3) for documentation.
I've noted the following:
1 - There's a clustering-standalone.xml configuration file in standalone/configuration that you can start the server with using ./standalone.sh -server-config=clustering-standalone.xml
2 - This configuration differs from the standard config in that:
- the org.jboss.as.clustering extension is enabled
- some additional items are configured in the urn:jboss:domain:osgi:1.0 subsystem
- 2 new subsystems configured (jgroups and infinispan)
- 6 new socket bindings added to the standard-sockets group for jgroups
So exactly what feature set does this give you out of the box for clustering?
I'm guessing session replication between standalone instances with JGroups for intra-node communication and Infinispan for storage?
Anything else?
Other questions:
How does each instance determine which other instances it should be clustered with?
Does this work with multiple instances on one machine (multi-homed or on different ports)?
Can multiple standalone instances using "cluster" configuration live on the same network but not all be one cluster? Like 10 instances as 2 clusters of 5 for example?
Aside from centralized management, what are the other key features from domain mode that you won't get from standalone clustering ?
Are there any known changes that are going to be made to this feature set for GA ?
Thanks in advance.
--
Darrin Mison
"I'm not a JBoss Developer, I just play one on TV"
Content Author - Engineering Content Services
Red Hat, Inc.
13 years, 8 months
Intermittent "Connection refused" when starting domain
by denstar
Hi folks!
Question:
After I've been developing for a while, doing various weird things I'm
wont to do, I'll try to start up domain.sh and get an error about
binding to the network interface.
Nothing else (that I know of) is bound to the port-- "lsof -i | grep
java" doesn't see anything. No java processes running, even.
I've seen this locally a few times and on an EC2 instance once so far.
A reboot "solves" the problem, which is probably something simple
that I'm just not considering? /me looks hopeful
Here's the stacktrace:
16:40:28,817 INFO [org.jboss.modules] (main) JBoss Modules version 1.0.0.Beta17
16:40:29,118 INFO [org.jboss.as.process.Host Controller.status]
(main) Starting process 'Host Controller'
[Host Controller] 16:40:29,527 INFO [org.jboss.modules] (main) JBoss
Modules version 1.0.0.Beta17
[Host Controller] 16:40:29,969 INFO [org.jboss.msc] (main) JBoss MSC
version 1.0.0.Beta8
[Host Controller] 16:40:30,113 ERROR [org.jboss.msc.service.fail] (MSC
service thread 1-8) MSC00001: Failed to start service
jboss.host.controller.process-controller-connection:
org.jboss.msc.service.StartException in service
jboss.host.controller.process-controller-connection:
java.net.ConnectException: Connection refused
[Host Controller] at
org.jboss.as.host.controller.ProcessControllerConnectionService.start(ProcessControllerConnectionService.java:127)
[Host Controller] at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675)
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
[:1.6.0_24]
[Host Controller] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
[:1.6.0_24]
[Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]
[Host Controller] Caused by: java.net.ConnectException: Connection refused
:Denny
--
There is no cure for birth and death save to enjoy the interval.
George Santayana
13 years, 8 months
deployment enabled attribute in domain.xml
by Alexey Loubyansky
It seems like it's not marshalled after a deployment has been undeployed
for a specific server group (this does work in standalone) although
read-attribute returns false.
[domain@localhost:9999 /]
/server-group=main-server-group/deployment=test-deployment.sar:undeploy()
{
"outcome" => "success",
"result" => {"server-groups" => {"main-server-group" => {
"server-two" => {
"host" => "local",
"response" => {
"outcome" => "success",
"result" => undefined,
"compensating-operation" => {
"operation" => "deploy",
"address" => [("deployment" => "test-deployment.sar")]
}
}
},
"server-one" => {
"host" => "local",
"response" => {
"outcome" => "success",
"result" => undefined,
"compensating-operation" => {
"operation" => "deploy",
"address" => [("deployment" => "test-deployment.sar")]
}
}
}
}}},
"compensating-operation" => {
"operation" => "deploy",
"address" => [
("server-group" => "main-server-group"),
("deployment" => "test-deployment.sar")
]
}
}
[domain@localhost:9999 /]
/server-group=main-server-group/deployment=test-deployment.sar:read-attribute(name=enabled)
{
"outcome" => "success",
"result" => false,
"compensating-operation" => undefined
}
<server-group name="main-server-group" profile="default">
<jvm name="default">
<heap size="64m" max-size="512m"/>
</jvm>
<socket-binding-group ref="standard-sockets"/>
<deployments>
<deployment name="test-deployment.sar"
runtime-name="test-deployment.sar"
sha1="694a230369425d4528d7621e7ccc0cb08f122c4c"/>
</deployments>
</server-group>
13 years, 8 months
help on startup parameters
by paulwerder＠fastmail.co.uk
Hi!
any JBoss dev can shed some light about these two questions ?
1) How to select a non-default configuration xml file for standalone
server on a Win box ?
(In an earlier post it's mentioned ./standalone.sh -server-config
However it doesn't work under windows)
2) How do you select a non-default profile for a domain server ?
Thanks a lot !
Paul
--
paulwerder(a)fastmail.co.uk
--
http://www.fastmail.fm - Email service worth paying for. Try it for free
13 years, 8 months
Re: [jboss-as7-dev] Build failed in Hudson: JBoss-AS-7.0.x #1018
by Brian Stansberry
I've saw an intermittent failure in the spec tests, and it looks like
Hudson has as well.
BTW, why are the spec tests running as part of every build?
On 4/28/11 9:38 AM, jboss-qa-internal(a)redhat.com wrote:
> See<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/1018/changes>
>
> Changes:
>
> [kabir] AS7-675: handle attributes for jvm:add
>
> ------------------------------------------
> [...truncated 5375 lines...]
> [INFO] Installing<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite/smoke/p...> to /home/hudson/.m2/repository/org/jboss/as/jboss-as-testsuite-smoke/7.0.0.Beta4-SNAPSHOT/jboss-as-testsuite-smoke-7.0.0.Beta4-SNAPSHOT.pom
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Test Suite: Aggregator 7.0.0.Beta4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jboss-as-testsuite2 ---
> [INFO] Deleting<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/target>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (ban-bad-dependencies) @ jboss-as-testsuite2 ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @ jboss-as-testsuite2 ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @ jboss-as-testsuite2 ---
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:copy (default) @ jboss-as-testsuite2 ---
> [INFO] Configured Artifact: org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:?:jar
> [INFO] Copying jboss-annotations-api_1.1_spec-1.0.0.Final.jar to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/target...>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (check-style) @ jboss-as-testsuite2 ---
> [INFO] Source directory does not exist - skipping report.
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ jboss-as-testsuite2 ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/../../...>
> [INFO]
> [INFO] --- maven-source-plugin:2.1.1:jar-no-fork (attach-sources) @ jboss-as-testsuite2 ---
> [INFO]
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ jboss-as-testsuite2 ---
> [INFO] Installing<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/pom.xml> to /home/hudson/.m2/repository/org/jboss/as/jboss-as-testsuite2/7.0.0.Beta4-SNAPSHOT/jboss-as-testsuite2-7.0.0.Beta4-SNAPSHOT.pom
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Test Suite: AS7 API Integration Tests 7.0.0.Beta4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jboss-as-testsuite2-integration-api ---
> [INFO] Deleting<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/ta...>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (ban-bad-dependencies) @ jboss-as-testsuite2-integration-api ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @ jboss-as-testsuite2-integration-api ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @ jboss-as-testsuite2-integration-api ---
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:copy (default) @ jboss-as-testsuite2-integration-api ---
> [INFO] Configured Artifact: org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:?:jar
> [INFO] Copying jboss-annotations-api_1.1_spec-1.0.0.Final.jar to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/ta...>
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ jboss-as-testsuite2-integration-api ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/sr...>
> [INFO]
> [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @ jboss-as-testsuite2-integration-api ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (check-style) @ jboss-as-testsuite2-integration-api ---
> [INFO] Source directory does not exist - skipping report.
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-testsuite2-integration-api ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/sr...>
> [INFO]
> [INFO] --- maven-compiler-plugin:2.1:testCompile (default-testCompile) @ jboss-as-testsuite2-integration-api ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ jboss-as-testsuite2-integration-api ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 728 resources
> [INFO]
> [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ jboss-as-testsuite2-integration-api ---
> [INFO] No tests to run.
> [INFO]
> [INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ jboss-as-testsuite2-integration-api ---
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] Building jar:<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/ta...>
> [INFO]
> [INFO] --- maven-source-plugin:2.1.1:jar-no-fork (attach-sources) @ jboss-as-testsuite2-integration-api ---
> [INFO] No sources in project. Archive not created.
> [INFO]
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ jboss-as-testsuite2-integration-api ---
> [INFO] Installing<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/ta...> to /home/hudson/.m2/repository/org/jboss/as/jboss-as-testsuite2-integration-api/7.0.0.Beta4-SNAPSHOT/jboss-as-testsuite2-integration-api-7.0.0.Beta4-SNAPSHOT.jar
> [INFO] Installing<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/api/po...> to /home/hudson/.m2/repository/org/jboss/as/jboss-as-testsuite2-integration-api/7.0.0.Beta4-SNAPSHOT/jboss-as-testsuite2-integration-api-7.0.0.Beta4-SNAPSHOT.pom
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Test Suite: Spec Integration Tests 7.0.0.Beta4-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Deleting<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...>
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (ban-bad-dependencies) @ jboss-as-testsuite2-integration-spec ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @ jboss-as-testsuite2-integration-spec ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @ jboss-as-testsuite2-integration-spec ---
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:copy (default) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Configured Artifact: org.jboss.spec.javax.annotation:jboss-annotations-api_1.1_spec:?:jar
> [INFO] Copying jboss-annotations-api_1.1_spec-1.0.0.Final.jar to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...>
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ jboss-as-testsuite2-integration-spec ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] skip non existing resourceDirectory<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/s...>
> [INFO]
> [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Compiling 4 source files to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...>
> [INFO]
> [INFO] --- maven-checkstyle-plugin:2.5:checkstyle (check-style) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Starting audit...
> Audit done.
>
> [WARNING] Unable to locate Source XRef to link to - DISABLED
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-testsuite2-integration-spec ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 5 resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.1:testCompile (default-testCompile) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Compiling 8 source files to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...>
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:copy-resources (copy-resources) @ jboss-as-testsuite2-integration-spec ---
> [debug] execute contextualize
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 728 resources
> [INFO]
> [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ jboss-as-testsuite2-integration-spec ---
> [INFO] Surefire report directory:<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...>
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.spec.ejb3.StatelessBeanTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.685 sec
> Running org.jboss.as.test.spec.servlet3.WebSecurityProgrammaticLoginTestCase
> Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 24.431 sec
> Running org.jboss.as.test.spec.ejb3.SlsbTestCase
> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.669 sec
> Running org.jboss.as.test.spec.ejb3.SingletonBeanTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.246 sec<<< FAILURE!
> Running org.jboss.as.test.spec.ejb3.AsyncBeanTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.242 sec<<< FAILURE!
> Running org.jboss.as.test.spec.ejb3.StatefulBeanTestCase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 2.177 sec<<< FAILURE!
>
> Results :
>
> Tests in error:
> org.jboss.as.test.spec.ejb3.SingletonBeanTestCase
> org.jboss.as.test.spec.ejb3.AsyncBeanTestCase
> org.jboss.as.test.spec.ejb3.StatefulBeanTestCase
>
> Tests run: 7, Failures: 0, Errors: 3, Skipped: 0
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [3.912s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [3.822s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [9.442s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.250s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.690s]
> [INFO] JBoss Application Server: Arquillian Container Commons SUCCESS [2.705s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.328s]
> [INFO] JBoss Application Server: Arquillian Testenricher CDI SUCCESS [1.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [0.235s]
> [INFO] JBoss Application Server: Arquillian Testenricher Resource SUCCESS [0.243s]
> [INFO] JBoss Application Server: Arquillian Protocol Servlet SUCCESS [2.989s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [16.151s]
> [INFO] JBoss Application Server: Domain HTTP API ......... SUCCESS [4.148s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [1.482s]
> [INFO] JBoss Application Server: Embedded ................ SUCCESS [1.726s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [3.499s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [12.563s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [3.019s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [5.799s]
> [INFO] JBoss Application Server: OSGi .................... SUCCESS [0.157s]
> [INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [6.893s]
> [INFO] JBoss Application Server: Arquillian Service ...... SUCCESS [3.298s]
> [INFO] JBoss Application Server: Command line interface .. SUCCESS [7.841s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [6.973s]
> [INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [6.527s]
> [INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [11.468s]
> [INFO] JBoss Application Server: EE ...................... SUCCESS [7.196s]
> [INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [4.691s]
> [INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [7.236s]
> [INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [11.827s]
> [INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [6.681s]
> [INFO] JBoss Application Server: Domain Controller ....... SUCCESS [5.414s]
> [INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [13.165s]
> [INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [9.812s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [9.458s]
> [INFO] JBoss Application Server: Weld Integration ........ SUCCESS [6.718s]
> [INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [4.185s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [7.748s]
> [INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [3.843s]
> [INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [7.471s]
> [INFO] JBoss Application Server: OSGi Config Admin ....... SUCCESS [3.018s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.836s]
> [INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [3.709s]
> [INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.139s]
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [11.183s]
> [INFO] JBoss Application Server: Build ................... SUCCESS [30.358s]
> [INFO] JBoss Application Server: Arquillian Container Managed SUCCESS [26.237s]
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SUCCESS [4.296s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [3.185s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [3.277s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.957s]
> [INFO] JBoss Application Server: Demos: Aggregator ....... SUCCESS [2.919s]
> [INFO] JBoss Application Server: Demos: Spec ............. SUCCESS [3.996s]
> [INFO] JBoss Application Server: Demos ................... SUCCESS [12.987s]
> [INFO] JBoss Application Server: Demos: AS7 API .......... SUCCESS [2.394s]
> [INFO] JBoss Application Server: Demos: AS7 Internals .... SUCCESS [1.877s]
> [INFO] JBoss Application Server: Microcontainer Subsystem SUCCESS [3.323s]
> [INFO] JBoss Application Server: OSGi Integration Plugin . SUCCESS [1.561s]
> [INFO] JBoss Application Server: Test Suite: Aggregator .. SUCCESS [0.865s]
> [INFO] JBoss Application Server: Test Suite: Smoke Tests . SUCCESS [1:28.161s]
> [INFO] JBoss Application Server: Test Suite: Aggregator .. SUCCESS [1.313s]
> [INFO] JBoss Application Server: Test Suite: AS7 API Integration Tests SUCCESS [2.344s]
> [INFO] JBoss Application Server: Test Suite: Spec Integration Tests FAILURE [53.631s]
> [INFO] JBoss Application Server: Test Suite: AS7 Internals Integration Tests SKIPPED
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 8:24.755s
> [INFO] Finished at: Thu Apr 28 10:38:09 EDT 2011
> [INFO] Final Memory: 213M/468M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.5:test (default-test) on project jboss-as-testsuite2-integration-spec: There are test failures.
> [ERROR]
> [ERROR] Please refer to<http://hudson.qa.jboss.com/hudson/job/JBoss-AS-7.0.x/ws/testsuite2/spec/t...> for the individual test results.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn<goals> -rf :jboss-as-testsuite2-integration-spec
> Recording test results
> Archiving artifacts
>
> _______________________________________________
> builds mailing list
> builds(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/builds
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
13 years, 8 months
