Hello Nikolai, Based on the hint provided on the thread, I did simple File search for "jetty" and found that in Ignite/libs directory, I have connector-layer folder and it have Jetty Server jars with different version "jetty-util-7.3.0.v20110203.jar". Removing them did that trick. Ignite starts up now without any error. Thanks a lot. I will still find out why they are there in libs/connector-layer folder.
Best Regards, Gaurav On Tue, Jan 3, 2017 at 1:38 PM, Nikolai Tikhonov <[email protected]> wrote: > Sorry, I'm missed that you don't use ignite as maven dependency in your > project but running it how standalone server. Could you please show which > modules in your C:\Users\D-NX29AE\Project\Software\shielding-gridgain- > enterprise-fabric-7.5.26\libs folder? (output dir commond in console) > > On Tue, Jan 3, 2017 at 3:34 PM, Gaurav Bajaj <[email protected]> > wrote: > >> Hello Nikolai, >> >> Sorry I am confused, where do I run this command? On my IntelliJ >> workspace? >> >> On Tue, Jan 3, 2017 at 1:22 PM, Nikolai Tikhonov <[email protected]> >> wrote: >> >>> Hi, >>> >>> It's really like on jar hell. You can use maven dependency tree which >>> allows to find conflict: >>> >>> *mvn dependency:tree -Dverbose -Dincludes=jetty-server* >>> >>> On Tue, Jan 3, 2017 at 2:30 PM, dkarachentsev < >>> [email protected]> wrote: >>> >>>> It looks like you have another version of Jetty in classpath. Do you >>>> have >>>> IGNITE_HOME environment variable set? >>>> >>>> >>>> >>>> -- >>>> View this message in context: http://apache-ignite-users.705 >>>> 18.x6.nabble.com/Error-with-ignite-rest-http-tp9835p9838.html >>>> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >>>> >>> >>> >> >
