Wildfly 10 support on Solaris 10

[tavleen]

Hi

I am trying to start WildFly 10 on Solaris 10 platform (java 1.8_91 64 bit) using standalon.sh

Solaris Info

bash-3.00# cat /etc/release

                       Solaris 10 5/08 s10s_u5wos_10 SPARC

          Copyright 2008 Sun Microsystems, Inc.  All Rights Reserved.

                        Use is subject to license terms.

                             Assembled 24 March 2008

On starting the sh i am getting the following error :-

bash-3.00# ./standalone.sh

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /export/home/XXX/wildfly

  JAVA: java

  JAVA_OPTS:  -server

=========================================================================

०८:०३:२२,७०० INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

०८:०३:२६,७०२ INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

०८:०३:२७,६१३ INFO  [org.jboss.as] (MSC service thread १-२) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting

०८:०३:४१,७३६ ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration

        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[213,9]

Message: Unexpected element '{urn:jboss:domain:infinispan:4.0}subsystem'

        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        ... 3 more

०८:०३:४१,७५८ FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

०८:०३:४१,७७२ INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.

०८:०३:४२,०१६ INFO  [org.jboss.as] (MSC service thread १-१) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in ३०ms

Could u please how to make it working ??

Regards

Tavleen

[ctomc]

Looks like something is broken in your installation.

try downloading & extracting it again.

or try zip, as I remember there is some special handling required on solaris to properly extract tar.gz

[tavleen]

Hi

I tried with new zip file , extract it on the Solaris platform still facing the same issue . Below is the console output

I have notice one thing, if i comment out urn:jboss:domain:infinispan:4.0 from the subsystem, then .sh file runs fine .

I haven't modified any of the .xml still facing the issue while starting WildFly 10.

Any pointer on how to solve this issue ?

Thanks in advance.

_____________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Console output...

bash-3.00# ./standalone.sh

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /export/home/SMC/wildfly_zip/wildfly-10.0.0.Final

  JAVA: java

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

१८:०५:३२,२८३ INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

१८:०५:३७,१९४ INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

१८:०५:३८,६५५ INFO  [org.jboss.as] (MSC service thread १-२) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting

१८:०५:५१,९६९ ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration

        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.ServerService.boot(ServerService.java:356) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_91]

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[213,9]

Message: Unexpected element '{urn:jboss:domain:infinispan:4.0}subsystem'

        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.parseServerProfile(StandaloneXml_4.java:546) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:242) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:141) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:103) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49) [wildfly-server-2.0.10.Final.jar:2.0.10.Final]

        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.2.0.Final.jar:1.2.0.Final]

        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123) [wildfly-controller-2.0.10.Final.jar:2.0.10.Final]

        ... 3 more

१८:०५:५१,९९४ FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.

१८:०५:५२,०४६ INFO  [org.jboss.as.server] (Thread-2) WFLYSRV0220: Server shutdown has been requested.

१८:०५:५२,३४७ INFO  [org.jboss.as] (MSC service thread १-१) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in १ms

[mnovak]

At the first look it might be related to your localization on Solaris 10. Some char encoding or something. It seems that server cannot read standalone.xml file.

[lafr]

Just tried this on my Solaris box. No problems.

cat /etc/release

                       Solaris 10 6/06 s10s_u2wos_09a SPARC

           Copyright 2006 Sun Microsystems, Inc.  All Rights Reserved.

                        Use is subject to license terms.

                             Assembled 09 June 2006

unzip -q wildfly-10.0.0.Final.zip

cd wildfly-10.0.0.Final/bin

/mbi/tmp/wildfly-10.0.0.Final/bin. ./standalone.sh

=========================================================================

  JBoss Bootstrap Environment

  JBOSS_HOME: /export/home/mbi/tmp/wildfly-10.0.0.Final

  JAVA: /mbi/tools/jdk/1.8.0/bin/java

  JAVA_OPTS:  -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

=========================================================================

22:26:45,550 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final

22:26:47,167 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

22:26:47,648 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting

22:26:55,533 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

22:26:55,646 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.4.Final

22:26:55,678 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.4.Final

22:26:56,016 INFO  [org.jboss.remoting] (MSC service thread 1-3) JBoss Remoting version 4.0.18.Final

22:26:56,185 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 53) WFLYSEC0002: Activating Security Subsystem

22:26:56,371 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 46) WFLYNAM0001: Activating Naming Subsystem

22:26:56,413 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 56) WFLYWS0002: Activating WebServices Extension

22:26:56,500 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 38) WFLYCLINF0001: Activating Infinispan subsystem.

22:26:56,423 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 54) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

22:26:56,612 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 44) WFLYJSF0007: Activated the following JSF Implementations: [main]

22:26:56,673 INFO  [org.jboss.as.security] (MSC service thread 1-2) WFLYSEC0001: Current PicketBox version=4.9.4.Final

22:26:57,037 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.3.15.Final starting

22:26:57,042 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0003: Undertow 1.3.15.Final starting

22:26:57,067 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service

22:26:57,280 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 37) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors

22:26:57,429 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 33) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

22:26:57,685 INFO  [org.jboss.as.connector] (MSC service thread 1-4) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.2.Final)

22:26:57,833 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

22:26:58,092 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = h2

22:26:58,517 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 55) WFLYUT0014: Creating file handler for path '/export/home/mbi/tmp/wildfly-10.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

22:26:58,703 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.

22:26:58,719 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting

22:26:59,549 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

22:26:59,951 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host.

22:26:59,951 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing.

22:27:00,850 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

22:27:01,914 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /export/home/mbi/tmp/wildfly-10.0.0.Final/standalone/deployments

22:27:02,808 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBossWS 5.1.3.Final (Apache CXF 3.1.4)

22:27:03,091 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Mahou' 8.1.0.Final

22:27:04,607 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

22:27:04,659 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

22:27:04,661 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) started in 21054ms - Started 267 of 553 services (371 services are lazy, passive or on-demand)

[tavleen]

hmm ... it seems Novak Miroslav's suggestion may work ...

Let me try it with different locale en_US. Since my Solaris box doesn't have this locale, it may take time to verify it ..

Will update once I verify it

Thanks a lot for the inputs

[tavleen]

Hey Miroslav ... thanks for the input on the issue ..

It was the locale problem indeed.

Followed the tutorial http://wildfly.org/news/2015/03/13/Offline-CLI/ and created an server with empty configuration. This in turn populated the standalone configuration with the extensions needed for Wildfly.

With hindi numeric it ran fine . On changing it to English it again created an issue

Thanks for the help everyone

[jaikiran]

Just so I understand this correctly, you used the WildFly CLI to create certain resources, like subsystems (which get persisted in standalone.xml configuration file) and while using the CLI, you were on a non-English locale and the CLI ended up creating a subsystem configuration in the XML with non-English characters? If that's the case, IMO, that is a bug.

[mnovak]

I'm glad you've managed to solve the issue

Jaikiran is right that if non-english locale is used then any xml configuration created by CLI commands should be correctly created. If it's not then it's a bug.

[ctomc]

Tavleen Oberoi wrote:

Hey Miroslav ... thanks for the input on the issue ..

It was the locale problem indeed.

Followed the tutorial http://wildfly.org/news/2015/03/13/Offline-CLI/ and created an server with empty configuration. This in turn populated the standalone configuration with the extensions needed for Wildfly.

With hindi numeric it ran fine . On changing it to English it again created an issue

Thanks for the help everyone

This sounds like odd bug, we should probably find out what is happening and fix it.

Could you rise issue in jira https://issues.jboss.org/browse/WFLY and provide simple way to reproduce this.

It is especially strange as this xml is generated by server after you ran CLI commands on it.

[jaikiran]

This turned out to be a straight-forward bug in the Infinispan subsystem XML writer, so I went ahead and created a PR containing the fix Use ENGLISH Locale while writing out the Infinispan subsystem namespace by jaikiran · Pull Request #9053 · wildfly/wildf….

I haven't created a JIRA for this yet to give tavleen a chance to take the credit for reporting the issue.

[ctomc]

jaikiran pai wrote:

This turned out to be a straight-forward bug in the Infinispan subsystem XML writer, so I went ahead and created a PR containing the fix Use ENGLISH Locale while writing out the Infinispan subsystem namespace by jaikiran · Pull Request #9053 · wildfly/wildf….

I haven't created a JIRA for this yet to give tavleen a chance to take the credit for reporting the issue.

Tnx Jaikiran, you are still our MVP!

[brian.stansberry]

Yes, indeed, thanks, Jaikiran, and thank you Tavleen.

I've opened [WFLY-6857] Infinispan subsystem writes incorrect xml namespace when system locale is not English - JBoss Issue Tracker for this. Tavleen, I'd be happy to change the Reporter to you if you'd like. Just send me an email with your JIRA account name.

[tavleen]

Thanks a lot for the input ...

As of now , I am able to continue the work so I am fine being an observer

Regards