in EAP7, we have set system variable jboss.server.data.dir repeatedly (various ways) and it seems to be set, but we are still getting this error:
16:54:06,015 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 100) WFLYUT0021: Registered web context: /stop
16:54:06,062 ERROR [io.undertow.servlet] (ServerService Thread Pool -- 98) Unable to initialize LoadCompanyIdsContext: java.io.FileNotFoundException: ${jboss.server.data.dir}/etc/companyIds.xml (No such file or directory)
at java.io.FileInputStream.open0(Native Method)......
(many more of these follow) Even though, that XML file is there!
Related
For some reason, if I start the server with the wars on the deployment path, the server will timeout. If I start the server and immediatly deploy the wars, they deploy with no issues. So, is there a way to delay deployments to post-startup only ?
Log until timeout appears :
[] 2019-10-17 14:25:01,442 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Software\wildfly-11.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
[] 2019-10-17 14:25:09,163 WARN [org.jboss.as.weld] (ServerService Thread Pool -- 69) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
[] 2019-10-17 14:25:13,953 WARN [org.jboss.as.dependency.private] (MSC service thread 1-5) WFLYSRV0018: Deployment "deployment.backend-2.0-SNAPSHOT.war" is using a private module ("org.apache.httpcomponents") which may be changed or removed in future versions without notice.
[] 2019-10-17 14:25:15,296 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,301 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,302 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,303 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,303 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,303 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,303 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,304 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,304 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,304 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,304 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,304 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,305 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,308 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 67) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:15,309 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 66) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:18,964 WARN [org.jboss.as.weld] (ServerService Thread Pool -- 77) WFLYWELD0052: Using deployment classloader to load proxy classes for module com.fasterxml.jackson.jaxrs.jackson-jaxrs-json-provider. Package-private access will not work. To fix this the module should declare dependencies on [org.jboss.weld.core, org.jboss.weld.spi]
[] 2019-10-17 14:25:25,824 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,824 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,824 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,824 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,825 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,825 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,825 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,825 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,825 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:25,826 WARN [org.hibernate.dialect.function.TemplateRenderer] (ServerService Thread Pool -- 74) HHH000174: Function template anticipated 4 arguments, but 1 arguments encountered
[] 2019-10-17 14:25:26,736 WARN [org.hibernate.jpa.internal.metamodel.MetadataContext] (ServerService Thread Pool -- 74) HHH015011: Unable to locate static metamodel field : eu.glsgroup.fpcs.persistence.backend.ShipmentTypeTranslation_#language; this may or may not indicate a problem with the static metamodel
[] 2019-10-17 14:25:26,736 WARN [org.hibernate.jpa.internal.metamodel.MetadataContext] (ServerService Thread Pool -- 74) HHH015011: Unable to locate static metamodel field : eu.glsgroup.fpcs.persistence.backend.ShipmentTypeTranslation_#importsource; this may or may not indicate a problem with the static metamodel
[] 2019-10-17 14:25:26,743 WARN [org.hibernate.jpa.internal.metamodel.MetadataContext] (ServerService Thread Pool -- 74) HHH015011: Unable to locate static metamodel field : eu.glsgroup.fpcs.persistence.backend.ShipmentSourceTranslation_#language; this may or may not indicate a problem with the static metamodel
[] 2019-10-17 14:25:26,743 WARN [org.hibernate.jpa.internal.metamodel.MetadataContext] (ServerService Thread Pool -- 74) HHH015011: Unable to locate static metamodel field : eu.glsgroup.fpcs.persistence.backend.ShipmentSourceTranslation_#importsource; this may or may not indicate a problem with the static metamodel
[] 2019-10-17 14:30:01,444 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0348: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
("core-service" => "management"),
("management-interface" => "http-interface")
]'
I think you might be interested in increasing the timeout of Wildfly, because the default timeout for applications is 5 minutes.
So you can adjust your standalone.xml and use something like this example, the time is in seconds by the way, so 900s would be 15 minutes...
Here is a link so you can check more variables that you may need (It is for Wildfly 10, but I think it is the same for Wildfly 11). So you can manage if you need a scan-interval or even if you want to deploy files that are in other directories by changing/adding a new path.
1 Option -> To increase timeout:
<system-properties>
<property name="jboss.as.management.blocking.timeout" value="900"/>
</system-properties>
...
<profile>
...
<subsystem xmlns="urn:jboss:domain:deployment-scanner:2.0">
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir"
scan-interval="5000" deployment-timeout="900"
runtime-failure-causes-rollback=
"${jboss.deployment.scanner.rollback.on.failure:false}"/>
</subsystem>
...
</profile>
2 Option -> To cancel scanning, to start Wildfly then to deploy, you can turn off scanning by changing your standalone.xml:
<deployment-scanner path="deployments" relative-to="jboss.server.base.dir" scan-interval="5000" scan-enabled="false"/>
So now you will just start Wildfly, after that, you will run jboss-cli.bat or jboss-cli.sh depending on your OS. Type "connect" and paste this /subsystem=deployment-scanner/scanner=default:write-attribute(name="scan-enabled",value=true)
So now your wars will be deployed at runtime - after your Wildfly already started 'clean' (PS.: I am considering the default ports and the default configuration of Wildfly). Regards
UPDATED
3 Option -> Modify your standalone.conf and increase your Wildfly JVM memory allocation to this values: set "JAVA_OPTS=-Xms2G -Xmx4G"
Then try to start Wildfly again, with your wars normally. (Just be sure to change the correct one, standalone.conf or standalone.conf.bat depending on your OS).
I think your memory allocation is causing this problem.
How to solve the error given below in eclipse ?
ERROR:
[org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [] startup failed due to previous errors
I'm trying to start WildFly 8.2 under a user that doesn't have permissions to write in a WildFly home directory and it's subdirectories. For this purpose I've copied standalone directory to a user home directory. Here is a command I use to start WildFly in cygwin:
$ /cygdrive/c/Program\ Files/wildfly-8.2.0.Final/bin/standalone.sh -Djboss.server.base.dir='C:\Users\above_mentioned_user\standalone' -c standalone.xml
And here is an output of this command:
cygpath: can't convert empty path
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: C:\Program Files\wildfly-8.2.0.Final
JAVA: /cygdrive/c/Program Files/Java/jdk1.7.0_51/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
java.lang.IllegalArgumentException: Failed to instantiate class "org.jboss.logmanager.handlers.PeriodicRotatingFileHandler" for handler "FILE"
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:119)
at org.jboss.logmanager.config.LogContextConfigurationImpl.doPrepare(LogContextConfigurationImpl.java:338)
at org.jboss.logmanager.config.LogContextConfigurationImpl.prepare(LogContextConfigurationImpl.java:291)
at org.jboss.logmanager.config.LogContextConfigurationImpl.commit(LogContextConfigurationImpl.java:300)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:542)
at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:97)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:300)
at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:262)
at java.util.logging.LogManager$2.run(LogManager.java:312)
at java.util.logging.LogManager$2.run(LogManager.java:310)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:310)
at java.util.logging.LogManager.getLogManager(LogManager.java:292)
at java.util.logging.Logger.<init>(Logger.java:264)
at java.util.logging.Logger.<init>(Logger.java:260)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1430)
at java.util.logging.LogManager$RootLogger.<init>(LogManager.java:1428)
at java.util.logging.LogManager$1.run(LogManager.java:196)
at java.security.AccessController.doPrivileged(Native Method)
at java.util.logging.LogManager.<clinit>(LogManager.java:173)
at org.jboss.modules.Main.main(Main.java:443)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.jboss.logmanager.config.AbstractPropertyConfiguration$ConstructAction.validate(AbstractPropertyConfiguration.java:117)
... 20 more
Caused by: java.io.FileNotFoundException: C:\Program Files\wildfly-8.2.0.Final\standalone\log\server.log (The system cannot find the path specified)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:154)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.setFile(PeriodicRotatingFileHandler.java:105)
at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:192)
at org.jboss.logmanager.handlers.FileHandler.<init>(FileHandler.java:122)
at org.jboss.logmanager.handlers.PeriodicRotatingFileHandler.<init>(PeriodicRotatingFileHandler.java:73)
... 25 more
14:17:42,875 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
14:17:42,884 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
14:17:42,859 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
14:17:42,882 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
14:17:42,895 INFO [org.jboss.remoting] (MSC service thread 1-8) JBoss Remoting version 4.0.6.Final
14:17:42,906 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
14:17:42,919 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
14:17:42,935 INFO [org.jboss.as.connector.logging] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
14:17:42,938 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 8 core threads with 64 task threads based on your 4 available processors
14:17:42,941 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
14:17:42,953 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
14:17:42,960 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.21.Final
14:17:42,967 INFO [org.jboss.as.naming] (MSC service thread 1-2) JBAS011802: Starting Naming Service
14:17:42,970 INFO [org.jboss.as.mail.extension] (MSC service thread 1-5) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:17:43,040 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017502: Undertow 1.1.0.Final starting
14:17:43,040 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
14:17:43,489 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path C:\Program Files\wildfly-8.2.0.Final/welcome-content
14:17:43,497 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017525: Started server default-server.
14:17:43,520 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
14:17:43,672 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
14:17:43,719 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory C:\Users\tazi0514\projects\nfv\r2\wildfly\deployments
14:17:43,808 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
14:17:43,994 INFO [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
14:17:44,114 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
14:17:44,115 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
14:17:44,116 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 3294ms - Started 184 of 234 services (82 services are lazy, passive or on-demand)
As you can see in the log above first WildFly tries writing to C:\Program Files\wildfly-8.2.0.Final\standalone\log\server.log even though there is another directory pointed out in the command line as a server base directory. Having failed to write there because of lack of permissions WildFly goes on starting a server normally.
Is there a way to make WildFly not to try writing a log in a default server base directory?
Try deleting logging.properties from your copied standalone directory. This is a generated file defining the absolute log file path which I suppose in your case still references the original location.
It seems like WildFly ignores a value of jboss.server.base.dir property. But it still takes into account a value of JBOSS_BASE_DIR environment variable. So I've just made the following alias in BASH to have a short way to start WildFly:
alias wildfly_start='JBOSS_BASE_DIR="$(realpath ~/wildfly)" /bin/bash -c "/cygdrive/c/Program\ Files/wildfly-8.2.0.Final/bin/standalone.sh -c standalone.xml"'
In my case a user home directory in cygwin coincides with a Windows user home directory.
I've installed WildFly 8.2.1 on Ubuntu 18.04 desktop. I could start WildFly from my terminal as root using standalone.sh with no problem, but when I started it from within Intellij IDEA, it showed the abovementioned error.
To fix it, I created a 'wildfly' group in Ubuntu and set it as the group for the WildFly installation folder using chgrp. Then I assigned rwx permissions to the group for that folder. Finally, I added my login user (which Intellij IDEA was running under) to the wildfly group. Now it runs in IDEA without complaining about permissions denied.
I'm bit new to JBoss, could you please help me out in finding the root cause in the below mentioned issue.Thanks and much appreciated,
Issue: Session replication is not happening between master(domain
controller) and slave(host). Following are the logs,
From master:
[Server:server-three] 07:53:38,246 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 65) ISPN000078: Starting JGroups Channel
[Server:server-three] 07:53:38,260 INFO [stdout] (ServerService Thread Pool -- 65)
[Server:server-three] 07:53:38,260 INFO [stdout] (ServerService Thread Pool -- 65) -------------------------------------------------------------------
[Server:server-three] 07:53:38,261 INFO [stdout] (ServerService Thread Pool -- 65) GMS: address=master:server-three/web, cluster=web, physical address=10.78.216.145:7850
[Server:server-three] 07:53:38,261 INFO [stdout] (ServerService Thread Pool -- 65) -------------------------------------------------------------------
[Host Controller] 07:53:40,511 INFO [org.jboss.as.domain] (Host Controller Service Threads - 25) JBAS010918: Registered remote slave host "slave", JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19)
[Server:server-three] 07:53:41,273 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 65) ISPN000094: Received new cluster view: [master:server-three/web|0] [master:server-three/web]
[Server:server-three] 07:53:41,275 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 65) ISPN000079: Cache local address is master:server-three/web, physical addresses are [10.78.216.145:7850]
[Server:server-three] 07:53:41,279 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 65) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.10.Final
[Server:server-three] 07:53:41,288 INFO [org.jboss.as.clustering] (MSC service thread 1-6) JBAS010238: Number of cluster members: 1
From slave:
[Server:server-three-slave] 07:53:36,274 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 67) ISPN000078: Starting JGroups Channel
[Server:server-three-slave] 07:53:36,287 INFO [stdout] (ServerService Thread Pool -- 67)
[Server:server-three-slave] 07:53:36,287 INFO [stdout] (ServerService Thread Pool -- 67) -------------------------------------------------------------------
[Server:server-three-slave] 07:53:36,288 INFO [stdout] (ServerService Thread Pool -- 67) GMS: address=slave:server-three-slave/web, cluster=web, physical address=10.78.216.36:7850
[Server:server-three-slave] 07:53:36,288 INFO [stdout] (ServerService Thread Pool -- 67) -------------------------------------------------------------------
[Server:server-three-slave] 07:53:39,301 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 67) ISPN000094: Received new cluster view: [slave:server-three-slave/web|0] [slave:server-three-slave/web]
[Server:server-three-slave] 07:53:39,302 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 67) ISPN000079: Cache local address is slave:server-three-slave/web, physical addresses are [10.78.216.36:7850]
[Server:server-three-slave] 07:53:39,306 INFO [org.infinispan.factories.GlobalComponentRegistry] (ServerService Thread Pool -- 67) ISPN000128: Infinispan version: Infinispan 'Delirium' 5.2.10.Final
[Server:server-three-slave] 07:53:39,315 INFO [org.jboss.as.clustering] (MSC service thread 1-5) JBAS010238: Number of cluster members: 1
I'm advertising my cluster and i can see the both master and slave nodes are present in the UI,
https://10.78.X.X:8445/mod_cluster_manager,
I have disabled firewall and SELinux to avoid network problems.I believe, i have made all the required configurations in domain.xml and ssl.conf of httpd. I have also added <distributable/> tag and jboss-web.xml changes in my war. It'd be of more help if anyone of you direct me in a different direction as i'm totally lost,
Even i can see the following in my master log:
[Host Controller] 07:18:58,862 INFO [org.jboss.as.domain] (Host Controller Service Threads - 28) JBAS010918: Registered remote slave host "slave", JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19)
[Server:server-three] 07:18:59,029 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (ServerService Thread Pool -- 69) ISPN000094: Received new cluster view: [master:server-three/web|0] [master:server-three/web]
I have tried adding ProxyPass with stickySession, didn't get much luck. any suggestion or help will be much appreciated,
Thanks,
Joy.
The <distributable/> tag must be added to the web.xml file not in jboss-web.xml
Enable Session Replication in Your Application
Overview
To take advantage of the JBoss Enterprise Application Platform's High Availability (HA) > features, configure your application
to be distributable. This procedure shows how to do that, and then
explains some of the advanced configuration options you can use.
Required: Indicate that your application is distributable.
If your application is not marked as distributable, its sessions will
never be distributed. Add the <distributable /> element inside the
<web-app> tag of your application's web.xml discriptor file. Here
is an example.
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<distributable/>
</web-app>
See more: Chapter 7. Clustering in Web Applications
I have been deploying a custom theme recently with no problems. However on a recent deploy Liferay reverted to the default classic theme and i had these errors in the log:
It doesn't unregister or register...
11:10:20,722 INFO [ServerService Thread Pool -- 254][PluginPackageUtil:1049] Reading plugin package for new-theme
11:10:20,731 INFO [ServerService Thread Pool -- 254][ThemeHotDeployListener:129] Unregistering themes for new-theme
11:10:20,732 INFO [ServerService Thread Pool -- 254][ThemeHotDeployListener:164] 0 themes for new-theme was unregistered
11:10:21,081 INFO [ServerService Thread Pool -- 273][HotDeployImpl:185] Deploying new-theme from queue
11:10:21,082 INFO [ServerService Thread Pool -- 273][PluginPackageUtil:1049] Reading plugin package for new-theme
11:10:21,148 INFO [ServerService Thread Pool -- 273][ThemeHotDeployListener:89] Registering themes for new-theme
11:10:21,232 INFO [ServerService Thread Pool -- 273][ThemeHotDeployListener:107] 0 themes for new-theme are available for use
There is nothing else related to the theme deployment in the logs as to why it hasn't been deployed.
It seems that your theme did not deployed correctly. This might happen if you have changed the database after deploying the theme. please check if your theme is deployed properly, it is present in your web-apps folder.
and you are referring to same database.