After upgrade from 2.7.2 to 2.7.3 or 2.7.4 my quarkus project doesn't start anymore. I get following Exception:
Caused by: java.lang.NoSuchFieldError: ACCESS_CONTROL_ALLOW_PRIVATE_NETWORK
at io.vertx.core.http.HttpHeaders.<clinit>(HttpHeaders.java:106)
at io.vertx.core.http.impl.headers.HeadersMultiMap.<clinit>(HeadersMultiMap.java:63)
at io.quarkus.smallrye.openapi.runtime.OpenApiHandler.<clinit>(OpenApiHandler.java:24)
at io.quarkus.smallrye.openapi.runtime.OpenApiRecorder.handler(OpenApiRecorder.java:35)
Maybe it is releated to the upgrade of open api https://github.com/quarkusio/quarkus/pull/23886
When I disable open api it starts
quarkus.smallrye-openapi.enable=false
Your problem seems to be related to this one, So i believe we have 2 workarounds:
First try using different browser than chrome (if you don't, go directly to second step)
Then, try enabling CORS in your application.properties like following :
quarkus.http.cors=true
My problem was caused by a dependency with an older version of netty.
Updating netty fixed the problem.
https://stackoverflow.com/a/71423882/9651670
Thanks, this answer helped me a lot. I had to force a specific netty version on a previous update for azure/microsoft libs to work. Now they work with default managed version from quarkus and i removed netty-bom from dependencymanagement instead of updating it.
Related
I am developing a simple xmpp server component,while I have been stucked by a little error for few days.After searching and trying all the solution,nothing gets improved. Some of the solutions did not work at all,others can not express how to fix it exactly.So helpless am I that I decide to ask this question by myself.
I use the Whack and Tinder as the externalcomponent library,everything works fine except this error cause by this code :ExternalComponentManager mgr = new ExternalComponentManager
That is the error :
Exception in thread "main" java.lang.NoClassDefFoundError: org/xmpp/component/Log
at Main.main(Main.java:10)
Caused by: java.lang.ClassNotFoundException: org.xmpp.component.Log
The instantiation of the ExternalComponentManager require the log class,which shoule be located in the Tinder library,but the tinder library has no more include this class.So ,how to fix this error ,is anything I have miss ? by the way,I have refrence the SVN of the whack and add all the jar files in my project classpath . I hope someone can help me to solve me ,Thanks.
Please use tinder 1.2.2 version. org.xmpp.component.Log has been removed in tinder 1.2.3 version. I had the same issue and downgraded the tinder jar to 1.2.2 which solved it. The whack jar version used is 1.0.0
Im in the process of evaluating the new interface of Apache Archiva. The user interface is really good and I was able to configure most of the settings.
However, when I try to deploy the artifact through eclipse Im getting the below error.
Error code 405, HTTP method PUT is not supported by this URL
I donot get this when I use the Apache Archiva 1.3.6.
Any idea?
This can happen if your repository URL is incorrect. See GitHub issue 4.
I have setup the new Archiva version 2.0.0. Apparently this issue has been fixed with the latest version.
I just upgraded to the App Engine 1.7.6 SDK for my python app and realised that breakpoints no longer work in PyDev (Eclipse plugin) when using the new dev_appserver.py.
Does anyone know of a way of enabling them again? I assume the new server is spawning a new process for the web server, and the debugger isn't attaching to that one. I'm not sure how to configure it to do that though.
In the meantime I am using the old_dev_appserver.py server.
UPDATE 2012-07-27:
Following the comment, I verified, the issue is solved after updating to
PyDev. 2.8 and App Engine 1.8.2
OBSOLETE:
I found the following analysis of the problem at googleappengine issues tracker
The reason why PDB doesn't work is because dev_appserver is using
stdin/stdout for interprocess communication. Python has built-in
libraries for IPC: http://docs.python.org/2/library/ipc.html.
dev_appserver should use these, and then stdin/stdout can be left
alone so that PDB still works.
So it seems that there is no workaround, rather than reverting to use old_dev_appserver.py
UPDATE 2013-04-23:
Inability to debug is annoying.
Many developers complain about it
PyDev Breakpoints in App Engine 1.7.6 broken?
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/ep5BWYKpQpU
https://groups.google.com/forum/?fromgroups=#!topic/google-appengine/TCQuJpF44cY
https://code.google.com/p/appengine-devappserver2-experiment/issues/detail?id=28
https://code.google.com/p/googleappengine/issues/detail?id=9012
I am keeping track of the development of this issue here:
http://goo.gl/XRU01
Yep, ran into the same problem.
Open your Run/Debug Configuration and set the Main Module to:
${GOOGLE_APP_ENGINE}/old_dev_appserver.py
Do you mean pdb.set_trace() isn't working?
Look for the function MonkeyPatchPdb() in google/appengine/tools/dev_appserver.py
Run that somewehere in your own project before you use pdb and it should fix it.
Must be the way Eclipse is set up. Anyone have any ideas?
Exception in thread "main" java.lang.NoSuchMethodError: com.sun.jersey.client.apache.DefaultApacheHttpMethodExecutor.headerValueToString(Ljava/lang/Object;)Ljava/lang/String;
at com.sun.jersey.client.apache.DefaultApacheHttpMethodExecutor.writeOutBoundHeaders(DefaultApacheHttpMethodExecutor.java:271)
It looks like DefaultApacheHttpMethodExecutor.headerValueToString was removed from the Jersey library after its 1.7 release:
http://java.net/projects/jersey/lists/commits/archive/2011-06/message/12
Here are some options:
Replace your current version of Jersey and with an older version of Jersey:
Use a newer version of the JIRA REST client. I don't know if any newer versions support the change to the Jersey API.
Actually, the "headerValueToString" method is supported in jersey-client-1.5.jar. Some later versions don't support the method yet, such as jersey-client-1.15.jar.
I use "jersey-apache-client-1.8.jar" downloaded from "http://download.java.net/maven/2/com/sun/jersey/contribs/jersey-apache-client/1.8/" and it works well
I'm trying to get up and running with Virgo, and I'm following along with what appears to be an excellent tutorial, but I'm at section 7.2 and I just can't figure out why EclipseRT / Virgo doesn't appear in my list of options.
So far I've been using SpringSource Tool Suite (STS) as the guide recommended and have installed all the Spring dm Server Tools and Developer Resources bundles.
Has anyone else run into this issue or have a solution to getting the EclipseRT/Virgo server adapter?
Virgo 2.1.0.RELEASE and STS 2.5.0.RELEASE are both now out. The problems you had with the docs should be resolved. The documentation has also been updated to show the latest information as well.
Be aware that the STS 2.6.0 upgrade removes this server adapter! Refer to the STS JIRA entry STS-1690 for details on this removal. You can simply go to the Dashboard > Extensions tab and select "dm Server Support Extension" to put it back.
Hey, have a look at this eclipse forum for virgo
Seems like you have to get used to playing with the update sites until you find the right one. I imagine that by the time anyone reads this the url will probably have morphed every so slightly yet again. Sigh. Comes of playing with tech while they're still actively releasing.
In case someone is searching for more recant information, one need to install DM Server Tooling from http://dist.springsource.com/release/DMS-TOOLS/update to get Virgo in the server add dialog.
I've been just playing around with Virgo 2.1.1 and Eclipse STS 2.7.1.
Indeed there is no Virgo server adapter, but you can install it from this update site:
http://download.eclipse.org/virgo/milestone/IDE
For the latest version of STS (3.1.0), I tried many ways suggested, and find only the Eclipse Virgo/Tooling wiki works.
(http://wiki.eclipse.org/Virgo/Tooling#Install_Eclipse)
It adds the EclipseRT/Virgo adapter in STS 3.1.0.