Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Starting with: 249 Mb memory isn't that much too begin with. I do remember reading that the jboss specs tell to have at least 512 Mb mem present, 1Gb (or more) is preferred.
The -Xms/Xmx size depends on what else is running on your machine.
If jboss is the only other thing: keep +/- 10% of your total mem (_not_ including swap space) for the system itself, the rest could be given to jboss. If other applications are also running you need to figure out what amount of mem they take and subtract it as well.
Also start with an Xms that is half the size of Xmx.
Hey, I dont know how it happened.
All I did is increased the memory to max: 600 and min: 512
But when I tried running this command it worked !!!
Code:
[root@webserver bin]# /opt/jboss-eap-4.3/jboss-as/bin/run.sh -c minimal
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-eap-4.3/jboss-as
JAVA: /opt/jdk1.6.0_17/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms512m -Xmx600m -XX:PermSize=512m -XX:MaxPermSize=600m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/jboss-eap-4.3/jboss-as/bin/run.jar:/opt/jdk1.6.0_17/lib/tools.jar
=========================================================================
19:32:04,272 INFO [Server] Starting JBoss (MX MicroKernel)...
19:32:04,316 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)
19:32:04,330 INFO [Server] Home Dir: /opt/jboss-eap-4.3/jboss-as
19:32:04,331 INFO [Server] Home URL: file:/opt/jboss-eap-4.3/jboss-as/
19:32:04,332 INFO [Server] Patch URL: null
19:32:04,332 INFO [Server] Server Name: minimal
19:32:04,333 INFO [Server] Server Home Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal
19:32:04,333 INFO [Server] Server Home URL: file:/opt/jboss-eap-4.3/jboss-as/server/minimal/
19:32:04,334 INFO [Server] Server Log Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal/log
19:32:04,334 INFO [Server] Server Temp Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal/tmp
19:32:04,335 INFO [Server] Root Deployment Filename: jboss-service.xml
19:32:06,066 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
19:32:06,067 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.
19:32:06,067 INFO [ServerInfo] OS-System: Linux 2.6.18-164.el5,i386
19:32:06,903 INFO [Server] Core system initialized
19:32:08,847 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
19:32:10,377 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)] Started in 6s:38ms
Are you doing wrong? If it works it works, so nothing wrong there. But....
Do keep in mind that your box is probably swapping pages to and from your swap space because of this. 249 Mb real mem + 509 swap is enough to handle the 600 Mb jboss is given/wants, but as you can see that includes swap. Not necessarily wrong but it will put a strain on your box if jboss gets (very?) busy.
I am facing an issue now.
I have been reading a book "Jboss at work" and trying to move a jar.war(from one of fictitious project chapter ch01/) into $JBOSS_HOME/server/default/deploy directory and run the JBoss as above with minimal option. But when I am trying to browse http://<ip>:8080/jaw/ its not working.
22:19:58,972 INFO [Server] Starting JBoss (MX MicroKernel)...
22:19:58,974 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)
22:19:58,976 INFO [Server] Home Dir: /opt/jboss-eap-4.3/jboss-as
22:19:58,976 INFO [Server] Home URL: file:/opt/jboss-eap-4.3/jboss-as/
22:19:58,977 INFO [Server] Patch URL: null
22:19:58,977 INFO [Server] Server Name: minimal
22:19:58,978 INFO [Server] Server Home Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal
22:19:58,978 INFO [Server] Server Home URL: file:/opt/jboss-eap-4.3/jboss-as/server/minimal/
22:19:58,978 INFO [Server] Server Log Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal/log
22:19:58,979 INFO [Server] Server Temp Dir: /opt/jboss-eap-4.3/jboss-as/server/minimal/tmp
22:19:58,980 INFO [Server] Root Deployment Filename: jboss-service.xml
22:19:59,493 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
22:19:59,494 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.
22:19:59,494 INFO [ServerInfo] OS-System: Linux 2.6.18-164.el5,i386
22:19:59,891 INFO [Server] Core system initialized
22:20:00,746 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
22:20:01,146 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
22:20:01,151 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)] Started in 2s:169ms
[/code]
Still the web browser not working.
I tried with default folder and it seems to be correctly running:
Code:
[root@webserver bin]# ./run.sh -c first -b localhost
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-eap-4.3/jboss-as
JAVA: /opt/jdk1.6.0_17/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -server -Xms512m -Xmx600m -XX:PermSize=512m - XX:MaxPermSize=600m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server .gcInterval=3600000 -Djava.net.preferIPv4Stack=true
CLASSPATH: /opt/jboss-eap-4.3/jboss-as/bin/run.jar:/opt/jdk1.6.0_17/lib/tools. jar
=========================================================================
22:58:56,344 INFO [Server] Starting JBoss (MX MicroKernel)...
22:58:56,345 INFO [Server] Release ID: JBoss [EAP] 4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)
22:58:56,348 INFO [Server] Home Dir: /opt/jboss-eap-4.3/jboss-as
22:58:56,348 INFO [Server] Home URL: file:/opt/jboss-eap-4.3/jboss-as/
22:58:56,349 INFO [Server] Patch URL: null
22:58:56,350 INFO [Server] Server Name: first
22:58:56,350 INFO [Server] Server Home Dir: /opt/jboss-eap-4.3/jboss-as/server/first
22:58:56,350 INFO [Server] Server Home URL: file:/opt/jboss-eap-4.3/jboss-as/server/first/
22:58:56,351 INFO [Server] Server Log Dir: /opt/jboss-eap-4.3/jboss-as/server/first/log
22:58:56,351 INFO [Server] Server Temp Dir: /opt/jboss-eap-4.3/jboss-as/server/first/tmp
22:58:56,352 INFO [Server] Root Deployment Filename: jboss-service.xml
22:59:00,849 INFO [ServerInfo] Java version: 1.6.0_17,Sun Microsystems Inc.
22:59:00,849 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 14.3-b01,Sun Microsystems Inc.
22:59:00,850 INFO [ServerInfo] OS-System: Linux 2.6.18-164.el5,i386
22:59:01,965 INFO [Server] Core system initialized
22:59:11,929 INFO [ServiceBindingManager] Initializing store
22:59:11,930 INFO [ServiceBindingManager] Using StoreURL: file:/opt/jboss-eap-4.3/jboss-as/docs/examples/binding-manager/sample-bindings.xml
22:59:32,947 INFO [WebService] Using RMI server codebase: http://localhost:8183/
22:59:32,950 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:jboss-log4j.xml
22:59:48,705 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version) - JBoss Inc.
22:59:48,706 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
22:59:49,194 INFO [TransactionManagerService] Starting recovery manager
22:59:49,323 INFO [TransactionManagerService] Recovery manager started
22:59:49,324 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
23:00:01,455 INFO [EJB3Deployer] Starting java:comp multiplexer
23:00:05,026 INFO [STDOUT] no object for null
23:00:05,030 INFO [STDOUT] no object for null
23:00:05,051 INFO [STDOUT] no object for null
23:00:05,121 INFO [STDOUT] no object for {urn:jboss:bean-deployer}supplyType
23:00:05,131 INFO [STDOUT] no object for {urn:jboss:bean-deployer}dependsType
23:00:10,428 INFO [NativeServerConfig] JBoss Web Services - Native
23:00:10,429 INFO [NativeServerConfig] jbossws-native-2.0.1.SP2_CP01 (build=200804021320)
23:00:12,070 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/jdk1.6.0_17/jre/lib/i386/server:/opt/jdk1.6.0_17/jre/lib/i386:/opt/jdk1.6.0_17/jre/../lib/i386:/usr/java/packages/lib/i386:/lib:/usr/lib
23:00:12,330 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8780
23:00:12,331 INFO [AjpProtocol] Initializing Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8709
23:00:12,331 INFO [Catalina] Initialization processed in 449 ms
23:00:12,332 INFO [StandardService] Starting service jboss.web
23:00:12,334 INFO [StandardEngine] Starting Servlet Engine: JBossWeb/2.0.0.GA_CP05
23:00:12,393 INFO [Catalina] Server startup in 61 ms
23:00:12,727 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
23:00:13,664 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/
23:00:14,167 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../deploy/jbossws.sar/jbossws-context.war/
23:00:15,186 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/
23:00:15,978 INFO [MailService] Mail Service bound to java:/Mail
23:00:16,679 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar
23:00:16,758 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar
23:00:16,790 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar
23:00:16,824 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar
23:00:16,884 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms-ra.rar
23:00:16,982 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/quartz-ra.rar
23:00:16,992 INFO [QuartzResourceAdapter] start quartz!!!
23:00:17,057 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
23:00:17,103 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
23:00:17,106 INFO [RAMJobStore] RAMJobStore initialized.
23:00:17,106 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
23:00:17,107 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
23:00:17,107 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
23:00:17,832 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
23:00:18,304 WARN [SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
23:00:18,315 INFO [ServerPeer] JBoss Messaging 1.4.0.SP3-CP02 server [0] started
23:00:18,836 INFO [ConnectionFactory] Connector bisocket://localhost:4557 has leasing enabled, lease period 10000 milliseconds
23:00:18,837 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@16ea15f started
23:00:18,840 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
23:00:18,840 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
23:00:18,881 INFO [ConnectionFactory] Connector bisocket://localhost:4557 has leasing enabled, lease period 10000 milliseconds
23:00:18,881 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@4c2849 started
23:00:18,883 INFO [ConnectionFactory] Connector bisocket://localhost:4557 has leasing enabled, lease period 10000 milliseconds
23:00:18,883 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@c3d9ac started
23:00:18,933 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,936 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,940 INFO [TopicService] Topic[/topic/testTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,941 INFO [TopicService] Topic[/topic/securedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,943 INFO [TopicService] Topic[/topic/testDurableTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,949 INFO [QueueService] Queue[/queue/testQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,955 INFO [QueueService] Queue[/queue/A] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,958 INFO [QueueService] Queue[/queue/B] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,961 INFO [QueueService] Queue[/queue/C] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,965 INFO [QueueService] Queue[/queue/D] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,968 INFO [QueueService] Queue[/queue/ex] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:18,972 INFO [QueueService] Queue[/queue/PrivateDLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,006 INFO [QueueService] Queue[/queue/PrivateExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,011 INFO [QueueService] Queue[/queue/QueueWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,012 INFO [TopicService] Topic[/topic/TopicWithOwnDLQAndExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,020 INFO [QueueService] Queue[/queue/QueueWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,021 INFO [TopicService] Topic[/topic/TopicWithOwnRedeliveryDelay] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,025 INFO [QueueService] Queue[/queue/testDistributedQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,027 INFO [TopicService] Topic[/topic/testDistributedTopic] started, fullSize=200000, pageSize=2000, downCacheSize=2000
23:00:19,692 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
23:00:19,875 INFO [TomcatDeployer] deploy, ctxPath=/jaw, warUrl=.../tmp/deploy/tmp8507365705309804289jaw-exp.war/
23:00:19,986 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
23:00:20,489 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8780
23:00:20,538 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8709
23:00:20,558 INFO [Server] JBoss (MX MicroKernel) [4.3.0.GA_CP01 (build: SVNTag=JBPAPP_4_3_0_GA_CP01 date=200804211657)] Started in 1m:24s:203ms
But what I need to supply at browser:
http://<ip>:?/jaw/
That looks like normal output when starting up jboss. The warnings are there for a reason, but are no show stopper (both are related to configuration stuff).
You should be able to reach it using: http://localhost:8080/. But maybe you need something extra (depends on the java program).
Have a look at the server.xml (the one somewhere in ../jboss-as/server/first). The shouls be a Connector port entry with a value, thats the default for this server (first in this case).
Good to see stuffs working now.
All i tried putting it lke this way:
./run.sh -c default -b 10.209.37.73 all
And it worked !!!
Now I can see the Jboss Interface on Web Browser without any issue.
But wonder ..I dont see anything with jboss-server.xml...All i can see jboss-services.xml.
Also , How can i access those values:
* Tomcat status (full) (XML)
* JMX Console
* JBoss Web Console
Last edited by your_shadow03; 02-23-2010 at 12:39 AM.
An add-on on my previous reply, didn't have the time for a more elaborate answer.....
I'm not sure if you know this already, but if you use -b 0.0.0.0 when starting up, jboss will listen on all interfaces.
I don't know enough about Tomcat to give you any advise, although it (tomcat) is not integrated in jboss. I don't think you can get status info for tomcat from jboss.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.