Category Archives: jboss

profile remote host jboss7 with jprofiler

June 24, 2014java, jboss, jprofileradmin

local machine
– create ssh tunnel : ssh -L 8849:127.0.0.1:8849 remoteuser@remotehost
– launch jprofiler : e.g. /mnt/jprofiler7/bin/jprofiler
– new session -> remote host -> enter host 127.0.0.1 as port 8849 -> save session (don’t start session you must accomplish remote host configuration and restart server before)

remote host (linux x64)
– install(unzip) jprofiler in any folder in remote host file system : e.g. /opt/jprofiler
– edit $JBOSS_HOME/bin/standlaone.sh and add following (this will launch jprofiler agent uppon jboss server. jprofiler agent will listen on port 8849)

export JAVA_OPTS="$JAVA_OPTS -agentpath:/opt/jprofiler/bin/linux-x64/libjprofilerti.so=port=8849"

1	export JAVA_OPTS="$JAVA_OPTS -agentpath:/opt/jprofiler/bin/linux-x64/libjprofilerti.so=port=8849"

– restart jboss server

local machine
– start jprofiler saved session

That’s all

Jboss7 (jboss-cli) : how to redirect specified class log in specified file

April 17, 2014jbossadmin

Don’t edit standalone.xml and then restart jboss, just use jboss-cli commands. Only three steps are enough

1. Add a file log handler

/subsystem=logging/file-handler=HANDLER_NAME:add(file={“path”=>”FILE_NAME“,”relative-to”=>”jboss.server.log.dir”},level=”LEVEL“)

2. Add a log category

/subsystem=logging/logger=CATEGORY_NAME:add(level=”LEVEL“)

3. Add a log handlers to a log category

/subsystem=logging/logger=CATEGORY_NAME:assign-handler(name=”HANDLER_NAME“)

done…

By example : We have to redirect net.witr.MyClass info logs to witr.log file

[witr@WITR-PC]#cd $JBOSS_HOME
[witr@WITR-PC]#./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9991 /] /subsystem=logging/file-handler=WITR_HANDLER:add(file={"path"=>"witr.log","relative-to"=>"jboss.server.log.dir"},level="INFO")
[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.MyClass:add(level="INFO")
[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.MyClass:assign-handler(name="WITR_HANDLER")

[witr@WITR-PC]#cd $JBOSS_HOME

[witr@WITR-PC]#./bin/jboss-cli.sh

You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.

[disconnected /] connect

[standalone@localhost:9991 /] /subsystem=logging/file-handler=WITR_HANDLER:add(file={"path"=>"witr.log","relative-to"=>"jboss.server.log.dir"},level="INFO")

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.MyClass:add(level="INFO")

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.MyClass:assign-handler(name="WITR_HANDLER")

Jboss7 : useful jboss-cli commands

March 20, 2014jbossadmin

jboss7 offer jboss-cli (command line interface) which makes live easier for administrators.

First of all connect to jboss-cli as following

connect to jboss-cli : connect

[witr@WITR-PC]#cd $JBOSS_HOME
[witr@WITR-PC]#./bin/jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
[standalone@localhost:9991 /]

[witr@WITR-PC]#cd $JBOSS_HOME

[witr@WITR-PC]#./bin/jboss-cli.sh

You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.

[disconnected /] connect

[standalone@localhost:9991 /]

Then, here some useful jboss-cli commands

undeploy and redeploy artifacts : deploy/undeploy

[standalone@localhost:9991 /] undeploy witr-4.2.15.war
[standalone@localhost:9991 /] deploy standalone/deployments/witr-4.2.15.war

1 2	[standalone@localhost:9991 /] undeploy witr-4.2.15.war [standalone@localhost:9991 /] deploy standalone/deployments/witr-4.2.15.war

list already deployed artifacts : deploy -l

[standalone@localhost:9991 /] deploy -l
NAME                          RUNTIME-NAME                  ENABLED STATUS 
wReport-4.0.13.war            wReport-4.0.13.war            true    OK     
witr-4.2.15.war               witr-4.2.15.war               true    OK     
witr-ws-4.0.1.jar             witr-ws-4.0.1.jar             true    OK     
[standalone@localhost:9991 /]

[standalone@localhost:9991 /] deploy -l

NAME RUNTIME-NAME ENABLED STATUS

wReport-4.0.13.war wReport-4.0.13.war true OK

witr-4.2.15.war witr-4.2.15.war true OK

witr-ws-4.0.1.jar witr-ws-4.0.1.jar true OK

[standalone@localhost:9991 /]

handle log levels : /subsystem=logging

Add new log level “INFO” on class net.witr.home.Himmel

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:add(level=INFO)
{"outcome" => "success"}
[standalone@localhost:9991 /]

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:add(level=INFO)

{"outcome" => "success"}

[standalone@localhost:9991 /]

Change log level of class net.witr.home.Himmel to “DEBUG”

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:change-log-level(level=DEBUG)
{"outcome" => "success"}
[standalone@localhost:9991 /]

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:change-log-level(level=DEBUG)

{"outcome" => "success"}

[standalone@localhost:9991 /]

Remove log level of class net.witr.home.Himmel

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:remove
{"outcome" => "success"}
[standalone@localhost:9991 /]

[standalone@localhost:9991 /] /subsystem=logging/logger=net.witr.home.Himmel:remove

{"outcome" => "success"}

[standalone@localhost:9991 /]

handle system properties : /system-property
Add, read and remove system property witrActive

[standalone@localhost:9991 /] /system-property=witrActive:add(value=Y)
{"outcome" => "success"}
[standalone@localhost:9991 /] /system-property=witrActive:read-resource
{
    "outcome" => "success",
    "result" => {"value" => "Y"}
}
[standalone@localhost:9991 /] /system-property=witrActive:remove
{"outcome" => "success"}

[standalone@localhost:9991 /] /system-property=witrActive:add(value=Y)

{"outcome" => "success"}

[standalone@localhost:9991 /] /system-property=witrActive:read-resource

{

"outcome" => "success",

"result" => {"value" => "Y"}

}

[standalone@localhost:9991 /] /system-property=witrActive:remove

{"outcome" => "success"}

ajax displaying jboss server state

January 17, 2014ajax, javascript, jboss, phpadmin

We aim to have web page which displays continually three jboss7 servers states.
For this we need the shell script (status.sh) to be found here.

environment requirement

apache server
three jboss7 servers: jboss1, jboss2, jboss3

get result of status.sh in our php file

Following php code displays one jboss server state

echo exec('/path/to/script/status.sh /path/to/jboss/home')

1	echo exec('/path/to/script/status.sh /path/to/jboss/home')

For our example we need three php files containing the previous one line php code corresponding to each one of the three jboss server : state-jboss1.php, state-jboss2.php, and state-jboss3.php

ajax state display

We need here the load() method of jquery javascript framework.

  <span id="jboss"></span><br/>

  <script language="javascript">
      $('#jboss').load('state-jboss.php');
  </script>

$('#jboss').load('state-jboss.php');

</script>

continuous update of servers state

We’ll resort to javascript timer

setInterval(function(){$('#jboss').load('state-jboss.php')},3000);

1	setInterval(function(){$('#jboss').load('state-jboss.php')},3000);

deloyment

create folder jboss-state in apache server root www

www/jboss-state/status.sh
www/jboss-state/index.html
www/jboss-state/state-jboss1.php
www/jboss-state/state-jboss2.php
www/jboss-state/state-jboss3.php

full code

status.sh (myArtifactName string in code must be replaced by the right artifact name)

#!/bin/bash

res=$($1/bin/jboss-cli.sh --commands="connect,read-attribute server-state" 2>&1)

if [[ $res != 'running' ]]
then
        echo "STOPPED ($res)"
else
        artifactDeployed=$($1/bin/jboss-cli.sh --commands="connect,deploy -l" | grep myArtifactName | grep OK  2>&1)
        if [[ X$artifactDeployed == 'X' ]]
        then
                echo "STARTING ($res / $artifactDeployed)"
        else
                echo "RUNNING ($res / $artifactDeployed)"
        fi
fi

#!/bin/bash

res=$($1/bin/jboss-cli.sh --commands="connect,read-attribute server-state" 2>&1)

if [[ $res != 'running' ]]

then

echo "STOPPED ($res)"

else

artifactDeployed=$($1/bin/jboss-cli.sh --commands="connect,deploy -l" | grep myArtifactName | grep OK 2>&1)

if [[ X$artifactDeployed == 'X' ]]

then

echo "STARTING ($res / $artifactDeployed)"

else

echo "RUNNING ($res / $artifactDeployed)"

state-jboss1.php

<?php echo exec('jboss-state/status.sh /path/to/jboss1/home'); ?>

1	<?php echo exec('jboss-state/status.sh /path/to/jboss1/home'); ?>

state-jboss2.php

<?php echo exec('jboss-state/status.sh /path/to/jboss2/home'); ?>

1	<?php echo exec('jboss-state/status.sh /path/to/jboss2/home'); ?>

state-jboss3.php

<?php echo exec('jboss-state/status.sh /path/to/jboss3/home'); ?>

1	<?php echo exec('jboss-state/status.sh /path/to/jboss3/home'); ?>

index.html

<html>
  <body>
    Jboss1 state : <span id="jboss1"></span><br/>
    Jboss2 state : <span id="jboss2"></span><br/>
    Jboss3 state : <span id="jboss3"></span><br/>

    <script language="javascript">
        setInterval(function(){$('#jboss1').load('state-jboss1.php')},3000);
        setInterval(function(){$('#jboss2').load('state-jboss2.php')},3000);
        setInterval(function(){$('#jboss3').load('state-jboss3.php')},3000);
    </script>
  </body>
</html>

<html>

<body>

Jboss1 state : <span id="jboss1"></span><br/>

Jboss2 state : <span id="jboss2"></span><br/>

Jboss3 state : <span id="jboss3"></span><br/>

setInterval(function(){$('#jboss1').load('state-jboss1.php')},3000);

setInterval(function(){$('#jboss2').load('state-jboss2.php')},3000);

setInterval(function(){$('#jboss3').load('state-jboss3.php')},3000);

</script>

</body>

</html>

get jboss7 server state with shell script

January 17, 2014jboss, shelladmin

Shell script (status.sh) bellow returns three jboss server state :

STOPPED : jboss is stopped (script could not connect with jboss-cli)
STARTING : jboss is starting (its state is running but project is not deployed)
RUNNING : jboss is ready (its state is running and project is deployed successfully)

Use :

> ./status.sh /path/to/jbossHome

This script may be improved …
Also you need to replace in code myArtifactName fake value by your right value

#!/bin/bash

res=$($1/bin/jboss-cli.sh --commands="connect,read-attribute server-state" 2>&1)

if [[ $res != 'running' ]]
then
        echo "STOPPED ($res)"
else
        artifactDeployed=$($1/bin/jboss-cli.sh --commands="connect,deploy -l" | grep myArtifactName | grep OK  2>&1)
        if [[ X$artifactDeployed == 'X' ]]
        then
                echo "STARTING ($res / $artifactDeployed)"
        else
                echo "RUNNING ($res / $artifactDeployed)"
        fi
fi

#!/bin/bash

res=$($1/bin/jboss-cli.sh --commands="connect,read-attribute server-state" 2>&1)

if [[ $res != 'running' ]]

then

echo "STOPPED ($res)"

else

artifactDeployed=$($1/bin/jboss-cli.sh --commands="connect,deploy -l" | grep myArtifactName | grep OK 2>&1)

if [[ X$artifactDeployed == 'X' ]]

then

echo "STARTING ($res / $artifactDeployed)"

else

echo "RUNNING ($res / $artifactDeployed)"

secure jboss7 with ssl (https)

June 27, 2013https, jboss, ssladmin

1. create keystore certificate for jboss user
> keytool -genkey -alias jboss -keyalg RSA

2. edit jboss configuration file standalone.xml:
– in interfaces : add new interface “local”

    <interfaces>
       ......
        <interface name="local">
            <inet-address value="127.0.0.1"/>
        </interface>
        ......
    </interfaces>

......

<inet-address value="127.0.0.1"/>

</interface>

......

</interfaces>

– in socket binding : add new socket binding “httpLocal” listening on localhost with http

    <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">
       ......
        <socket-binding name="httpLocal" interface="local" port="8080"/>
       ......
    </socket-binding-group>

<socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}">

......

<socket-binding name="httpLocal" interface="local" port="8080"/>

......

</socket-binding-group>

– remove http connector :
~~<connector name=”http” protocol=”HTTP/1.1″ scheme=”http” socket-binding=”http”/>~~

– add local http connector (for modules having to communicate in http with each others)

– add new https connector

in subsystem web we must finally have :

        <subsystem xmlns="urn:jboss:domain:web:1.1" default-virtual-server="default-host" native="false" >
            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="httpLocal"/>
            <connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
              <ssl password="pwd typed in step 1" />
            </connector>
            <virtual-server name="default-host" enable-welcome-root="true">
                <alias name="localhost"/>
                <alias name="example.com"/>
            </virtual-server>
        </subsystem>

</connector>

<virtual-server name="default-host" enable-welcome-root="true">

</virtual-server>

</subsystem>

exception: Service entry ‘org.jboss.as.jsf.deployment.JsfInjectionProvider’ does not extend

May 28, 2013exception, jboss, jsfadmin

=========================================== 28/05/2013
exception:
Service entry ‘org.jboss.as.jsf.deployment.JsfInjectionProvider’ does not extend DiscoverableInjectionProvider
==> solution add in web.xml

org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL

true

allow remote debug for jboss7

May 27, 2013jbossadmin

=========================================== 27/05/2013
allow remote debug for jboss7
(https://community.jboss.org/thread/175385)
1. Check the standalone.conf (or standalone.conf.bat for Windows OS) and uncomment the following line:
#JAVA_OPTS=”$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=n”

setup hsqldb with jboss7

May 25, 2013hsqldb, jbossadmin

jboss7 comes with h2 already installed and setup.
For hsqldb, just take h2 setup as example.

Following steps helps to setup hsqldb with jboss7.

A. create new jboss7 module: hsqldb module

1. first create directory $JBOSS_HOME/modules/org/hsqldb/main

cd $JBOSS_HOME
mkdir -p modules/org/hsqldb/main

1 2	cd $JBOSS_HOME mkdir -p modules/org/hsqldb/main

2. download hsqldb and put the hsqldb.jar into created directory main
3. create into main directory following module.xml file (assuming hsqldb jar is hsqldb-x.x.x.jar)

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="org.hsqldb">
  <resources>
    <resource-root path="hsqldb-x.x.x.jar"/>
  </resources>
   <dependencies>
     <module name="javax.api"/>
     <module name="javax.transaction.api"/>
   </dependencies>
</module>

<?xml version="1.0" encoding="UTF-8"?>

<resource-root path="hsqldb-x.x.x.jar"/>

</resources>

</dependencies>

</module>

B. setup hsqldb datasource

1. add hsql driver by editing $JBOSS_HOME/standalone/configuration/standalone.xml (locate drivers in standalone.xml file)

<drivers>  
  <driver name="hsqldb" module="org.hsqldb"/>  
  ...  
</drivers>

...

</drivers>

2. finally add hsqldb datasource in $JBOSS_HOME/standalone/configuration/standalone.xml (locate datasources in the file)
we consider a file hsqldb database created into /home/hsqldb/data/witrHsqldb

<datasource jndi-name="java:/jboss/datasources/witrHsqldb" pool-name="witrHsqldb" enabled="true" jta="true" use-java-context="true" use-ccm="true">  
  <connection-url>  
    jdbc:hsqldb:file:/home/hsqldb/data/witrHsqldb
  </connection-url>  
  <driver>  
    hsqldb  
  </driver>  
  <pool>  
    <prefill>false</prefill>  
    <use-strict-min>false</use-strict-min>  
    <flush-strategy>FailingConnectionOnly</flush-strategy>  
  </pool>  
  <security>  
    <user-name>  
      sa  
    </user-name>  
    <password>  
    </password>  
  </security>  
</datasource>

<connection-url>

jdbc:hsqldb:file:/home/hsqldb/data/witrHsqldb

</connection-url>

hsqldb

</driver>

<pool>

<prefill>false</prefill>

<use-strict-min>false</use-strict-min>

<flush-strategy>FailingConnectionOnly</flush-strategy>

</pool>

<user-name>

</user-name>

</password>

</security>

</datasource>

jrebel/eclipse/remote jbossAS server step by step

April 19, 2013jbossadmin

April 19, 2013

install jrebel with eclipse:
– get licence from jrebel web site
– install jrebel eclipse plugin. Restart eclipse and activate you licence
– in jrebel config center : select one projet in projects panel, and enter in corresponding “deployment URL” field your jboss7 server url (example http://myserver:8080)
you will have “Server responded with an error: null”, don’t worry, this because server was not yet configured to respond to remote requests
– now compile and package your project and then put it in your server jboss.

install jrebel under jboss7
– copy “C:UsersYOURHOME.jrebeljrebel.lic” et “C:UsersYOURHOME.jrebeljrebel.properties” to the home of your server user launching jboss : /home/user_launchig_jboss/.jrebel/
– get jrebel.jar from jrebel web site and put it in your host machine
– add following in the script launching jboss7 before call standalone.sh :
export JAVA_OPTS=”$JAVA_OPTS -javaagent:/path/to/jrebel.jar -Drebel.log.file=$JBOSS_HOME/standalone/log/jrebel.log -Drebel.remoting_plugin=true”
– start server jboss7
=============================
if you have following error : Server responded with an error: null ==> this because remoting is not enabled in jrebel java agent : add -Drebel.remoting_plugin=true in java_opts
if you have following error : Server responded with an error: Remoting module’navco-module-delegal-postes-pm’ was not found ==> redeploy your project in jboss7 (jrebel remoting needs the rebel-remote.xml)

Witr Quote

IT blog

Category Archives: jboss

profile remote host jboss7 with jprofiler

Jboss7 (jboss-cli) : how to redirect specified class log in specified file

Jboss7 : useful jboss-cli commands

ajax displaying jboss server state

environment requirement

get result of status.sh in our php file

ajax state display

continuous update of servers state

deloyment

full code

get jboss7 server state with shell script

secure jboss7 with ssl (https)

exception: Service entry ‘org.jboss.as.jsf.deployment.JsfInjectionProvider’ does not extend

allow remote debug for jboss7

setup hsqldb with jboss7

jrebel/eclipse/remote jbossAS server step by step