Re: [jboss-as7-dev] problems with deployment overlays and linking
by Brian Stansberry
Do you see value in cherry-picking his patch and adjusting the command
first? The issues you find implementing the command are what led to
these changes, so it'd be nice to know your commands work before merging
his stuff.
On 8/31/12 5:03 AM, Alexey Loubyansky wrote:
> Great. Once it's merged I'll adjust the deployment-overlay command and
> submit a pull request.
>
> Thanks,
> Alexey
>
> On 08/31/2012 05:29 AM, Stuart Douglas wrote:
>>
>> I have done up an initial implementation of this here
>> https://github.com/jbossas/jboss-as/pull/2989 .
>>
>>
>> Stuart
>>
>> On 24/08/2012, at 2:08 AM, Brian Stansberry <brian.stansberry(a)redhat.com
>> <mailto:brian.stansberry@redhat.com>> wrote:
>>
>>> On 8/23/12 3:39 AM, Emanuel Muckenhuber wrote:
>>>> On 08/23/2012 01:11 AM, Brian Stansberry wrote:
>>>>> Sorry for the slow responses on this thread.
>>>>>
>>>>> I think we should go with Stuart's approach, particularly if Alexey is
>>>>> comfortable that the CLI can support high level commands associated
>>>>> with it.
>>>>>
>>>>
>>>> Yeah, i am fine then as well - nevertheless some comments inline :)
>>>>
>>>
>>> Me too. ;)
>>>
>>>>>
>>>>> On 8/22/12 8:22 AM, Emanuel Muckenhuber wrote:
>>>>>>
>>>>>> My main concern is regarding the domain mode, since the additional
>>>>>> linking does not seem to be necessary to me and just additional steps
>>>>>> mgmt clients have to take care of.
>>>>>>
>>>>>> Whereas the deployment-scanner is a single client for standalone,
>>>>>> which
>>>>>> is under our control. So i wanted to see if we there is a way we can
>>>>>> make this work which also satisfies your use cases.
>>>>>>
>>>>>> I have two things in mind which i'll try to explain quickly:
>>>>>>
>>>>>> 1) you still link the overlays as part of the <deployment />, however
>>>>>> the deploment-scanner is aware of that and won't remove deployments
>>>>>> with
>>>>>> overlays until you use a specific invalidation marker.
>>>>>>
>>>>>
>>>>> This requires that the overlays be controlled by the scanner as well.
>>>>> Why? Because we don't persist the model resource for
>>>>> scanner-controlled
>>>>> deployments. So if a user linked a non-scanner-controlled overlay to a
>>>>> scanner controlled deployment (which seems quite rational if the
>>>>> overlay
>>>>> involves some environmental settings that never change), the link
>>>>> information will be lost on server reboot.
>>>>>
>>>>
>>>> I know, but that's an ancient limitation. I guess we could just
>>>> start to
>>>> persist stuff.
>>>>
>>>
>>> We'd have to persist some association between a deployment and a scanner
>>> (e.g. scanner="default" on the deployment element) and then use that to
>>> indicate that the server should not auto-deploy on boot but should defer
>>> to the scanner to tell it what to do. And then alter the scanner to add
>>> logic for it to reconcile the state it sees in the scan directory vs
>>> what the model shows.
>>>
>>> Doable, but a fair bit of work.
>>>
>>> I considered this before going with the "don't persist" approach. I
>>> don't recall though if there was some fundamental problem with it that
>>> I'm not remembering, or if it was solely that "don't persist" was doable
>>> within the time constraints.
>>>
>>>>>> 2) use overlay directories - this is more the file based approach,
>>>>>> Where
>>>>>> we just pick the "deployment.name + suffix" for the overlay. So there
>>>>>> would be an automatic overlay/linking done by the deployment-scanner.
>>>>>>
>>>>>
>>>>> Same issue as 1).
>>>>>
>>>>
>>>> Not really. It can automatically recreate the overlays therefore it
>>>> does
>>>> not require persistent information.
>>>>
>>>
>>> It can only recreate the association for overlays that it scans, not
>>> ones that were added via CLI/console.
>>>
>>>>>> 2.1) the overlay directory could be just a link to a virtual file (a
>>>>>> shared <deployment-overlay />) [1] - so in this case the overlays are
>>>>>> managed by the model and are not linked to the deployment lifecycle.
>>>>>>
>>>>>
>>>>> I confess I don't understand this. In particular, how does it
>>>>> fundamentally differ from what Stuart proposes in terms of how to
>>>>> organize the data?
>>>>>
>>>>
>>>> Well that is the point. It's basically the same, just that it removes
>>>> the requirement for the additional linking in the domain.
>>>>
>>>
>>> Ok, then I still don't understand it. If it solves a problem I'd like to
>>> understand. Can you explain further?
>>>
>>>>>> On 08/22/2012 01:03 AM, Stuart Douglas wrote:
>>>>>>>
>>>>>>> So what are we going to do here? Personally I much prefer the idea
>>>>>>> of having this stored in the model and linking it to a deployment,
>>>>>>> so the overlay lifecycle is not tied to that of the deployment.
>>>>>>>
>>>>>>> Another idea I had is that we could do something like define the
>>>>>>> overlays at domain level, but then define the links at server
>>>>>>> group or server level using the same name. basically something like:
>>>>>>>
>>>>>>> /deployment-overlay=myOverlay/content=WEB-INF/web.xml
>>>>>>> /deployment-overlay=myOverlay/content=WEB-INF/ejb-jar.xml
>>>>>>>
>>>>>>> /server-group=server-group1/deployment-overlay=myOverlay/deployment=test.war
>>>>>>>
>>>>>>> /server-group=server-group1/deployment-overlay=myOverlay/deployment=*.war
>>>>>>>
>>>>>>>
>>>>>>> For standalone they would just be combined, similar to what I had
>>>>>>> below:
>>>>>>>
>>>>>>>
>>>>>>> /deployment-overlay=myOverlay/content=WEB-INF/web.xml
>>>>>>> /deployment-overlay=myOverlay/content=WEB-INF/ejb-jar.xml
>>>>>>> /deployment-overlay=myOverlay/deployment=test.war
>>>>>>> /deployment-overlay=myOverlay/deployment=*.war
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Stuart
>>>>>>>
>>>>>>> On 17/08/2012, at 11:03 PM, Emanuel Muckenhuber
>>>>>>> <emuckenh(a)redhat.com <mailto:emuckenh@redhat.com>> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On 08/17/2012 02:52 AM, Stuart Douglas wrote:
>>>>>>>>> The big problem with this is that it does not work with the
>>>>>>>>> deployment scanner.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yeah, the deployment-scanner is always a story for itself.
>>>>>>>> However i think we could actually make it persist information and
>>>>>>>> be aware of overlays.
>>>>>>>>
>>>>>>>> Having overlays as part of the deployment means the lifecycle is
>>>>>>>> managed together, so the deployment-scanner could define it's own
>>>>>>>> invalidation policy. May it be based on whether the content got
>>>>>>>> removed or we have a specific marker for that.
>>>>>>>>
>>>>>>>> We could also think of providing a file-based overlay solution,
>>>>>>>> managed by the deployment scanner only. In the end people use the
>>>>>>>> deployment-scanner for a reason, so perhaps not having to worry
>>>>>>>> about the model or "content" folder could be interesting. This
>>>>>>>> would not even need to access persistent information though.
>>>>>>>> Anyway just some ideas on the side.
>>>>>>>>
>>>>>>>>> It also has to be specified on every re-deploy.
>>>>>>>>
>>>>>>>> When you do a "remove" and "add" then yes. We do have specific
>>>>>>>> operations to replace the content and redeploy the deployment
>>>>>>>> without removing the information from the model.
>>>>>>>>
>>>>>>>>> I think the simplest solution here
>>>>>>>>> is to just move the links under the deployment-overlays element
>>>>>>>>> and loose the
>>>>>>>>> flexibility to link at different levels. e.g:
>>>>>>>>>
>>>>>>>>> /deployment-overlay=myOverlay/deployment=test.war
>>>>>>>>> /deployment-overlay=myOverlay/deployment=*.jar
>>>>>>>>>
>>>>>>>>
>>>>>>>> Yes, i was not really going for the simplest solution for now -
>>>>>>>> this would most likely would be it :)
>>>>>>>
>>>>>> _______________________________________________
>>>>>> jboss-as7-dev mailing list
>>>>>> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jboss-as7-dev mailing list
>>>> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>>>
>>>
>>>
>>> --
>>> Brian Stansberry
>>> Principal Software Engineer
>>> JBoss by Red Hat
>>> _______________________________________________
>>> jboss-as7-dev mailing list
>>> jboss-as7-dev(a)lists.jboss.org <mailto:jboss-as7-dev@lists.jboss.org>
>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
--
Brian Stansberry
Principal Software Engineer
JBoss by Red Hat
12 years, 3 months
jboss-all.xml external to the deployment
by Thomas Diesler
Stuart,
how would I associate an jboss-all.xml descriptor with a deployment in
the same management op? I don't want touch the deployment and I don't
want to wrap it. Is that supported?
cheers
--thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
12 years, 3 months
Build failed in Jenkins: as7-7.1-testsuite #576
by ci-builds＠redhat.com
See <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
------------------------------------------
[...truncated 4620 lines...]
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ jboss-as-spec-api-test ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-checkstyle-plugin:2.5:checkstyle (check-style) @ jboss-as-spec-api-test ---
[INFO] Source directory does not exist - skipping report.
[INFO]
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ jboss-as-spec-api-test ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-spec-api-test ---
[INFO] Compiling 1 source file to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-surefire-plugin:2.11:test (default-test) @ jboss-as-spec-api-test ---
[INFO] Surefire report directory: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ jboss-as-spec-api-test ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...>
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar-no-fork (attach-sources) @ jboss-as-spec-api-test ---
[INFO] No sources in project. Archive not created.
[INFO]
[INFO] --- maven-install-plugin:2.3.1:install (default-install) @ jboss-as-spec-api-test ---
[INFO] Installing <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> to /home/jenkins/.m2/repository/org/jboss/as/jboss-as-spec-api-test/7.1.3.Final-SNAPSHOT/jboss-as-spec-api-test-7.1.3.Final-SNAPSHOT.jar
[INFO] Installing <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> to /home/jenkins/.m2/repository/org/jboss/as/jboss-as-spec-api-test/7.1.3.Final-SNAPSHOT/jboss-as-spec-api-test-7.1.3.Final-SNAPSHOT.pom
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server: Web Services Tests Integration Subsystem
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Shared
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Aggregator
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - Smoke
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - Basic
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - Clustering
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - IIOP
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - XTS
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - Multinode Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Integration - Manual Mode Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Compatibility Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Domain Mode Integration Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Benchmark Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Skipping JBoss Application Server Test Suite: Stress Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [3.950s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [2.041s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.366s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.380s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [16.611s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [7.397s]
[INFO] JBoss Application Server: Controller Core ......... FAILURE [29.639s]
[INFO] JBoss Application Server: Domain Management ....... SKIPPED
[INFO] JBoss Application Server: Domain HTTP Interface ... SKIPPED
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [4.169s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [4.432s]
[INFO] JBoss Application Server: Platform MBean integration SKIPPED
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [10.191s]
[INFO] JBoss Application Server: Network ................. SUCCESS [3.335s]
[INFO] JBoss Application Server: Threading Subsystem ..... SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Server .................. SKIPPED
[INFO] JBoss Application Server: Subsystem Test Harness .. SKIPPED
[INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Naming Subsystem ........ SKIPPED
[INFO] JBoss Application Server: EE ...................... SKIPPED
[INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED
[INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.512s]
[INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.799s]
[INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED
[INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED
[INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED
[INFO] JBoss Application Server: Security Subsystem ...... SKIPPED
[INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED
[INFO] JBoss Application Server: Clustered registry service SKIPPED
[INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [4.943s]
[INFO] JBoss Application Server: Clustering Server API implementation SKIPPED
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED
[INFO] JBoss Application Server: Web Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.235s]
[INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED
[INFO] JBoss Application Server: Application Client Bootstrap SKIPPED
[INFO] JBoss Application Server: Config Assembly ......... SKIPPED
[INFO] JBoss Application Server: Command line interface .. SKIPPED
[INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.327s]
[INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.362s]
[INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [3.296s]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED
[INFO] JBoss Application Server: Clustered service provider registry services SKIPPED
[INFO] JBoss Application Server: Clustered singleton services SKIPPED
[INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED
[INFO] JBoss Application Server: Config Admin ............ SKIPPED
[INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED
[INFO] JBoss Application Server: EE Deployment ........... SKIPPED
[INFO] JBoss Application Server: JAXR Client ............. SKIPPED
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.237s]
[INFO] JBoss Application Server: JPA SPI ................. SKIPPED
[INFO] JBoss Application Server: JPA UTIL ................ SKIPPED
[INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Weld Integration ........ SKIPPED
[INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED
[INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.326s]
[INFO] JBoss Application Server: JDR ..................... SKIPPED
[INFO] JBoss Application Server: JSF Support jar ......... SKIPPED
[INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED
[INFO] JBoss Application Server: Management Client Content SKIPPED
[INFO] JBoss Application Server: Host Controller ......... SKIPPED
[INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED
[INFO] JBoss Application Server: Mail subsystem .......... SKIPPED
[INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED
[INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED
[INFO] JBoss Application Server: OSGi .................... SUCCESS [0.355s]
[INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED
[INFO] JBoss Application Server: OSGi ConfigurationAdmin . SKIPPED
[INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED
[INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [2.008s]
[INFO] JBoss Application Server: Service Archive Subsystem SKIPPED
[INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED
[INFO] JBoss Application Server: Build ................... SKIPPED
[INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.420s]
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED
[INFO] JBoss Application Server: Arquillian Common ....... SKIPPED
[INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Container SKIPPED
[INFO] JBoss Application Server: Arquillian Remote Container SKIPPED
[INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [1.095s]
[INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED
[INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
[INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
[INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
[INFO] JBoss Application Server: Distribution ............ SKIPPED
[INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED
[INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [1.695s]
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED
[INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED
[INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED
[INFO] JBoss Application Server Test Suite: Integration .. SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Basic SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Clustering SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - IIOP SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - XTS SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Multinode Tests SKIPPED
[INFO] JBoss Application Server Test Suite: Integration - Manual Mode Tests SKIPPED
[INFO] JBoss Application Server Test Suite: Compatibility Tests SKIPPED
[INFO] JBoss Application Server Test Suite: Domain Mode Integration Tests SKIPPED
[INFO] JBoss Application Server Test Suite: Benchmark Tests SKIPPED
[INFO] JBoss Application Server Test Suite: Stress Tests . SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 2:01.499s
[INFO] Finished at: Wed Sep 05 16:18:20 EDT 2012
[INFO] Final Memory: 187M/492M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-controller: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-7.1-testsuite/...> 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-controller
+ gzip testsuite/integration/basic/target/jbossas/standalone/log/server.log
gzip: testsuite/integration/basic/target/jbossas/standalone/log/server.log.gz already exists; not overwritten
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
12 years, 3 months
GitHub Pull Request Processing Issues
by Jason Greene
There was a change to the GitHub API that is affecting automated testing of some of our pull requests. I will have a fix sometime tomorrow.
Sorry for the inconvenience.
--
Jason T. Greene
JBoss AS Lead / EAP Platform Architect
JBoss, a division of Red Hat
12 years, 3 months
JndiNamingDependencySetupProcessor limiting deployment phase
by Eduardo Martins
This naming processor, which sets up a DU attachment for a set of jndi binding service dependencies (to be added later on the component start service so JNDI bindings are up when the component needs), is currently bound to INSTALL phase, and this is limiting the usage of such set. For instance in https://issues.jboss.org/browse/AS7-5443 the naming processors who set up app and module context, which are bound to POST_MODULE phase, need to setup java:app/AppName and java:module/ModuleName, and these need to be also up when the component needs (e.g. @PreDestroy).
I see two ways of minimise such limitations:
a) This attachment is a set, which needs concrete setup, we could change it to a list, and take advantage of Attachable#addToAttachmentList(...), which inits the attachment list on demand. AFAIK the change from set to list would not be an issue, cause duplicated entries in this list would be MSC filtered/ignored (anyway we could always introduce Attachable#addToAttachmentSet(...)). In the case this has no side effects, we could even move the remaining logic of the processor to JndiNamingDependencyProcessor and remove it.
b) Move the Processor to an earlier phase, to ensure the attachment set is already setup.
Opinions?
-- E
12 years, 3 months
rename jboss-cli.sh?
by Cheng Fang
I've been playing with jboss as7 cli and like to share my experience. I
understand that in AS7-2310, it was renamed from jboss-admin.sh to
jboss-cli.sh, so a second renaming seems disruptive, but anyway here it
goes...
First, can we remove the .sh file extension? Tools like ant, mvn and
groovy are all shell scripts but do not have the .sh extension. Users
just need to execute it, without concerning if it is written as a shell
script to binary. Having the .sh extension limits ourselves in impl
options. On Windows we continue to have .bat, which is unavoidable, but
users just need to run "jboss-cli" with .bat extension.
jboss-cli.sh is quite some typing for users, and the first TAB
completion will not enough. It takes 2 tabs to complete jboss-cli.sh
Secondly, can we remove the -cli part to further simplify the name? It
seems to be superfluous as many terminal commands are cli. IMO, a name
needs to reflect the purpose of the tool, rather than its form. By
having -cli in the name, we are again restricting it to be a cli tool.
But didn't we have a GUI form that can be launched by 'jboss-cli.sh --gui'?
I personally like the old name jboss-admin.sh better, except that it's
too long.
Cheng
12 years, 3 months
EJB Over HTTP
by Eduardo Martins
Hi everyone, I'm about to (finally) start working on EJB over HTTP, which seems to be an essential feature that we had in previous AS versions.
I don't know much yet about the previous design and implementation, but here is a doc wrt AS5 that explains it: https://community.jboss.org/wiki/EJB3OverHTTPHTTPSInJBossAS-5
The JIRA issue for this development is https://issues.jboss.org/browse/AS7-4714 , which contains already some ideas for the implementation.
So, first question, anyone knows if the old design and/or implementation was good enough to be migrated? Or perhaps someone knows if it had any issues?
In a IRC chat and in the JIRA issue, websockets and xnio were mentioned as possible foundations for the AS7 implementation, which would mean to discard previous code already at low level. What is the reasoning for this, i.e., what advantages does the adaption of either of these bring to the feature and to AS7 as a whole?
Your contribution on this feature discussion is very welcome, thanks ;-)
-- E
12 years, 3 months
Build failed in Jenkins: as7-master-build #8788
by ci-builds＠redhat.com
See <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-build/8...>
------------------------------------------
[...truncated 19174 lines...]
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.946 sec
Running org.jboss.as.test.smoke.osgi.SimpleEJBTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.078 sec
Running org.jboss.as.test.smoke.osgi.SimpleServerDeploymentTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.857 sec
Running org.jboss.as.test.smoke.osgi.SimpleWebAppTestCase
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.542 sec
Running org.jboss.as.test.smoke.osgi.SimpleRunAsClientTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.704 sec
Running org.jboss.as.test.smoke.osgi.SimpleEnterpriseArchiveTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.087 sec
Running org.jboss.as.test.smoke.osgi.SimpleModuleRegistrationTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.514 sec
Running org.jboss.as.test.smoke.osgi.SimpleBundleTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.482 sec
Running org.jboss.as.test.smoke.osgi.SimplePackageAdminTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.313 sec
Running org.jboss.as.test.smoke.osgi.SimpleRepositoryTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.984 sec
Running org.jboss.as.test.smoke.osgi.SimpleManagedBeanTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.913 sec
Running org.jboss.as.test.smoke.osgi.SimpleArquillianDeployerTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.501 sec
Running org.jboss.as.test.smoke.osgi.SimpleHttpServiceTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.993 sec
Running org.jboss.as.test.smoke.jaxrs.JaxrsTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.819 sec
Running org.jboss.as.test.smoke.web.WarTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.302 sec
Running org.jboss.as.test.smoke.serviceloader.ServiceLoaderTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.268 sec
Running org.jboss.as.test.smoke.sar.SarTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.432 sec
Running org.jboss.as.test.smoke.configadmin.ConfigAdminServiceTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.747 sec
Running org.jboss.as.test.smoke.managedbean.ManagedBeanTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.718 sec
Running org.jboss.as.test.smoke.subsystem.xml.XSDValidationUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.867 sec
Running org.jboss.as.test.smoke.subsystem.xml.StandardConfigsXMLValidationUnitTestCase
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.768 sec
Running org.jboss.as.test.smoke.subsystem.threads.ThreadsSubsystemTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.278 sec
Running org.jboss.as.test.smoke.stilts.SimpleStompletTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.393 sec
Running org.jboss.as.test.smoke.TestsuiteSanityTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec
Running org.jboss.as.test.smoke.webservices.WSTestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 4.732 sec
Running org.jboss.as.test.smoke.ejb3.dd.DDBasedEJBTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.963 sec
Running org.jboss.as.test.smoke.ejb3.jndi.StandaloneModuleEjbJndiBindingTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.376 sec
Running org.jboss.as.test.smoke.ejb3.jndi.EarDeploymentEjbJndiBindingTestCase
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.336 sec
Running org.jboss.as.test.smoke.jsr88.JSR88DeploymentTestCase
Tests run: 9, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 7.934 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.multiactivation.MultipleActivationTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.245 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.inflow.InflowTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.614 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.pure.PureTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.683 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.redeployment.ReDeploymentTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.551 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.eardeployment.EarDeploymentTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.387 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.earpackage.EarPackagedDeploymentTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.514 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.multiobjectactivation.MultipleObjectActivationTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.54 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.earmultirar.EarPackagedMultiRarDeploymentTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.55 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.afterresourcecreation.AfterResourceCreationDeploymentTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.215 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.multiobjectpartialactivation.MultipleObjectPartialActivationTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.358 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.configproperty.ConfigPropertyTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.737 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.activation.IronJacamarActivationTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.61 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.basic.BasicDeploymentTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.462 sec
Running org.jboss.as.test.smoke.deployment.rar.tests.raconnection.RaTestConnectionTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.434 sec
Running org.jboss.as.test.smoke.rar.RarTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.513 sec
Running org.jboss.as.test.smoke.datasource.DsTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.482 sec
Running org.jboss.as.test.smoke.property.EjbDDWithPropertyTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.284 sec
Running org.jboss.as.test.smoke.mgmt.servermodule.ServerInModuleStartupTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.884 sec
Running org.jboss.as.test.smoke.mgmt.servermodule.ValidateModelTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.644 sec
Running org.jboss.as.test.smoke.mgmt.servermodule.HttpDeploymentUploadUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.177 sec
Running org.jboss.as.test.smoke.mgmt.servermodule.ServerInModuleDeploymentTestCase
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.932 sec
Running org.jboss.as.test.smoke.mgmt.DescribeOperationUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.276 sec
Running org.jboss.as.test.smoke.mgmt.resourceadapter.ResourceAdapterOperationsUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.291 sec
Running org.jboss.as.test.smoke.mgmt.PlatformMBeansUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.023 sec
Running org.jboss.as.test.smoke.mgmt.datasource.DataSourceResourcesUnitTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec
Running org.jboss.as.test.smoke.mgmt.datasource.DataSourceOperationsUnitTestCase
Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.993 sec
Running org.jboss.as.test.smoke.mgmt.datasource.AddMySqlDataSourceOperationsUnitTestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.233 sec
Running org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase
Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.722 sec
Results :
Tests in error:
org.jboss.as.test.smoke.osgi.SimpleStartLevelTestCase: Cannot deploy: startlevel-bundle
Tests run: 143, Failures: 0, Errors: 1, Skipped: 2
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] JBoss Application Server: Build Configuration ..... SUCCESS [2.831s]
[INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.374s]
[INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [11.888s]
[INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.884s]
[INFO] JBoss Application Server: Controller Core ......... SUCCESS [31.606s]
[INFO] JBoss Application Server: Deployment Repository ... SUCCESS [2.912s]
[INFO] JBoss Application Server: Process Controller ...... SUCCESS [8.504s]
[INFO] JBoss Application Server: Platform MBean integration SUCCESS [6.282s]
[INFO] JBoss Application Server: Domain Management ....... SUCCESS [7.412s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.322s]
[INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [3.255s]
[INFO] JBoss Application Server: Embedded ................ SUCCESS [3.660s]
[INFO] JBoss Application Server: Network ................. SUCCESS [3.141s]
[INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [7.930s]
[INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.609s]
[INFO] JBoss Application Server: Server .................. SUCCESS [15.076s]
[INFO] JBoss Application Server: Management Client Content SUCCESS [2.790s]
[INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [3.162s]
[INFO] JBoss Application Server: Host Controller ......... SUCCESS [13.951s]
[INFO] JBoss Application Server: Core Model Test Harness and Tests SUCCESS [21.838s]
[INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [0.701s]
[INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [7.245s]
[INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [18.764s]
[INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [8.971s]
[INFO] JBoss Application Server: EE ...................... SUCCESS [9.255s]
[INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [12.338s]
[INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [7.959s]
[INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.301s]
[INFO] JBoss Application Server: Clustering Server API ... SUCCESS [11.849s]
[INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [4.832s]
[INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [9.177s]
[INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [49.402s]
[INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [12.094s]
[INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [14.635s]
[INFO] JBoss Application Server: Clustered registry service SUCCESS [2.172s]
[INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [30.523s]
[INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [3.451s]
[INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [3.880s]
[INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [6.969s]
[INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [29.741s]
[INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.095s]
[INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [12.378s]
[INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [5.134s]
[INFO] JBoss Application Server: Config Assembly ......... SUCCESS [3.020s]
[INFO] JBoss Application Server: Command line interface .. SUCCESS [13.852s]
[INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.073s]
[INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.254s]
[INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [2.601s]
[INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [4.276s]
[INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [3.620s]
[INFO] JBoss Application Server: Clustered singleton services SUCCESS [4.042s]
[INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [21.545s]
[INFO] JBoss Application Server: Config Admin ............ SUCCESS [5.482s]
[INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [7.746s]
[INFO] JBoss Application Server: EE Deployment ........... SUCCESS [3.809s]
[INFO] JBoss Application Server: JAXR Client ............. SUCCESS [6.292s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.221s]
[INFO] JBoss Application Server: JPA SPI ................. SUCCESS [3.746s]
[INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [2.095s]
[INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [9.333s]
[INFO] JBoss Application Server: Weld Integration ........ SUCCESS [10.638s]
[INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [7.217s]
[INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.156s]
[INFO] JBoss Application Server: JDR ..................... SUCCESS [9.587s]
[INFO] JBoss Application Server: JSF Integration ......... SUCCESS [7.473s]
[INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [7.386s]
[INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [10.529s]
[INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [7.040s]
[INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [17.045s]
[INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [6.873s]
[INFO] JBoss Application Server: OSGi .................... SUCCESS [0.094s]
[INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [9.532s]
[INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [4.440s]
[INFO] JBoss Application Server: OSGi Integration ........ SUCCESS [3.277s]
[INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [9.076s]
[INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [5.403s]
[INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [1.598s]
[INFO] JBoss Application Server: System JMX Module ....... SUCCESS [1.902s]
[INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [6.027s]
[INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [2.954s]
[INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [4.034s]
[INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [5.904s]
[INFO] JBoss Application Server: Build ................... SUCCESS [31.154s]
[INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.229s]
[INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [1.662s]
[INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [2.816s]
[INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.178s]
[INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [22.069s]
[INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.274s]
[INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.133s]
[INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [21.732s]
[INFO] JBoss Application Server: Arquillian Common Domain SUCCESS [2.776s]
[INFO] JBoss Application Server: Arquillian Remote Domain Container SUCCESS [2.100s]
[INFO] JBoss Application Server: Arquillian Managed Domain Container SUCCESS [36.365s]
[INFO] JBoss Application Server: Distribution ............ SUCCESS [7.641s]
[INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [4.524s]
[INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [1.322s]
[INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [2.681s]
[INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [12.734s]
[INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [17.068s]
[INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [3.072s]
[INFO] JBoss Application Server Test Suite: Integration - Smoke FAILURE [2:25.783s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16:18.289s
[INFO] Finished at: Mon Sep 03 18:17:29 EDT 2012
[INFO] Final Memory: 354M/455M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (smoke-web.surefire) on project jboss-as-ts-integ-smoke: There are test failures.
[ERROR]
[ERROR] Please refer to <http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-build/w...> 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-ts-integ-smoke
Build step 'Execute shell' marked build as failure
Archiving artifacts
Recording test results
12 years, 3 months
Why we have build emails
by Jason Greene
We are sending build emails (for failures and restores only) to this list because a key priority is fixing or disabling all intermittent tests. It's a reminder that we all need to look at them and see what's going wrong. If you can spare a few minutes to help it would be much appreciated.
I estimate in a few weeks these intermittent failures will be gone, and only a "screw up" will lead to these emails being sent. This will hopefully lead to the data being useful and helpful to identifying problems.
If you are a casual observer, Jenkins sets a few headers that can easily be filtered. If it's still an annoyance I can try to tweak things to make them less common (digested once a day).
I hope everyone understands and appreciates the focus on improving out quality.
Thanks!
12 years, 3 months
Invoking remote EJBs on JBoss AS 4/5/6 from JBoss AS 7
by Stephen Coy
Hi there,
For interest sake last week I worked out a solution to a user's problem related to calling remote EJBs from JBoss 7 that were hosted on older versions of JBoss.
See <https://community.jboss.org/thread/204513?tstart=0> for the background.
Anyway, I have since worked out that I could bundle this up in a module so that clients would only need to add a jboss-deployment-structure.xml to their apps to get this functionality:
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.jboss.ejb-client.compatibility" />
</dependencies>
</deployment>
</jboss-deployment-structure>
I've incorporated the module into my clone of the current JBoss master branch at <https://github.com/sfcoy/jboss-as/tree/ejb-client.compatibility>.
Should I send a pull request for this?
Cheers,
Stephen Coy
12 years, 3 months
