-
15. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jaikiran Jul 7, 2015 8:17 AM (in response to jure12347)Jure Zajnic wrote:
It wont, because it seys heap memory is insufficient.
Please post that exact error that you are seeing. If you do want to change some of the heap settings, please use a better editor (since it looks like notepad was causing that problem) and do not copy/paste the value from some document.
-
16. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 8:19 AM (in response to jaikiran)Sry bud, but the error comes up after this.
I dont want to post huge pages of text, but here is the section of interest:
JBoss Bootstrap Environment
JBOSS_HOME: D:\Jure\jboss eap\jboss-eap-6.1
JAVA: C:\Program Files (x86)\Java\jdk1.7.0_79\jre\bin\java
JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms512M -Xmx512M -XX:MaxPermSize=512M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
=============================================================================
INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
ERROR [stderr] (main) JBAS015801: Invalid option 'ľc'
INFO [stdout] (main)
That is exactly how it happens.
-
17. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 8:23 AM (in response to jaikiran)Here's what happens with all files unedited:
JBoss Bootstrap Environment
JBOSS_HOME: D:\Jure\jboss eap\jboss-eap-6.1
JAVA: C:\Program Files (x86)\Java\jdk1.7.0_79\jre\bin\java
JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms1303M -Xmx1303M -XX:MaxPermSize=256M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
=============================================================================
Error occurred during initialization of VM
Could not reserve enough space for object heap
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Hope this explains something.
I tries using Notepad++ for editing after this, but to no avail. Same error pops up.
-
18. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 8:43 AM (in response to jure12347)I started just standalone.bat, with added memory heap size (512M) and this is the result:
D:\Jure\jboss eap\jboss-eap-6.1\bin>standalone.bat
Calling "D:\Jure\jboss eap\jboss-eap-6.1\bin\standalone.conf.bat"
===============================================================================
JBoss Bootstrap Environment
JBOSS_HOME: D:\Jure\jboss eap\jboss-eap-6.1
JAVA: C:\Program Files (x86)\Java\jdk1.7.0_79\jre\bin\java
JAVA_OPTS: -client -Dprogram.name=standalone.bat -Xms512M -Xmx512M -XX:MaxPermSize=512M -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman
===============================================================================
14:33:45,535 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
14:33:45,806 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1
14:33:45,867 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
14:33:47,233 INFO [org.xnio] (MSC service thread 1-2) XNIO Version 3.0.7.GA-redhat-1
14:33:47,236 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
14:33:47,240 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
14:33:47,248 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 3.2.16.GA-redhat-1
14:33:47,460 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 29) JBAS010280: Activating Infinispan subsystem.
14:33:47,468 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 25) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:33:47,478 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.17.Final-redhat-1)
14:33:47,634 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
14:33:47,475 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 35) JBAS012605: Activated the following JSF Implementations: [main, 1.2]
14:33:47,622 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 37) JBAS011800: Activating Naming Subsystem
14:33:47,602 INFO [org.jboss.as.security] (ServerService Thread Pool -- 42) JBAS013171: Activating Security Subsystem
14:33:47,914 INFO [org.apache.coyote.http11] (MSC service thread 1-4) JBWEB003001: Coyote HTTP/1.1 initializing on : http-/127.0.0.1:8080
14:33:47,885 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
14:33:48,059 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.17.Final-redhat-1
14:33:48,048 INFO [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.1.3.Final-redhat-3
14:33:48,119 INFO [org.apache.coyote.http11] (MSC service thread 1-4) JBWEB003000: Coyote HTTP/1.1 starting on: http-/127.0.0.1:8080
14:33:48,118 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:33:48,142 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory D:\Jure\jboss eap\jboss-eap-6.1\standalone\deployments
14:33:48,151 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "mytestjms.war" (runtime-name: "mytestjms.war")
14:33:48,151 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015876: Starting deployment of "mytestmdb.ear" (runtime-name: "mytestmdb.ear")
14:33:48,183 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:224) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_79]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:162)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:190) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
14:33:48,219 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447
14:33:48,208 WARN [org.jboss.metadata.parser.jboss.JBossAppMetaDataParser] (MSC service thread 1-2) loader-repository element in jboss-app.xml is deprecated and has been ignored
14:33:48,206 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on 127.0.0.1:9999
14:33:48,260 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "null" (runtime-name: "mytestmdb.jar")
14:33:48,287 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "mytestmdb.jar" of deployment "mytestmdb.ear"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79]
Caused by: org.jboss.msc.service.ServiceNotFoundException: Service service jboss.ejb.default-resource-adapter-name-service not found
at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:448) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.getDefaultResourceAdapterName(MessageDrivenComponentDescriptionFactory.java:270)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processMessageBeans(MessageDrivenComponentDescriptionFactory.java:152)
at org.jboss.as.ejb3.deployment.processors.MessageDrivenComponentDescriptionFactory.processAnnotations(MessageDrivenComponentDescriptionFactory.java:80)
at org.jboss.as.ejb3.deployment.processors.AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.processAnnotations(AnnotatedEJBComponentDescriptionDeploymentUnitProcessor.java:58)
at org.jboss.as.ejb3.deployment.processors.AbstractDeploymentUnitProcessor.deploy(AbstractDeploymentUnitProcessor.java:81)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
14:33:48,300 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:33:48,397 INFO [org.jboss.web] (ServerService Thread Pool -- 53) JBAS018210: Register web context: /mytestjms
14:33:49,049 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "mytestmdb.ear" (runtime-name : "mytestmdb.ear")
14:33:49,051 INFO [org.jboss.as.server] (ServerService Thread Pool -- 26) JBAS018559: Deployed "mytestjms.war" (runtime-name : "mytestjms.war")
14:33:49,052 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "mytestmdb.jar" of deployment "mytestmdb.ear"
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
14:33:49,156 INFO [org.jboss.as] (Controller Boot Thread) JBAS015964: Http management interface is not enabled
14:33:49,157 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
14:33:49,158 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) started (with errors) in 4010ms - Started 169 of 230 services (4 services failed or missing dependencies, 56 services are passive or on-demand)
-
19. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
mmusaji Jul 7, 2015 9:01 AM (in response to jure12347)jure12347 wrote:
Caused by: java.net.BindException: Address already in use: bind
at sun.nio.ch.Net.bind0(Native Method) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:444) [rt.jar:1.7.0_79]
at sun.nio.ch.Net.bind(Net.java:436) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) [rt.jar:1.7.0_79]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) [rt.jar:1.7.0_79]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:144)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:162)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:190) [jboss-as-server-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
... 5 more
JBAS014777: Services which failed to start: service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."mytestmdb.ear"."mytestmdb.jar".PARSE: JBAS018733: Failed to process phase PARSE of subdeployment "mytestmdb.jar" of deployment "mytestmdb.ear"
service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Address already in use: bind /127.0.0.1:9990
The error tells you what the problem is, i.e. there is already something running on the same address your using to start up JBoss using the port 9990. Possibly another instance of JBoss?
-
20. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 9:30 AM (in response to mmusaji)It was this:
http://stackoverflow.com/questions/17973025/error-starting-jboss-7-1-1-on-windows-7-64bit
I disabled the process and now the server is running fine.
However i still don't know what is wrong whit the test file configuration (unrecognised character)? Any ideas? Clearly text editor is not the cause, because i edited the standalone.config.bat this time too and it worked.
-
21. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 10:40 AM (in response to jure12347)How do i find out in which module or xml the error is hiding?
JBoss MSC version 1.0.4.GA-redhat-1 --> Is it here, since this was reported loading last?
Or is it in the next thing to be loaded?
-
22. Re: JBAS015801: Invalid option 'ľc' in Jboss EAP 6.1
jure12347 Jul 7, 2015 10:56 AM (in response to jure12347)After changing the system locale to english-US the problem persists, only this time like this:
16:48:01,984 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1
16:48:03,017 ERROR [stderr] (main) JBAS015801: Invalid option 'ûc'
Do you guys think this is system locale problem?