2:24 p.m.
Folks I'm trying to deploy aerogear on Kubernetes. I'm using the wildfly
image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
As I have my databases outside of Kubernetes I've built the image as
described here:
docker build -t aerogear/unifiedpush-wildfly .
With the following dockerfile:
https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
Unfortunately the dockerfile seems to point to an invalid tarball:
RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
$UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
So I went to:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/
And got:
https://github.com/aerogear/aerogear-unifiedpush-server/
releases/download/1.2.0-beta.1/aerogear-unifiedpush-server-
1.2.0-beta.1-dist.tar.gz
Then tried to deploy the wars getting a ton of errors:
https://pastebin.com/G89f3EpM
It seems that among other problems a mysql is being deployed on my server
which makes no sense as I've provided the variables in standalone.xml:
<connection-url>jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_
TCP_ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPUSH_ENV_MYSQL_
DATABASE}?useUnicode=true&characterEncoding=UTF-8</connection-url>
<user-name>${env.UNIFIEDPUSH_ENV_MYSQL_USER}</user-name>
<password>${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}</password>
<connection-url>jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_
ADDR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_MYSQL_DATABASE}?
useUnicode=true&characterEncoding=UTF-8</connection-url>
<user-name>${env.KEYCLOAK_ENV_MYSQL_USER}</user-name>
<password>${env.KEYCLOAK_ENV_MYSQL_PASSWORD}</password>
<core-environment>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
I'm not sure if the case is related to:
https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-
2117?filter=allopenissues
Anyone had success deploying in kubernetes?
9:40 a.m.
On Fri, Jun 23, 2017 at 3:24 PM, Victor Silva <vfbsilva(a)gmail.com> wrote:
Folks I'm trying to deploy aerogear on Kubernetes. I'm using
the wildfly
image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
As I have my databases outside of Kubernetes I've built the image as
described here:
docker build -t aerogear/unifiedpush-wildfly .
With the following dockerfile:
https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
Unfortunately the dockerfile seems to point to an invalid tarball:
RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
$UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
So I went to:
https://github.com/aerogear/aerogear-unifiedpush-server/releases/
And got:
https://github.com/aerogear/aerogear-unifiedpush-server/rele
ases/download/1.2.0-beta.1/aerogear-unifiedpush-server-1.
2.0-beta.1-dist.tar.gz
Then tried to deploy the wars getting a ton of errors:
https://pastebin.com/G89f3EpM
It seems that among other problems a mysql is being deployed on my server
which makes no sense as I've provided the variables in standalone.xml:
<connection-url>jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_TCP
_ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPU
SH_ENV_MYSQL_DATABASE}?useUnicode=true&characterE
ncoding=UTF-8</connection-url>
<user-name>${env.UNIFIEDPUSH_ENV_MYSQL_USER}</user-name>
<password>${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}</password>
<connection-url>jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_AD
DR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_
MYSQL_DATABASE}?useUnicode=true&characterEncoding=
UTF-8</connection-url>
<user-name>${env.KEYCLOAK_ENV_MYSQL_USER}</user-name>
<password>${env.KEYCLOAK_ENV_MYSQL_PASSWORD}</password>
<core-environment>
</core-environment>
<recovery-environment socket-binding="txn-recovery-environment"
status-socket-binding="txn-status-manager"/>
<socket-binding name="txn-recovery-environment" port="4712"/>
I'm not sure if the case is related to:
https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-2117?
filter=allopenissues
Anyone had success deploying in kubernetes?
The Dockerfile points to a valid tarball; the Dockerfile also copies
resources from the local directory into the image in order to setup the
mysql connections.
You can *NOT* get a working image by copying the Dockerfile on dockerhub
to your machine and running `docker build` because you are missing the
local files. If you want to build a dockerfile you can either make your
own dockerfile that extends the UPS docker image, or you can clone
https://github.com/jboss-dockerfiles/aerogear, edit the files as you see
fit, and then build from that.
I don't think you need to though. All you need to do is set the
environment variables in the standalone.xml file you sent when you perform
your docker run.
Source : I am running UPS in a Kubernetes POD right now.
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
2:23 p.m.
Hello Summers thanks for the reply I'm redoing all steps here:
/[root@localhost aerogear]# git clone
https://github.com/jboss-dockerfiles/aerogear.git
Cloning into 'aerogear'...
remote: Counting objects: 235, done.
remote: Total 235 (delta 0), reused 0 (delta 0), pack-reused 235
Receiving objects: 100% (235/235), 53.08 KiB | 88.00 KiB/s, done.
Resolving deltas: 100% (104/104), done.
[root@localhost aerogear]# ls
aerogear
[root@localhost aerogear]# cd aerogear/
[root@localhost aerogear]# ls
netty README.md wildfly
[root@localhost aerogear]# ls
netty README.md wildfly
[root@localhost aerogear]# cd wildfly/
[root@localhost wildfly]# ls
[root@localhost wildfly]# docker build -t aerogear/unifiedpush-wildfly .
Sending build context to Docker daemon 56.83 kB
Step 1 : FROM jboss/wildfly:10.0.0.Final
---> 905e36b7def0
Step 2 : MAINTAINER Bruno Oliveira <bruno(a)abstractj.org>
---> Using cache
---> 6c433f53b853
Step 3 : USER root
---> Using cache
---> aa2fc19196c2
Step 4 : RUN yum install -y unzip wget && yum -q clean all
---> Using cache
---> d8b80b8fbac5
Step 5 : ENV mysql_module_dir $JBOSS_HOME/modules/com/mysql/jdbc/main/
---> Using cache
---> 39cab60cae70
Step 6 : RUN mkdir -p ${mysql_module_dir}
---> Using cache
---> 783baedaeaa2
Step 7 : RUN wget -O mysql-connector-java-5.1.18.jar
http://search.maven.org/remotecontent\?filepath\=mysql/mysql-connector-ja...
---> Using cache
---> 84ccd208a93a
Step 8 : RUN mv mysql-connector-java-5.1.18.jar ${mysql_module_dir}
---> Using cache
---> 04bd7743dbaa
Step 9 : COPY configuration/xml/mysql-module.xml
${mysql_module_dir}/module.xml
---> f1e9de3f3b87
Removing intermediate container b404cd429890
Step 10 : RUN mv $JBOSS_HOME/standalone/configuration/standalone.xml
$JBOSS_HOME/standalone/configuration/standalone.xml.orig
---> Running in e37a49388ebf
---> 23eea83f5d94
Removing intermediate container e37a49388ebf
Step 11 : ADD configuration/xml/standalone-full-sample.xml
$JBOSS_HOME/standalone/configuration/standalone.xml
---> 180f831e1d38
Removing intermediate container 7933c6d6da9f
Step 12 : ADD configuration/certs/
$JBOSS_HOME/standalone/configuration/certs
---> c9dae64655d7
Removing intermediate container 3085fd179162
Step 13 : WORKDIR /opt/jboss/wildfly/standalone/configuration/certs
---> Running in c9cc46ef71aa
---> e66a1c4b864c
Removing intermediate container c9cc46ef71aa
Step 14 : RUN ./certificate.sh
---> Running in 79ba27ab9e4f
Certificate stored in file <client.aerogear.dev.cer>
Certificate was added to keystore
---> ae7c97d42dd7
Removing intermediate container 79ba27ab9e4f
Step 15 : WORKDIR /opt/jboss/wildfly
---> Running in de1fbd754db3
---> 4d4ae6b8b4ce
Removing intermediate container de1fbd754db3
Step 16 : EXPOSE 8443
---> Running in aea24644db6e
---> 7f7419df178c
Removing intermediate container aea24644db6e
Successfully built 7f7419df178c
/
Pushed to my images repo and redeployed. Still the deployments folder is
empty:
/[root@aerogear-3231627257-k8698 standalone]# cd deployments/
[root@aerogear-3231627257-k8698 deployments]# ls
README.txt/
Because the url seems invalid so I downloaded it from:
/wget
https://github.com/aerogear/aerogear-unifiedpush-server/releases/download...
and deployed getting:
/cat /opt/jboss/wildfly/standalone/log/server.log
2017-06-28 19:01:44,160 INFO [org.jboss.modules] (main) JBoss Modules
version 1.5.2.Final
2017-06-28 19:01:44,474 INFO [org.jboss.msc] (main) JBoss MSC version
1.2.6.Final
2017-06-28 19:01:44,587 INFO [org.jboss.as] (MSC service thread 1-7)
WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) starting
2017-06-28 19:01:44,589 DEBUG [org.jboss.as.config] (MSC service thread 1-7)
Configured system properties:
[Standalone] =
awt.toolkit = sun.awt.X11.XToolkit
file.encoding = ANSI_X3.4-1968
file.encoding.pkg = sun.io
file.separator = /
java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment
java.awt.headless = true
java.awt.printerjob = sun.print.PSPrinterJob
java.class.path = /opt/jboss/wildfly/jboss-modules.jar
java.class.version = 52.0
java.endorsed.dirs =
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/endorsed
java.ext.dirs =
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/ext:/usr/java/packages/lib/ext
java.home =
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre
java.io.tmpdir = /tmp
java.library.path =
/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
java.net.preferIPv4Stack = true
java.runtime.name = OpenJDK Runtime Environment
java.runtime.version = 1.8.0_131-b12
java.specification.name = Java Platform API Specification
java.specification.vendor = Oracle Corporation
java.specification.version = 1.8
java.util.logging.manager = org.jboss.logmanager.LogManager
java.vendor = Oracle Corporation
java.vendor.url = http://java.oracle.com/
java.vendor.url.bug = http://bugreport.sun.com/bugreport/
java.version = 1.8.0_131
java.vm.info = mixed mode
java.vm.name = OpenJDK 64-Bit Server VM
java.vm.specification.name = Java Virtual Machine Specification
java.vm.specification.vendor = Oracle Corporation
java.vm.specification.version = 1.8
java.vm.vendor = Oracle Corporation
java.vm.version = 25.131-b12
javax.management.builder.initial =
org.jboss.as.jmx.PluggableMBeanServerBuilder
javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory
javax.xml.parsers.DocumentBuilderFactory =
__redirected.__DocumentBuilderFactory
javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory
javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory
javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory
javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory
javax.xml.transform.TransformerFactory =
__redirected.__TransformerFactory
javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema
= __redirected.__SchemaFactory
javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom =
__redirected.__XPathFactory
jboss.bind.address = 0.0.0.0
jboss.home.dir = /opt/jboss/wildfly
jboss.host.name = aerogear-3231627257-k8698
jboss.modules.dir = /opt/jboss/wildfly/modules
jboss.modules.system.pkgs = org.jboss.byteman
jboss.node.name = aerogear-3231627257-k8698
jboss.qualified.host.name = aerogear-3231627257-k8698
jboss.server.base.dir = /opt/jboss/wildfly/standalone
jboss.server.config.dir =
/opt/jboss/wildfly/standalone/configuration
jboss.server.data.dir = /opt/jboss/wildfly/standalone/data
jboss.server.deploy.dir = /opt/jboss/wildfly/standalone/data/content
jboss.server.log.dir = /opt/jboss/wildfly/standalone/log
jboss.server.name = aerogear-3231627257-k8698
jboss.server.persist.config = true
jboss.server.temp.dir = /opt/jboss/wildfly/standalone/tmp
line.separator =
logging.configuration =
file:/opt/jboss/wildfly/standalone/configuration/logging.properties
module.path = /opt/jboss/wildfly/modules
org.jboss.boot.log.file =
/opt/jboss/wildfly/standalone/log/server.log
org.jboss.resolver.warning = true
org.xml.sax.driver = __redirected.__XMLReaderFactory
os.arch = amd64
os.name = Linux
os.version = 4.9.9-coreos-r1
path.separator = :
sun.arch.data.model = 64
sun.boot.class.path =
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/jsse.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/jce.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/charsets.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/jfr.jar:/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/classes
sun.boot.library.path =
/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.131-3.b12.el7_3.x86_64/jre/lib/amd64
sun.cpu.endian = little
sun.cpu.isalist =
sun.io.unicode.encoding = UnicodeLittle
sun.java.command = /opt/jboss/wildfly/jboss-modules.jar -mp
/opt/jboss/wildfly/modules org.jboss.as.standalone
-Djboss.home.dir=/opt/jboss/wildfly
-Djboss.server.base.dir=/opt/jboss/wildfly/standalone -b 0.0.0.0
sun.java.launcher = SUN_STANDARD
sun.jnu.encoding = ANSI_X3.4-1968
sun.management.compiler = HotSpot 64-Bit Tiered Compilers
sun.os.patch.level = unknown
user.country = US
user.dir = /opt/jboss/wildfly
user.home = /root
user.language = en
user.name = root
user.timezone = UTC
2017-06-28 19:01:44,590 DEBUG [org.jboss.as.config] (MSC service thread 1-7)
VM Arguments: -D[Standalone] -Xms64m -Xmx512m -XX:MetaspaceSize=96M
-XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
-Dorg.jboss.boot.log.file=/opt/jboss/wildfly/standalone/log/server.log
-Dlogging.configuration=file:/opt/jboss/wildfly/standalone/configuration/logging.properties
2017-06-28 19:01:47,034 INFO [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0039: Creating http management service using socket-binding
(management-http)
2017-06-28 19:01:47,065 INFO [org.xnio] (MSC service thread 1-2) XNIO
version 3.4.0.Final
2017-06-28 19:01:47,080 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO
NIO Implementation Version 3.4.0.Final
2017-06-28 19:01:47,152 INFO [org.jboss.remoting] (MSC service thread 1-2)
JBoss Remoting version 4.0.21.Final
2017-06-28 19:01:47,256 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan
subsystem.
2017-06-28 19:01:47,270 INFO [org.jboss.as.naming] (ServerService Thread
Pool -- 52) WFLYNAM0001: Activating Naming Subsystem
2017-06-28 19:01:47,271 INFO [org.wildfly.extension.io] (ServerService
Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 16
core threads with 128 task threads based on your 8 available processors
2017-06-28 19:01:47,283 INFO [org.wildfly.iiop.openjdk] (ServerService
Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem
2017-06-28 19:01:47,317 INFO [org.jboss.as.jsf] (ServerService Thread Pool
-- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]
2017-06-28 19:01:47,321 WARN [org.jboss.as.txn] (ServerService Thread Pool
-- 60) WFLYTX0013: Node identifier property is set to the default value.
Please make sure it is unique.
2017-06-28 19:01:47,360 INFO [org.jboss.as.security] (ServerService Thread
Pool -- 59) WFLYSEC0002: Activating Security Subsystem
2017-06-28 19:01:47,394 INFO [org.jboss.as.security] (MSC service thread
1-6) WFLYSEC0001: Current PicketBox version=4.9.6.Final
2017-06-28 19:01:47,438 INFO [org.jboss.as.webservices] (ServerService
Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension
2017-06-28 19:01:47,466 INFO [org.jboss.as.connector] (MSC service thread
1-8) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.3.4.Final)
2017-06-28 19:01:47,568 INFO [org.jboss.as.naming] (MSC service thread 1-2)
WFLYNAM0003: Starting Naming Service
2017-06-28 19:01:47,576 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool
-- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.3)
2017-06-28 19:01:47,597 INFO [org.jboss.as.mail.extension] (MSC service
thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
2017-06-28 19:01:47,606 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-4) WFLYUT0003: Undertow 1.4.0.Final starting
2017-06-28 19:01:47,637 INFO [org.jboss.as.connector.deployers.jdbc] (MSC
service thread 1-3) WFLYJCA0018: Started Driver service with driver-name =
h2
2017-06-28 19:01:47,771 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool
-- 36) WFLYJCA0005: Deploying non-JDBC-compliant driver class
com.mysql.jdbc.Driver (version 5.1)
2017-06-28 19:01:47,780 INFO [org.jboss.as.connector.deployers.jdbc] (MSC
service thread 1-1) WFLYJCA0018: Started Driver service with driver-name =
mysql
2017-06-28 19:01:48,021 INFO [org.jboss.as.ejb3] (MSC service thread 1-8)
WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size
of 128 (per class), which is derived from thread worker pool sizing.
2017-06-28 19:01:48,021 INFO [org.jboss.as.ejb3] (MSC service thread 1-7)
WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of
32 (per class), which is derived from the number of CPUs on this host.
2017-06-28 19:01:48,052 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path
'/opt/jboss/wildfly/welcome-content' with options [directory-listing:
'false', follow-symlink: 'false', case-sensitive: 'true',
safe-symlink-paths: '[]']
2017-06-28 19:01:48,095 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-7) WFLYUT0012: Started server default-server.
2017-06-28 19:01:48,097 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-3) WFLYUT0018: Host default-host starting
2017-06-28 19:01:48,238 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-7) WFLYUT0006: Undertow HTTP listener default listening on
0.0.0.0:8080
2017-06-28 19:01:48,501 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8)
WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
2017-06-28 19:01:48,507 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2)
WFLYJCA0001: Bound data source [java:jboss/datasources/UnifiedPushDS]
2017-06-28 19:01:48,507 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7)
WFLYJCA0001: Bound data source [java:jboss/datasources/KeycloakDS]
2017-06-28 19:01:48,612 INFO [org.wildfly.iiop.openjdk] (MSC service thread
1-4) WFLYIIOP0009: CORBA ORB Service started
2017-06-28 19:01:48,774 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-1) WFLYMSGAMQ0075: AIO wasn't located on this
platform, it will fall back to using pure Java NIO. Your platform is Linux,
install LibAIO to enable the AIO journal and achieve optimal performance.
2017-06-28 19:01:48,916 INFO [org.jboss.as.server.deployment.scanner] (MSC
service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for
directory /opt/jboss/wildfly/standalone/deployments
2017-06-28 19:01:49,005 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting
with configuration Broker Configuration
(clustered=false,journalDirectory=/opt/jboss/wildfly/standalone/data/activemq/journal,bindingsDirectory=/opt/jboss/wildfly/standalone/data/activemq/bindings,largeMessagesDirectory=/opt/jboss/wildfly/standalone/data/activemq/largemessages,pagingDirectory=/opt/jboss/wildfly/standalone/data/activemq/paging)
2017-06-28 19:01:49,411 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221013: Using NIO Journal
2017-06-28 19:01:49,450 INFO
[org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-8)
ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final
2017-06-28 19:01:49,582 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 68) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:01:49,595 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 66) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:01:49,596 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 68) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:01:49,597 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 66) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:01:49,698 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on
0.0.0.0:8443
2017-06-28 19:01:49,839 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221043: Protocol module found:
[artemis-server]. Adding protocol support for: CORE
2017-06-28 19:01:49,850 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221043: Protocol module found:
[artemis-amqp-protocol]. Adding protocol support for: AMQP
2017-06-28 19:01:49,869 INFO [org.jboss.ws.common.management] (MSC service
thread 1-4) JBWS022052: Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)
2017-06-28 19:01:49,878 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221043: Protocol module found:
[artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
2017-06-28 19:01:49,887 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221043: Protocol module found:
[artemis-stomp-protocol]. Adding protocol support for: STOMP
2017-06-28 19:01:50,210 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for
activemq-remoting protocol handled by http-acceptor acceptor
2017-06-28 19:01:50,211 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-2) WFLYMSGAMQ0016: Registered HTTP upgrade for
activemq-remoting protocol handled by http-acceptor acceptor
2017-06-28 19:01:50,210 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for
activemq-remoting protocol handled by http-acceptor-throughput acceptor
2017-06-28 19:01:50,224 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for
activemq-remoting protocol handled by http-acceptor-throughput acceptor
2017-06-28 19:01:50,306 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221007: Server is now live
2017-06-28 19:01:50,307 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221001: Apache ActiveMQ Artemis Message
Broker version 1.1.0.wildfly-017
[nodeID=3d02608b-5c34-11e7-8086-a9d987a9ae38]
2017-06-28 19:01:50,312 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 68) AMQ221003: trying to deploy queue
jms.queue.WNSPushMessageQueue
2017-06-28 19:01:50,509 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 82) AMQ221003: trying to deploy queue
jms.queue.MPNSPushMessageQueue
2017-06-28 19:01:50,515 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 85) AMQ221003: trying to deploy queue
jms.queue.AdmTokenBatchQueue
2017-06-28 19:01:50,518 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 79) AMQ221003: trying to deploy queue
jms.queue.AdmPushMessageQueue
2017-06-28 19:01:50,520 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 72) AMQ221003: trying to deploy queue
jms.queue.APNsTokenBatchQueue
2017-06-28 19:01:50,526 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 78) AMQ221003: trying to deploy queue
jms.queue.SimplePushTokenBatchQueue
2017-06-28 19:01:50,528 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 80) AMQ221003: trying to deploy queue
jms.queue.GCMPushMessageQueue
2017-06-28 19:01:50,545 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 77) AMQ221003: trying to deploy queue
jms.queue.TriggerMetricCollectionQueue
2017-06-28 19:01:50,554 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 81) AMQ221003: trying to deploy queue
jms.topic.MetricsProcessingStartedTopic
2017-06-28 19:01:50,570 INFO [org.jboss.as.connector.deployment] (MSC
service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA
2017-06-28 19:01:50,620 INFO [org.wildfly.extension.messaging-activemq]
(ServerService Thread Pool -- 71) WFLYMSGAMQ0002: Bound messaging object to
jndi name java:/ConnectionFactory
2017-06-28 19:01:50,623 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 87) AMQ221003: trying to deploy queue
jms.queue.MPNSTokenBatchQueue
2017-06-28 19:01:50,627 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 86) AMQ221003: trying to deploy queue
jms.queue.AllBatchesLoadedQueue
2017-06-28 19:01:50,630 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 84) AMQ221003: trying to deploy queue
jms.queue.DLQ
2017-06-28 19:01:50,634 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 83) AMQ221003: trying to deploy queue
jms.queue.TriggerVariantMetricCollectionQueue
2017-06-28 19:01:50,640 INFO [org.apache.activemq.artemis.jms.server]
(ServerService Thread Pool -- 75) AMQ121005: Invalid "host" value
"0.0.0.0"
detected for "http-connector" connector. Switching to
"aerogear-3231627257-k8698". If this new address is incorrect please
manually configure the connector to use the proper one.
2017-06-28 19:01:50,641 INFO [org.wildfly.extension.messaging-activemq]
(ServerService Thread Pool -- 75) WFLYMSGAMQ0002: Bound messaging object to
jndi name java:jboss/exported/jms/RemoteConnectionFactory
2017-06-28 19:01:50,641 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 74) AMQ221003: trying to deploy queue
jms.queue.BatchLoadedQueue
2017-06-28 19:01:50,644 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 76) AMQ221003: trying to deploy queue
jms.queue.SimplePushMessageQueue
2017-06-28 19:01:50,657 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 73) AMQ221003: trying to deploy queue
jms.queue.MetricsQueue
2017-06-28 19:01:50,659 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 65) AMQ221003: trying to deploy queue
jms.queue.GCMTokenBatchQueue
2017-06-28 19:01:50,662 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 69) AMQ221003: trying to deploy queue
jms.queue.ExpiryQueue
2017-06-28 19:01:50,665 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 70) AMQ221003: trying to deploy queue
jms.queue.WNSTokenBatchQueue
2017-06-28 19:01:50,669 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 67) AMQ221003: trying to deploy queue
jms.queue.FreeServiceSlotQueue
2017-06-28 19:01:50,672 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 66) AMQ221003: trying to deploy queue
jms.queue.APNsPushMessageQueue
2017-06-28 19:01:50,687 INFO [org.apache.activemq.artemis.ra] (MSC service
thread 1-1) Resource adaptor started
2017-06-28 19:01:50,689 INFO
[org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator]
(MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra
2017-06-28 19:01:50,701 INFO [org.jboss.as.connector.deployment] (MSC
service thread 1-5) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
2017-06-28 19:01:50,701 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-5) WFLYMSGAMQ0002: Bound messaging object to jndi name
java:jboss/DefaultJMSConnectionFactory
2017-06-28 19:01:51,005 INFO [org.jboss.as] (Controller Boot Thread)
WFLYSRV0060: Http management interface listening on
http://127.0.0.1:9990/management
2017-06-28 19:01:51,006 INFO [org.jboss.as] (Controller Boot Thread)
WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2017-06-28 19:01:51,007 INFO [org.jboss.as] (Controller Boot Thread)
WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in
7365ms - Started 414 of 649 services (431 services are lazy, passive or
on-demand)
2017-06-28 19:06:39,351 INFO [org.jboss.as.repository]
(DeploymentScanner-threads - 1) WFLYDR0001: Content added at location
/opt/jboss/wildfly/standalone/data/content/a3/3756444b7334e04a07e49542f80cb6ed55b0c0/content
2017-06-28 19:06:39,605 INFO [org.jboss.as.repository]
(DeploymentScanner-threads - 1) WFLYDR0001: Content added at location
/opt/jboss/wildfly/standalone/data/content/bc/19249d29335afa4c200b2bba31d87c35919fa3/content
2017-06-28 19:06:39,631 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-4) WFLYSRV0027: Starting deployment of
"unifiedpush-server-wildfly.war" (runtime-name:
"unifiedpush-server-wildfly.war")
2017-06-28 19:06:39,631 INFO [org.jboss.as.server.deployment] (MSC service
thread 1-6) WFLYSRV0027: Starting deployment of
"unifiedpush-auth-server.war" (runtime-name:
"unifiedpush-auth-server.war")
2017-06-28 19:06:43,264 WARN [org.jboss.as.server.deployment] (MSC service
thread 1-5) WFLYSRV0059: Class Path entry jaxb-api.jar in
/content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does
not point to a valid jar for a Class-Path reference.
2017-06-28 19:06:43,264 WARN [org.jboss.as.server.deployment] (MSC service
thread 1-5) WFLYSRV0059: Class Path entry activation.jar in
/content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does
not point to a valid jar for a Class-Path reference.
2017-06-28 19:06:43,265 WARN [org.jboss.as.server.deployment] (MSC service
thread 1-5) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in
/content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does
not point to a valid jar for a Class-Path reference.
2017-06-28 19:06:43,265 WARN [org.jboss.as.server.deployment] (MSC service
thread 1-5) WFLYSRV0059: Class Path entry jaxb1-impl.jar in
/content/unifiedpush-auth-server.war/WEB-INF/lib/jaxb-impl-2.2.4.jar does
not point to a valid jar for a Class-Path reference.
2017-06-28 19:06:43,274 WARN [org.jboss.as.server.deployment] (MSC service
thread 1-5) WFLYSRV0059: Class Path entry lib/snakeyaml-1.13.jar in
/content/unifiedpush-auth-server.war/WEB-INF/lib/liquibase-core-3.4.1.jar
does not point to a valid jar for a Class-Path reference.
2017-06-28 19:06:43,868 INFO [org.jboss.as.jpa] (MSC service thread 1-6)
WFLYJPA0002: Read persistence.xml for keycloak-default
2017-06-28 19:06:44,513 WARN [org.jboss.as.dependency.private] (MSC service
thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war"
is using a private module ("org.codehaus.jackson.jackson-core-asl:main")
which may be changed or removed in future versions without notice.
2017-06-28 19:06:44,513 WARN [org.jboss.as.dependency.private] (MSC service
thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war"
is using a private module ("org.codehaus.jackson.jackson-mapper-asl:main")
which may be changed or removed in future versions without notice.
2017-06-28 19:06:44,517 WARN [org.jboss.as.dependency.private] (MSC service
thread 1-4) WFLYSRV0018: Deployment "deployment.unifiedpush-auth-server.war"
is using a private module ("org.infinispan:main") which may be changed or
removed in future versions without notice.
2017-06-28 19:06:45,159 INFO [org.jboss.as.jpa] (MSC service thread 1-1)
WFLYJPA0002: Read persistence.xml for unifiedpush-default
2017-06-28 19:06:45,504 INFO [org.jboss.as.jpa] (ServerService Thread Pool
-- 97) WFLYJPA0010: Starting Persistence Unit (phase 1 of 2) Service
'unifiedpush-server-wildfly.war#unifiedpush-default'
2017-06-28 19:06:45,520 INFO [org.hibernate.jpa.internal.util.LogHelper]
(ServerService Thread Pool -- 97) HHH000204: Processing PersistenceUnitInfo
[
name: unifiedpush-default
...]
2017-06-28 19:06:45,759 INFO [org.jboss.weld.deployer] (MSC service thread
1-3) WFLYWELD0003: Processing weld deployment unifiedpush-server-wildfly.war
2017-06-28 19:06:45,787 INFO [org.hibernate.Version] (ServerService Thread
Pool -- 97) HHH000412: Hibernate Core {5.0.10.Final}
2017-06-28 19:06:45,788 INFO [org.hibernate.cfg.Environment] (ServerService
Thread Pool -- 97) HHH000206: hibernate.properties not found
2017-06-28 19:06:45,790 INFO [org.hibernate.cfg.Environment] (ServerService
Thread Pool -- 97) HHH000021: Bytecode provider name : javassist
2017-06-28 19:06:45,805 WARN
[org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl]
(ServerService Thread Pool -- 97) HHH000059: Defining
hibernate.transaction.flush_before_completion=true ignored in HEM
2017-06-28 19:06:45,889 INFO [org.hibernate.annotations.common.Version]
(ServerService Thread Pool -- 97) HCANN000001: Hibernate Commons Annotations
{5.0.1.Final}
2017-06-28 19:06:45,902 INFO
[org.hibernate.validator.internal.util.Version] (MSC service thread 1-3)
HV000001: Hibernate Validator 5.2.4.Final
2017-06-28 19:06:46,005 WARN [org.hibernate.orm.deprecation] (ServerService
Thread Pool -- 97) HHH90000012: Recognized obsolete hibernate namespace
http://hibernate.sourceforge.net/hibernate-mapping. Use namespace
http://www.hibernate.org/dtd/hibernate-mapping instead. Support for
obsolete DTD/XSD namespaces may be removed at any time.
2017-06-28 19:06:46,178 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'HealthNetworkServiceImpl' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
java:app/ag-push/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
java:module/HealthNetworkServiceImpl!org.jboss.aerogear.unifiedpush.message.HealthNetworkService
java:global/ag-push/HealthNetworkServiceImpl
java:app/ag-push/HealthNetworkServiceImpl
java:module/HealthNetworkServiceImpl
2017-06-28 19:06:46,181 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'MetricCollectionTrigger' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
java:app/ag-push/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
java:module/MetricCollectionTrigger!org.jboss.aerogear.unifiedpush.message.jms.MetricCollectionTrigger
java:global/ag-push/MetricCollectionTrigger
java:app/ag-push/MetricCollectionTrigger
java:module/MetricCollectionTrigger
2017-06-28 19:06:46,181 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'ClientInstallationServiceImpl' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
java:app/ag-push/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
java:module/ClientInstallationServiceImpl!org.jboss.aerogear.unifiedpush.service.ClientInstallationService
java:global/ag-push/ClientInstallationServiceImpl
java:app/ag-push/ClientInstallationServiceImpl
java:module/ClientInstallationServiceImpl
2017-06-28 19:06:46,183 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'VariantMetricInformationProducer' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
java:app/ag-push/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
java:module/VariantMetricInformationProducer!org.jboss.aerogear.unifiedpush.message.jms.VariantMetricInformationProducer
java:global/ag-push/VariantMetricInformationProducer
java:app/ag-push/VariantMetricInformationProducer
java:module/VariantMetricInformationProducer
2017-06-28 19:06:46,183 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'SimpleApnsClientCache' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/SimpleApnsClientCache!org.jboss.aerogear.unifiedpush.message.cache.SimpleApnsClientCache
java:app/ag-push/SimpleApnsClientCache!org.jboss.aerogear.unifiedpush.message.cache.SimpleApnsClientCache
java:module/SimpleApnsClientCache!org.jboss.aerogear.unifiedpush.message.cache.SimpleApnsClientCache
java:global/ag-push/SimpleApnsClientCache
java:app/ag-push/SimpleApnsClientCache
java:module/SimpleApnsClientCache
2017-06-28 19:06:46,183 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'PushMessageMetricsService' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
java:app/ag-push/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
java:module/PushMessageMetricsService!org.jboss.aerogear.unifiedpush.service.metrics.PushMessageMetricsService
java:global/ag-push/PushMessageMetricsService
java:app/ag-push/PushMessageMetricsService
java:module/PushMessageMetricsService
2017-06-28 19:06:46,183 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'GenericVariantServiceImpl' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
java:app/ag-push/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
java:module/GenericVariantServiceImpl!org.jboss.aerogear.unifiedpush.service.GenericVariantService
java:global/ag-push/GenericVariantServiceImpl
java:app/ag-push/GenericVariantServiceImpl
java:module/GenericVariantServiceImpl
2017-06-28 19:06:46,184 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'JmsClient' in
deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as
follows:
java:global/ag-push/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
java:app/ag-push/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
java:module/JmsClient!org.jboss.aerogear.unifiedpush.message.util.JmsClient
java:global/ag-push/JmsClient
java:app/ag-push/JmsClient
java:module/JmsClient
2017-06-28 19:06:46,184 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'HealthServiceImpl' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
java:app/ag-push/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
java:module/HealthServiceImpl!org.jboss.aerogear.unifiedpush.service.HealthDBService
java:global/ag-push/HealthServiceImpl
java:app/ag-push/HealthServiceImpl
java:module/HealthServiceImpl
2017-06-28 19:06:46,184 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'MessageHolderWithVariantsProducer' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
java:app/ag-push/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
java:module/MessageHolderWithVariantsProducer!org.jboss.aerogear.unifiedpush.message.jms.MessageHolderWithVariantsProducer
java:global/ag-push/MessageHolderWithVariantsProducer
java:app/ag-push/MessageHolderWithVariantsProducer
java:module/MessageHolderWithVariantsProducer
2017-06-28 19:06:46,185 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'PushyApnsSender' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/PushyApnsSender!org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender
java:app/ag-push/PushyApnsSender!org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender
java:module/PushyApnsSender!org.jboss.aerogear.unifiedpush.message.sender.PushNotificationSender
java:global/ag-push/PushyApnsSender
java:app/ag-push/PushyApnsSender
java:module/PushyApnsSender
2017-06-28 19:06:46,185 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'MetricsCollector' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
java:app/ag-push/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
java:module/MetricsCollector!org.jboss.aerogear.unifiedpush.message.MetricsCollector
java:global/ag-push/MetricsCollector
java:app/ag-push/MetricsCollector
java:module/MetricsCollector
2017-06-28 19:06:46,186 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'NotificationRouter' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
java:app/ag-push/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
java:module/NotificationRouter!org.jboss.aerogear.unifiedpush.message.NotificationRouter
java:global/ag-push/NotificationRouter
java:app/ag-push/NotificationRouter
java:module/NotificationRouter
2017-06-28 19:06:46,186 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'NotificationDispatcher' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
java:app/ag-push/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
java:module/NotificationDispatcher!org.jboss.aerogear.unifiedpush.message.NotificationDispatcher
java:global/ag-push/NotificationDispatcher
java:app/ag-push/NotificationDispatcher
java:module/NotificationDispatcher
2017-06-28 19:06:46,186 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'DeleteOldPushMessageInformationScheduler' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
java:app/ag-push/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
java:module/DeleteOldPushMessageInformationScheduler!org.jboss.aerogear.unifiedpush.service.metrics.DeleteOldPushMessageInformationScheduler
java:global/ag-push/DeleteOldPushMessageInformationScheduler
java:app/ag-push/DeleteOldPushMessageInformationScheduler
java:module/DeleteOldPushMessageInformationScheduler
2017-06-28 19:06:46,187 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'PushApplicationServiceImpl' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
java:app/ag-push/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
java:module/PushApplicationServiceImpl!org.jboss.aerogear.unifiedpush.service.PushApplicationService
java:global/ag-push/PushApplicationServiceImpl
java:app/ag-push/PushApplicationServiceImpl
java:module/PushApplicationServiceImpl
2017-06-28 19:06:46,187 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named
'ProxyConfiguration' in deployment unit 'deployment
"unifiedpush-server-wildfly.war"' are as follows:
java:global/ag-push/ProxyConfiguration!org.jboss.aerogear.unifiedpush.service.proxy.ProxyConfiguration
java:app/ag-push/ProxyConfiguration!org.jboss.aerogear.unifiedpush.service.proxy.ProxyConfiguration
java:module/ProxyConfiguration!org.jboss.aerogear.unifiedpush.service.proxy.ProxyConfiguration
java:global/ag-push/ProxyConfiguration
java:app/ag-push/ProxyConfiguration
java:module/ProxyConfiguration
2017-06-28 19:06:46,187 INFO [org.jboss.as.ejb3.deployment] (MSC service
thread 1-3) WFLYEJB0473: JNDI bindings for session bean named 'TokenLoader'
in deployment unit 'deployment "unifiedpush-server-wildfly.war"' are as
follows:
java:global/ag-push/TokenLoader!org.jboss.aerogear.unifiedpush.message.token.TokenLoader
java:app/ag-push/TokenLoader!org.jboss.aerogear.unifiedpush.message.token.TokenLoader
java:module/TokenLoader!org.jboss.aerogear.unifiedpush.message.token.TokenLoader
java:global/ag-push/TokenLoader
java:app/ag-push/TokenLoader
java:module/TokenLoader
2017-06-28 19:06:46,346 INFO
[org.keycloak.services.resources.KeycloakApplication] (ServerService Thread
Pool -- 94) Load config from
vfs:/content/unifiedpush-auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json
2017-06-28 19:06:46,944 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 96) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:06:46,945 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 96) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.
2017-06-28 19:06:47,116 INFO [org.jboss.weld.Version] (MSC service thread
1-8) WELD-000900: 2.3.5 (Final)
2017-06-28 19:06:47,275 INFO [org.jboss.as.ejb3] (MSC service thread 1-7)
WFLYEJB0042: Started message driven bean 'GCMPushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,276 INFO [org.jboss.as.ejb3] (MSC service thread 1-1)
WFLYEJB0042: Started message driven bean 'TriggerMetricsCollectionConsumer'
with 'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,277 INFO [org.jboss.as.ejb3] (MSC service thread 1-2)
WFLYEJB0042: Started message driven bean 'WNSPushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,277 INFO [org.jboss.as.ejb3] (MSC service thread 1-8)
WFLYEJB0042: Started message driven bean 'WNSTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,292 INFO [org.jboss.as.ejb3] (MSC service thread 1-6)
WFLYEJB0042: Started message driven bean 'APNsTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,295 INFO [org.jboss.as.ejb3] (MSC service thread 1-4)
WFLYEJB0042: Started message driven bean 'SimplePushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,295 INFO [org.jboss.as.ejb3] (MSC service thread 1-3)
WFLYEJB0042: Started message driven bean 'APNsPushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,296 INFO [org.jboss.as.ejb3] (MSC service thread 1-5)
WFLYEJB0042: Started message driven bean 'AdmTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,299 INFO [org.jboss.as.ejb3] (MSC service thread 1-1)
WFLYEJB0042: Started message driven bean 'GCMTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,317 INFO [org.jboss.as.ejb3] (MSC service thread 1-2)
WFLYEJB0042: Started message driven bean
'TriggerVariantMetricCollectionConsumer' with 'activemq-ra.rar' resource
adapter
2017-06-28 19:06:47,327 INFO [org.jboss.as.ejb3] (MSC service thread 1-7)
WFLYEJB0042: Started message driven bean 'MetricsProcessingStartedConsumer'
with 'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,329 INFO [org.jboss.as.ejb3] (MSC service thread 1-8)
WFLYEJB0042: Started message driven bean 'AdmPushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,332 INFO [org.jboss.as.ejb3] (MSC service thread 1-5)
WFLYEJB0042: Started message driven bean 'MPNSPushMessageConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,333 INFO [org.jboss.as.ejb3] (MSC service thread 1-3)
WFLYEJB0042: Started message driven bean 'SimplePushTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,335 INFO [org.jboss.as.ejb3] (MSC service thread 1-6)
WFLYEJB0042: Started message driven bean 'MPNSTokenBatchConsumer' with
'activemq-ra.rar' resource adapter
2017-06-28 19:06:47,908 INFO [org.jboss.as.jpa] (ServerService Thread Pool
-- 97) WFLYJPA0010: Starting Persistence Unit (phase 2 of 2) Service
'unifiedpush-server-wildfly.war#unifiedpush-default'
2017-06-28 19:06:47,919 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 96) WFLYCLINF0002: Started client-mappings
cache from ejb container
2017-06-28 19:06:48,643 INFO [org.hibernate.dialect.Dialect] (ServerService
Thread Pool -- 97) HHH000400: Using dialect:
org.jboss.aerogear.unifiedpush.jpa.Mysql5BitBooleanDialect
2017-06-28 19:06:48,650 WARN [org.hibernate.ejb.HibernatePersistence]
(ServerService Thread Pool -- 94) HHH015016: Encountered a deprecated
javax.persistence.spi.PersistenceProvider
[org.hibernate.ejb.HibernatePersistence]; use
[org.hibernate.jpa.HibernatePersistenceProvider] instead.
2017-06-28 19:06:48,665 WARN [org.hibernate.ejb.HibernatePersistence]
(ServerService Thread Pool -- 94) HHH015016: Encountered a deprecated
javax.persistence.spi.PersistenceProvider
[org.hibernate.ejb.HibernatePersistence]; use
[org.hibernate.jpa.HibernatePersistenceProvider] instead.
2017-06-28 19:06:48,665 WARN [org.hibernate.ejb.HibernatePersistence]
(ServerService Thread Pool -- 94) HHH015016: Encountered a deprecated
javax.persistence.spi.PersistenceProvider
[org.hibernate.ejb.HibernatePersistence]; use
[org.hibernate.jpa.HibernatePersistenceProvider] instead.
2017-06-28 19:06:48,768 INFO [org.hibernate.jpa.internal.util.LogHelper]
(ServerService Thread Pool -- 94) HHH000204: Processing PersistenceUnitInfo
[
name: keycloak-default
...]
2017-06-28 19:06:48,806 INFO
[org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread
Pool -- 97) Envers integration enabled? : true
2017-06-28 19:06:48,824 INFO [org.hibernate.dialect.Dialect] (ServerService
Thread Pool -- 94) HHH000400: Using dialect:
org.hibernate.dialect.MySQL5Dialect
2017-06-28 19:06:48,838 INFO
[org.hibernate.envers.boot.internal.EnversServiceImpl] (ServerService Thread
Pool -- 94) Envers integration enabled? : true
2017-06-28 19:06:49,147 WARN
[org.hibernate.cfg.annotations.reflection.JPAOverriddenAnnotationReader]
(ServerService Thread Pool -- 97) HHH000207: Property
org.jboss.aerogear.unifiedpush.api.iOSVariant.certificateData not found in
class but described in <mapping-file/> (possible typo error)
2017-06-28 19:06:49,153 WARN [org.hibernate.cfg.AnnotationBinder]
(ServerService Thread Pool -- 97) HHH000457: Joined inheritance hierarchy
[org.jboss.aerogear.unifiedpush.api.Variant] defined explicit
@DiscriminatorColumn. Legacy Hibernate behavior was to ignore the
@DiscriminatorColumn. However, as part of issue HHH-6911 we now apply the
explicit @DiscriminatorColumn. If you would prefer the legacy behavior,
enable the `hibernate.discriminator.ignore_explicit_for_joined` setting
(hibernate.discriminator.ignore_explicit_for_joined=true)
2017-06-28 19:06:51,653 INFO [org.hibernate.tool.hbm2ddl.SchemaValidator]
(ServerService Thread Pool -- 97) HHH000229: Running schema validator
2017-06-28 19:06:51,678 INFO
[org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl]
(ServerService Thread Pool -- 97) HHH000262: Table not found: adm_variant
2017-06-28 19:06:51,686 INFO
[org.hibernate.tool.schema.extract.internal.InformationExtractorJdbcDatabaseMetaDataImpl]
(ServerService Thread Pool -- 97) HHH000262: Table not found: adm_variant
2017-06-28 19:06:51,699 ERROR [org.jboss.msc.service.fail] (ServerService
Thread Pool -- 97) MSC000001: Failed to start service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
javax.persistence.PersistenceException: [PersistenceUnit:
unifiedpush-default] Unable to build Hibernate SessionFactory
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:179)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:121)
at
org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:667)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:193)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:748)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
unifiedpush-default] Unable to build Hibernate SessionFactory
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:954)
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:882)
at
org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:161)
... 7 more
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException:
Schema-validation: missing table [adm_variant]
at
org.hibernate.tool.schema.internal.SchemaValidatorImpl.validateTable(SchemaValidatorImpl.java:67)
at
org.hibernate.tool.schema.internal.SchemaValidatorImpl.doValidation(SchemaValidatorImpl.java:50)
at
org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:91)
at
org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:473)
at
org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:444)
at
org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:879)
... 9 more
2017-06-28 19:06:51,832 INFO
[org.hibernate.hql.internal.QueryTranslatorFactoryInitiator] (ServerService
Thread Pool -- 94) HHH000397: Using ASTQueryTranslatorFactory
2017-06-28 19:06:54,025 INFO
[org.keycloak.services.resources.KeycloakApplication] (ServerService Thread
Pool -- 94) Not importing realm aerogear from resource
/WEB-INF/ups-realm.json. It already exists.
2017-06-28 19:06:54,117 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002225: Deploying
javax.ws.rs.core.Application: class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,119 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002200: Adding class resource
org.keycloak.services.resources.ThemeResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,119 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002200: Adding class resource
org.keycloak.services.resources.WelcomeResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,119 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002200: Adding class resource
org.keycloak.services.resources.QRCodeResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,120 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002200: Adding class resource
org.keycloak.services.resources.JsResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,120 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002220: Adding singleton resource
org.keycloak.services.resources.RealmsResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,120 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002220: Adding singleton resource
org.keycloak.services.resources.admin.AdminRoot from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,121 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002220: Adding singleton resource
org.keycloak.services.resources.ServerVersionResource from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,121 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002210: Adding provider singleton
org.keycloak.services.resources.ModelExceptionMapper from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,121 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n]
(ServerService Thread Pool -- 94) RESTEASY002210: Adding provider singleton
org.keycloak.services.util.ObjectMapperResolver from Application class
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication
2017-06-28 19:06:54,231 INFO [org.wildfly.extension.undertow]
(ServerService Thread Pool -- 94) WFLYUT0021: Registered web context: /auth
2017-06-28 19:06:54,243 ERROR [org.jboss.as.controller.management-operation]
(DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed -
address: ([("deployment" => "unifiedpush-server-wildfly.war")]) -
failure
description: {
"WFLYCTL0080: Failed services" =>
{"jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\""
=> "org.jboss.msc.service.StartException in service
jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\":
javax.persistence.PersistenceException: [PersistenceUnit:
unifiedpush-default] Unable to build Hibernate SessionFactory
Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
unifiedpush-default] Unable to build Hibernate SessionFactory
Caused by: org.hibernate.tool.schema.spi.SchemaManagementException:
Schema-validation: missing table [adm_variant]"},
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.persistenceunit.\"unifiedpush-server-wildfly.war#unifiedpush-default\""],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
undefined
}
2017-06-28 19:06:54,308 ERROR [stderr] (DeploymentScanner-threads - 1)
java.io.IOException: Mount point not found
2017-06-28 19:06:54,309 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.LinuxFileStore.findMountEntry(LinuxFileStore.java:91)
2017-06-28 19:06:54,309 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.UnixFileStore.<init>(UnixFileStore.java:65)
2017-06-28 19:06:54,309 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.LinuxFileStore.<init>(LinuxFileStore.java:44)
2017-06-28 19:06:54,309 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:51)
2017-06-28 19:06:54,310 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.LinuxFileSystemProvider.getFileStore(LinuxFileSystemProvider.java:39)
2017-06-28 19:06:54,310 ERROR [stderr] (DeploymentScanner-threads - 1) at
sun.nio.fs.UnixFileSystemProvider.getFileStore(UnixFileSystemProvider.java:368)
2017-06-28 19:06:54,310 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.nio.file.Files.getFileStore(Files.java:1461)
2017-06-28 19:06:54,310 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.persistence.FilePersistenceUtils.getPosixAttributes(FilePersistenceUtils.java:124)
2017-06-28 19:06:54,322 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.persistence.FilePersistenceUtils.createTempFileWithAttributes(FilePersistenceUtils.java:112)
2017-06-28 19:06:54,323 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.persistence.FilePersistenceUtils.writeToTempFile(FilePersistenceUtils.java:99)
2017-06-28 19:06:54,323 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.persistence.ConfigurationFilePersistenceResource.doCommit(ConfigurationFilePersistenceResource.java:55)
2017-06-28 19:06:54,323 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.persistence.AbstractFilePersistenceResource.commit(AbstractFilePersistenceResource.java:58)
2017-06-28 19:06:54,334 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl$4.commit(ModelControllerImpl.java:789)
2017-06-28 19:06:54,334 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.AbstractOperationContext.executeDoneStage(AbstractOperationContext.java:743)
2017-06-28 19:06:54,335 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:680)
2017-06-28 19:06:54,336 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:370)
2017-06-28 19:06:54,336 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1329)
2017-06-28 19:06:54,336 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:400)
2017-06-28 19:06:54,336 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:222)
2017-06-28 19:06:54,336 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:756)
2017-06-28 19:06:54,337 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl$3$1$1.run(ModelControllerImpl.java:750)
2017-06-28 19:06:54,337 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.security.AccessController.doPrivileged(Native Method)
2017-06-28 19:06:54,337 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.as.controller.ModelControllerImpl$3$1.run(ModelControllerImpl.java:750)
2017-06-28 19:06:54,337 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
2017-06-28 19:06:54,338 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.FutureTask.run(FutureTask.java:266)
2017-06-28 19:06:54,338 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
2017-06-28 19:06:54,338 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
2017-06-28 19:06:54,338 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
2017-06-28 19:06:54,338 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
2017-06-28 19:06:54,339 ERROR [stderr] (DeploymentScanner-threads - 1) at
java.lang.Thread.run(Thread.java:748)
2017-06-28 19:06:54,339 ERROR [stderr] (DeploymentScanner-threads - 1) at
org.jboss.threads.JBossThread.run(JBossThread.java:320)
2017-06-28 19:06:54,347 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) WFLYSRV0010: Deployed
"unifiedpush-auth-server.war" (runtime-name :
"unifiedpush-auth-server.war")
2017-06-28 19:06:54,348 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) WFLYSRV0010: Deployed
"unifiedpush-server-wildfly.war" (runtime-name :
"unifiedpush-server-wildfly.war")
2017-06-28 19:06:54,349 INFO [org.jboss.as.controller]
(DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
javax.persistence.PersistenceException: [PersistenceUnit:
unifiedpush-default] Unable to build Hibernate SessionFactory
/
Summers Pittman wrote
On Fri, Jun 23, 2017 at 3:24 PM, Victor Silva <
vfbsilva@
> wrote:
> Folks I'm trying to deploy aerogear on Kubernetes. I'm using the wildfly
> image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
>
> As I have my databases outside of Kubernetes I've built the image as
> described here:
>
> docker build -t aerogear/unifiedpush-wildfly .
>
>
> With the following dockerfile:
> https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
>
> Unfortunately the dockerfile seems to point to an invalid tarball:
> RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
> $UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
>
> So I went to:
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/
> And got:
> https://github.com/aerogear/aerogear-unifiedpush-server/rele
> ases/download/1.2.0-beta.1/aerogear-unifiedpush-server-1.
> 2.0-beta.1-dist.tar.gz
>
> Then tried to deploy the wars getting a ton of errors:
> https://pastebin.com/G89f3EpM
>
> It seems that among other problems a mysql is being deployed on my server
> which makes no sense as I've provided the variables in standalone.xml:
>
>
<connection-url>
jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_TCP
> _ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPU
> SH_ENV_MYSQL_DATABASE}?useUnicode=true&characterE
> ncoding=UTF-8
</connection-url>
>
<user-name>
${env.UNIFIEDPUSH_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}
</password>
>
<connection-url>
jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_AD
> DR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_
> MYSQL_DATABASE}?useUnicode=true&characterEncoding=
> UTF-8
</connection-url>
>
<user-name>
${env.KEYCLOAK_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.KEYCLOAK_ENV_MYSQL_PASSWORD}
</password>
>
<core-environment>
>
</core-environment>
>
<recovery-environment socket-binding="txn-recovery-environment"
>
status-socket-binding="txn-status-manager"/>
>
<socket-binding name="txn-recovery-environment" port="4712"/>
>
>
> I'm not sure if the case is related to:
>
> https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-2117?
> filter=allopenissues
>
> Anyone had success deploying in kubernetes?
>
>
The Dockerfile points to a valid tarball; the Dockerfile also copies
resources from the local directory into the image in order to setup the
mysql connections.
You can *NOT* get a working image by copying the Dockerfile on dockerhub
to your machine and running `docker build` because you are missing the
local files. If you want to build a dockerfile you can either make your
own dockerfile that extends the UPS docker image, or you can clone
https://github.com/jboss-dockerfiles/aerogear, edit the files as you see
fit, and then build from that.
I don't think you need to though. All you need to do is set the
environment variables in the standalone.xml file you sent when you perform
your docker run.
Source : I am running UPS in a Kubernetes POD right now.
>
>
> _______________________________________________
> Aerogear-users mailing list
>
Aerogear-users@.jboss
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
Summers Pittman wrote
On Fri, Jun 23, 2017 at 3:24 PM, Victor Silva <
vfbsilva@
> wrote:
> Folks I'm trying to deploy aerogear on Kubernetes. I'm using the wildfly
> image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
>
> As I have my databases outside of Kubernetes I've built the image as
> described here:
>
> docker build -t aerogear/unifiedpush-wildfly .
>
>
> With the following dockerfile:
> https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
>
> Unfortunately the dockerfile seems to point to an invalid tarball:
> RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
> $UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
>
> So I went to:
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/
> And got:
> https://github.com/aerogear/aerogear-unifiedpush-server/rele
> ases/download/1.2.0-beta.1/aerogear-unifiedpush-server-1.
> 2.0-beta.1-dist.tar.gz
>
> Then tried to deploy the wars getting a ton of errors:
> https://pastebin.com/G89f3EpM
>
> It seems that among other problems a mysql is being deployed on my server
> which makes no sense as I've provided the variables in standalone.xml:
>
>
<connection-url>
jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_TCP
> _ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPU
> SH_ENV_MYSQL_DATABASE}?useUnicode=true&characterE
> ncoding=UTF-8
</connection-url>
>
<user-name>
${env.UNIFIEDPUSH_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}
</password>
>
<connection-url>
jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_AD
> DR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_
> MYSQL_DATABASE}?useUnicode=true&characterEncoding=
> UTF-8
</connection-url>
>
<user-name>
${env.KEYCLOAK_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.KEYCLOAK_ENV_MYSQL_PASSWORD}
</password>
>
<core-environment>
>
</core-environment>
>
<recovery-environment socket-binding="txn-recovery-environment"
>
status-socket-binding="txn-status-manager"/>
>
<socket-binding name="txn-recovery-environment" port="4712"/>
>
>
> I'm not sure if the case is related to:
>
> https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-2117?
> filter=allopenissues
>
> Anyone had success deploying in kubernetes?
>
>
The Dockerfile points to a valid tarball; the Dockerfile also copies
resources from the local directory into the image in order to setup the
mysql connections.
You can *NOT* get a working image by copying the Dockerfile on dockerhub
to your machine and running `docker build` because you are missing the
local files. If you want to build a dockerfile you can either make your
own dockerfile that extends the UPS docker image, or you can clone
https://github.com/jboss-dockerfiles/aerogear, edit the files as you see
fit, and then build from that.
I don't think you need to though. All you need to do is set the
environment variables in the standalone.xml file you sent when you perform
your docker run.
Source : I am running UPS in a Kubernetes POD right now.
>
>
> _______________________________________________
> Aerogear-users mailing list
>
Aerogear-users@.jboss
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
Summers Pittman wrote
On Fri, Jun 23, 2017 at 3:24 PM, Victor Silva <
vfbsilva@
> wrote:
> Folks I'm trying to deploy aerogear on Kubernetes. I'm using the wildfly
> image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
>
> As I have my databases outside of Kubernetes I've built the image as
> described here:
>
> docker build -t aerogear/unifiedpush-wildfly .
>
>
> With the following dockerfile:
> https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
>
> Unfortunately the dockerfile seems to point to an invalid tarball:
> RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
> $UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
>
> So I went to:
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/
> And got:
> https://github.com/aerogear/aerogear-unifiedpush-server/rele
> ases/download/1.2.0-beta.1/aerogear-unifiedpush-server-1.
> 2.0-beta.1-dist.tar.gz
>
> Then tried to deploy the wars getting a ton of errors:
> https://pastebin.com/G89f3EpM
>
> It seems that among other problems a mysql is being deployed on my server
> which makes no sense as I've provided the variables in standalone.xml:
>
>
<connection-url>
jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_TCP
> _ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPU
> SH_ENV_MYSQL_DATABASE}?useUnicode=true&characterE
> ncoding=UTF-8
</connection-url>
>
<user-name>
${env.UNIFIEDPUSH_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}
</password>
>
<connection-url>
jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_AD
> DR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_
> MYSQL_DATABASE}?useUnicode=true&characterEncoding=
> UTF-8
</connection-url>
>
<user-name>
${env.KEYCLOAK_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.KEYCLOAK_ENV_MYSQL_PASSWORD}
</password>
>
<core-environment>
>
</core-environment>
>
<recovery-environment socket-binding="txn-recovery-environment"
>
status-socket-binding="txn-status-manager"/>
>
<socket-binding name="txn-recovery-environment" port="4712"/>
>
>
> I'm not sure if the case is related to:
>
> https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-2117?
> filter=allopenissues
>
> Anyone had success deploying in kubernetes?
>
>
The Dockerfile points to a valid tarball; the Dockerfile also copies
resources from the local directory into the image in order to setup the
mysql connections.
You can *NOT* get a working image by copying the Dockerfile on dockerhub
to your machine and running `docker build` because you are missing the
local files. If you want to build a dockerfile you can either make your
own dockerfile that extends the UPS docker image, or you can clone
https://github.com/jboss-dockerfiles/aerogear, edit the files as you see
fit, and then build from that.
I don't think you need to though. All you need to do is set the
environment variables in the standalone.xml file you sent when you perform
your docker run.
Source : I am running UPS in a Kubernetes POD right now.
>
>
> _______________________________________________
> Aerogear-users mailing list
>
Aerogear-users@.jboss
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
Summers Pittman wrote
On Fri, Jun 23, 2017 at 3:24 PM, Victor Silva <
vfbsilva@
> wrote:
> Folks I'm trying to deploy aerogear on Kubernetes. I'm using the wildfly
> image from: https://hub.docker.com/r/aerogear/unifiedpush-wildfly/
>
> As I have my databases outside of Kubernetes I've built the image as
> described here:
>
> docker build -t aerogear/unifiedpush-wildfly .
>
>
> With the following dockerfile:
> https://hub.docker.com/r/aerogear/unifiedpush-wildfly/~/dockerfile/
>
> Unfortunately the dockerfile seems to point to an invalid tarball:
> RUN curl -L -o /opt/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/download/
> $UPSVER/aerogear-unifiedpush-server-$UPSVER-dist.tar.gz
>
> So I went to:
> https://github.com/aerogear/aerogear-unifiedpush-server/releases/
> And got:
> https://github.com/aerogear/aerogear-unifiedpush-server/rele
> ases/download/1.2.0-beta.1/aerogear-unifiedpush-server-1.
> 2.0-beta.1-dist.tar.gz
>
> Then tried to deploy the wars getting a ton of errors:
> https://pastebin.com/G89f3EpM
>
> It seems that among other problems a mysql is being deployed on my server
> which makes no sense as I've provided the variables in standalone.xml:
>
>
<connection-url>
jdbc:mysql://${env.UNIFIEDPUSH_PORT_3306_TCP
> _ADDR}:${env.UNIFIEDPUSH_PORT_3306_TCP_PORT}/${env.UNIFIEDPU
> SH_ENV_MYSQL_DATABASE}?useUnicode=true&characterE
> ncoding=UTF-8
</connection-url>
>
<user-name>
${env.UNIFIEDPUSH_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.UNIFIEDPUSH_ENV_MYSQL_PASSWORD}
</password>
>
<connection-url>
jdbc:mysql://${env.KEYCLOAK_PORT_3306_TCP_AD
> DR}:${env.KEYCLOAK_PORT_3306_TCP_PORT}/${env.KEYCLOAK_ENV_
> MYSQL_DATABASE}?useUnicode=true&characterEncoding=
> UTF-8
</connection-url>
>
<user-name>
${env.KEYCLOAK_ENV_MYSQL_USER}
</user-name>
>
<password>
${env.KEYCLOAK_ENV_MYSQL_PASSWORD}
</password>
>
<core-environment>
>
</core-environment>
>
<recovery-environment socket-binding="txn-recovery-environment"
>
status-socket-binding="txn-status-manager"/>
>
<socket-binding name="txn-recovery-environment" port="4712"/>
>
>
> I'm not sure if the case is related to:
>
> https://issues.jboss.org/projects/AGPUSH/issues/AGPUSH-2117?
> filter=allopenissues
>
> Anyone had success deploying in kubernetes?
>
>
The Dockerfile points to a valid tarball; the Dockerfile also copies
resources from the local directory into the image in order to setup the
mysql connections.
You can *NOT* get a working image by copying the Dockerfile on dockerhub
to your machine and running `docker build` because you are missing the
local files. If you want to build a dockerfile you can either make your
own dockerfile that extends the UPS docker image, or you can clone
https://github.com/jboss-dockerfiles/aerogear, edit the files as you see
fit, and then build from that.
I don't think you need to though. All you need to do is set the
environment variables in the standalone.xml file you sent when you perform
your docker run.
Source : I am running UPS in a Kubernetes POD right now.
>
>
> _______________________________________________
> Aerogear-users mailing list
>
Aerogear-users@.jboss
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deply...
Sent from the aerogear-users mailing list archive at Nabble.com.
1:17 p.m.
Summers, seems I was missing:
/./bin/ups-migrator update/
It was not clear from me when building the image I needed to perform this
step. Now I'm facing some SSL miss configuration, whenever I try to acess
/ag-push/ or /auth I get an SSL error:
/Exception handling request to /ag-push/: java.lang.RuntimeException: Unable
to resolve realm public key remotely/
the image ships with self-signed certs under:
*standalone/configuration/certs/*
I've ran certificate.sh providing my domain name and adding it to
standalone.xml still seems it is not importing my key. What am I missing?
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deply...
Sent from the aerogear-users mailing list archive at Nabble.com.
7:35 a.m.
On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva <vfbsilva(a)gmail.com> wrote:
Summers, seems I was missing:
/./bin/ups-migrator update/
It was not clear from me when building the image I needed to perform this
step. Now I'm facing some SSL miss configuration, whenever I try to acess
/ag-push/ or /auth I get an SSL error:
/Exception handling request to /ag-push/: java.lang.RuntimeException:
Unable
to resolve realm public key remotely/
the image ships with self-signed certs under:
*standalone/configuration/certs/*
I've ran certificate.sh providing my domain name and adding it to
standalone.xml still seems it is not importing my key. What am I missing?
Looping back in for posterity :
The ag-auth deployment isn't running in Kubernetes for some reason. The
error you are getting is from the auth system not deploying not from SSL.
The realm public key is a configuration option there. I've created
https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However
that issue may never get fixed because we are splitting up auth from the
deployed package "soon". Since auth will be deployed separately the
problem just won't exist any more.
Summers
--
View this message in context: http://aerogear-users.1116366.
n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-
kubernetes-with-wildfly-eap-tp1132p1135.html
Sent from the aerogear-users mailing list archive at Nabble.com.
_______________________________________________
Aerogear-users mailing list
Aerogear-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-users
10:43 a.m.
How can it work in jboss and do not work on kubernetes as containers are
"like" real machines? What is the difference in the code run inside of a
pod vs a real machine?
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deply...
Sent from the aerogear-users mailing list archive at Nabble.com.
12:42 p.m.
On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman <supittma(a)redhat.com> wrote:
On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva <vfbsilva(a)gmail.com> wrote:
> Summers, seems I was missing:
>
> /./bin/ups-migrator update/
>
> It was not clear from me when building the image I needed to perform this
> step. Now I'm facing some SSL miss configuration, whenever I try to acess
> /ag-push/ or /auth I get an SSL error:
>
> /Exception handling request to /ag-push/: java.lang.RuntimeException:
> Unable
> to resolve realm public key remotely/
>
>
> the image ships with self-signed certs under:
>
> *standalone/configuration/certs/*
>
> I've ran certificate.sh providing my domain name and adding it to
> standalone.xml still seems it is not importing my key. What am I missing?
>
>
>
Looping back in for posterity :
The ag-auth deployment isn't running in Kubernetes for some reason. The
error you are getting is from the auth system not deploying not from SSL.
The realm public key is a configuration option there. I've created
https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However
that issue may never get fixed because we are splitting up auth from the
deployed package "soon". Since auth will be deployed separately the
problem just won't exist any more.
So it looks like resetting my mySQL databases solved the problem I was
having and UPS deployed normally in kubernetes. I also switched to the
aerogear/unifiedpush-wildfly-dev image which may or may not have affected
the result as well.
Summers
>
>
>
> --
> View this message in context: http://aerogear-users.1116366.
> n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-k
> ubernetes-with-wildfly-eap-tp1132p1135.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
3:16 p.m.
Summers I circumvented the problem here. Seems the application doesn't like
my ingress:
/ingress.yaml
kind: Ingress
apiVersion: extensions/v1beta1
metadata:
annotations:
ingress.kubernetes.io/whitelist-source-range: 10.0.0.0/8,127.0.0.1/32
ingress.kubernetes.io/proxy-body-size: 1m
ingress.kubernetes.io/rewrite-target: /
ingress.kubernetes.io/ssl-redirect: "true"
name: aerogear
namespace: blah-v
spec:
rules:
- host:myhost.com
http:
paths:
- backend:
serviceName: aerogear
servicePort: 8080
path: /
tls:
- hosts:
- myhost.com/
I've ran the same image same databases without this ingress pointing a dns
directly to it. And it works. So now we know where is the problem still I
cannot grasp its reason.
Summers Pittman wrote
On Wed, Jul 5, 2017 at 8:35 AM, Summers Pittman <
supittma@
> wrote:
>
>
> On Mon, Jul 3, 2017 at 2:17 PM, vfbsilva <
vfbsilva@
> wrote:
>
>> Summers, seems I was missing:
>>
>> /./bin/ups-migrator update/
>>
>> It was not clear from me when building the image I needed to perform
>> this
>> step. Now I'm facing some SSL miss configuration, whenever I try to
>> acess
>> /ag-push/ or /auth I get an SSL error:
>>
>> /Exception handling request to /ag-push/: java.lang.RuntimeException:
>> Unable
>> to resolve realm public key remotely/
>>
>>
>> the image ships with self-signed certs under:
>>
>> *standalone/configuration/certs/*
>>
>> I've ran certificate.sh providing my domain name and adding it to
>> standalone.xml still seems it is not importing my key. What am I
>> missing?
>>
>>
>>
> Looping back in for posterity :
>
> The ag-auth deployment isn't running in Kubernetes for some reason. The
> error you are getting is from the auth system not deploying not from SSL.
> The realm public key is a configuration option there. I've created
> https://issues.jboss.org/browse/AEROGEAR-1747 with more details. However
> that issue may never get fixed because we are splitting up auth from the
> deployed package "soon". Since auth will be deployed separately the
> problem just won't exist any more.
>
>
So it looks like resetting my mySQL databases solved the problem I was
having and UPS deployed normally in kubernetes. I also switched to the
aerogear/unifiedpush-wildfly-dev image which may or may not have affected
the result as well.
> Summers
>
>
>>
>>
>>
>> --
>> View this message in context: http://aerogear-users.1116366.
>> n5.nabble.com/Aerogear-users-Problems-deplying-aerogear-in-k
>> ubernetes-with-wildfly-eap-tp1132p1135.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> Aerogear-users mailing list
>>
Aerogear-users@.jboss
>>>
>
>
_______________________________________________
Aerogear-users mailing list
Aerogear-users@.jboss
--
View this message in context:
http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Problems-deply...
Sent from the aerogear-users mailing list archive at Nabble.com.
2693
days inactive
2707
days old
aerogear-users@lists.jboss.org
7 comments
3 participants
participants (3)
-
Summers Pittman -
vfbsilva -
Victor Silva