Register | Login

Published Articles


In order to deploy your application without specifying any context path, You need to delete Root.war and deploy your application in the same name at the same location.


Once the JBoss is up it will point to the Root.war. Since your application is deployed over there, Jboss will point your application without any context path.


In a clustered environment the war or ear files needs to be deployed in each and every instances.


Using the farm deployment, the *.ear or *.war files will be deployed only in the farm directory.


JBoss will automatically deploy the *.ear or *.war in the farm directory to all instance in the cluster.


 


Note: Farm deployment w


Jboss instances are normally started using run.sh in foreground or background. If the Jboss server is started in the foreground then it can be stopped by using Ctrl-c. Consider a scenario where the Jboss server is started in the background and you want to stop the server. If we kill the Jboss instance then the server will stop abruptly. The correct way

In order to start SSH session through command prompt first copy the putty.exe to system32 folder in windows.


 


then give the following command


putty 192.168.0.1 -l login_id -pw password -ssh


-l : to pass user login details


-pw to pass password of the user


-ssh represents to make ssh connection to the client


Note: without -ssh putty w

In many unix flavour operating systems we have top command to monitor cpu utilizations.


In Solaris we have prstat to monitor cpu utilization.


use the below command to get the similar output of top in prstat,


prstat -s cpu -a -n 8


 


Solaris version of netstat does not have the sophistication of telling which process is using the port. This can be achieved using lsof command.


Consider a scenario that we need to identify the process id using port 8080,


lsof |grep 8080

This will list the process id that is using port 8080.


Error : There is a problem in JMS message sending or receivingjavax.jms.JMSException: mq server can not receive message, MQ timeout error:2033


If this error occurs then it means no message in the queue. The applciation is trying to get msg from the queue but there is no message in the queue.


 


Another occuring scenario for 2033

If the heap size needs to be set for all the instance to the same value then use the run.conf in the bin directory


e.g. $JBOSS_HOME/bin/run.conf


set the JAVA_OPTS value as


JAVA_OPTS="-Xms1303m -Xmx1303m”


The good

System Dumps generation in AIX

Posted by madeeswer 2371 days ago (Editorial)

System dumps are taken to get a clear picture of systems utilization at that exact moment.


Normally system dumps are taken along with the java heap dump and thread dump for getting a clear picture about the system.


 


following are the steps to generate system dumps,


 


1.  Login  as root user


2. generate gencore file




Normally Jboss will allow command line arguments. The good practice is to keep a separate file for command line argument and point that file during start up.


In order to point a file containing arguments '-P' is the option used.


e.g.


make a file

Manually generating thread dump in jboss 4 or 5

Posted by madeeswer 2376 days ago (Editorial)


Thread dumps are generated by JVM either automatically or manually. In order to figure out a problem proactively, we might require to generate thread dumps in various scenarios.


Thread dumps are generated using the following command


kill -3 pid



Sort News
Username:

Password:

Remember:
YourWiz.com, is a website that will allow everyone to share their knowledge, tip or information through community micro blogging.