AeroGear unified push notification
by Walto, David
Hi, I a new AeroGear unified push notification user. I am trying to create a simple push notification from a WebSphere java application.
I have created a couple of push notification classes to test (below) and both version I get the error:
SenderClient E Send did not succeed: java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 64
I have the following jars for this application.
[cid:image001.png@01D0EB25.5E1F6EE0]
[cid:image003.png@01D0EB25.C89EC4F0]
Any direction how to resolve this would be greatly appreciated.
Thanks in advance.
David Walto
Senior Application Engineer | EMR Engineering and Integration
Baystate Health | Information & Technology
1550 Main Street, Springfield, MA 01199 | p: 413-794-0627 | f: 413-794-5570
----------------------------------------------------------------------
Please view our annual report at http://baystatehealth.org/annualreport
CONFIDENTIALITY NOTICE: This e-mail communication and any attachments may contain confidential and privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please reply to the sender immediately or by telephone at 413-794-0000 and destroy all copies of this communication and any attachments. For further information regarding Baystate Health's privacy policy, please visit our Internet site at http://baystatehealth.org.
7 years, 2 months
Unified push server development environment setup
by mo
Hi,
I'm trying to run the unified push server in a development environment to
troubleshoot and understand it better. I'm wondering if there is any
documentation available to assist me with setting up development environment
for it. I've looked though documents under "Contributing to AeroGear", but
I am in need of a more detailed guide. I'd like to get to a point where I
can run unified push, break point, and inspect variables, and so on.
So far I've managed to run 'mvn test' successfully on the unified push
server source code. I use Eclipse, so I wanted to import the project. I
get quite a lot of errors in doing so.
I am troubleshooting version 1.0.2. We use OpenShift to deploy the aerogear
server.
I appreciate any help. Thank you.
Michi Oshima
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unified-push-server-developme...
Sent from the aerogear-users mailing list archive at Nabble.com.
8 years, 1 month
Failed to process phase PARSE of deployment “unifiedpush-server-wildfly.war”
by Sachidananda Patra
*I found the below error while unifiedpush-auth-server.war and
unifiedpush-server-wildfly.war deployed to
jboss-wildfly-10.1.0\standalone\deployments. >> Prerequisite
jboss-wildfly-10.1.0 server is running in below mode*
$ ./standalone.sh --server-config=standalone-full.xml15:54:10,589 ERROR
[org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to
start service jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153:
Failed to process phase PARSE of deployment "unifiedpush-server-wildfly.war"
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
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:745) Caused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml
at
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)
at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
... 5 more Caused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xml
at
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)
... 6 more Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[20,1] Message: Unexpected element
'{urn:jboss:messaging-deployment:1.0}messaging-deployment' at
org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) at
org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) at
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)
... 6
more-----------------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
-----------------------------------------------------------
--------------Details Console Logs : USER ~$ cd D:/jboss-wildfly-10.1.0/bin
USER /cygdrive/d/jboss-wildfly-10.1.0/bin$ ./standalone.sh
--server-config=standalone-full.xml=========================================================================
JBoss Bootstrap Environment JBOSS_HOME: D:\jboss-wildfly-10.1.0 JAVA:
/cygdrive/c/Program Files (x86)/Java/jdk1.8.0_31/bin/java JAVA_OPTS:
-server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m
-Djava.net.preferIPv4Stack=true
-Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
15:52:59,638 INFO [org.jboss.modules] (main) JBoss Modules version
1.5.2.Final15:52:59,857 INFO [org.jboss.msc] (main) JBoss MSC version
1.2.6.Final15:52:59,920 INFO [org.jboss.as] (MSC service thread 1-7)
WFLYSRV0049: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
starting15:53:02,124 INFO [org.jboss.as.server] (Controller Boot Thread)
WFLYSRV0039: Creating http management service using socket-binding
(management-http)15:53:02,172 INFO [org.xnio] (MSC service thread 1-5) XNIO
version 3.4.0.Final15:53:02,180 INFO [org.xnio.nio] (MSC service thread
1-5) XNIO NIO Implementation Version 3.4.0.Final15:53:02,232 INFO
[org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool
-- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver
(version 1.3)15:53:02,263 INFO [org.wildfly.extension.io] (ServerService
Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 8 core
threads with 64 task threads based on your 4 available
processors15:53:02,372 INFO [org.jboss.as.clustering.infinispan]
(ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan
subsystem.15:53:02,441 INFO [org.jboss.as.security] (ServerService Thread
Pool -- 59) WFLYSEC0002: Activating Security Subsystem15:53:02,446 INFO
[org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated
the following JSF Implementations: [main]15:53:02,480 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.15:53:02,501 INFO [org.jboss.as.security] (MSC service thread 1-6)
WFLYSEC0001: Current PicketBox version=4.9.6.Final15:53:02,510 INFO
[org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001:
Activating Naming Subsystem15:53:02,511 INFO [org.wildfly.iiop.openjdk]
(ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP
Subsystem15:53:02,521 INFO [org.jboss.as.connector] (MSC service thread
1-1) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar
1.3.4.Final)15:53:02,553 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-2) WFLYUT0003: Undertow 1.4.0.Final starting15:53:02,553 INFO
[org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1)
WFLYJCA0018: Started Driver service with driver-name = h215:53:02,581 INFO
[org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002:
Activating WebServices Extension15:53:02,606 INFO [org.jboss.as.naming]
(MSC service thread 1-2) WFLYNAM0003: Starting Naming Service15:53:02,606
INFO [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001:
Bound mail session [java:jboss/mail/Default]15:53:02,651 INFO
[org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version
4.0.21.Final15:53:02,756 INFO [org.jboss.as.ejb3] (MSC service thread 1-5)
WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size
of 64 (per class), which is derived from thread worker pool
sizing.15:53:02,757 INFO [org.jboss.as.ejb3] (MSC service thread 1-3)
WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of
16 (per class), which is derived from the number of CPUs on this
host.15:53:02,833 INFO [org.wildfly.extension.undertow] (ServerService
Thread Pool -- 61) WFLYUT0014: Creating file handler for path
'D:\jboss-wildfly-10.1.0/welcome-content' with options [directory-listing:
'false', follow-symlink: 'false', case-sensitive: 'true',
safe-symlink-paths: '[]']15:53:02,870 INFO [org.wildfly.extension.undertow]
(MSC service thread 1-4) WFLYUT0012: Started server
default-server.15:53:02,871 INFO [org.wildfly.extension.undertow] (MSC
service thread 1-4) WFLYUT0018: Host default-host starting15:53:03,041 INFO
[org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006:
Undertow HTTP listener default listening on 127.0.0.1:808015:53:03,528 WARN
[org.jboss.as.domain.management.security] (MSC service thread 1-5)
WFLYDM0111: Keystore
D:\jboss-wildfly-10.1.0\standalone\configuration\application.keystore not
found, it will be auto generated on first use with a self signed certificate
for host localhost15:53:03,553 INFO [org.jboss.as.server.deployment.scanner]
(MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for
directory D:\jboss-wildfly-10.1.0\standalone\deployments15:53:03,658 INFO
[org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6)
WFLYJCA0001: Bound data source
[java:jboss/datasources/ExampleDS]15:53:03,680 INFO
[org.wildfly.iiop.openjdk] (MSC service thread 1-1) WFLYIIOP0009: CORBA ORB
Service started15:53:03,688 INFO [org.wildfly.extension.messaging-activemq]
(MSC service thread 1-2) WFLYMSGAMQ0001: AIO wasn't located on this
platform, it will fall back to using pure Java NIO.15:53:03,773 INFO
[org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-5)
ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.4.Final15:53:03,834
INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 69) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,835 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 69) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,838 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 64) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,839 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 64) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,841 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 65) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,841 INFO
[org.infinispan.configuration.cache.EvictionConfigurationBuilder]
(ServerService Thread Pool -- 65) ISPN000152: Passivation configured without
an eviction policy being selected. Only manually evicted entities will be
passivated.15:53:03,923 INFO [org.wildfly.extension.undertow] (MSC service
thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on
127.0.0.1:844315:53:04,108 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221000: live Message Broker is starting
with configuration Broker Configuration
(clustered=false,journalDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\journal,bindingsDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\bindings,largeMessagesDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\largemessages,pagingDirectory=D:\jboss-wildfly-10.1.0\standalone\data\activemq\paging)15:53:04,185
INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool --
64) AMQ221013: Using NIO Journal15:53:04,853 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64)
AMQ221043: Protocol module found: [artemis-server]. Adding protocol support
for: CORE15:53:04,897 INFO [org.apache.activemq.artemis.core.server]
(ServerService Thread Pool -- 64) AMQ221043: Protocol module found:
[artemis-amqp-protocol]. Adding protocol support for: AMQP15:53:04,935 INFO
[org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052:
Starting JBossWS 5.1.5.Final (Apache CXF 3.1.6)15:53:04,968 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64)
AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding
protocol support for: HORNETQ15:53:04,971 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64)
AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol
support for: STOMP15:53:06,397 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-1)
WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol
handled by http-acceptor acceptor15:53:06,398 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-7)
WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol
handled by http-acceptor acceptor15:53:06,403 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-6)
WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol
handled by http-acceptor-throughput acceptor15:53:06,400 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-5)
WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol
handled by http-acceptor-throughput acceptor15:53:06,558 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64)
AMQ221007: Server is now live15:53:06,559 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 64)
AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.1.0.wildfly-017
[nodeID=cc5214e7-78d4-11e6-a2b4-79dfc4ded2f5]15:53:06,561 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69)
AMQ221003: trying to deploy queue jms.queue.ExpiryQueue15:53:06,706 INFO
[org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 66)
AMQ221003: trying to deploy queue jms.queue.DLQ15:53:06,733 INFO
[org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 65)
WFLYMSGAMQ0002: Bound messaging object to jndi name
java:/ConnectionFactory15:53:06,734 INFO
[org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68)
WFLYMSGAMQ0002: Bound messaging object to jndi name
java:jboss/exported/jms/RemoteConnectionFactory15:53:06,746 INFO
[org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007:
Registered connection factory java:/JmsXA15:53:06,836 INFO
[org.apache.activemq.artemis.ra] (MSC service thread 1-3) Resource adaptor
started15:53:06,836 INFO
[org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator]
(MSC service thread 1-3) IJ020002: Deployed:
file://RaActivatoractivemq-ra15:53:06,838 INFO
[org.jboss.as.connector.deployment] (MSC service thread 1-6) WFLYJCA0002:
Bound JCA ConnectionFactory [java:/JmsXA]15:53:06,838 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-2)
WFLYMSGAMQ0002: Bound messaging object to jndi name
java:jboss/DefaultJMSConnectionFactory15:53:07,164 INFO [org.jboss.as]
(Controller Boot Thread) WFLYSRV0060: Http management interface listening on
http://127.0.0.1:9990/management15:53:07,165 INFO [org.jboss.as]
(Controller Boot Thread) WFLYSRV0051: Admin console listening on
http://127.0.0.1:999015:53:07,166 INFO [org.jboss.as] (Controller Boot
Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
started in 7916ms - Started 370 of 615 services (408 services are lazy,
passive or on-demand) 15:54:03,799 INFO [org.jboss.as.repository]
(DeploymentScanner-threads - 1) WFLYDR0001: Content added at location
D:\jboss-wildfly-10.1.0\standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content
15:53:06,838 INFO [org.jboss.as.connector.deployment] (MSC service thread
1-6) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]15:53:06,838 INFO
[org.wildfly.extension.messaging-activemq] (MSC service thread 1-2)
WFLYMSGAMQ0002: Bound messaging object to jndi name
java:jboss/DefaultJMSConnectionFactory15:53:07,164 INFO [org.jboss.as]
(Controller Boot Thread) WFLYSRV0060: Http management interface listening on
http://127.0.0.1:9990/management15:53:07,165 INFO [org.jboss.as]
(Controller Boot Thread) WFLYSRV0051: Admin console listening on
http://127.0.0.1:999015:53:07,166 INFO [org.jboss.as] (Controller Boot
Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final)
started in 7916ms - Started 370 of 615 services (408 services are lazy,
passive or on-demand) 15:54:03,799 INFO [org.jboss.as.repository]
(DeploymentScanner-threads - 1) WFLYDR0001: Content added at location
D:\jboss-wildfly-10.1.0\standalone\data\content\e8\0ec98a850ae6460df834d03dc1c594dfa5c3e2\content15:54:03,949
INFO [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001:
Content added at location
D:\jboss-wildfly-10.1.0\standalone\data\content\03\3e00399f37e4aeec988109e2171565d5aedfb2\content15:54:03,967
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")15:54:03,967 INFO
[org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027:
Starting deployment of "unifiedpush-server-wildfly.war" (runtime-name:
"unifiedpush-server-wildfly.war")15:54:07,536 WARN
[org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0059: Class
Path entry lib/snakeyaml-1.13.jar in
/D:/jboss-wildfly-10.1.0/bin/content/unifiedpush-auth-server.war/WEB-INF/lib/liquibase-core-3.3.5.jar
does not point to a valid jar for a Class-Path reference.15:54:07,669 INFO
[org.jboss.as.jpa] (MSC service thread 1-4) WFLYJPA0002: Read
persistence.xml for keycloak-default15:54:08,413 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.15:54:08,414 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.15:54:08,415 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.15:54:10,579 INFO [org.jboss.as.jpa] (MSC service
thread 1-7) WFLYJPA0002: Read persistence.xml for
unifiedpush-default15:54:10,589 ERROR [org.jboss.msc.service.fail] (MSC
service thread 1-7) MSC000001: Failed to start service
jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE:
org.jboss.msc.service.StartException in service jboss.deployment.unit.
"unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153: Failed to process phase
PARSE of deployment "unifiedpush-server-wildfly.war"at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)at
org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)at
org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)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:745)Caused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xmlat
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)at
org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)...
5 moreCaused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\jboss-wildfly-10.1.0\standalone\tmp\vfs\temp\temp46e687319f527ed3\content-a52cb55da5bbb09d\WEB-INF\hornetq-jms.xmlat
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)...
6 moreCaused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[20,1]Message: Unexpected element
'{urn:jboss:messaging-deployment:1.0}messaging-deployment'at
org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)at
org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)at
org.wildfly.extension.messaging.activemq.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)...
6 more 15:54:11,627 INFO
[org.keycloak.services.resources.KeycloakApplication] (ServerService Thread
Pool -- 76) Load config from
vfs:/D:/jboss-wildfly-10.1.0/bin/content/unifiedpush-auth-server.war/WEB-INF/classes/META-INF/keycloak-server.json15:54:11,988
ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 76)
MSC000001: Failed to start service
jboss.undertow.deployment.default-server.default-host./auth:
org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth:
java.lang.RuntimeException: RESTEASY003325: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:85)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:745) at
org.jboss.threads.JBossThread.run(JBossThread.java:320)Caused by:
java.lang.RuntimeException: RESTEASY003325: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
at
org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:162)
at
org.jboss.resteasy.spi.ResteasyProviderFactory.createProviderInstance(ResteasyProviderFactory.java:2246)
at
org.jboss.resteasy.spi.ResteasyDeployment.createApplication(ResteasyDeployment.java:304)
at
org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:245)
at
org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:113)
at
org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36)
at
io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:117)
at
org.wildfly.extension.undertow.security.RunAsLifecycleInterceptor.init(RunAsLifecycleInterceptor.java:78)
at
io.undertow.servlet.core.LifecyleInterceptorInvocation.proceed(LifecyleInterceptorInvocation.java:103)
at
io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:250)
at
io.undertow.servlet.core.ManagedServlet.createServlet(ManagedServlet.java:133)
at
io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:546)
at
io.undertow.servlet.core.DeploymentManagerImpl$2.call(DeploymentManagerImpl.java:517)
at
io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
at
io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.api.LegacyThreadSetupActionWrapper$1.call(LegacyThreadSetupActionWrapper.java:44)
at
io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:559)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:101)
at
org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:82)
... 6 moreCaused by: java.lang.RuntimeException: Failed to connect to
database at
org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:184)
at
org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.lazyInit(DefaultJpaConnectionProviderFactory.java:130)
at
org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:35)
at
org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.create(DefaultJpaConnectionProviderFactory.java:25)
at
org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99)
at
org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:34)
at
org.keycloak.models.jpa.JpaRealmProviderFactory.create(JpaRealmProviderFactory.java:16)
at
org.keycloak.services.DefaultKeycloakSession.getProvider(DefaultKeycloakSession.java:99)
at
org.keycloak.models.cache.DefaultCacheRealmProvider.getDelegate(DefaultCacheRealmProvider.java:70)
at
org.keycloak.models.cache.DefaultCacheRealmProvider.getRealm(DefaultCacheRealmProvider.java:163)
at
org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:40)
at
org.keycloak.services.managers.ApplianceBootstrap.bootstrap(ApplianceBootstrap.java:31)
at
org.keycloak.services.resources.KeycloakApplication.setupDefaultRealm(KeycloakApplication.java:157)
at
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.setupDefaultRealm(UpsKeycloakApplication.java:40)
at
org.keycloak.services.resources.KeycloakApplication.(KeycloakApplication.java:87)
at
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication.(UpsKeycloakApplication.java:35)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at
org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:150)
... 29 moreCaused by: javax.naming.NameNotFoundException:
datasources/KeycloakDS -- service
jboss.naming.context.java.jboss.datasources.KeycloakDS at
org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:184)
at
org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:237)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
at javax.naming.InitialContext.lookup(InitialContext.java:417) at
javax.naming.InitialContext.lookup(InitialContext.java:417) at
org.keycloak.connections.jpa.DefaultJpaConnectionProviderFactory.getConnection(DefaultJpaConnectionProviderFactory.java:177)
... 49 more 15:54:11,994 ERROR
[org.jboss.as.controller.management-operation] (DeploymentScanner-threads -
1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" =>
"unifiedpush-auth-server.war")]) - failure description: { "WFLYCTL0080:
Failed services" =>
{"jboss.undertow.deployment.default-server.default-host./auth" =>
"org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth:
java.lang.RuntimeException: RESTEASY003325: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: java.lang.RuntimeException: RESTEASY003325: Failed to construct
public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
Caused by: java.lang.RuntimeException: Failed to connect to database
Caused by: javax.naming.NameNotFoundException: datasources/KeycloakDS --
service jboss.naming.context.java.jboss.datasources.KeycloakDS"},
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.undertow.deployment.default-server.default-host./auth"],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
undefined}15:54:11,994 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.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE" =>
"org.jboss.msc.service.StartException in service
jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE: WFLYSRV0153:
Failed to process phase PARSE of deployment
\"unifiedpush-server-wildfly.war\" Caused by:
org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\\jboss-wildfly-10.1.0\\standalone\\tmp\\vfs\\temp\\temp46e687319f527ed3\\content-a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException:
WFLYMSGAMQ0055: Could not parse file
D:\\jboss-wildfly-10.1.0\\standalone\\tmp\\vfs\\temp\\temp46e687319f527ed3\\content-a52cb55da5bbb09d\\WEB-INF\\hornetq-jms.xml
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[20,1]Message: Unexpected element
'{urn:jboss:messaging-deployment:1.0}messaging-deployment'"},
"WFLYCTL0412: Required services that are not installed:" =>
["jboss.deployment.unit.\"unifiedpush-server-wildfly.war\".PARSE"],
"WFLYCTL0180: Services with missing/unavailable dependencies" =>
undefined}15:54:12,053 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) WFLYSRV0010: Deployed
"unifiedpush-server-wildfly.war" (runtime-name :
"unifiedpush-server-wildfly.war")15:54:12,053 INFO [org.jboss.as.server]
(DeploymentScanner-threads - 1) WFLYSRV0010: Deployed
"unifiedpush-auth-server.war" (runtime-name :
"unifiedpush-auth-server.war")15:54:12,053 INFO [org.jboss.as.controller]
(DeploymentScanner-threads - 1) WFLYCTL0183: Service status
reportWFLYCTL0186: Services which failed to start: service
jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE:
org.jboss.msc.service.StartException in service
jboss.deployment.unit."unifiedpush-server-wildfly.war".PARSE: WFLYSRV0153:
Failed to process phase PARSE of deployment
"unifiedpush-server-wildfly.war"service
jboss.undertow.deployment.default-server.default-host./auth:
org.jboss.msc.service.StartException in service
jboss.undertow.deployment.default-server.default-host./auth:
java.lang.RuntimeException: RESTEASY003325: Failed to construct public
org.jboss.aerogear.unifiedpush.keycloak.UpsKeycloakApplication(javax.servlet.ServletContext,org.jboss.resteasy.core.Dispatcher)
--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Failed-to-process-phase-PARSE...
Sent from the aerogear-users mailing list archive at Nabble.com.
8 years, 1 month
aerogear-cordova-push 3.0.1
by Erik Jan de Wit
Hi,
We fixed a couple of bug on aerogear-cordova-push and would like to release
it. The 3.0.x branch is ready for testing
--
Cheers,
Erik Jan
8 years, 2 months
categories have been hijacked
by Kelvin Lunsford
Setting "categories" in the push payload was working for android and ios in cordova push plugin 1.1.1.
For version 2.0.2 "categories" only works for ios.
It looks like "categories" is being hijacked in android for a GCM feature called "topics".
I liked "categories". I was using it. Now it's gone. GCM topics is not a drop-in replacement. It's not the same thing.
New features should get new names and new commands.
- Kelvin
8 years, 2 months
Aerogear Plugin issue - Notification opened metric
by Prasad, Ganesh
Hello
We were testing the usage of notification opened metric and our application is Cordova based
pushConfig: {
'pushServerURL': 'url',
'alias': 'app name',
'sendMetricInfo': 'true',
Below are the observation
1. Clicking on the push notification while the app is in the background increments the opened count
2. If the app is completely shut down, on receiving push notification :
* Clicking on the push notification starts the app but does not increment the opened count
Is there any fix available for #2 ?
Thanks
ganesh
8 years, 2 months
All requests to server are hanging, never completing
by Yoann Archambault
Hello,
Our deployment of Aerogear in production has stopped responding to requests
on the ag-push.war or auth.war applications (wildfly admin console works
fine). I can only see one type of stack trace when i do a kill -3 (see
bellow). So far i've tried restarting wildfly, undeploying/deploying both
WARs, rebooting the server and nothing has had any effect. There has been
no change in configuration or code for a few weeks now and i've had a
couple of service restarts without a issue. I'm using UPS 1.1.3-final on a
CentOS server.
Also i'm not sure if its relevant but since the start we've been using a
slightly modified version of UPS which we built with maven. The only change
is using the push_message_info.client_identifier for our own purpose. Its
basically a one line code change.
"default task-62" #221 prio=5 os_prio=0 tid=0x00007fc7901a9000 nid=0x32c4
runnable [0x00007fc6eb7f5000]
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
at java.net.SocketInputStream.read(SocketInputStream.java:170)
at java.net.SocketInputStream.read(SocketInputStream.java:141)
at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
at sun.security.ssl.InputRecord.read(InputRecord.java:503)
at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
- locked <0x00000006c5abff60> (a java.lang.Object)
at sun.security.ssl.SSLSocketImpl.readDataRecord(
SSLSocketImpl.java:930)
at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
- locked <0x00000006c5ac0020> (a sun.security.ssl.AppInputStream)
at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(
AbstractSessionInputBuffer.java:160)
at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(
SocketInputBuffer.java:84)
at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(
AbstractSessionInputBuffer.java:273)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
DefaultHttpResponseParser.java:140)
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(
DefaultHttpResponseParser.java:57)
at org.apache.http.impl.io.AbstractMessageParser.parse(
AbstractMessageParser.java:260)
at org.apache.http.impl.AbstractHttpClientConnection.
receiveResponseHeader(AbstractHttpClientConnection.java:283)
at org.apache.http.impl.conn.DefaultClientConnection.
receiveResponseHeader(DefaultClientConnection.java:251)
at org.apache.http.impl.conn.AbstractClientConnAdapter.
receiveResponseHeader(AbstractClientConnAdapter.java:223)
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(
HttpRequestExecutor.java:271)
at org.apache.http.protocol.HttpRequestExecutor.execute(
HttpRequestExecutor.java:123)
at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(
DefaultRequestDirector.java:685)
at org.apache.http.impl.client.DefaultRequestDirector.execute(
DefaultRequestDirector.java:487)
at org.apache.http.impl.client.AbstractHttpClient.doExecute(
AbstractHttpClient.java:863)
at org.apache.http.impl.client.CloseableHttpClient.execute(
CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(
CloseableHttpClient.java:106)
at org.apache.http.impl.client.CloseableHttpClient.execute(
CloseableHttpClient.java:57)
at org.keycloak.adapters.AdapterDeploymentContext.resolveRealmKey(
AdapterDeploymentContext.java:105)
at org.keycloak.adapters.AdapterDeploymentContext.resolveDeployment(
AdapterDeploymentContext.java:83)
at org.keycloak.adapters.PreAuthActionsHandler.preflightCors(
PreAuthActionsHandler.java:71)
at org.keycloak.adapters.PreAuthActionsHandler.handleRequest(
PreAuthActionsHandler.java:47)
at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.
handleRequest(ServletPreAuthActionsHandler.java:68)
at io.undertow.server.handlers.PredicateHandler.handleRequest(
PredicateHandler.java:43)
at io.undertow.servlet.handlers.ServletInitialHandler.
handleFirstRequest(ServletInitialHandler.java:282)
at io.undertow.servlet.handlers.ServletInitialHandler.
dispatchRequest(ServletInitialHandler.java:261)
at io.undertow.servlet.handlers.ServletInitialHandler.access$
000(ServletInitialHandler.java:80)
at io.undertow.servlet.handlers.ServletInitialHandler$1.
handleRequest(ServletInitialHandler.java:172)
at io.undertow.server.Connectors.executeRootHandler(Connectors.
java:199)
at io.undertow.server.HttpServerExchange$1.run(
HttpServerExchange.java:774)
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:745)
I've been trying to solve this for 2 days without success, so at this point
any help would be greatly appreciated!
--
Yoann
8 years, 2 months
Using aerogear-cordova-push 3.0.0 - Success callback fires only once in IOS
by Jesús Martín González
Hello,
I am using aerogear-cordova-push 3.0.0 in my cordova app, everything work
fine in android but in iOS the success callback fires only once, for
example if i try to change categories, them change but succces callback is
not invoked.
I have seen that in AGCORDOVA-125 you resolved it for Android
https://issues.jboss.org/browse/AGCORDOVA-125
Can you help me, to solve it on iOS? I think it is an important bug.
Its easy to reproduce, just call push.register two times, the first will
work and the second wont (Working with of iOS-4.2.1 and cordova 6.2.0)
Thank you in advance!
--
Jesús Martín Gonzalez
Tel: +34 654420529
8 years, 2 months
