JBoss 7.0.2--More Than A Smoke Test

Jboss 7.0.2 is Java EE 6 WebProfile certified, opensource server.
The test:

  1. Download size of Jboss 7.0.2. "Web Profile Only (Java EE6 Certified)" is: 68 MB. The size of "everything edition" is: 75 MB
  2. Installation = Unzip
  3. Disc size: 88,9 MB after installation
  4. Startup: Execution of jboss-as-7.0.2.Final/bin/standalone.sh -server-config=standalone-preview.xml (this activates the "full" Java EE 6 features) is: 07:40:42,312 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.0.2.Final "Arc" started in 2384ms - Started 93 of 148 services (55 services are passive or on-demand)
  5. Instead of the simplistic ServerSmokeTest.war, I used the fully featured x-ray application for test this time. Only the name of the datasource was changed and a single hibernate parameter provided. You will find these changes in the jboss-as-7 branch in the GIT repo The persistence.xml was changed at two places:
    
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
      <persistence-unit name="hitscounter" transaction-type="JTA">
        <jta-data-source>java:jboss/datasources/ExampleDS</jta-data-source>
        <properties>
          <property name="eclipselink.ddl-generation" value="create-tables"/>
          <property name="eclipselink.cache.size.default" value="10000"/>
          <property name="eclipselink.cache.type.default" value="Soft"/>
          <!-- <property name="eclipselink.logging.parameters" value="true"/> -->
          <property name="hibernate.hbm2ddl.auto" value="create-drop"/>
        </properties>
      </persistence-unit>
    </persistence>
    
    
  6. X-ray (it is the statistic application in the right upper corner in my blog, and a book sample), works without any modification on GlassFish 3.1.1 and Jboss 7.0.2. X-ray uses JPA, EJB 3.1 (@Asynchronous, @Schedule, dynamic timers), CDI (@Produces, @Qualifiers), Interceptors, JMX beans etc… The deployment took ~3 sec (with table creation etc.) and worked without any problems.
  7. Jboss 7 works in the clouds as well.
  8. Conclusion: Jboss 7.0.2 looks promising: it is fast and lean. The only problem is rather "political". It is not easy (impossible?) to get commercial support from RedHat for Jboss 7.0.2.

Comments:

For commercial support from RedHat, you have to wait for the JBoss EAP 6 version. It will be based on JBoss AS 7.1. I don't know if a release date has already been announced, but I saw that it would be scheduled for Q1-2012.

The bad part is that the commercial support is not provided on the AS version, but on a specific one ; just like for the AS 5 / EAP 5.

Posted by Alexis Hassler on October 13, 2011 at 03:13 PM CEST #

Nice entry, Adam.

One note: Commercial Support for JBoss AS7 will be available as part of EAP6 once launched. Our community versions are the upstream for the supported product.

S,
ALR

Posted by Andrew Lee Rubinger on October 14, 2011 at 11:14 AM CEST #

@Andrew,

I would make the commercial support more straight-forward: just download + pay :-)

That is the feedback I frequently get.

Is there no commercially supported"early access program?

thanks for your comment!,

adam

Posted by Adam Bien on October 14, 2011 at 11:54 AM CEST #

Adam, commercial support will be available when we release JBoss EAP 6 (based on JBoss AS 7.1.something).

Right now EAP 6 is in the Early Access phase - we're working closely with a small number of customers. By the end of the year we will have a broader Beta release which customers and prospects will be able to access via Red Hat's customer portal.

EAP 6 GA is planned for the first qtr on next calendar year.

Rich Sharples
Red Hat

Posted by Rich Sharples on October 14, 2011 at 04:31 PM CEST #

@Adam:

The problem w/ "Download and Pay" is that it doesn't scale so nicely. We want to allow the upstream to move much, much faster than the product intentionally; once forked, EAP receives only bug fixes in order to protect customers and ensure that upgrades go smoothly. The differentiation is about stability vs. pacing.

There is an Early Access Program for EAP6, however: http://www.jboss.com/eap6-early-access/

S,
ALR

Posted by Andrew Lee Rubinger on October 14, 2011 at 08:10 PM CEST #

Adam, there is an early access program for select customers:

http://www.jboss.com/eap6-early-access/

Posted by Dimitris Andreadis on October 14, 2011 at 09:39 PM CEST #

I tried to deploy the x-ray.war to jboss 7.0.2. The database is created.

16:54:29,543 INFO [org.jboss.web] (MSC service thread 1-2) registering web context: /x-ray
16:54:29,629 INFO [org.jboss.as.server.controller] (HttpManagementService-threads - 2) Deployed "x-ray.war"

but when I go to http://localhost:8080/xray
I get a 404 error.

Is there any other file part from the persistence i need to modify?

Posted by dimitri on November 16, 2011 at 06:25 PM CET #

Post a Comment:
  • HTML Syntax: NOT allowed
...the last 150 posts
...the last 10 comments
License