Problem creating suspicion profile
LUIZ DE ALMEIDA (230●1●61●92)
| asked Feb 21 '13, 8:33 a.m.
retagged Feb 21 '13, 9:04 a.m. by Laura W. Hinson (161●2●6) Hi All, I am trying to create a suspicion profile in RRC 4.0.1 and the following problem is occurring: |
8 answers
I had a same problem under 4.0.5 and found a possible work around.
When I looked over jts.log and rm.log, it seemed that JTS or RM was trying to access CCM using a URI like this: https://alpha.example.com:19443/ccm/oslc/context/_R0yFsJRiEeOG2_LA_qSMNA/shapes/workitems/変更管理票"変更管理票" is a Japanese word which is defined as a work item type ID in my case. I think URIs must be encoded to base64 to comply with RFC3986. In Luiz and Egor's case, Spanish or Russian specific character(s) may be used. After I changed work item type ID into a simple English word, the error disappeared. Comments 1
This is possibly the answer. We just recently fixed a defect on end to resolve this issue and should be available in a future release. Please see When shapes URL contains non-UTF-8 characters, calls to /rm/suspectDiscovery result in 500 response (85044) |
Hi Luiz,
The 4.0.1 information center contains more details about that message at http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.messages.CLMic/CRRSL6012E.html. According to the message details, you should close and reopen the browser, and then log in again. If that doesn't help, you might need to contact a server administrator to check its status. Comments Thanks, Laura. But it didn't work. The server is operating correctly because all other functions are running well. Do I have to do any configuration in the server to work with suspicion profile? Start any service or anything like this? I don't think you need to configure the server to work with suspicion profiles, but I have forwarded your question to a couple other developers to get their thoughts.
|
Marc, The log is: 2013-02-25 10:12:33,165 [ WebContainer : 22] ERROR .hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler - https://something(line 1 column 1): Content is not allowed in prolog.
2013-02-25 10:12:33,183 [ WebContainer : 22] ERROR ces.suspectlinks.discovery.SuspectDiscoveryService - Erro de Servidor: Entrada [e1765bd90600758e]
Comments This particular error can be difficult to debug, but the "Content is not allowed in prolog" portion typically indicates that there's an OAuth problem and the RM server is not able to communicate with one of the registered applications (RTC, RQM).
@lcesaralmeida Are you seeing any issues with creating links between RRC and RTC or RQM? You might also try a full restart of the CLM server to see if that resolves your issue.
LUIZ DE ALMEIDA
commented Mar 25 '13, 6:59 p.m.
Marc,
I noted that this problem occurs with some project areas, but not with others in the same environment. It makes me think that problem is with project area configuration...but what configuration?
In the project area that problem occurs, i don't have problem creating links with RTC or RQM.
In my environment, the applications are in different servers.
I will try to restart the RM server.
|
|
Hi all
We had the exact same problem. None of the above did not help to solve it, The server works correctly, links between RTC, CCM, RRC are created correctly Help please, what else should I check? |
Log from server
2013-09-27 11:00:58,677 [ WebContainer : 7] ERROR .hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler - https://hs22-33.ca.sbrf.ru:9443/jazz/oslc/context/_EotoYHGqEeCFqOnGonZFzA/shapes/workitems/релиз(line 1 column 1): Атрибут содержимого (Content) Content is not allowed in prolog.
2013-09-27 11:00:58,677 [ WebContainer : 7] ERROR ces.suspectlinks.discovery.SuspectDiscoveryService - Server Error: Entry [41ed12bef94b9649]
com.hp.hpl.jena.shared.JenaException: org.xml.sax.SAXParseException: Атрибут содержимого (Content) Content is not allowed in prolog.
at com.hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler.fatalError(RDFDefaultErrorHandler.java:60)
at com.hp.hpl.jena.rdf.arp.impl.ARPSaxErrorHandler.fatalError(ARPSaxErrorHandler.java:51)
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.warning(XMLHandler.java:211)
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.fatalError(XMLHandler.java:241)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:155)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:173)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232)
at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.performRdfGet(DiscoveryBuilderInternal.java:424)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.buildResourceShapeResource(DiscoveryBuilderInternal.java:307)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.buildServiceProviderModel(DiscoveryBuilderInternal.java:294)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.SuspectDiscoveryServiceInternal.doGetInternal(SuspectDiscoveryServiceInternal.java:88)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:764)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:687)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doGet(RRSRestServiceBase.java:127)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:403)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:222)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:155)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
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:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1658)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1598)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:139)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:172)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:80)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:935)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:503)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3954)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:942)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
Caused by: org.xml.sax.SAXParseException: Атрибут содержимого (Content) нельзя указывать в прологе.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
... 65 more
2013-09-27 11:01:28,626 [ WebContainer : 7] ERROR .hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler - Непредвиденный конец файла.
2013-09-27 11:01:28,626 [ WebContainer : 7] ERROR serPreferences.internal.UserPreferencesRestService - Ошибка сервера: запись [c2b6b7f35b1082b]
com.hp.hpl.jena.shared.JenaException: org.xml.sax.SAXParseException: Непредвиденный конец файла.
at com.hp.hpl.jena.rdf.model.impl.RDFDefaultErrorHandler.fatalError(RDFDefaultErrorHandler.java:60)
at com.hp.hpl.jena.rdf.arp.impl.ARPSaxErrorHandler.fatalError(ARPSaxErrorHandler.java:51)
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.warning(XMLHandler.java:211)
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.fatalError(XMLHandler.java:241)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$XMLDeclDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:155)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:173)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:160)
at com.hp.hpl.jena.rdf.arp.JenaReader.read(JenaReader.java:232)
at com.hp.hpl.jena.rdf.model.impl.ModelCom.read(ModelCom.java:235)
at com.ibm.rdm.fronting.server.services.userPreferences.internal.UserPreferencesDomainService.doPostInternal(UserPreferencesDomainService.java:78)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.runInternalMethod(RRSRestServiceBase.java:770)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:687)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doPost(RRSRestServiceBase.java:142)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:409)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:222)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.dispatchRequest(AppContainerServlet.java:155)
at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:281)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
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:831)
at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120)
at com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1658)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1598)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:149)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:139)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:172)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:80)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:935)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:503)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181)
at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:91)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:875)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:186)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:83)
at com.ibm.ws.ssl.channel.impl.SSLReadServiceContext$SSLReadCompletedCallback.complete(SSLReadServiceContext.java:1784)
at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:165)
at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217)
at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161)
at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138)
at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204)
at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775)
at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1646)
Caused by: org.xml.sax.SAXParseException: Непредвиденный конец файла.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
... 61 more
|
At this point, the best option is to likely open a support request so that we can debug further individually. From the sounds of it, there's something wrong with the project information we are fetching from the servers. One thing I could think of is that some special characters aren't being correctly encoded for XML and causing things to parse incorrectly.
In Egor's example: "Caused by: org.xml.sax.SAXParseException: Непредвиденный конец файла." Some of those characters may be causing an issue and with a support request open against RM, we would likely be able to determine what needs to be fixed in the product and/or come up with a workaround to get it functioning in your environments.
|
Hi all,
Marc B. mentioned this in a comment above, but this should be fixed via the RRC defect When shapes URL contains non-UTF-8 characters, calls to /rm/suspectDiscovery result in 500 response (85044) which should be available in RRC 5.0 once it releases this year.
Basically, the problem was that RRC was not properly ASCII-encoding URLs which contained non-UTF-8 characters, so a request to URLs such as "https://alpha.example.com:19443/ccm/oslc/context/_R0yFsJRiEeOG2_LA_qSMNA/shapes/workitems/変更管理票" would result in an error, and the attempt to parse this erroneous result would result in a SAXParseException (seen in the stack traces above). A workaround for this issue would be to define CCM work item Titles/IDs to use UTF-8 characters, and this should allow suspicion profiles to function properly.
Hope this helps!
Mike Jaworski
|
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.
Comments
Hi Luiz, could you post the portion of your RM server log that corresponds to the error you are seeing? That may help us pinpoint the problem.