[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4146:
----------------------------------
Related issue: https://bugzilla.redhat.com/show_bug.cgi?id=1389302
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 10.x
>
> Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, eclipse-log-after-new-workspace.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim resolved JBIDE-16596.
--------------------------------------
Assignee: Andre Dietisheim
Resolution: Cannot Reproduce Bug
> Server Adapter Editor: Timeouts and publishing fields are too small
> -------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.4.2.AM3
>
> Attachments: server-adapter-openshift2-timeouts.png, server-adapter-openshift3-timeouts.png, small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16596:
-------------------------------------
Fix Version/s: 4.4.2.AM3
(was: 4.4.x)
> Server Adapter Editor: Timeouts and publishing fields are too small
> -------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.4.2.AM3
>
> Attachments: server-adapter-openshift2-timeouts.png, server-adapter-openshift3-timeouts.png, small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16596:
------------------------------------------
This wont happen in my FC23. Neither for OpenShift 3 nor 2 (I guess that they share the very same code).
!server-adapter-openshift2-timeouts.png!
!server-adapter-openshift3-timeouts.png!
> Server Adapter Editor: Timeouts and publishing fields are too small
> -------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.4.2.AM3
>
> Attachments: small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16596:
-------------------------------------
Attachment: server-adapter-openshift2-timeouts.png
> Server Adapter Editor: Timeouts and publishing fields are too small
> -------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.4.2.AM3
>
> Attachments: server-adapter-openshift2-timeouts.png, server-adapter-openshift3-timeouts.png, small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-16596) Server Adapter Editor: Timeouts and publishing fields are too small
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16596?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16596:
-------------------------------------
Attachment: server-adapter-openshift3-timeouts.png
> Server Adapter Editor: Timeouts and publishing fields are too small
> -------------------------------------------------------------------
>
> Key: JBIDE-16596
> URL: https://issues.jboss.org/browse/JBIDE-16596
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.4.2.AM3
>
> Attachments: server-adapter-openshift2-timeouts.png, server-adapter-openshift3-timeouts.png, small_field.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4133:
----------------------------------
We need to include 3.5 in the TP because Eclipse Help system and other upstream platform things need it (when installed into Windows or OSX).
But since we need to ALSO run on RHEL, where there is no 3.5 available, I would recommend Xavier's approach of porting OUR code to run on 5.4.1 so we can safely run there too. Fedora & RHEL will move to Lucene 5.6 in the next few months so we might as well stay current.
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, osgi-console-lucene.png, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22259:
------------------------------------------
This caused JBIDE-23030
> Server Adapter: Debugging of OS 3 application creates a new replication controller
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-22259
> URL: https://issues.jboss.org/browse/JBIDE-22259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
>
> Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-22259) Server Adapter: Debugging of OS 3 application creates a new replication controller
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22259?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22259:
------------------------------------------
[~jcantrill]
{quote}
e should only need to modify the rc
{quote}
Is the approach where we modify the rc vs the current one, where we modify the dc already possible or is there work on the server to be done?
> Server Adapter: Debugging of OS 3 application creates a new replication controller
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-22259
> URL: https://issues.jboss.org/browse/JBIDE-22259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.x
>
>
> Restart in debug on OS 3 server adapter of eap 6.4 application and related workspace project creates a new replication controller. Every time server is stopped and started, new replication controller is created (although server has been stopped and then started) and a this new replication controller is still debugging (has set debug port).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4146 at 11/9/16 9:07 AM:
-----------------------------------------------------------
So, the issue here is that when rh-eclipse46-eclipse-epp-logging-2.0.3-1.1.el7.noarch and/or eclipse-epp-logging-2.0.3-1.fc24.noarch are built, Mat Booth patched [0] the MANIFEST.MF files to include the latest lucene 5.4.1 instead of 3.5.0 (on Aug 2 2016) [1]
[0] http://pkgs.devel.redhat.com/cgit/rpms/eclipse-epp-logging/tree/lucene-up...
[1] http://pkgs.devel.redhat.com/cgit/rpms/eclipse-epp-logging/tree/eclipse-e...
was (Author: nickboldt):
So, the issue here is that when rh-eclipse46-eclipse-epp-logging-2.0.3-1.1.el7.noarch and/or eclipse-epp-logging-2.0.3-1.fc24.noarch are built, someone changed the MANIFEST.MF files to include the latest lucene 5.4.1 instead of 3.5.0.
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 10.x
>
> Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, eclipse-log-after-new-workspace.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months