Jboss version with single line command in unix - jboss

Can you please let me know how can i Jboss version running in my servers, i am not able to find standalone.sh script file in some of the servers. is there any log or single command to find out Jboss.
Thanks

To find out which version of EAP you have installed on machine, grep jboss-modules.jar. Called as $JBOSS_HOME. Once you location of EAP installer i.e $JBOSS_HOME, you will find version.txt at same location which will tell you exact version of EAP.
If you already know location of EAP, chekc version.txt to know the exact version of EAP or grep server.log file present in $JBOSS_HOME/standalone/log

Related

Missing jboss-modules.jar in jboss 7.2

i try to open add-user.bat in jboss v7.2 but i receive this error
WARNING: The JBOSS_HOME ("C:\Users\PC\Ep\bin") that this script uses points to a different installation than the one that this script resides in ("C:\Users\PC\Ep"). Unpredictable results may occur.
JBOSS_HOME: "C:\Users\PC\Ep\bin"
Could not locate "C:\Users\PC\Ep\bin\jboss-modules.jar".
Please check that you are in the bin directory when running this script.
I find this in eclipse :
The home directory is missing a required file or folder: C:/Users/PC/Ep/bin/jboss-modules.jar
Any idea to solve this problem?
I need link to download jboss-modules.jar relative to jboss red hat 7.2
You're JBOSS_HOME environment variable looks wrong. It should be set to C:\Users\PC\Ep\. The bin directory should not be in the environment variable.

JBOSS EAP 6.4 run as service does not pick the correct JAVA

I have installed JBOSS EAP6.4 on a RHEL box and during the installation it has created default service. I am trying to start the service root user service jbossas start through and it fails with following message: /usr/share/jbossas/bin/standalone.sh: line 306: /usr/lib/jvm/jre/bin/java: No such file or directory
However server starts perfects fine when it is standard through /usr/share/jbossas/bin/standalone.sh
As I understand, jboss user underwhich service would be running somehow picking up the incorrect java path - again default path.
I could be wrong here, as such how do I fix this issue?
You can set the JAVA_HOME environment variable for the user's profile in the OS level.
Another way to do this, but you should avoid that, is to set JAVA_HOME environment variable through the /etc/init.d/jbossas service script file of EAP 6 (installed as RPM installation). Such variables should be set through /etc/jbossas/jbossas.conf file which is used internally by the service script of the installation.

TIBCO MFT Server Installation

I've asked by manager to check and confirm where the TIBCO MFT is installed on IBM AIX server. I'm completely new to TIBCO and don't know what is the installation directory of this software.
Could somebody please help me to find where it is installed on AIX server.
If your server is configured properly, then you should have an environment variable called CFROOT set that points to the installation directory (execute a echo $CFROOT to see its value).
The installation directory can be set during the installation process to some arbitrary directory, so in theory it could be anywhere. The default however should be /mftps, other likely options include /opt/mftps, or /opt/tibco/mftps.
Althaf ,
You can use "find" command as well to search for mftps on Server to know the directory.

lsof all /tmp/serverlist.lock and jboss error too many open files

I use JBoss EAP 5.1.2. In Linux, I got error of "too many open files". Then I used lsof to look file handle, I found:
java 16752 ch_as 582u REG 202,3 0 1573210 /tmp/serverlist.lock
there are 8690 rows for the above file, is it too much?
I want know ,what is /tmp/serverlist.lock and how I fix it?
DB: DB2 9.5.7
Linux: SUSE
JBoss: JBoss EAP 5.1.2
serverlist.lock is file that DB2 JDBC driver creates and uses for its operation.
There is some talk about it in release notes for jdbc driver.
All I could recommend you is to use latest Type 4 JDBC driver(if not already) and if problem still persists ask IBM support about it.

.war files packaged as RPMs for JBOSS/Tomcat - best practices?

I'm planing to package WAR files as RPMs. Current deployment process just doesn't work for us and my idea of fixing it would be to create a new Custom Channel in RHN Satellite and publish my WAR files through that Channel. Currently (as we are trying to win some time) I'm managing some config files through Satellite so configs are not a big problem. We don't keep them in WAR for many reasons but that's different story.
Anyway, has anyone packaged WAR as RPMs? Do you do hot deployment or do you force JBOSS/Tomcat to restart? Is that After RPM installation or as a part of it? What's your SPEC file looks like? Can I please see it as an example? Do you check in your SPEC for JBOSS/Java/Oracle client or just install WAR? Any stories to tell? Any major problems?
Should I consider something else?
I can build RPMs no problem but I'd like to hear what's the best way of doing this with WAR files and JBOSS (some Tomcats are still running here but they will be phased out soon-ish so I'm not too worried about them).
I do appropriate any input.
Thanks in advance
Kind Regards
Chris
I have packaged a WAR file and its companion config file as RPM. My SPEC file checks whether JBoss is running. If it is, the installation exits with an error message, requesting that JBoss be stopped before installation.
In general, it is not a good idea to kill processes or force restart through RPMs. The person in charge of installation should have a separate procedure for doing this.
Other considerations:
1. Does your organization have other installations on the same server?
If so, you might want to standardize on a path under which all installations on the server will go. (For example, /usr/local/bin/myorg/)
It might also help to have a custom *nix user and group, for which file attributes are set for all installations on the server.
2. Do you want a relocatable RPM?
Is there ever a chance that you might want to change the default path for your installation? If so, a relocatable RPM will help.
There are conditions where a relocatable RPM may not work, so check out these things to consider at www.rpm.org.
3. Do you want to back up an existing deployment when your RPM runs?
If so, you would need to write that code in your SPEC file.
Here is my complete SPEC file:
Summary: Summary for my Java project
Name: Name for my Java project
Version: 2.1.2
Release: 5
Requires: jboss >= 5.1
BuildArch: noarch
Group: Internet / Applications
Prefix: /usr/local/bin
License: (C) Copyright my organization
Vendor: my organization
%description
Description for my Java project
%prep
# Check if the WAR file has been created
%install
# Copy war file to buildroot's Jboss deployment directory
# Copy config file to buildroot's Jboss config directory
%files
# Set file permissions and ownership
%pre
# Check if JBoss deployment path exists on the web server.
# If not, exit with an error.
# Check if JBoss config file path exists on the web server.
# If not, exit with an error.
# Check if custom user 'myuser' exists. If not, exit with an error.
# Check if custom group 'mygroup' exists. If not, exit with an error
# Check if JBOSS is running. If yes, exit with an error.
# Take backup of existing deployment, if needed.
%post
# Perform post-installation steps, if needed.
echo "Installation complete."
We plan to somehow standardize Java webapp installation on Fedora, but there is nothing yet.
Debian guys created a rather nice proposal http://dep.debian.net/deps/dep7 which you should probably read to get an idea what you'd have to deal with more or less.
As for JBoss/Tomcat restart, I would advise against it. Leave it to the system (webserver) administrator. They should know what they are updating and why. Forcing restart of webserver all the time is asking for trouble IMO (especially if one server is hosting multiple webapps)
I would put the wars in /usr/share/webapps-java. Then probably have JBoss/Tomcat use that directory. That said, no spec files, sorry.