7:14 p.m.
Thanks for your reply. Yes your right the reason why we have choose
wildfly9.0.2.Final is, currently our application has been devloped with
jdk1.7.0_72
On Tue, May 29, 2018 at 3:36 PM, Matej Novotny <manovotn(a)redhat.com> wrote:
Hello,
while upgrading from AS 7.1 to WFLY 9, you updated Weld from 1.x to 2.x
and I bet there was also major upgrade in Jersey.
You might want to check the migration notes of those two and then probably
read up on jersey integration with CDI/Weld.
Weld changes don't seem to be causing this though.
If I were you I would try and identify the Jersey versions in both servers
and go from there.
One last thing - note that you are basically upgrading from pre-historic
version to outdated one (3y old); currently, there is WildFly 12 as the
latest release.
As you will likely face many migration difficulties, it may be worth it to
instead look into migration to latest WildFly right away.
Though I understand it may not be possible in your case for various
reasons.
Regards
Matej
----- Original Message -----
> From: "wildflyuser" <elayaraja.s(a)gmail.com>
> To: wildfly-dev(a)lists.jboss.org
> Sent: Tuesday, May 29, 2018 10:51:25 AM
> Subject: [wildfly-dev] wildfly-9.0.2.Final: Failed to start service
jboss.deployment.unit."app.ear".WeldStartService:
>
> Not sure what we are missing, getting below error. Upraded from
> jboss-as-7.1.1.Final to wildfly-9.0.2.Final
>
>
>
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001:
> Failed to start service jboss.deployment.unit."app.
ear".WeldStartService:
> org.jboss.msc.service.StartException in service
> jboss.deployment.unit."app.ear".WeldStartService: Failed to start
service
>
> at
> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(
ServiceControllerImpl.java:1904)
>
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1145)
>
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:615)
>
> at java.lang.Thread.run(Thread.java:745)
>
> Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001408:
> Unsatisfied dependencies for type ServiceLocator with qualifiers @Default
>
> at injection point [UnbackedAnnotatedField] @Inject private
> org.glassfish.jersey.server.mvc.internal.ViewableMessageBodyWriter.
serviceLocator
>
> at
> org.glassfish.jersey.server.mvc.internal.ViewableMessageBodyWriter.
serviceLocator(ViewableMessageBodyWriter.java:0)
>
>
>
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeplo
ymentProblems(Validator.java:359)
>
> at
> org.jboss.weld.bootstrap.Validator.validateInjectionPoint(
Validator.java:281)
>
> at
> org.jboss.weld.bootstrap.Validator.validateGeneralBean(
Validator.java:134)
>
> at org.jboss.weld.bootstrap.Validator.validateRIBean(
Validator.java:155)
>
> at org.jboss.weld.bootstrap.Validator.validateBean(
Validator.java:518)
>
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(
ConcurrentValidator.java:68)
>
> at
> org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(
ConcurrentValidator.java:66)
>
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(
IterativeWorkerTaskFactory.java:60)
>
> at
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(
IterativeWorkerTaskFactory.java:53)
>
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>
>
>
> --
> Sent from: http://wildfly-development.1055759.n5.nabble.com/
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>