Red Hat
Nov 24, 2011
by Max Rydahl Andersen

Yesterday JBoss AS team released JBoss AS 7.1 Beta1 - the best release ever with some great stuff and an out-of-the-box secured server.

 

Note:

Since this blog post was written a new version of AS 7.1 and JBoss Tools have been released which works out-of-the-box.

See details at http://community.jboss.org/community/tools/blog/2011/12/23/jboss-tools-m5-is-coming-to-town

 

We knew that the out-of-the-box secured server would require changes to JBoss Tools to handle it, but it also turns out there is an unforseen incompatibility between the AS 7.1 Beta1 and AS 7.0 Final client jars that we use to talk to the AS server.

 

Thus if you use JBoss AS 7.1 Beta1 with JBoss Tools and start it up without changing anything you will see errors similar to this in the console output of the server:

 

19:40:43,780 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 64726693 to /127.0.0.1:62248
19:40:43,895 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 69123787 to /127.0.0.1:62249
19:40:44,006 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: java.io.IOException: JBREM000201: Received invalid message on Remoting connection 190a621a to /127.0.0.1:62250

 

These are caused from the server seeing our "ping" to the server trying to get an answer to if the server is ready and launched but because of the incompatiblity bug it is resulting in these errors instead.

 

Eventually JBoss Tools will give up and report an error about the server startup not being detected.

 

To avoid seeing these errors and to be able to work with the server even though you secure it, there is a workaround for JBoss Tools.

 

You simply need to change the "Startup Poller" from "JBoss 7 Manager Service" to use "Web Port" instead and disable the Automatic detection of the management port. The details on that is described below.

 

How to workaround AS 7.1 not being recognized

 

In the "Servers" view double click on the server and it should open up the server editor:

 

Note that since JBoss Tools only know about "JBoss 7.0" that is what the default server will be called if you haven't typed in something else.

 

jbossas7_1oob.png

In here are the settings that need to be changed.

 

  1. Change "Startup Poller" to "Web Port"
  2. Remove the checkmark from "Automatically detect" under "Server Ports/Management"
  3. Type in '9999' into the Management field.
  4. Save (Ctrl+S) the configuration

 

Once you have done that it should look something like this:

 

as7_1_fixed.png

 

Now when you start this server we will no longer use the management API to check if the server is running but instead

just check if http://localhost:8080 is available.

 

I'm sorry for the trouble and we are working hard on getting it fixed and supported in next milestone of JBoss Tools.

 

You can monitor JBIDE-10224 to see the progress on the JBoss Tools side.

 

But do try to still Have Fun,

Max