Problem creating suspicion profile
8 answers
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
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)
1 vote
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.
In the meantime, have you checked the help topic about creating profiles? If you haven't, you can find it at http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.rational.rrm.help.doc/topics/t_create_suspect_profiles.html.
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]
com.hp.hpl.jena.shared.JenaException: org.xml.sax.SAXParseException: 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.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.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:268)
at com.ibm.rdm.fronting.server.common.util.RdfXmlConv.toModel(RdfXmlConv.java:85)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.performRdfGet(DiscoveryBuilderInternal.java:422)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.buildResourceShapeResource(DiscoveryBuilderInternal.java:305)
at com.ibm.rdm.fronting.server.services.suspectlinks.discovery.internal.DiscoveryBuilderInternal.buildServiceProviderModel(DiscoveryBuilderInternal.java:292)
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:683)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.handleMethod(RRSRestServiceBase.java:611)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.doGet(RRSRestServiceBase.java:123)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.performService(RRSRestServiceBase.java:330)
at com.ibm.rdm.fronting.server.core.internal.RRSRestServiceBase.service(RRSRestServiceBase.java:214)
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:668)
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:668)
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:668)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1214)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:774)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:456)
at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:178)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.invokeTarget(WebAppFilterChain.java:125)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:92)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.processDelegate(BridgeFilter.java:133)
at com.ibm.team.repository.server.servletbridge.BridgeFilter.doFilter(BridgeFilter.java:154)
at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:192)
at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:89)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:926)
at com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters(WebAppFilterManager.java:1023)
at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3703)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:304)
at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:962)
at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1662)
at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:195)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:458)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:522)
at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:311)
at com.ibm.ws.http.channel.inbound.impl.HttpICLReadCallback.complete(HttpICLReadCallback.java:87)
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:1783)
Caused by: org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
... 66 more
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).
Comments
Marc Baumbach
FORUM MODERATOR / JAZZ DEVELOPER Feb 22 '13, 3:30 p.m.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.