Eclipse client connection to Jetty Server throws error
Prakash Behrani (28●9●10)
| asked Aug 18 '14, 8:07 p.m.
edited Aug 19 '14, 4:37 p.m. by Stephanie Taylor (241●1●5)
When trying to connect Eclipse client to Jetty Server throws the following error:
JIT - 20091016_1845ifx7_r8 GC - 20091026_AA BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product com.ibm.team.concert.product Command-line arguments: -product com.ibm.team.concert.product -data C:\RTC301Dev\workspaces\DEV\WS1/../WS2 -dev file:C:/RTC301Dev/workspaces/DEV/WS1/.metadata/.plugins/org.eclipse.pde.core/RTC Eclipse Client/dev.properties -os win32 -ws win32 -arch x86 Error Mon Aug 18 19:21:36 EDT 2014 CRJAZ0106I The request for the URL "/jazz/service/com.ibm.team.scm.common.internal.IScmQueryService" was denied. The status is Not Available". Any thoughts on what might not be configured correctly on the Jetty Server. Any feedback is highly appreciated. Thanks. |
One answer
Hello,
are you running your Jetty server in debug mode (from and Eclipse workspace)?
Also check your server's admin page, and run diagnostics, so as to ensure all services are up and running.
Eric
Comments
Prakash Behrani
commented Aug 19 '14, 11:03 a.m.
Yes, Jetty Server was started using Debug Configuration from Eclipse.
So you should see a bunch of errors in server's Eclipse console
Prakash Behrani
commented Aug 19 '14, 11:17 a.m.
I see one error related to log4j.properties not found as shown below.
right - so you're missing com.ibm.team.common.tests.utils
in your Eclipse wks.
you have to load it
Prakash Behrani
commented Aug 19 '14, 12:18 p.m.
Actually, com.ibm.team.common.tests.utils is already loaded. The only thing missing was the log4j.properties file.
Hello,
possibly, your dev wks is not correctly set-up.
Please refer to https://jazz.net/wiki/bin/view/Main/TAPDevEnvironment
and give it a go.
Thanks,
Eric
Prakash Behrani
commented Aug 20 '14, 11:05 a.m.
Thanks Eric. I reviewed the technote.
showing 5 of 7
show 2 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.