Demonstrating Red Hat JBoss AMQ 7 HA Replication Failover

A few weeks ago the newest version of Red Hat JBoss AMQ was released. AMQ 7 is the result of Red Hat’s efforts on creating an unified messaging platform for it’s middleware offerings. One of the most interesting features of this new version is the new backing strategies for failovering when configured in high availability. This feature allows clients connections to migrate from one server to another in event of server failure so client applications can continue to operate.Read More »

JBoss AMQ 7 GA Announced, Download it Today

Red Hat, Inc. (NYSE: RHT), the world’s leading provider of open source solutions, today introduced Red Hat JBoss AMQ 7. The latest release of Red Hat’s messaging platform combines the performance and efficiency of reactive programming with a more flexible architecture, giving customers a strong foundation for building distributed, reactive message-driven applications.Read More »

Implementing a Log Collector using JBoss Fuse and JBoss Data Grid

Most of the time, when we think about collecting, parsing and storing Logs, the first thing that pops in our mind is the ElasticStack or ELK.  It is well positioned in developer’s and sysadmin’s minds. The stack combines the popular Elasticsearch, Logstash and Kibana projects together to easy the collection/aggregation, store and visualization of application logs. As an Apache Camel rider and Infinispan enthusiast, I prepared this exercise to produce my own log collector and store stack using Red Hat’s products, JBoss Fuse and JBoss Data Grid, instead.Read More »

Log4j & JBoss

Quien no se ha enfrentado en algun momento con el siguiente mensaje:

ERROR: invalid console appender config detected, console stream is looping

Esto normalmente sucede al querer utilizar nuestras propias configuraciones de Log4j debido a que JBoss ya incluye configuración para el uso de esta librería. La solución es simple y no requiere de cambios en el codigo. Sólo debe incluirse la siguiente linea en las propiedades de la maquina virtual que se esta ejecutando:

-Dorg.jboss.logging.Log4jService.catchSystemOut=false

Configuracion de Log4j en JBoss
Configuracion de Log4j para JBoss

Con esto, dejamos lista la configuración para que los mensajes que enviemos al flujo de salida no sean administrados por el servicio de Log4j de JBoss. Espero les sea de utilidad ya que es una de las cosas que siempre me pasan cuando empiezo a trabajar con este servidor de aplicaciones.