Skip navigation

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.



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


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: JBREM000201: Received invalid message on Remoting connection 64726693 to /
19:40:43,895 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: JBREM000201: Received invalid message on Remoting connection 69123787 to /
19:40:44,006 ERROR [org.jboss.remoting.remote] (Remoting "greybeard:MANAGEMENT" read-1) JBREM000200: Remote connection failed: JBREM000201: Received invalid message on Remoting connection 190a621a to /


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.



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:




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,



Three Crazy Weeks

Posted by maxandersen Nov 22, 2011

I’ve been on the road two out of the last three weeks, speaking and attending three conferences: JUDCon London, EclipseCon in Ludwigsburg and finally Devoxx in Antwerp.

JUDCon London

At JUDCon I was co-hosting the third live JBoss Asylum Podcast together with Emmanuel Bernard. The topic was “Polyglot JBoss” with Marek Goldmann and Galder Zamarreno as guests talking about how JBoss supports, extends and develop on multiple languages outside just Java.

The recording of this is available on JBoss Asylum site or iTunes. curtesy Eric D. Schabell.


After the panel we got a set of lightning talks done by JBossians and external contributors which I had the pleasure of moderating. Was great fun.

I did the first lightning talk about how you make your examples for your framework/distribution the most accessible to users. Not everyone liked the conclusion, but I got good feedback on the content, thus I re-recorded the audio for this talk.


I’ve made the slides available together with the audio on JBoss Tools Vimeo group.



If  you just want the the slides you can get those from my SlideShare


At JUDCon I spent most of my time talking with attendees and colleagoues, but also did find time to attend a few talks. One of those stood out, namely “Hibernate Puzzlers” by Patrycja from @yonlabs. She presented a set of puzzlers and even though I knew all the issues she was presenting on, her puzzlers did caught me being unsure what the right answer was. Well worth watching if you get a chance.



At Eclipsecon Europe they were celebrating it was 10 years since the first release of Eclipse the IDE. I unfortunately missed out on the party and cake since I was sure the celebration would be on the Thursday not Wednesday. Instead I spent that evening having early dinner with Fred Bricon and then we went separate ways to prepare for our talks the next day.


Fred did his first public presentation for Red Hat called “Workaround Driven Development: How Maven integrates with Eclipse WTP”. He covered how the m2e-wtp project makes Maven usable in context of Eclipse WTP projects and how it was technically done by bridging Eclipse and Maven’s two different worldviews on projects.


All during EclipseCon we got very good feedback from users of m2e-wtp and how it was the piece they were missing to actually be productive within their work on enterprise projects - always good to hear we and especially Fred's work are making a difference.


My talk was about the experiences we’ve done with the move to Tycho on the JBoss Tools project. It was hard to boil it down to a 20 minutes presentation but I think I succeded.


If you want to see and hear the presentation it is available from EclipseCon’s audio/video recordings under: Tycho - The good, the bad and the ugly




Devoxx also had its 10th anniversary in Antwerp and I had the pleasure to attend and speak again this year. This year with a quickie  on how to “Deploy Java EE Applications to OpenShift”. I also got to reveal the news and do a demo of the new Jenkins support on OpenShift.

All in all a good talk but I don’t have a recording of this talk but the OpenShift team released a video covering similar content.



“Deploying Java Apps to the Cloud with the OpenShift Eclipse Plug-in”

They even made a cartoon over the whole OpenShift release including JBoss Tools called “A Comprehensive Lifecycle for Java Developers in the Cloud with OpenShift



Devoxx is also the conference in Europe where I get to meet up with many of the JBoss folks speaking there and this year was no exception. What was exceptional this year was though that we had a small booth this year leaving no space for the traditional fussball table. That was no fun. Lincoln, Kabir and I did though find a way have fun since there was beer and helium baloons at the booth:



AS7 is lightweight and superfast



Beyond having fun with helium I was also happy to hear that Google finally announced their opensourcing of their GWT Eclipse plugin tools. You can read my thoughts on that in my previous blog entry.


The most work was though on helping getting the Ceylon website and Eclipse updatesite ready for the planned launch at the end of Emmanuel Bernard and Stephan’s talk about Ceylon.


That turned out to be quite tricky despite Devoxx wifi being the best ever, but we made it through and now everyone can try out David Festal's Ceylon IDE by following the instructions on


Pierre-Antoine Gregorie snapped a photo of us hacking away on getting the site in shape:

Hacking on Ceylon


All in all three very busy weeks and I here I’m not even covering all the other work that went on, but I’ll hopefully be able to write about the end-results of that in the upcoming weeks and months.


Until then, Have fun!

Google today announced they are making “Google Plugin for Eclipse” and "GWT Designer" fully open source and available under the Eclipse Public license.


We have many developers using Google’s Eclipse plugin to develop GWT-based applications targeting the JBoss Application Server.


With the open sourcing of the plugin we are looking forward to working even more closely with the Google team and the rest of the community on making the developer experience even more productive and an integrated part of Eclipse platform.


We are especially interested in seeing the Google Eclipse plugins being able to target multiple runtimes such as the JBoss Enterprise Application Platform and Google App Engine in a uniform way, working more seamlessly with standards-based tools and frameworks.


This targeting of multiple runtimes will also help users of JBoss AS, Glassfish, Tomcat and any other server that provides an Eclipse Web Tools compatible server adapter.

JBoss Tools GWT Integration


JBoss Tools already provide integration with the previous release of GPE via our experimental JBoss GWT Integration.


Our experimental plugin allows you to easily use the Eclipse standard web wizards and projects instead of the Google specific wizards to create and deploy projects.


One of the reasons we marked this integration “experimental” was because opposite to what many believe large parts of Google’s plugins for Eclipse was not open sourced. That made the implementation dependent on non-public API and to use it you needed the GPE GWT plugins that was not possible to distribute freely.


Those concerns were the reasons I’ve been urging Google to make the GWT plugins open source so we and users could actually distribute and use the plugins freely and at the same time we could start contributing fixes and features and not just bugreports.


In the end this should allow for much more stable and uniform user experience. This goes not only for JBoss Tools plugins integration, but for integration across the Eclipse ecosystem such as Eclipse Web Tools Project and m2eclipse.


Some of the issues we had, have been fixed in GPE 2.0. Now with Google open sourcing their plugin we and others can help contribute and fix the remaining issues and implement enhancements to make easy usage of Google GWT across multiple platforms from Eclipse a reality.


None of this of course happen automatically but the open sourcing of the Google plugins definitely make it much easier and I look forward to see and support the work around these plugins.


Thank you Google - now let’s go and have Fun

Shift Happens in the last planned milestone of JBoss Tools 3.3. Read on for more...

3.3 M4 (Shift Happens)

[Download] [Update Site] [What's New] [Forums] [JIRA] [Twitter]


JBoss Tools is a set of plugins for Eclipse that complements, enhances and goes beyond the support that exist for JBoss and related technologies in the default Eclipse distribution.


This time around we are adding in a central hub for users called JBoss Central, support for OpenShift, some OSGi magic, Runtime downloads and more...




As always, get and install Eclipse 3.7 (Indigo) JEE bundle - with the JEE bundle you get majority of the dependencies letting you save bandwidth:


Once you have installed Eclipse, you either find us on Eclipse Marketplace under "JBoss Tools (Indigo)" or use our update site directly.


The updatesite URL to use from Help > Install New Software... is:

JBoss Central

First time you install JBoss Tools M4 you will be greeted with what we've named JBoss Central. JBoss Central is a hub for getting easy access to Project Wizards, Examples, news and additional Eclipse plugin installation.


It will show up on every startup by default which if you don't want it can be disabled in preferences. The editor will also show up when there are new updates to JBoss Tools plugins installed.


If you want to open central later you can find it under Help > JBoss Central.


OpenShift Express

OpenShift Express by Red Hat provides free, auto-scaling platform-as-a-service for Java, Ruby, PHP, Perl and Python applications. Until now to use it you've had to use command line tools like git and rhc-* commands; with JBoss Tools support for OpenShift you can do all of the hard work in the comfort of Eclipse.


To get started use the OpenShift Express Application Wizard available from File > New > OpenShift.


If you are a new user the wizard will walk you through the needed steps to setup an account, create domain and create applications.

If you are an existing user with existing applications it will allow you to log in, choose an application and import the project into Eclipse and in case of it being a JBoss 7 type application we will even setup a server for you in Eclipse server view that allows you to easily publish directly to OpenShift.


This publish is just a Git commit & push which you can also do from command line or manually via eGit in Eclipse - but with the server adapter integration you get a simple and easy way of doing it without having to deal with git manually.


Materialize Library

Eclipse likes to encapsulate jar library access in Classpath Container's and sometimes these classpath containers are great to begin with but for various reasons you might want to decouple your Eclipse projects from the plugin providing the classpath container or maybe you've used one of the great Project Examples or quickstarts we provide via JBoss Central but you don't want to use Maven to manage your libraries/build then this feature also comes handy.


We've added an experimental feature named "Materialize Library" which is available in the context menu of classpath containers in Eclipse.


Once you click that JBoss Tools will present you with a dialog asking where to put the libraries and once you press Ok your project will no longer be dependent on the classpath container, but instead have a copy of the jars and all configured as it was inside Java Build path still; allowing you to more easy build and migrate your project to another setup if need be.



Richfaces 4

We've implemented support in the visual page editor for the new and updated JSF components in Richfaces 4.


CDI & Seam Solder

The CDI tooling this time around continues to add more quick fixes, improved navigation and adds an "Open Named CDI Bean" dialog for easy lookup of named CDI beans.


It also adds support for the new package naming in Seam 3.1.Beta4 for the Solder and Config modules, while still maintaing support for previous Seam 3 releases.


Forge in Color

Forge console now has better editing, is now using color rendering and is made easily available with the new Ctrl+4 (or Cmd+4 on OSX) shortcut.




JBoss OSGi

The JBoss adapter now supports dragging Eclipse PDE (OSGi) projects to the server and it will use the default PDE export to create and bundle the archive.


Runtime downloads

JBoss Tools now provide easy access to download runtimes such as JBoss AS and Seam (more to be added in the future).

This feature are directly available from JBoss Tools Runtime Detection preference page.

or via use of Project Examples that requires a runtime.


The downloaded runtimes will be installed in a directory of your choosing and will be configured to be ready for use within Eclipse/JBoss Tools.


And more...

There are additional screenshot and features to browse over at What's New & Noteworthy


This is our last planned milestone, beta is next thus its time to make your voice heard and speak up if there are features that aren't giving you what you need.


Leave a comment to let us know!


And as always,

Have fun!

Filter Blog

By date:
By tag: