Description of problem: create an aerogear-push-0.8.0 app,then check server.log, some service can't be start normally eg: 2013/07/24 01:12:44,557 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.netty.simplepush-server: org.jboss.msc.service.StartException in service jboss.netty.simplepush-server: [PersistenceUnit: SimplePushPU] Unable to build EntityManagerFactory 2013/07/24 01:12:47,911 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.1.Final "Brontes" started (with errors) in 19705ms - Started 174 of 294 services (1 services failed or missing dependencies, 115 services are passive or on-demand) detail log has attached. Version-Release number of selected component (if applicable): fork_ami_aerogear_push_709 How reproducible: Always Steps to Reproduce: 1. create an aerogear-push-0.8.0 rhc app create ap1 aerogear-push-0.8.0 mysql-5.1 2. check the server.log Actual results: some service can't be started normally pls. refer to the detail log in attachment Expected results: all the service can be started successfully without any error
Created attachment 777646 [details] detail log
I haven't been able to reproduce this using a devenv instance based on the latest fork AMI (fork_ami_aerogear_push_709). In particular, all of the services start successfully for me. However, this could be a timing issue, i.e., it could be that the datasource service sometimes isn't started when the Netty service starts up. Dan is looking into this (see https://issues.jboss.org/browse/AGPUSH-213).
A dependency on jpa has been added to the Netty module (see https://issues.jboss.org/browse/AGPUSH-213). This bug should no longer occur once a new fork AMI has been created.
A new fork AMI that contains the fix for this issue is now available for testing.
test on for_ami_pmorie_736, issue still can be reproduced. server.log has attached. pls. check it. thanks.
Created attachment 781038 [details] 0731_server.log (fork_ami_pmorie_736)
A dependency on the datasource has been added to the netty subsystem. A new fork AMI that contains this fix is currently being built.
The new fork AMI is still not ready for test. will re-test it once the new fork ami is ready. Thanks.
The new fork AMI is now ready: fork_ami_aerogear_push_748
test on fork_ami_aerogear_push_748 still show some error in server.log, pls. refer to the attachment. Thanks.
Created attachment 783639 [details] fork_ami_aerogear_push_748 test log
Could you please also attach boot.log for the latest run? We have added a log statement at info level when we add the dependency to the configured data source. I don't see this in the log file attached and I like to verify. Thanks
Created attachment 783662 [details] boot log
Thanks for attaching the boot.log. I can see the log statement so this looks correct. It has been difficult for us to reproduce this issue and the only way has been to set breakpoints in the code. Obviously adding the dependency is not working and I'll look into this. Thanks
A dependency on the datasource being bound in JNDI (as opposed to a dependency on the datasource service itself) has been added to the cartridge (as Dan described in https://issues.jboss.org/browse/AGPUSH-213?focusedCommentId=12795533&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12795533). This bug should hopefully no longer occur once the new fork AMI is ready.
The new fork AMI is now ready for testing: fork_ami_aerogear_push_758
test on fork_ami_aerogear_push_758, most of the previous error in server.log disappeared, but seems still show ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate], (and i tried to create jbossas-7 app, there is no such error shown with jbossas-7 app.) You can refer detail log in attachment. thanks.
Created attachment 786002 [details] fork_ami_aerogear_push_758 log
Hello Yan, the ERROR is not a stopper, however a fix has been created. Please see this JIRA ticket for more details: https://issues.jboss.org/browse/AGPUSH-273
The new fork AMI is now ready for testing: fork_ami_aerogear_push_809
test on fork_ami_aerogear_push_809 no error shown when creating aerogear push server application. move the bug to verified.