Archive | jboss RSS feed for this section

JBoss World 2011 Presentations

(Full Story: JBoss World 2011 Presentations)


JBoss Tattletale – betraying your project’s naughty little secrets

The tool will provide you with reports that can help you

Identify dependencies between JAR files
Find missing classes from the classpath
Spot if a class/package is located in multiple JAR files
Spot if the same JAR file is located in multiple locations
With a list of what each JAR file requires and provides
Verify the SerialVersionUID of a class
Find similar JAR files that have different version numbers
Find JAR files without a version number
Find unused JAR archives
Identify sealed / signed JAR archives
Locate a class in a JAR file
Get the OSGi status of your project
Remove black listed API usage
And generate the same reports for your .WAR and .EAR archives

(Full Story: JBoss Tattletale – betraying your project’s naughty little secrets)

How JBoss Did It

One of the key points to understand about this model: instead of building a very expensive marketing process like their competitors BEA and IBM, JBoss used their R&D resources to build a free product that achieved the same goal: widespread product awareness, and high customer demand – all for zero marketing costs.

(Full Story: How JBoss Did It)

Migrating RESTful Transactions to OpenShift Express: Part 1 on Vimeo

Part 1 of two videos showing the process of how to migrate applications to the Red Hat OpenShift infrastructure. Part 1 describes the application and demonstrates how to deploy and run it locally. The application comprises two REST based services: a transaction coordinator which is deployed to a JBoss AS7 container and a simple service deployed into an embedded container. The client that interacts with the two services, written using javascript starts a transaction, makes transactional calls to two web services and then ends the transaction. Recovery from failures is also demonstrated.

(Full Story: Migrating RESTful Transactions to OpenShift Express: Part 1 on Vimeo)

Largest JGroups cluster ever: 536 nodes – Bela’s Blog

The setup was 130 celeron based blades with 1GB of memory, each running 4 JVMs with 96MB of heap, plus 4 embedded devices with 4 JVMs running on each. Each blade had 2 1GB NICs setup with IP Bonding. Note that the 4 processes are competing for CPU time and network IO, so with more blades or more physical memory available, I’m convinced we could go to 1000+ nodes !

(Full Story: Largest JGroups cluster ever: 536 nodes – Bela’s Blog)

Verizon Recognized for Technological Achievements and Innovation in Use of Open Source and Middleware Solutions

The award, announced during the Red Hat Summit and JBoss World on May 6 in Boston, recognizes Verizon for “the most successful migration from proprietary solutions to open source alternatives.”
Specifically, Verizon won the award for the company’s implementation of a new standards-based business process-management system for the company’s Integrated Management Platform for Advanced Communications Technologies automated platform, which monitors, troubleshoots and resolves network service interruptions.

(Full Story: Verizon Recognized for Technological Achievements and Innovation in Use of Open Source and Middleware Solutions)

JBoss MAT – Migration Assessment Tool

This tool is used as a starting point for estimating the effort required to migrate a group of J2EE applications from an Oracle/BEA WebLogic environment to a JBOSS AS environment.
The tool produces reports, in HTML format, on the following information:1) Class Dependencies:2) WebLogic Server Configuration:3) Applications deployment configuration

(Full Story: JBoss MAT – Migration Assessment Tool)

Stay Productive with Java Server Growl Notifications

When developing it’s easy to get distracted while waiting for a Java Application Server to restart.

Inspired by Ben Ellingson I went looking for a way to get Growl notifications when my local JBoss server had started.   I couldn’t find much so I threw a java solution together such that whenever your JBoss server has started or shuts down you get a notification like:

I think this might be useful to others, so the code is below and the installation instructions for JBoss 5 are:

  1. If you don’t already have them, install growl and growlnotify
  2. Copy the compiled Growler.class (remove .odt from this) and Growler.command (remove .odt from this) to <JBOSS_HOME>/bin
  3. Configure the last line in Growler.command, the options are:
    1. -u Specify the username for JBoss authentication(defaults to admin)
    2. -p Specify the password for JBoss authentication(defaults to admin)
    3. -s Use sticky growl notification windows(defaults to not sticky)
    4. -i The location of the JBoss Developer Studio.ico file (defaults to /Applications/jbds/eclipse/jbds.ico)
  4. If you want to run Growler on demand simply launch Growler.command whenever you launch eclipse
  5. However if you want Growler to always be running you’ll need to create a Launch Agent, to do so:
    1. Copy the attached info.sordyl.Growler.plist (remove .odt from this) to your user Launch Agent folder at ~/Library/LaunchAgents/
    2. Open your copy of info.sordyl.Growler.plist
    3. Edit Item 0 under ProgramArguments and update YOUR_JBOSS_HOME_PATH to point to where your Growler.command file lives in <JBOSS_HOME>/bin

Here is the source as well; the code can be easily modified to monitor for changes in any JMX property, to access other JMX enabled servers or to access remote server(s).  As written this assumes JBoss 5.x.

import gnu.getopt.Getopt;
import java.util.ArrayList;
import javax.naming.CommunicationException;
import javax.naming.InitialContext;
import javax.naming.NamingException;

 * Install growl and growlnotify
 * usage: Growler [options]
 * -u <name>    	Specify the username for authentication
 * -p <name>    	Specify the password for authentication
 * -s    			Use sticky growl notification windows
 * -i <filepath>	The location of the JBoss Developer Studio .ico file
 * @author <a href="">Brent Sordyl</a>
public class Growler {

	// Use sensible defaults for all properties
	private String username = "admin";
	private String password = "admin";
	private int pollingFrequency = 3;
	private String jbdsIconLocation = "/Applications/jbds/eclipse/jbds.ico";
	private String growlTitle = "JBoss Application Server";
	private String serverStartedMessage = "Server Started";
	private String serverShutdownMessage = "Server is shutting down";
	private boolean stickyGrowlNotifications = false;
	private String jndiUrl = "jnp://localhost:1099";

	public Growler(String[] args) {

	 * The main method that checks for changes in
	 * server state and sends growl notifications.
	 * @param args the command line arguments
	public static void main(String[] args) {
		Growler g = new Growler(args);
		boolean lastStatus = false;

		while (true) {
				boolean currentStatus = g.isJBoss5Up();
				if ( (currentStatus != lastStatus) && currentStatus) {
					sendNotification(g.growlTitle, g.serverStartedMessage,  g.jbdsIconLocation, g.stickyGrowlNotifications);
				} else if (currentStatus != lastStatus) {
					sendNotification(g.growlTitle, g.serverShutdownMessage, g.jbdsIconLocation, g.stickyGrowlNotifications);

				lastStatus = currentStatus;
				Thread.sleep(g.pollingFrequency * 1000);
			} catch (Exception e) {

	 * Checks if the JBoss 5 server is up, this
	 * will need to change for JBoss 6 per
	 * @return true, if is server up
	 * @throws Exception the exception
	private boolean isJBoss5Up() throws Exception
		boolean up = false;
		try {
			SecurityAssociation.setPrincipal(new SimplePrincipal(username));

	    	System.setProperty("java.naming.provider.url", jndiUrl);
		  	System.setProperty("java.naming.factory.initial", "org.jnp.interfaces.NamingContextFactory");
	    	System.setProperty("java.naming.provider.url.pkgs", "org.jboss.naming");
	    	System.setProperty("java.naming.provider.url.pkgs", "org.jnp.interfaces");

			InitialContext ctx = new InitialContext();
			MBeanServerConnection server = (MBeanServerConnection) ctx.lookup("jmx/invoker/RMIAdaptor");
			up = Boolean.parseBoolean((server.getAttribute(new ObjectName("jboss.system:type=Server"), "Started")).toString());
		} catch (CommunicationException ce) {} 	// Exception expected when server is shutdown
		  catch (NamingException ne) {} 		// Exception expected when server is starting or stopping

		return up;

	 * Sends a growl notification using growlnotify.
	 * @param title the title
	 * @param message the message
	 * @param jbdsIconLocation the jbds icon location
	 * @param sticky the sticky
	private static void sendNotification(String title, String message, String jbdsIconLocation, boolean sticky) {
		ArrayList<String> args = new ArrayList<String>();
		if (sticky)

		try {
			Process exec = Runtime.getRuntime().exec( args.toArray(new String[] {}) );
		} catch (IOException e) {

	 * Process command line arguments
	 * to override default values.
	 * @param args the command line args to parse
	private void processArguments(final String[] args) {
		try {
			String sopts = "u:p:i:s";
			Getopt getopt = new Getopt("Growler", args, sopts);
			int code;
			while ((code = getopt.getopt()) != -1) {
				switch (code) {
					case 'u':
						username = getopt.getOptarg();
					case 'p':
						password = getopt.getOptarg();
					case 's':
						stickyGrowlNotifications = true;
					case 'i':
						jbdsIconLocation = getopt.getOptarg();
		} catch (Exception e) {