Test Day:2012-04-17 JBoss Application Server: Difference between revisions

Latest revision as of 21:34, 26 June 2015

Fedora Test Days

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

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]

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.

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 ...

Marek Goldmann (mgoldmann on IRC)

Prerequisite for Test Day[edit]

An Fedora 17 pre-release with all updates from updates-testing installed, Rawhide (tips on installing Rawhide below), or a nightly live image
Time
(optional) Your hardware profile uploaded to Smolt according to these instructions
(optional) Beer (if you're adult)

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]

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]

Deployment[edit]

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	warn ^[1]	fail ^[2]	none	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345
Pavel Zhukov	HW	none	none	none	none	none	none	none	none
vicodan	[VirtualBox VM x86_64]	pass	warn ^[1]	pass	pass	pass	warn ^[2]	pass	pass	↑ files are owned by root ↑ will provide further details shortly
Guido Grazioli	rawhide qemu-kvm	pass	warn ^[1]	pass ^[2]	pass	pass	pass	pass	none	↑ /etc/jboss-as/domain/mgmt-users.properties unexpectedly owned by root ↑ need jboss-drm >= 1.1.1-4.fc18
Marek Goldmann	HW	none	none	pass	pass	pass	pass	pass	pass
Jóhann B. Guðmundsson	HW	pass	warn ^[1]	pass	pass	none	none	none	none	↑ Confirmed /etc/jboss-as/{standalone\|domain}/mgmt-users.properties unexpected owned by root
Stanislav Ochotnicky	HW	warn ^[1]	pass	pass	pass	pass	pass	pass	pass	↑ At one point systemctl status showed jboss as running even though the process failed (due to incorrect current JVM)
Filipe Rosset	HW	warn ^[1]	warn ^[2]	pass	pass	none	none	none	pass	↑ I had to remove the sun JDK/JVM and update my alternatives for java, javac and jar ↑ Confirmed /etc/jboss-as/{standalone\|domain}/mgmt-users.properties unexpected owned by root

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[3] s are owned by root

[4] will provide further details shortly

[5] /etc/jboss-as/domain/mgmt-users.properties unexpectedly owned by root

[6] ss-drm >= 1.1.1-4.fc18

[7] Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root

[8] At one point systemctl status showed jboss as running even though the process failed (due to incorrect current JVM)

[9] I had to remove the sun JDK/JVM and update my alternatives for java, javac and jar

[10] Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root

[1]

[2]

[1]

[2]

[1]

[2]

[1]

[1]

[1]

[2]

@@ Line 49: / Line 49: @@
 == How to test? ==
-High level details on how a contributor can get involved.  This can include (but not limited to):
+Additional to below test cases, you can (or even should!) do some testing on your own!
-* Areas to target with exploratory testing
+Some hints:
-* A list of pre-defined test cases to execute
-* How to report back results
-Here's another common chunk (again, replace XX as above):
+* 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!)
-=== '''Update your machine''' ===
-If you're running Fedora XX, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the [[Releases/Rawhide|Rawhide]] page on the various ways in which you can install or update to Rawhide. Or:
-=== '''Live image''' ===
-Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at [[FedoraLiveCD]]. Live images can be found [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ here].
 == Test Cases ==
-=== Basic ===
+{{admon/important|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 [https://admin.fedoraproject.org/updates/jboss-as-7.1.0-3.fc17 submitted as an update]. It should be available in <code>updates-testing</code> for the Test Day time. If not - please download it directly from Koji.}}
-# [[QA:Testcase_JBoss_AS_Install_and_run|Install and run]]
 === Management ===
-TBD
+# [[QA:Testcase_JBoss_AS_Install_and_run|Install and run]]
+# [[QA:Testcase_JBoss_AS_Add_management_user|Add management user]]
+# [[QA:Testcase_JBoss_AS_Execute_readonly_management_tasks|Execute readonly management tasks]]
+# [[QA:Testcase_JBoss_AS_Execute_read-write_management_tasks|Execute read-write management tasks]]
 === Deployment ===
-TBD
+# [[QA:Testcase_JBoss_AS_Deploy_servlet_application|Deploy servlet application]]
+# [[QA:Testcase_JBoss_AS_Deploy_CDI_application|Deploy CDI application]]
+# [[QA:Testcase_JBoss_AS_Deploy_EJB_application|Deploy EJB application]]
+# [[QA:Testcase_JBoss_AS_Deploy_EJB_in_WAR|Deploy EJB-in-WAR quickstart]]
+{{admon/tip|Other applications|A pretty good resource for sample apps is the [http://openejb.apache.org/examples-trunk/index.html OpenEJB site]. But be careful when reporting issues.}}
 == Test Results ==
-Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
+If you have problems with any of the tests, [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=17&component=jboss-as report a bug] to [https://bugzilla.redhat.com Bugzilla].
-If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
+'''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 [[Template:result|result template]] to enter your result, as shown in the example result line.
 {|
 ! User
 ! Smolt Profile
-! [[QA:Testcase_sample_1|Sample test 1]]
+! [[QA:Testcase_JBoss_AS_Install_and_run|Install and run]]
-! [[QA:Testcase_sample_2|Sample test 2]]
+! [[QA:Testcase_JBoss_AS_Add_management_user|Add management user]]
-! [[QA:Testcase_sample_3|Sample test 3]]
+! [[QA:Testcase_JBoss_AS_Execute_readonly_management_tasks|Execute readonly management tasks]]
-! [[QA:Testcase_sample_4|Sample test 4]]
+! [[QA:Testcase_JBoss_AS_Execute_read-write_management_tasks|Execute read-write management tasks]]
+! [[QA:Testcase_JBoss_AS_Deploy_servlet_application|Deploy servlet application]]
+! [[QA:Testcase_JBoss_AS_Deploy_CDI_application|Deploy CDI application]]
+! [[QA:Testcase_JBoss_AS_Deploy_EJB_application|Deploy EJB application]]
+! [[QA:Testcase_JBoss_AS_Deploy_EJB_in_WAR|Deploy EJB-in-WAR quickstart]]
 ! References
 |-
 | [[User:SampleUser|Sample User]]
 | [http://www.smolts.org/client/show/pub_84465125-1350-4f83-87b9-5f16f7430eb8 HW]
 | {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
 | {{result|pass}}
 | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
 | {{result|fail}} <ref>{{bz|12345}}</ref>
+| {{result|none}}
+| <references/>
+|-
+| [[User:Landgraf|Pavel Zhukov]]
+| [http://www.smolts.org/client/show/pub_d48e8798-a431-4297-a9c9-9e3fd31afd88 HW]
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
 | <references/>
 |-
+| [[User:vicodan|vicodan]]
+| [VirtualBox VM x86_64]
+| {{result|pass}}
+| {{result|warn}} <ref>files are owned by root</ref>
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|warn}} <ref>will provide further details shortly</ref>
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+| [[User:Guidograzioli|Guido Grazioli]]
+| rawhide qemu-kvm
+| {{result|pass}}
+| {{result|warn}} <ref>/etc/jboss-as/domain/mgmt-users.properties unexpectedly owned by root</ref>
+| {{result|pass}} <ref>need jboss-drm >= 1.1.1-4.fc18</ref>
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|none}}
+| <references/>
+|-
+| [[User:Goldmann|Marek Goldmann]]
+| [http://www.smolts.org/client/show/pub_7587511c-90d3-4d99-a825-5f67a06b7cd9 HW]
+| {{result|none}}
+| {{result|none}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+| [[User:Johannbg|Jóhann B. Guðmundsson]]
+| [http://www.smolts.org/client/show/pub_cd69e3f0-d810-4db9-b6b5-6118afd28f5d HW]
+| {{result|pass}}
+| {{result|warn}} <ref> Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root</ref>
+| {{result|pass}}
+| {{result|pass}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| <references/>
+|-
+| [[User:Sochotni|Stanislav Ochotnicky]]
+| [http://www.smolts.org/client/show/pub_d04c3a62-20da-45e9-9433-63846b3d90ca HW]
+| {{result|warn}} <ref>At one point systemctl status showed jboss as running even though the process failed (due to incorrect current JVM)</ref>
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| {{result|pass}}
+| <references/>
+|-
+| [[User:filiperosset|Filipe Rosset]]
+| [http://www.smolts.org/client/show/pub_e477e58a-ed32-4ca9-8888-9183b85725ca HW]
+| {{result|warn}} <ref> I had to remove the sun JDK/JVM and update my alternatives for java, javac and jar </ref>
+| {{result|warn}} <ref> Confirmed /etc/jboss-as/{standalone|domain}/mgmt-users.properties unexpected owned by root</ref>
+| {{result|pass}}
+| {{result|pass}}
+| {{result|none}}
+| {{result|none}}
+| {{result|none}}
+| {{result|pass}}
+| <references/>
 |}
-[[Category:Test Days]]
-[[Category:QA Templates]]
+[[Category:Fedora 17 Test Days|s]]

Search