tekir 4 depoyment issue , please help me to solve this issue

[masumcse1]

19-06-20 21:14:02,700 INFO [com.ozguryazilim.telve.messagebus.TelveCamelContext] (MSC service thread 1-5) Total 23 routes, of which 23 are started
2019-06-20 21:14:02,703 INFO [com.ozguryazilim.telve.messagebus.TelveCamelContext] (MSC service thread 1-5) Apache Camel 2.22.2 (CamelContext: telve) started in 2.249 seconds
2019-06-20 21:14:03,983 INFO [liquibase.integration.cdi.CDILiquibase] (MSC service thread 1-5) Booting Liquibase 3.5.4
2019-06-20 21:14:04,955 INFO [liquibase] (MSC service thread 1-5) Successfully acquired change log lock
2019-06-20 21:14:08,307 INFO [liquibase] (MSC service thread 1-5) Creating database history table with name: employeeinfo.DATABASECHANGELOG
2019-06-20 21:14:08,401 INFO [liquibase] (MSC service thread 1-5) Reading from employeeinfo.DATABASECHANGELOG
2019-06-20 21:14:08,995 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,995 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,996 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,996 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,996 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,997 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,997 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,998 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,998 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,999 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:08,999 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,000 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,000 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,000 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,001 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,001 WARN [liquibase] (MSC service thread 1-5) modifyDataType will lose primary key/autoincrement/not null settings for mysql. Use and re-specify all configuration if this is the case
2019-06-20 21:14:09,057 INFO [liquibase] (MSC service thread 1-5) Successfully released change log lock
2019-06-20 21:14:09,075 INFO [com.ozguryazilim.telve.suggestion.SuggestionGroupRegistery] (MSC service thread 1-5) Registered SuggestionCode : userGroup, false
2019-06-20 21:14:09,115 INFO [com.ozguryazilim.telve.suggestion.SuggestionGroupRegistery] (MSC service thread 1-5) Registered SuggestionCode : Genel, false
2019-06-20 21:14:09,160 ERROR [com.ozguryazilim.telve.attachment.modeshape.ModeShapeRepositoryFactory] (MSC service thread 1-5) !!! ModeShape Starter on Development Mode !!!
2019-06-20 21:14:09,248 INFO [org.modeshape.common.logging.LogFactory] (MSC service thread 1-5) Log4j located in the classpath. It will be used by ModeShape for logging.
2019-06-20 21:14:09,366 INFO [com.ozguryazilim.telve.attachment.modeshape.ModeShapeRepositoryFactory] (MSC service thread 1-5) ModeShape Engine Started
2019-06-20 21:14:09,393 INFO [org.modeshape.jcr.JcrRepository] (MSC service thread 1-5) ModeShape version 5.4.0.Final
2019-06-20 21:14:09,485 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."Tekir-Web.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."Tekir-Web.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1730)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1558)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-000049: Unable to invoke public void liquibase.integration.cdi.CDILiquibase.onStartup() on liquibase.integration.cdi.CDILiquibase@17f9745
at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:38)
at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:28)
at org.jboss.weld.bootstrap.WeldStartup.validateBeans(WeldStartup.java:505)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:93)
at org.jboss.as.weld.WeldStartService.start(WeldStartService.java:98)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1738)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1700)
... 6 more
Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void liquibase.integration.cdi.CDILiquibase.onStartup() on liquibase.integration.cdi.CDILiquibase@17f9745
at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:85)
at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.postConstruct(DefaultLifecycleCallbackInvoker.java:66)
at org.jboss.weld.injection.producer.BasicInjectionTarget.postConstruct(BasicInjectionTarget.java:122)
at liquibase.integration.cdi.CDIBootstrap$1.create(CDIBootstrap.java:95)
at liquibase.integration.cdi.CDIBootstrap$1.create(CDIBootstrap.java:38)
at org.jboss.weld.contexts.AbstractContext.get(AbstractContext.java:96)
at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:100)
at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:102)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.getInstance(ProxyMethodHandler.java:131)
at liquibase.integration.cdi.CDILiquibase$Proxy$_$$_WeldClientProxy.toString(Unknown Source)
at liquibase.integration.cdi.CDIBootstrap.afterDeploymentValidation(CDIBootstrap.java:111)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:95)
at org.jboss.weld.injection.MethodInvocationStrategy$SpecialParamPlusBeanManagerStrategy.invoke(MethodInvocationStrategy.java:144)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:330)
at org.jboss.weld.event.ExtensionObserverMethodImpl.sendEvent(ExtensionObserverMethodImpl.java:123)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:308)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:286)
at javax.enterprise.inject.spi.ObserverMethod.notify(ObserverMethod.java:124)
at org.jboss.weld.util.Observers.notify(Observers.java:166)
at org.jboss.weld.event.ObserverNotifier.notifySyncObservers(ObserverNotifier.java:285)
at org.jboss.weld.event.ObserverNotifier.notify(ObserverNotifier.java:273)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:177)
at org.jboss.weld.event.ObserverNotifier.fireEvent(ObserverNotifier.java:171)
at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:53)
at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:35)
... 12 more
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jboss.weld.injection.producer.DefaultLifecycleCallbackInvoker.invokeMethods(DefaultLifecycleCallbackInvoker.java:83)
... 41 more
Caused by: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.ValidationFailedException: Validation Failed:
2 changes have validation failures
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-3::ercan
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-4::ercan

at liquibase.integration.cdi.CDILiquibase.onStartup(CDILiquibase.java:118)
... 46 more

Caused by: liquibase.exception.ValidationFailedException: Validation Failed:
2 changes have validation failures
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-3::ercan
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-4::ercan

at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:266)
at liquibase.Liquibase.update(Liquibase.java:210)
at liquibase.Liquibase.update(Liquibase.java:192)
at liquibase.integration.cdi.CDILiquibase.performUpdate(CDILiquibase.java:129)
at liquibase.integration.cdi.CDILiquibase.onStartup(CDILiquibase.java:116)
... 46 more

2019-06-20 21:14:09,510 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "Tekir-Web.war")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit."Tekir-Web.war".WeldStartService" => "Failed to start service
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-000049: Unable to invoke public void liquibase.integration.cdi.CDILiquibase.onStartup() on liquibase.integration.cdi.CDILiquibase@17f9745
Caused by: org.jboss.weld.exceptions.WeldException: WELD-000049: Unable to invoke public void liquibase.integration.cdi.CDILiquibase.onStartup() on liquibase.integration.cdi.CDILiquibase@17f9745
Caused by: java.lang.reflect.InvocationTargetException
Caused by: liquibase.exception.UnexpectedLiquibaseException: liquibase.exception.ValidationFailedException: Validation Failed:
2 changes have validation failures
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-3::ercan
columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-4::ercan

Caused by: liquibase.exception.ValidationFailedException: Validation Failed:
 2 changes have validation failures
      columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-3::ercan
      columnDataType is required for renameColumn on mysql, liquibase/migration/tekir-recruit-4.0.0.xml::1540279012-4::ercan

"}}
2019-06-20 21:14:09,885 INFO [org.jboss.as.server] (ServerService Thread Pool -- 43) WFLYSRV0010: Deployed "Tekir-Web.war" (runtime-name : "Tekir-Web.war")
2019-06-20 21:14:09,898 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0186: Services which failed to start: service jboss.deployment.unit."Tekir-Web.war".WeldStartService: Failed to start service
WFLYCTL0448: 88 additional services are down due to their dependencies being missing or failed
2019-06-20 21:14:10,062 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
2019-06-20 21:14:10,065 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
2019-06-20 21:14:10,065 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
2019-06-20 21:14:10,066 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started (with errors) in 86592ms - Started 608 of 872 services (93 services failed or missing dependencies, 331 services are lazy, passive or on-demand)