Sorry for a silly question. I am starting JBoss for a first time. I need to know what is happening.
I started server on my linux machine with command:
./standalone.sh -Djboss.bind.address=127.0.0.1 -Djboss.bind.address.management=127.0.0.1&
This is what I see in terminal right now:
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /usr/local/share/jboss
JAVA: /usr/lib/jvm/java-8-oracle/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
13:46:46,874 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.2.Final-redhat-1
13:46:47,032 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
13:46:47,090 INFO [org.jboss.as] (MSC service thread 1-7) JBAS015899: JBoss EAP 6.1.1.GA (AS 7.2.1.Final-redhat-10) starting
The silly question is: which port I should try to find JBoss there?
Default port is 8080 for web applications. Admin web console is on 9990
Related
How could I make a common jar availabe in jboss 6.4 redhat ?
Is it possible to put it in JBOSS_HOME/standalone/lib ?
01:00:42,659 DEBUG [org.jboss.as.server.deployment] (MSC service thread 1-2) Adding dependency ModuleDependency [identifier=LogManager4JBoss-4.1.0rc2.jar:main, moduleLoader=local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base)), export=false, optional=false, importServices=false] to module deployment.tserver-5.0.0.jar:main
01:00:42,670 TRACE [org.jboss.modules] (MSC service thread 1-2) Locally loading module LogManager4JBoss-4.1.0rc2.jar:main from local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base))
01:00:42,671 TRACE [org.jboss.modules] (MSC service thread 1-2) Module LogManager4JBoss-4.1.0rc2.jar:main not found from local module loader #16f65612 (finder: local module finder #311d617d (roots: /opt/jboss6/modules,/opt/jboss6/modules/system/layers/base))
tserver-5.0.0.jar needs some common log stuff from LogManager4JBoss-4.1.0rc2.jar, all the documentation I read so far is confusing, I can't figure out where to put the common jar, this is working in a jboss 4.2.3, I need to use hibernate 3.5 for oracle db synonym support, from jboss 6
Environment:
Jboss 7.2
Java 11
On loading JBoss 7.2 server I am getting an issue obtaining CDI 1.1 utilities. How could I to resolve this problem?
Server log SEVERE error on loading
...
08:24:15,561 SEVERE [javax.enterprise.resource.webcontainer.jsf.flow] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
08:24:15,562 SEVERE [javax.enterprise.resource.webcontainer.jsf.application.view] (MSC service thread 1-7) Unable to obtain CDI 1.1 utilities for Mojarra
...
I am currently trying to set up the jboss server and every time I use the command ./standalone.sh to start it....I end up with the following results.
jamess-iMac:bin jameslockhart$ ls
add-user.bat domain.conf jconsole.sh standalone.sh
add-user.sh domain.conf.bat jdr.bat vault.bat
appclient.bat domain.sh jdr.sh vault.sh
appclient.conf init.d run.bat wsconsume.bat
appclient.conf.bat jboss-cli.bat run.sh wsconsume.sh
appclient.sh jboss-cli.sh standalone.bat wsprovide.bat
client jboss-cli.xml standalone.conf wsprovide.sh
domain.bat jconsole.bat standalone.conf.bat
jamess-iMac:bin jameslockhart$ ./standalone.sh
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /Users/jameslockhart/desktop/apps/jboss
JAVA:/Library/Java/JavaVirtualMachines/jdk1.8.0_40.jdk/Contents/Home/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m-Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
19:08:17,223 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
19:08:17,362 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
19:08:17,400 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.1.Final "Brontes" starting
All the tutorials I have watched have it going beyond the "Brontes" starting. Mine just sits there. Does anyone know what is wrong?
Any help would be appreciated!!
There was a bug in JBoss 7.1.1 that prevented it from starting on JDK8. JBoss AS7 is extremely outdated, you need to either use JDK7, or ideally upgrade to a recent version of Wildfly or JBoss EAP.
I was able to download wildfly and the system works flawlessly. Thanks for the help everyone.
I've been facing this error for few days, appreciate if somebody could kindly advise.
My pom is configured with jboss auto deploy plugin version 7.1.1.Final. When I build the project from jenkins it builds fine but cannot deploy to jboss, fails with below exception:
Oct 21, 2013 6:55:02 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.3.GA
Authenticating against security realm: ManagementRealm
Exception in thread "management-client-thread 1-1" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2271)
at java.io.ByteArrayOutputStream.grow(ByteArrayOutputStream.java:113)
at java.io.ByteArrayOutputStream.ensureCapacity(ByteArrayOutputStream.java:93)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:140)
at org.jboss.as.protocol.StreamUtils.copyStream(StreamUtils.java:49)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler.copyStream(AbstractModelControllerClient.java:226)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$ReadAttachmentInputStreamRequestHandler$1.execute(AbstractModelControllerClient.java:202)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:287)
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:487)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
This is jvm setting I've got:
-Xms128m -Xmx512m -XX:MaxPermSize=256m
Thanks
Prash
Add more memory to Maven:
(Windows) Set the Variable name to MAVEN_OPTS and set the Variable value to -Xmx1024m (or more)
In IntellijIdea Settings -> Build, Excecution, Deployment ->Build tools-> Maven -> Runner -> add param (-Xmx1024m (or more)) to VM Options.
I am deploying a OSGI bundle in Jboss 7.1.1 by using Jboss as maven plugin and I am successfully deployed it into my jboss, my console shows following massege after deployment.
00:54:51,080 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "services-1.0-SNAPSHOT.jar"
00:54:51,110 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011001: Bundle installed: testAapi:1.0.0.SNAPSHOT
00:54:51,190 INFO [org.jboss.as.server] (management-handler-thread - 7) JBAS018562: Redeployed "services-1.0-SNAPSHOT.jar"
But now I dont understand how can I start my osgi bundle automatically using the same maven plugin means jboss as maven plugin
Means I am deploying bundle using mvn jboss-as:deploy and it is deployed but it is not started.
See here: http://community.jboss.org/message/759637#759637