You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ryan McKinley (Created) (JIRA)" <ji...@apache.org> on 2012/02/24 02:45:49 UTC
[jira] [Created] (SOLR-3159) Upgrade to Jetty 8
Upgrade to Jetty 8
------------------
Key: SOLR-3159
URL: https://issues.apache.org/jira/browse/SOLR-3159
Project: Solr
Issue Type: Task
Reporter: Ryan McKinley
Priority: Minor
Fix For: 4.0
Solr is currently tested (and bundled) with a patched jetty-6 version.
Ideally we can release and test with a standard version.
Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Uwe Schindler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224831#comment-13224831 ]
Uwe Schindler commented on SOLR-3159:
-------------------------------------
That should not matter as the servlet-api.jar is just a interface hull, version is irrelevant. To compile solr, an older servlet API would be even better as requirement, so the WAR is enforced to also run in older tomcats :-)
So I would revert the jar file in the lib/ folder of solr to 2.4 and only use the 3.0 one for executing jetty8.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215304#comment-13215304 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
I will make a branch for this so that it is easy to compare the two options.
One kicker is that JSP in Jetty 7 or 8 requires a JDK, not just the JRE.
But with progress on the new UI, I think we can drop JSP entirely (good riddance!)
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Resolved] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley resolved SOLR-3159.
---------------------------------
Resolution: Fixed
Assignee: Ryan McKinley
We can open a new issue for any subsequent problems
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Uwe Schindler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224713#comment-13224713 ]
Uwe Schindler commented on SOLR-3159:
-------------------------------------
I would strongly suggest to upgrade jetty also on 3.x, otherwise we could get the commons-csv proble a second time here...
In Jetty 8 the unicode bug seems fixed, not sure about Jetty 7. The work for upgrade should not be so hard here, because Jetty already uses the eclipse package name? so its just a backport with Jetty 7 JARs?
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224747#comment-13224747 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
bq. is 8.x just stable enough?
I'm confident the server is stable. I am not confident we have the most appropriate settings in solr/example/etc/jetty.xml
These are the same settings we had for jetty 6, but I do not know if this is still the best choice. In particular, I'm not sure about the .bio.SocketConnector vs .nio.SelectChannelConnector
Uwe: to backport, we can use the same setup (jetty 8) but need to add in the JSP jar files and change docs about starting the example. Unlike the commons-csv issue, I am not concerned about the patched dependency here because if someone wants to use a different jetty release they can do it and avoid the JAR hell problems.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215315#comment-13215315 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
Check:
https://svn.apache.org/repos/asf/lucene/dev/branches/solr_3159_jetty8/
Can someone with a benchmarking setup take it for a spin?
If things look good, I'll sort out the JSP issues.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Yonik Seeley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232622#comment-13232622 ]
Yonik Seeley commented on SOLR-3159:
------------------------------------
>From that link, it looks like it should probably be:
{code}
<Call name="setAttribute">
<Arg>org.eclipse.jetty.server.Request.maxFormContentSize</Arg>
<Arg>200000</Arg>
</Call>
{code}
Can anyone test and confirm this works?
bq. These are the same settings we had for jetty 6, but I do not know if this is still the best choice. In particular, I'm not sure about the .bio.SocketConnector vs .nio.SelectChannelConnector
The NIO connector was causing intermittent failures on Jenkins. I have no idea if the bugs were ever found/fixed in Jetty land - but it's a risk. It would be nice to move to the NIO connector if it is now stable though, since it could possibly allow for better logging/debugging (i.e. if we can specify our own thread pool to handle requests such that we can tell different jetty instances apart during logging).
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224709#comment-13224709 ]
Robert Muir commented on SOLR-3159:
-----------------------------------
As far as 3.x, i don't quite understand http://wiki.eclipse.org/Jetty/Starting/Jetty_Version_Comparison_Table
What does this mean? does 'experimental' mean like Lucene's FST APIs or does it just mean its only a few years old :)
Stable/experimental is not absolute and I'm just curious what opinions are.
Obviously jetty7 for 3.x is possibly an option?
*but*
Are the unicode bug fixes applied there?
Ryan already did the work for 8.x, 7.x would cost much more man hours...? is 8.x just stable enough?
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe updated SOLR-3159:
------------------------------
Attachment: SOLR-3159-maven.patch
Maven configuration:
# Removed from top-level POM the installation to local Maven repository of optional/test-only Jetty artifacts.
# Switched Jetty dependencies to v8.1.1 Maven Central artifacts
# Switched Servlet API dependecy to Jetty Orbit jar (this will need to be fixed if/when the 2.4 servlet jar is put back into {{solr/lib/}}
Committing shortly.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225688#comment-13225688 ]
Steven Rowe commented on SOLR-3159:
-----------------------------------
bq. apparently fixed in 8.1.2 ?
Wierdly, I don't see an annoucement for v8.1.2 on [the jetty-announce list archives|http://dev.eclipse.org/mhonarc/lists/jetty-announce/] (unlike v8.1.1, which was announced), and the Maven artifacts haven't shown up in Maven central (again, unlike the v8.1.1 artifacts).
The full 8.1.2 version name is 8.1.2.v20120302, where AFAICT the suffix is the release date, six days ago.
Unlike 8.1.2, the Maven Central artifacts for 8.1.0 and 8.1.1 are dated one day after the (assumed) release date from the version number.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Hoss Man (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225674#comment-13225674 ]
Hoss Man commented on SOLR-3159:
--------------------------------
FWIW: on trunk, using an svn checkout, and runing "java -jar start.jar" i'm getting the following error in the jetty logging after solr starts up...
{noformat}
2012-03-08 15:16:09.382:WARN:oejw.WebAppContext:Failed startup of context o.e.j.w.WebAppContext{/.svn,file:/home/hossman/lucene/dev/solr/example/webapps/.svn/},/home/hossman/lucene/dev/solr/example/webapps/.svn
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:686)
at org.eclipse.jetty.util.log.StdErrLog.condensePackageString(StdErrLog.java:210)
at org.eclipse.jetty.util.log.StdErrLog.<init>(StdErrLog.java:105)
at org.eclipse.jetty.util.log.StdErrLog.<init>(StdErrLog.java:97)
at org.eclipse.jetty.util.log.StdErrLog.newLogger(StdErrLog.java:569)
at org.eclipse.jetty.util.log.AbstractLogger.getLogger(AbstractLogger.java:21)
at org.eclipse.jetty.util.log.Log.getLogger(Log.java:438)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:677)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:454)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:36)
at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:183)
at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:491)
at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:138)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:142)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:53)
at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:604)
at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:535)
at org.eclipse.jetty.util.Scanner.scan(Scanner.java:398)
at org.eclipse.jetty.util.Scanner.doStart(Scanner.java:332)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:118)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:552)
at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:227)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at org.eclipse.jetty.util.component.AggregateLifeCycle.doStart(AggregateLifeCycle.java:58)
at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:53)
at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:91)
at org.eclipse.jetty.server.Server.doStart(Server.java:263)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:59)
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1215)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1138)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.jetty.start.Main.invokeMain(Main.java:457)
at org.eclipse.jetty.start.Main.start(Main.java:602)
at org.eclipse.jetty.start.Main.main(Main.java:82)
{noformat}
...solr is functioning just fine, but it seems like something has changed subtley in either how jetty handles the webapps dir, or how we have it configured to handle the webapps dir, such that it is trying to load .svn as a webapp.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224827#comment-13224827 ]
Steven Rowe commented on SOLR-3159:
-----------------------------------
Hi Ryan,
I'm trying to fix the Maven build to use Jetty 8, and I see that you've upgraded servlet-api jar to v3.0, but I can't find that version in the Maven Central repository. The two closest I found are [javax.servlet:javax-servlet.api:3.0.1|http://repo1.maven.org/maven2/javax/servlet/javax.servlet-api/3.0.1/] and [javax.servlet:servlet-api:3.0-alpha-1|http://repo1.maven.org/maven2/javax/servlet/servlet-api/3.0-alpha-1/]. Am I missing something?
If you don't know of a 3.0 Maven artifact, can we upgrade to the 3.0.1 artifact in Maven central? (I did not test this myself.)
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3159) Upgrade to Jetty 8
Posted by "Uwe Schindler (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224831#comment-13224831 ]
Uwe Schindler edited comment on SOLR-3159 at 3/7/12 11:33 PM:
--------------------------------------------------------------
That should not matter as the servlet-api.jar is just a interface hull, version is irrelevant. To compile solr, an older servlet API would be even better as requirement, so the WAR is enforced to also run in older tomcats :-)
So I would revert the jar file in the lib/ folder for *compiling* of solr to 2.4 and only use the 3.0 one for *executing* jetty8 in the example or when running tests.
was (Author: thetaphi):
That should not matter as the servlet-api.jar is just a interface hull, version is irrelevant. To compile solr, an older servlet API would be even better as requirement, so the WAR is enforced to also run in older tomcats :-)
So I would revert the jar file in the lib/ folder of solr to 2.4 and only use the 3.0 one for executing jetty8.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Bill Bell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232171#comment-13232171 ]
Bill Bell commented on SOLR-3159:
---------------------------------
Is this back ported to 3x? There is also a BIO issue in Jetty 6
https://jira.codehaus.org/browse/JETTY-1458
The ticket for 3159 only says Solr 4.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Shawn Heisey (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224505#comment-13224505 ]
Shawn Heisey commented on SOLR-3159:
------------------------------------
I asked this on the mailing list, got zero response. I would like to know if there are any good reasons to upgrade to Jetty 8 with an older release, specifically 3.5.0. Also, the Jetty 8 distribution has a fair number of config files in etc, but the example Solr only has jetty.xml and webdefault.xml. What sort of recommendations do you have as far as config changes when upgrading?
I am using the JDK, so I would I be OK with the presence of JSP in the pre-trunk version? Solr is not directly reachable from the outside world, it is used on the internal network by our web application.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224835#comment-13224835 ]
Steven Rowe commented on SOLR-3159:
-----------------------------------
bq. Am I missing something?
Woohoo! Found it!: [org.eclipse.jetty.orbit:javax.servlet:3.0.0.v201112011016|http://repo1.maven.org/maven2/org/eclipse/jetty/orbit/javax.servlet/3.0.0.v201112011016/]
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224900#comment-13224900 ]
Steven Rowe commented on SOLR-3159:
-----------------------------------
bq. Maven configuration: [...] Committing shortly.
Done: r1298247
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Issue Comment Edited] (SOLR-3159) Upgrade to Jetty 8
Posted by "Bill Bell (Issue Comment Edited) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232420#comment-13232420 ]
Bill Bell edited comment on SOLR-3159 at 3/19/12 3:30 AM:
----------------------------------------------------------
For sharding we probably want to add back the equivalent for MAX POST size.
{code}
<!-- Increase the maximum POST size to 1 MB to be able to handle large shard requests -->
<Call class="java.lang.System" name="setProperty">
<Arg>org.mortbay.jetty.Request.maxFormContentSize</Arg>
<Arg>1000000</Arg>
</Call>
{code}
To something like:
{code}
<Call class="java.lang.System" name="setProperty">
<Arg>org.eclipse.jetty.Request.maxFormContentSize</Arg>
<Arg>1000000</Arg>
</Call>
{code}
See http://wiki.eclipse.org/Jetty/Howto/Configure_Form_Size#Changing_the_Maximum_Form_Size_for_All_Apps_on_a_Server
was (Author: billnbell):
For sharding we probably want to add back the equivalent for MAX POST size.
{code}
<!-- Increase the maximum POST size to 1 MB to be able to handle large shard requests -->
<Call class="java.lang.System" name="setProperty">
<Arg>org.mortbay.jetty.Request.maxFormContentSize</Arg>
<Arg>1000000</Arg>
</Call>
{code}
To something like:
{code}
<Call class="java.lang.System" name="setProperty">
<Arg>org.eclipse.jetty.Request.maxFormContentSize</Arg>
<Arg>500000</Arg>
</Call>
{code}
See http://wiki.eclipse.org/Jetty/Howto/Configure_Form_Size#Changing_the_Maximum_Form_Size_for_All_Apps_on_a_Server
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Bill Bell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13232420#comment-13232420 ]
Bill Bell commented on SOLR-3159:
---------------------------------
For sharding we probably want to add back the equivalent for MAX POST size.
{code}
<!-- Increase the maximum POST size to 1 MB to be able to handle large shard requests -->
<Call class="java.lang.System" name="setProperty">
<Arg>org.mortbay.jetty.Request.maxFormContentSize</Arg>
<Arg>1000000</Arg>
</Call>
{code}
To something like:
{code}
<Call class="java.lang.System" name="setProperty">
<Arg>org.eclipse.jetty.Request.maxFormContentSize</Arg>
<Arg>500000</Arg>
</Call>
{code}
See http://wiki.eclipse.org/Jetty/Howto/Configure_Form_Size#Changing_the_Maximum_Form_Size_for_All_Apps_on_a_Server
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Steven Rowe (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226520#comment-13226520 ]
Steven Rowe commented on SOLR-3159:
-----------------------------------
{quote}
bq. Wierdly, I don't see an annoucement for v8.1.2
Sorry .. poor wording on my part: the issue is marked fixed in 8.1.2 but the jetty Jira system lists 8.1.2 as unreleased (ie: fixed on jetty's 8.1 branch for hte next release i guess)
{quote}
Well, the weirdness from my perspective is that 8.1.2 is downloadable and marked as a release: http://download.eclipse.org/jetty/
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224721#comment-13224721 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
weird -- I'm guessing that page is out of date... but it is not confidence inspiring!
Jetty 7/8 have been around since 2009. Work has even started on Jetty 9
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Uwe Schindler (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224836#comment-13224836 ]
Uwe Schindler commented on SOLR-3159:
-------------------------------------
This was also the reason why before Ryans commit in the lib/ folder was a genric servlet-api-2.4.jar while in the example there was the jetty-supplied.
For compiling the solr source code we should in all cases use 2.4, otherwise we cannot gurantee that we are still compatible with older servlet containers like JBoss or Tomcat 6.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Bill Bell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13233174#comment-13233174 ]
Bill Bell commented on SOLR-3159:
---------------------------------
Can you point to the JENKINS issue? If there is not one, we should post an issue on the JENKINS JIRA...
Are you saying that it might be isolated to JENKINS? I have been avoiding NIO - maybe for the wrong reasons. I heard that BIO ran better on Windows 2008 ?
(DOn't ask why we are running SOLR on Windows).
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Hoss Man (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225675#comment-13225675 ]
Hoss Man commented on SOLR-3159:
--------------------------------
https://jira.codehaus.org/browse/JETTY-1489 - apparently fixed in 8.1.2 ?
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Stefan Matheis (steffkes) (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227459#comment-13227459 ]
Stefan Matheis (steffkes) commented on SOLR-3159:
-------------------------------------------------
bq. Another little glitch i just noticed is that aparently with the new jetty configs JSP support isn't enabled? loading http://localhost:8983/solr/ works fine, but http://localhost:8983/solr/admin/dataimport.jsp gives a 500 error "JSP support not configured"
Yepp, just created SOLR-3234 for that. We have just missed them, while sorting out all JSP-Files in SOLR-3202. They should be no longer required ,since we use now Handlers and Servlets for all the UI related stuff.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Shawn Heisey (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13225685#comment-13225685 ]
Shawn Heisey commented on SOLR-3159:
------------------------------------
bq. The pile of config files in etc are for the various features you can enable – this just includes the ones I think we need
I checked out trunk from SVN and took a look at the example etc directory. It only includes jetty.xml and webdefault.xml, so once things on this issue have settled down, I'll compare my config with yours and go ahead with an upgrade on my test server.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Robert Muir (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224732#comment-13224732 ]
Robert Muir commented on SOLR-3159:
-----------------------------------
I mean i lean towards jetty 8 anyway, because the work is already done :)
We can't just look at the stability of jetty itself: having the single jetty version across both trunk/branch_3x
will mean we have more testing for our integration, which is probably what matters the most anyway.
Just asking questions.... not an opinion on this patch because i don't have enough knowledge.
as long as my unicode test passes I am +1!
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Massimo Carro (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273124#comment-13273124 ]
Massimo Carro commented on SOLR-3159:
-------------------------------------
I use solr 4 with jetty 8 : highlight inside qt definition doesn't go.
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Assignee: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13224703#comment-13224703 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
committed to trunk in #1298108
What are thoughts on porting to 3.x? I am -0 for a few reasons:
* 3.6 is hopefully soon -- I would like to see this test for a while
* JSP complications
** requires JDK (not just JRE)
** the start.jar would need to be run with:
{code}
java -jar start.jar -OPTIONS=jsp
{code}
- - - -
Shawn, to run this with any .war file you can put the .war file in webapps
The pile of config files in etc are for the various features you can enable -- this just includes the ones I think we need
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Hoss Man (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226349#comment-13226349 ]
Hoss Man commented on SOLR-3159:
--------------------------------
bq. Wierdly, I don't see an annoucement for v8.1.2
Sorry .. poor wording on my part: the issue is marked fixed in 8.1.2 but the jetty Jira system lists 8.1.2 as unreleased (ie: fixed on jetty's 8.1 branch for hte next release i guess)
---
Another little glitch i just noticed is that aparently with the new jetty configs JSP support isn't enabled? loading http://localhost:8983/solr/ works fine, but http://localhost:8983/solr/admin/dataimport.jsp gives a 500 error "JSP support not configured"
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Commented] (SOLR-3159) Upgrade to Jetty 8
Posted by "Ryan McKinley (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226978#comment-13226978 ]
Ryan McKinley commented on SOLR-3159:
-------------------------------------
They had a real 8.1.2 release... and I upgraded the .jar files in revision: 1299325
> Upgrade to Jetty 8
> ------------------
>
> Key: SOLR-3159
> URL: https://issues.apache.org/jira/browse/SOLR-3159
> Project: Solr
> Issue Type: Task
> Reporter: Ryan McKinley
> Priority: Minor
> Fix For: 4.0
>
> Attachments: SOLR-3159-maven.patch
>
>
> Solr is currently tested (and bundled) with a patched jetty-6 version.
> Ideally we can release and test with a standard version.
> Jetty-6 (at codehaus) is just maintenance now. New development and improvements are now hosted at eclipse. Assuming performance is equivalent, I think we should switch to Jetty 8.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org