JBOSS - Profiles - socket binding - offset - Groups - Server
In JBOSS above are some common yet important terminology.
Each Server instance will fall under a group. It can follow its own socket binding.
Each group falls under a profile. Default , Full , Full-has etc
Based on socket binding default HTTP port and server offset we need to find out the server running http port.
In JBOSS above are some common yet important terminology.
Each Server instance will fall under a group. It can follow its own socket binding.
Each group falls under a profile. Default , Full , Full-has etc
Based on socket binding default HTTP port and server offset we need to find out the server running http port.
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'abc.jar' at path 'abc.jar' (position: END_TAG seen ...
Getting the below error ? Global modules classes not available ?
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'abc.jar' at path 'abc.jar' (position: END_TAG seen ...\n... @8:33) caused by: java.util.zip.ZipException: error in opening zip file
at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:723) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:572) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:394) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:219) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:153) [jboss-modules.jar:1.3.3.Final-redhat-1]
... 18 more
Solution : This is just because your global module jar file is corrupted and can not be read. Delete and copy the jar properly.
More similar error :
09:38:16,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.TestWebProj.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.TestWebProj.war".main: JBAS018759: Failed to load module: deployment.TestWebProj.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_95]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_95]
at java.lang.Thread.run(Thread.java:682) [rt.jar:1.6.0_95]
Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'abc.jar' at path 'abc.jar' (position: END_TAG seen ...
at org.jboss.modules.ModuleXmlParser.parseResourceRoot(ModuleXmlParser.java:723) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseResources(ModuleXmlParser.java:572) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleContents(ModuleXmlParser.java:394) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseDocument(ModuleXmlParser.java:219) [jboss-modules.jar:1.3.3.Final-redhat-1]
at org.jboss.modules.ModuleXmlParser.parseModuleXml(ModuleXmlParser.java:153) [jboss-modules.jar:1.3.3.Final-redhat-1]
... 18 more
Solution : This is just because your global module jar file is corrupted and can not be read. Delete and copy the jar properly.
More similar error :
09:38:16,093 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.module.service."deployment.TestWebProj.war".main: org.jboss.msc.service.StartException in service jboss.module.service."deployment.TestWebProj.war".main: JBAS018759: Failed to load module: deployment.TestWebProj.war:main
at org.jboss.as.server.moduleservice.ModuleLoadService.start(ModuleLoadService.java:91) [jboss-as-server-7.4.0.Final-redhat-19.jar:7.4.0.Final-redhat-19]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_95]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_95]
at java.lang.Thread.run(Thread.java:682) [rt.jar:1.6.0_95]
Below is simple example of deploying the list of WARs from a props file and deploy into JBOSS.
---------Script 1 invokes script 2 and creates a log file---------
#!/bin/sh
datestr=$(date +%Y%m%d_%H%M%S)
./connectToCLLI.sh > AsocDeploymentLog_$datestr
-----------------------------------------------------------------------
----------SCRIPT 2 , reads props file and get the WAR file and Group information-------
#!/bin/ksh
echo "Setting JBOSS Env"
export JBOSS_HOME=/export/opt/jboss/jboss-eap-6.3
export JAVA_HOME=/opt/app/java/jdk/jdk160
export PATH=$PATH:$JBOSS_HOME/bin:$JAVA_HOME/bin
export JB_CLI=$JBOSS_HOME/bin/jboss-cli.sh
DEPLOYMENT_HOST=`nslookup \`hostname\` |grep Name | awk '/:/{print $2}'`
export HOME_DIR=/pbcf/ctfr1603/
echo "JBOSS Environment is ready and connecting to CLLI"
allDeployed=0
for LINE in `cat deploymentDescABC.props | grep -v "#"`
{
VAL1=`echo $LINE |cut -d '|' -f1 `
GROUPS=`echo $LINE |cut -d '|' -f2 `
export WAR_FILE=$HOME_DIR$VAL1
echo "Deploying $WAR_FILE now"
#export COMMANDS="connect,deploy $WAR_FILE --force,quit"
export COMMANDS="connect,deploy $WAR_FILE --server-groups=$GROUPS,quit"
echo "COMMANDS is $COMMANDS"
if $JB_CLI -c --controller=$DEPLOYMENT_HOST:9999 --commands="$COMMANDS"
then
echo "Deployment successful for $WAR_FILE !!"
else
echo "Deployment failed for $WAR_FILE "
allDeployed=1
break
fi
}
if [ $allDeployed = "0" ]
then
echo "Overall deployment of all WARs is successful"
else
echo "Overall deployment FAILED !!"
fi
---------------------------------------------------------------------------------------------------------
----------Sample Props file -------------
# list of WARs for ASOC Module
/abc/def/MyTestwar|G2
/abc/def/YourTestwar|G2
All WARs done#
----------------------------------------------
Sample Deploy and undeploy commands :
[jboss@hex0015 bin]$ ./jboss-cli.sh --controller=hex0015.abc.com:9999
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
----------------------------
[disconnected /] connect
[domain@hex0015.abc.com:9999 /] deploy /ssd/etc/jboss_config/atp/csac/PressQuery.war --all-server-groups
[domain@hex0015.abc.com:9999 /] undeploy PressQuery.war --all-relevant-server-groups
---------Script 1 invokes script 2 and creates a log file---------
#!/bin/sh
datestr=$(date +%Y%m%d_%H%M%S)
./connectToCLLI.sh > AsocDeploymentLog_$datestr
-----------------------------------------------------------------------
----------SCRIPT 2 , reads props file and get the WAR file and Group information-------
#!/bin/ksh
echo "Setting JBOSS Env"
export JBOSS_HOME=/export/opt/jboss/jboss-eap-6.3
export JAVA_HOME=/opt/app/java/jdk/jdk160
export PATH=$PATH:$JBOSS_HOME/bin:$JAVA_HOME/bin
export JB_CLI=$JBOSS_HOME/bin/jboss-cli.sh
DEPLOYMENT_HOST=`nslookup \`hostname\` |grep Name | awk '/:/{print $2}'`
export HOME_DIR=/pbcf/ctfr1603/
echo "JBOSS Environment is ready and connecting to CLLI"
allDeployed=0
for LINE in `cat deploymentDescABC.props | grep -v "#"`
{
VAL1=`echo $LINE |cut -d '|' -f1 `
GROUPS=`echo $LINE |cut -d '|' -f2 `
export WAR_FILE=$HOME_DIR$VAL1
echo "Deploying $WAR_FILE now"
#export COMMANDS="connect,deploy $WAR_FILE --force,quit"
export COMMANDS="connect,deploy $WAR_FILE --server-groups=$GROUPS,quit"
echo "COMMANDS is $COMMANDS"
if $JB_CLI -c --controller=$DEPLOYMENT_HOST:9999 --commands="$COMMANDS"
then
echo "Deployment successful for $WAR_FILE !!"
else
echo "Deployment failed for $WAR_FILE "
allDeployed=1
break
fi
}
if [ $allDeployed = "0" ]
then
echo "Overall deployment of all WARs is successful"
else
echo "Overall deployment FAILED !!"
fi
---------------------------------------------------------------------------------------------------------
----------Sample Props file -------------
# list of WARs for ASOC Module
/abc/def/MyTestwar|G2
/abc/def/YourTestwar|G2
All WARs done#
----------------------------------------------
Sample Deploy and undeploy commands :
[jboss@hex0015 bin]$ ./jboss-cli.sh --controller=hex0015.abc.com:9999
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
----------------------------
[disconnected /] connect
[domain@hex0015.abc.com:9999 /] deploy /ssd/etc/jboss_config/atp/csac/PressQuery.war --all-server-groups
[domain@hex0015.abc.com:9999 /] undeploy PressQuery.war --all-relevant-server-groups
JBOSS global modules is one of the best feature provided by JBOSS to share all common jars / libraries in one place to be used across all WAR / EARs deployed.
To used jboss global modules we need to writed module.xml with list of jars under
/export/opt/jboss/jboss-eap-6.3/modules//..//module.xml
Example : /export/opt/jboss/jboss-eap-6.3/modules/com/abc/main/module.xml
After having this module.xml and copying the required jars into dir :
/export/opt/jboss/jboss-eap-6.3/modules/com/abc/main
We need to add entry to the
domain.xml
false
true
false
But this is very important to add under rite profile. For example if you want to share these global modules under default profile your servers also should fall under the same default profile.
If you server exists under a group which follows full profile you should have this entry in the full profile.
To used jboss global modules we need to writed module.xml with list of jars under
/export/opt/jboss/jboss-eap-6.3/modules/
Example : /export/opt/jboss/jboss-eap-6.3/modules/com/abc/main/module.xml
After having this module.xml and copying the required jars into dir :
/export/opt/jboss/jboss-eap-6.3/modules/com/abc/main
We need to add entry to the
domain.xml
But this is very important to add under rite profile. For example if you want to share these global modules under default profile your servers also should fall under the same default profile.
If you server exists under a group which follows full profile you should have this entry in the full profile.
ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to zldv7606.vci.att.com/135.49.207.238:6666, configuration will be reset: null
Are you seeing below error in jboss host controller machine server logs continuously ?
ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to zldv7606.vci.att.com/135.49.207.238:6666, configuration will be reset: null
Solution :
export PATH=$PATH:/opt/app/java/jdk/jdk160/bin
bldv0014:/opt/app/jboss/jboss-eap-6.3/bin> ./jboss-cli.sh --controller=abcd0015.cddef.pbc.com:9999
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
Authenticating against security realm: ManagementRealm
Username: jbadmin
Password:
[domain@abcs0015.cdef.pbc.com:9999 /] /profile=full-ha/subsystem=modcluster:remove
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
ERROR [org.jboss.modcluster] (ContainerBackgroundProcessor[StandardEngine[jboss.web]]) MODCLUSTER000042: Error null sending INFO command to zldv7606.vci.att.com/135.49.207.238:6666, configuration will be reset: null
Solution :
export PATH=$PATH:/opt/app/java/jdk/jdk160/bin
bldv0014:/opt/app/jboss/jboss-eap-6.3/bin> ./jboss-cli.sh --controller=abcd0015.cddef.pbc.com:9999
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect
Authenticating against security realm: ManagementRealm
Username: jbadmin
Password:
[domain@abcs0015.cdef.pbc.com:9999 /] /profile=full-ha/subsystem=modcluster:remove
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
How to print request and response XML data (HTTP communication information) in jboss server logs ?
Set the below property to JVM process being run for jboss
-Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
Set the below property to JVM process being run for jboss
-Dcom.sun.xml.ws.transport.http.client.HttpTransportPipe.dump=true
After writing sample client and while running many a times we get confused whether actual SSL handshake is successful or not with the provided keystore and password parameters , in such cases below parameter helps understanding ssl handshake details.
-Djavax.net.debug=ssl
Sample run command :
java -Djavax.net.ssl.trustStore=/spl/etc/iscks.jks -Djavax.net.ssl.trustStorePassword=csi123 -Djavax.net.ssl.keyStore=/lps/etc/iscks.jks -Djavax.net.ssl.keyStorePassword=csi123 -Djavax.net.debug=ssl spl.isc.ISCWebServiceClient
And another common problem is that we want to see how soap request and response is happening .
in such case use the below java code in the client to see how soap request and response happens
-Djavax.net.debug=ssl
Other way : with in java client code.
System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump", "true");
System.setProperty("com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump", "true");
System.setProperty("com.sun.xml.ws.transport.http.HttpAdapter.dump", "true");
System.setProperty("com.sun.xml.internal.ws.transport.http.HttpAdapter.dump", "true");
-Djavax.net.debug=ssl
Sample run command :
java -Djavax.net.ssl.trustStore=/spl/etc/iscks.jks -Djavax.net.ssl.trustStorePassword=csi123 -Djavax.net.ssl.keyStore=/lps/etc/iscks.jks -Djavax.net.ssl.keyStorePassword=csi123 -Djavax.net.debug=ssl spl.isc.ISCWebServiceClient
And another common problem is that we want to see how soap request and response is happening .
in such case use the below java code in the client to see how soap request and response happens
-Djavax.net.debug=ssl
Other way : with in java client code.
System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump", "true");
System.setProperty("com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump", "true");
System.setProperty("com.sun.xml.ws.transport.http.HttpAdapter.dump", "true");
System.setProperty("com.sun.xml.internal.ws.transport.http.HttpAdapter.dump", "true");
Popular Posts
-
The best solution to know about these init levels is to understand the " man init " command output on Unix. There are basically 8...
-
How to Unlock BSNL 3G data card to use it with Airtel and Vodafone Model no : LW272 ? How to unlock BSNL 3G data card( Model no : LW272 )us...
-
How to transfer bike registration from one State to other (Karnataka to Andhra)?? Most of us having two wheelers purchased and registered in...
-
ఓం శ్రీ స్వామియే శరణం ఆయ్యప్ప!! Related posts : Trip to Sabarimala - Part 1 Trip to Sabarimala - Part 2 Ayappa Deeksha required things...
-
Following are some of interesting blogs I found till now ...please comment to add your blog here. Blogs in English : http://nitawriter.word...
Popular posts
- Airtel and vodafone GPRS settings for pocket PC phones
- Andhra 2 America
- Ayyappa Deeksha required things
- Blogs I watch !
- Captions for your bike
- DB2 FAQs
- Deepavali Vs The Goddes of sleep
- ETV - Dhee D2 D3
- Evolution of smoking in India Women
- How to make credit card payments?
- init 0, init 1, init 2 ..
- Java-J2EE interview preparation
- mCheck Application jar or jad download
- My SQL FAQs
- My Travelogues
- Old is blod - New is italic
- Online pay methids for credit cards
- Oracle FAQs
- Pilgrimages
- Smoking in Indian Women
- Technology Vs Humans
- Twitter feeds for all Telugu stars on single page.
- Unix best practices
- Unix FAQs
Buffs ...
Tags
Powered by WidgetsForFree
Archives
-
▼
2015
(7)
-
▼
September
(7)
- JBOSS - Profiles - socket binding - offset - Group...
- Caused by: org.jboss.modules.xml.XmlPullParserExce...
- JBOSS : WARs deployment shell script
- JBOSS - Global modules - profiles modules.xml
- ERROR [org.jboss.modcluster] (ContainerBackgroundP...
- How to print request and response XML data (HTTP c...
- Webservice HTTPS client running - SSL handshake co...
-
▼
September
(7)