It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882
×10,914
×62

question asked: Nov 08 '14, 5:48 a.m.
question was seen: 4,326 times
last updated: Nov 21 '14, 7:42 a.m.

Related questions

internalDevelopmentLines is not a valid property for TeamArea error

0
Karthik Krishnan (889●9●123●165) | asked Nov 08 '14, 5:48 a.m.
edited Nov 08 '14, 3:48 p.m.
When updating a workitem via OSLC, we see the following error in CCM logs and the work item is note updated 

2014-11-07 13:56:59,619 [http-bio-9443-exec-87 @@ 13:56 user /ccm/oslc/types/_6e3mcFnmEeS6vJhdZWMotg] ERROR com.ibm.team.workitem.service                      
 - Failed to serve the request - 'oslc/types/_6e3mcFnmEeS6vJhdZWMotg'. Reason - 'internalDevelopmentLines is not a valid property for TeamArea'. 
com.ibm.team.repository.common.InternalRepositoryException: internalDevelopmentLines is not a valid property for TeamArea
	at com.ibm.team.repository.service.internal.dataaccess.MediatorUtils.reduceItem(MediatorUtils.java:103)
	at com.ibm.team.repository.service.internal.dataaccess.MediatorUtils.reduceItemToRequestedProperties(MediatorUtils.java:82)
	at com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.internalFetchCurrentState(RdbRepositoryDataMediator.java:1580)
	at com.ibm.team.repository.service.internal.RdbRepositoryDataMediator.fetchItem(RdbRepositoryDataMediator.java:2141)
	at com.ibm.team.repository.service.internal.RepositoryItemService.doFetchItem(RepositoryItemService.java:541)
	at com.ibm.team.repository.service.internal.RepositoryItemService.access$4(RepositoryItemService.java:537)
	at com.ibm.team.repository.service.internal.RepositoryItemService$4.run(RepositoryItemService.java:517)
	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$Transaction.run(RepositoryDatabase.java:496)
	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase$1.run(RepositoryDatabase.java:320)
	at com.ibm.team.repository.service.internal.rdb.ConnectionPoolService.withCurrentConnection(ConnectionPoolService.java:439)
	at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy57.withCurrentConnection(Unknown Source)
	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runTransaction(RepositoryDatabase.java:316)
	at com.ibm.team.repository.service.internal.rdb.RepositoryDatabase.runInTransaction(RepositoryDatabase.java:271)
	at com.ibm.team.repository.service.internal.PrimitiveTransactionService.runInTransaction(PrimitiveTransactionService.java:96)
	at sun.reflect.GeneratedMethodAccessor250.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy98.runInTransaction(Unknown Source)
	at com.ibm.team.repository.service.internal.RepositoryItemService.fetchItem(RepositoryItemService.java:515)
	at sun.reflect.GeneratedMethodAccessor274.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy203.fetchItem(Unknown Source)
	at com.ibm.team.repository.service.internal.ComponentRepositoryItemService.fetchItem(ComponentRepositoryItemService.java:598)
	at com.ibm.team.workitem.service.internal.AuditableServer.resolveAuditable(AuditableServer.java:112)
	at com.ibm.team.workitem.service.internal.oslc.resources.WorkItemTypeCollectionResource.getProjectArea(WorkItemTypeCollectionResource.java:98)
	at com.ibm.team.workitem.service.internal.oslc.resources.WorkItemTypeCollectionResource.getETag(WorkItemTypeCollectionResource.java:89)
	at com.ibm.team.workitem.service.internal.oslc.representations.AbstractResourceRepresentation.generateETag(AbstractResourceRepresentation.java:221)
	at com.ibm.team.workitem.service.internal.oslc.representations.AbstractResourceRepresentation.getETag(AbstractResourceRepresentation.java:209)
	at com.ibm.team.workitem.service.internal.oslc.RequestHandler.handleGET(RequestHandler.java:141)
	at com.ibm.team.workitem.service.internal.oslc.RequestHandler.handleGET(RequestHandler.java:123)
	at com.ibm.team.workitem.service.internal.oslc.OSLCService.perform_GET(OSLCService.java:35)
	at com.ibm.team.repository.service.TeamRawService.service(TeamRawService.java:84)
	at sun.reflect.GeneratedMethodAccessor725.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
	at java.lang.reflect.Method.invoke(Method.java:611)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:361)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:347)
	at org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56)
	at com.sun.proxy.$Proxy961.service(Unknown Source)
	at com.ibm.team.repository.servlet.AbstractTeamServerServlet.doRestService(AbstractTeamServerServlet.java:909)
	at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest2(AbstractTeamServerServlet.java:2349)
	at com.ibm.team.repository.servlet.AbstractTeamServerServlet.handleRequest(AbstractTeamServerServlet.java:2153)
	at com.ibm.team.repository.servlet.AbstractTeamServerServlet.service(AbstractTeamServerServlet.java:1963)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:180)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.service(ServletRegistration.java:61)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:126)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:76)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
	at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:74)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:165)
	at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:198)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:581)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99)
	at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:336)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1002)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:585)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:906)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:929)
	at java.lang.Thread.run(Thread.java:738)

Any idea what this means?

I am able to submit the values via Eclipse / Web client and save the work item. Only issue is with OSLC
Comments
sam detweiler commented Nov 08 '14, 4:20 p.m.

Can u show us the URL you are using? 

Karthik Krishnan commented Nov 09 '14, 5:24 a.m.

 Well actually we are using a 3rd party tool which builds the url and posts to RTC. I don't have the source code to show the url as we give inputs to the tool and it uses OSLC to post to RTC. 


I am wondering what this "internalDevelopmentLines is not a valid property for TeamArea" error means

Couldn't find any info about this anywhere

sam detweiler commented Nov 09 '14, 7:09 a.m.

sounds like the URL has something in it that is causing the problem.  Maybe they used something that is no longer working..

can u put a proxy server in between to see the URL?

Donald Nong commented Nov 09 '14, 5:49 p.m.

I would suggest you do a GET /ccm/oslc/types/_6e3mcFnmEeS6vJhdZWMotg (the URL quoted in the error message) and it may give you more information about what is going on.

Kevin Eifinger commented Nov 10 '14, 4:27 a.m.

Hi Karthik,

I had a similar problem when I was trying to set a Category with the plainjava API. I was having problems getting a Handle by using the id.

Is internalDevelopmentLines the Name of the TeamArea? Have you tried using the ID instead?

Karthik Krishnan commented Nov 10 '14, 5:35 a.m.

@dnong:
I get this when I do a GET /ccm/oslc/types/_6e3mcFnmEeS6vJhdZWMotg 

<oslc_cm:error xmlns:oslc_cm="http://open-services.net/xmlns/cm/1.0/">
<oslc_cm:status>500</oslc_cm:status>
<oslc_cm:message>internalDevelopmentLines is not a valid property for TeamArea</oslc_cm:message>
</oslc_cm:error>

Karthik Krishnan commented Nov 10 '14, 5:36 a.m.

Hi Kevin

the internalDevelopmentLines is the error thrown from RTC. I was thinking it is something do with the association of Team area and Timeline

Donald Nong commented Nov 10 '14, 7:51 p.m.

A 500 internal error for the GET request does not sound good. If the offending URL is not hard coded in your OSLC application, there may be some corruption in the system. I suggest you open a PMR with Support.

showing 5 of 8 show 3 more comments

2 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Karthik Krishnan (889●9●123●165) | answered Nov 21 '14, 7:42 a.m.
Finally found the Issue what was causing this

It seem like that in my case oslc/types/_6e3mcFnmEeS6vJhdZWMotg

-> _6e3mcFnmEeS6vJhdZWMotg Seem to be the ID of team area and RTC was expecting ProjectArea ID

Interesting thing is  that this error occurs only when "Restrict Work item access" is enabled in "Categories"

Else no error is thrown

The error message is very cryptic though

thanks to other who was trying to help me here

Cheers

0
permanent link
Karthik Krishnan (889●9●123●165) | answered Nov 11 '14, 8:27 a.m.
Since comments are too big, posting it here

- Found out that only when "Restrict Workitem access" is enabled, we get this error
and of course the user which is updating is part of the team area and has correct roles

Any clues?

Comments
sam detweiler commented Nov 11 '14, 8:38 a.m.

just to clarify, the user executing the script (curl or whatever) is logged on with the users credentials, and not some userid used for the tooling.

if so, then I'd say you may have found a bug.

Karthik Krishnan commented Nov 11 '14, 8:40 a.m. | edited Nov 11 '14, 8:52 a.m.

the user id's are same. Tested it many times

Also tried to update the OSLC as JazzAdmin still same issue. So not sure

Your answer

Register or to post 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.