From Fedora Project Wiki

(Drop direct Test Days category membership)
 
(6 intermediate revisions by 4 users not shown)
Line 123: Line 123:
| {{result|pass}}
| {{result|pass}}
| {{result|warn}} <ref>files are owned by root</ref>   
| {{result|warn}} <ref>files are owned by root</ref>   
| {{result|inprogress}}
| {{result|pass}}
| {{result|inprogress}}
| {{result|pass}}
| {{result|inprogress}}
| {{result|pass}}
| {{result|inprogress}}  
| {{result|warn}} <ref>will provide further details shortly</ref>
| {{result|inprogress}}  
| {{result|pass}}  
| {{result|inprogress}}  
| {{result|pass}}  
| <references/>
| <references/>
|-
|-
Line 192: Line 192:
|}
|}


[[Category:Test Days]]
 
[[Category:Fedora 17 Test Days|s]]

Latest revision as of 21:34, 26 June 2015

Fedora Test Days
Jbossas7 ligature 128.png
JBoss AS 7

Date 17.04.2012
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)
Mailing list java-devel


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?[edit]

Jbossas7 ligature 128.png

JBoss Application Server 7[edit]

Today's instalment of Fedora Test Day will focus on JBoss Application Server. This time we're testing version 7.1.0 which is planned as a Feature for Fedora 17.

JBoss Application Server 7 is the latest release in a series of JBoss Application Server offerings. JBoss Application Server 7, is a fast, powerful, implementation of the Java Enterprise Edition 6 specification. The state-of-the-art architecture built on the Modular Service Container enables services on-demand when your application requires them.

For more information about JBoss AS please refer to its homepage.

Custom build[edit]

The included JBoss Application Server is a custom build. It means that it's not exactly the same as upstream's distribution. The Fedora version includes only JEE 6 web-profile. The main reson for that were time constraints.

Important.png
No JPA2 implementation
Although we tried to make it happen, at this point there is no Hibernate 4 (JPA2 implementation) included in Fedora. Sad, but true. The reason for that are issues with packaging Gradle (build tool used in Hibernate). For more info please contact Carlo de Wolf.

JBoss AS will be extended with new updates to the full version over the time.

Who's available[edit]

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day[edit]

How to test?[edit]

Additional to below test cases, you can (or even should!) do some testing on your own!

Some hints:

  • Please use CLI to manage and deploy, make sure it works correctly. We don't have the web management interface yet, so we need to use CLI.
  • Deploy your own apps (note that this is a custom build and not all subsystems are available!)

Test Cases[edit]

Important.png
Use jboss-as-7.1.0-3 or later
Almost all test cases require jboss-as-7.1.0-3 or later. Note that today (16th April) the 7.1.0-3 package was submitted as an update. It should be available in updates-testing for the Test Day time. If not - please download it directly from Koji.

Management[edit]

  1. Install and run
  2. Add management user
  3. Execute readonly management tasks
  4. Execute read-write management tasks

Deployment[edit]

  1. Deploy servlet application
  2. Deploy CDI application
  3. Deploy EJB application
  4. Deploy EJB-in-WAR quickstart
Idea.png
Other applications
A pretty good resource for sample apps is the OpenEJB site. But be careful when reporting issues.

Test Results[edit]

If you have problems with any of the tests, report a bug to Bugzilla.

If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

User Smolt Profile Install and run Add management user Execute readonly management tasks Execute read-write management tasks Deploy servlet application Deploy CDI application Deploy EJB application Deploy EJB-in-WAR quickstart References
Sample User HW
none
none
none
none
Pass pass
Warning warn
[1]
Fail fail
[2]
none
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345
Pavel Zhukov HW
none
none
none
none
none
none
none
none
vicodan [VirtualBox VM x86_64]
Pass pass
Warning warn
[1]
Pass pass
Pass pass
Pass pass
Warning warn
[2]
Pass pass
Pass pass
  1. files are owned by root
  2. will provide further details shortly
Guido Grazioli rawhide qemu-kvm
Pass pass
Warning warn
[1]
Pass pass
[2]
Pass pass
Pass pass
Pass pass
Pass pass
none
  1. /etc/jboss-as/domain/mgmt-users.properties unexpectedly owned by root
  2. need jboss-drm >= 1.1.1-4.fc18
Marek Goldmann HW
none
none
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Jóhann B. Guðmundsson HW
Pass pass
Warning warn
[1]
Pass pass
Pass pass
none
none
none
none
  1. Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root
Stanislav Ochotnicky HW
Warning warn
[1]
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
Pass pass
  1. At one point systemctl status showed jboss as running even though the process failed (due to incorrect current JVM)
Filipe Rosset HW
Warning warn
[1]
Warning warn
[2]
Pass pass
Pass pass
none
none
none
Pass pass
  1. I had to remove the sun JDK/JVM and update my alternatives for java, javac and jar
  2. Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root