[aerogear-dev] Problem on migrating to 1.1.0-Final

[Matthias Wessendorf]

Hwllo,

I see "as7" - what version of JBoss are you using? We don't really support
the JBoss7.1 server anymore. We have support for WildFly 8 and 9. Bsides
that we have EAP_6.4.0 as one of the supported servers

On Tue, Nov 24, 2015 at 2:08 PM, Javornik, Romain <
Romain.Javornik at saint-gobain.com> wrote:

> Hello Matthias,
>
>
>
> I try to do a step by step like you suggest.
>
>
>
> The migration of the database between 1.0.2 and 1.03 worked perfectly, but
> I can’t deploy  unifiedpush-server-as7.war
>
>
>
> 2015-11-24 11:45:45,457 INFO  [org.jboss.as.server.deployment] (MSC
> service thread 1-1) JBAS015877: Stopped deployment
> unifiedpush-server-as7.war in 20ms
>
> 2015-11-24 11:45:45,458 ERROR [org.jboss.as.server.deployment.scanner]
> (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed
> and was rolled back. Steps that failed:" => {"Operation step-2" =>
> {"JBAS014671: Failed services" =>
> {"jboss.persistenceunit.\"unifiedpush-server as7.war#unifiedpush-default\""
> => "org.jboss.msc.service.StartException in service
> jboss.persistenceunit.\"unifiedpush-server-as7.war#unifiedpush-default\":
> javax.persistence.Persisten
>
> ceException: [PersistenceUnit: unifiedpush-default] Unable to build
> EntityManagerFactory
>
>     Caused by: javax.persistence.PersistenceException: [PersistenceUnit:
> unifiedpush-default] Unable to build EntityManagerFactory
>
>     Caused by: org.hibernate.HibernateException: Wrong column type in
> unifiedpush_tmp.VariantMetricInformation for column deliveryStatus. Found:
> bit, expected: boolean"
>
>
>
> I’m currently trying to make some change in the type of the column
> deliveryStatus to see if it make a difference.
>
>
>
> Best Regards,
>
> Romain
>
>
>
> *De :* aerogear-dev-bounces at lists.jboss.org [mailto:
> aerogear-dev-bounces at lists.jboss.org] *De l**a part de* Matthias
> Wessendorf
> *Envoyé :* jeudi 19 novembre 2015 15:25
> *À :* AeroGear Developer Mailing List
> *Objet :* Re: [aerogear-dev] Problem on migrating to 1.1.0-Final
>
>
>
> Hi Romain,
>
>
>
> unfortunately I don't think the 1.0.2 -> 1.1.0.Final really works. I think
> you have to go to 1.0.3 first, before being able to run the migration
> towards 1.1.0.Final.
>
>
>
>
>
>
>
>
>
> On Thu, Nov 19, 2015 at 11:22 AM, Javornik, Romain <
> Romain.Javornik at saint-gobain.com> wrote:
>
> Hello,
>
>
>
> I don’t really know if this is the right email address for asking question
> but I give it a try, please redirect me if I’m wrong !
>
>
>
>
>
>
>
>
>
> ------ Problem in the UnifiedPush Server User Guide ------
>
>
>
> Before explaining my problem I want to tell you that something isn’t clear
> enough from my point of view in your migration guide (
> https://aerogear.org/docs/unifiedpush/ups_userguide/index/#migration-guide
> ).
>
>
>
> On the part where you explain the database migration for mysql you write :
>             MySQL
>
> Inside of the extracted zip file, there is a
> liquibase-mysql-example.properties, copy that to liquibase.properties.
>
> cp liquibase-mysql-example.properties liquibase.properties
>
> Once done, you need to edit the new file to match your database name and
> credentials.
>
>
>
> The problem with this is that you can’t choose the version you want to
> upgrade to.
>
> Since I have “changeLogFile=liquibase/master.xml” in my
> liquidbase.properties, the only upgrade I was able to make was to the
> 1.0.0-Final and I’m on the 1.0.2.
>
> I had to open the ups-migrator.jar (wich wasn’t really userfriendly) to
> see what was my option. And then I was able to go the version I want
> (exemple -> “changeLogFile=liquibase/1.1.0-Final/releasechanges.xml”)
>
>
>
> To conclude I think that just a small explanation in the migration guide
> will make everything more clear.
>
>
>
>
>
>
>
>
>
>
>
> ------ My migration problem ------
>
>
>
> I’m currently using AerogearPush Server 1.0.2 and I want to go to the
> 1.1.0-Final version.
>
>
>
> I download the last package (1.1.0-Final) on this page
> https://aerogear.org/getstarted/downloads
>
>
>
> Like explain above I had some trouble make it work to move to the version
> I wanted.
>
> Right now in 1.0.2 I can use the Migrator Tool to make sure that my 1.0.2
> Mysql database is good and to upgrade it to 1.0.3.
>
>
>
> But I can’t go the 1.1.0-Final, I join to this email the error I get from
> the Migrator Tool.
>
>
>
> Can you please tell me where the problem might come from or if you have
> any solution ?
>
>
>
>
>
>
>
> Best Regards,
>
> Romain
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
>
>
> --
>
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20151124/6c0df24f/attachment.html