Error when searching???
Im getting this error when trying to search or when trying to look at my threads. Whats going on :confused: :confused:
Search results provided by: ibSearch from Internet Brands HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception org.springframework.web.util.NestedServletExceptio n: Request processing failed; nested exception is java.lang.StringIndexOutOfBoundsException: String index out of range: -1 org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:487) org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:440) javax.servlet.http.HttpServlet.service(HttpServlet .java:710) javax.servlet.http.HttpServlet.service(HttpServlet .java:803) root cause java.lang.StringIndexOutOfBoundsException: String index out of range: -1 java.lang.String.<init>(String.java:208) org.apache.lucene.store.IndexInput.readString(Inde xInput.java:94) org.apache.lucene.index.SegmentInfo.<init>(Segment Info.java:115) org.apache.lucene.index.SegmentInfos.read(SegmentI nfos.java:213) org.apache.lucene.index.SegmentInfos$2.doBody(Segm entInfos.java:363) org.apache.lucene.index.SegmentInfos.run(SegmentIn fos.java:610) org.apache.lucene.index.SegmentInfos.readCurrentVe rsion(SegmentInfos.java:338) org.apache.lucene.index.IndexReader.isCurrent(Inde xReader.java:341) com.internetbrands.ibsearch.service.LuceneIndexSer vice.search(LuceneIndexService.java:308) com.internetbrands.ibsearch.data.VBulletinSearch.s earch(VBulletinSearch.java:681) com.internetbrands.ibsearch.web.EmbeddedSearchCont roller.onSubmit(EmbeddedSearchController.java:59) org.springframework.web.servlet.mvc.SimpleFormCont roller.onSubmit(SimpleFormController.java:381) org.springframework.web.servlet.mvc.SimpleFormCont roller.processFormSubmission(SimpleFormController. java:267) org.springframework.web.servlet.mvc.AbstractFormCo ntroller.handleRequestInternal(AbstractFormControl ler.java:250) org.springframework.web.servlet.mvc.AbstractContro ller.handleRequest(AbstractController.java:153) org.springframework.web.servlet.mvc.SimpleControll erHandlerAdapter.handle(SimpleControllerHandlerAda pter.java:48) org.springframework.web.servlet.DispatcherServlet. doDispatch(DispatcherServlet.java:857) org.springframework.web.servlet.DispatcherServlet. doService(DispatcherServlet.java:792) org.springframework.web.servlet.FrameworkServlet.p rocessRequest(FrameworkServlet.java:475) org.springframework.web.servlet.FrameworkServlet.d oPost(FrameworkServlet.java:440) javax.servlet.http.HttpServlet.service(HttpServlet .java:710) javax.servlet.http.HttpServlet.service(HttpServlet .java:803) note The full stack trace of the root cause is available in the Apache Tomcat/6.0.14 logs. |
Thanks, it's already been reported to IB. Tests for the forthcoming upgrade are currently taking place which are resulting in issues such as this. They'll all be sorted soon :)
|
You'd think being the "massive" company they are they'd copy the Vbul database and do all this in a test environment rather than f*ck up a live one.
:rolleyes: I'd be shot if I did this to our SAP system |
Originally Posted by dazdavies
(Post 8511426)
You'd think being the "massive" company they are they'd copy the Vbul database and do all this in a test environment rather than f*ck up a live one.
:rolleyes: I'd be shot if I did this to our SAP system Tried searching yesterday and search wouldn't work properly, it seems as though it has lost a count of previous posts????? Anyone else having this prob? Baly |
Please try now.
|
Originally Posted by dazdavies
(Post 8511426)
You'd think being the "massive" company they are they'd copy the Vbul database and do all this in a test environment rather than f*ck up a live one.
The mods need to be tweaked on the live platform so the engineers can try old legacy code mixed with new software code when loaded up in the real world so as to be able to accurately monitor and datalog real world performance. I can only apologise for all the inconvenience it is causing but the fact is, we didnt break it to start with, we are simply trying to fix it whilst creating minimal downtime for the users. |
All times are GMT +1. The time now is 07:14 AM. |
© 2024 MH Sub I, LLC dba Internet Brands