Notifications
Clear all
Topic starter
This has happened to us for the 3rd time. Randomly, CPS decides to not like the Problems list search screen. When we try to search for a problem, CPS crashes. And the only way we have found to fix this is to uninstall the entire CPS page and uninstall, re-install JBoss... then add all custom stuff back on. Has anyone else dealt with this? Is there an easier fix?
Posted : June 26, 2015 6:40 am
What version/sp are you on? Is this related to the 'known' issue as documented in the SP9 release notes about the IE conflict with the new centricity framework/problem window? (SPR 60319 & 60320)
Posted : June 26, 2015 7:00 am
Topic starter
CPS 12 SP 7
I do not think it is related to that. It happens to everyone. Once i do the full un-install on the Jboss and the webpage, and reinstall, it works fine. It randomly happens.
Posted : June 26, 2015 7:30 am
Haven't seen this but I have heard of issues like this. I'd push GE for an answer that isn't uninstall and reinstall JBoss.
Posted : June 27, 2015 11:43 am
I have this problem as well, with CPS 12.0.9.1771. As soon as a single character is typed in the Problem search dialog, CPS crashes.
Jen - can you elaborate on SPR 60319 & 60320? I don't see anything about them in the SP9 release notes.
acantu - What do you think could possibly have changed that is fixed by a JBoss reinstall? If you're still having this issue and you're willing to look into it, it might be worth copying the JBoss folder after a fresh install and then after the problem appears, run a diff between the before/after versions of the JBoss folder. Of course it could also be something in the JBoss database, which would be a little harder to track down. I'd do this myself but we never had a time without this issue.
Posted : July 30, 2015 9:34 am
Reinstalling JBoss and the website fixed the problem. I ran a diff on the working/broken versions and didn't find a definitive solution. But one noticable difference was Solr indexes, whatever that is. It stood out because this was one of the errors I found in JBoss logs:
request: http://localhost:9080/solr/centricitypsQS/select?q=id:CustomList*&sort=ProblemSortField asc&rows=1000&fq=CustomListId:1632486404506110&wt=javabin&version=2 at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:432) at org.apache.solr.client.solrj.impl.CommonsHttpSolrServer.request(CommonsHttpSolrServer.java:246) at org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:89) ... 97 more
If we have this issue again, I will try resetting the Solr indexes. I'll either delete the files manually or do something along these lines:
http://stackoverflow.com/questions/7722508/how-to-delete-all-data-from-solr-and-hbase
Posted : August 4, 2015 7:45 am
My only other lead is a JBoss log entry reporting an illegal character in a path. Here's the error:
at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050) at org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.IllegalArgumentException at java.net.URI.create(URI.java:842) at org.apache.cxf.catalog.OASISCatalogManager.loadCatalogs(OASISCatalogManager.java:147) at org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:133) at org.apache.cxf.catalog.OASISCatalogManager.loadContextCatalogs(OASISCatalogManager.java:129) at org.apache.cxf.catalog.OASISCatalogManager.setBus(OASISCatalogManager.java:125) ... 35 more Caused by: java.net.URISyntaxException: Illegal character in path at index 18: vfszip:/C:/Program Files/Centricity Practice Solution/jboss/server/default/deploy/demo12.ear/lib/cxf-2.6.2.jar/META-INF/jax-ws-catalog.xml at java.net.URI$Parser.fail(URI.java:2809) at java.net.URI$Parser.checkChars(URI.java:2982) at java.net.URI$Parser.parseHierarchical(URI.java:3066) at java.net.URI$Parser.parse(URI.java:3014) at java.net.URI.<init>(URI.java:578) at java.net.URI.create(URI.java:840) ... 39 more
So it's possible a path string was saved at some point with an illegal character in it. I searched through the JBoss installation and couldn't find a relevant configuration setting. If anyone comes across one, please post it here. Thanks.
Posted : August 4, 2015 7:52 am
