My logs are getting full of exceptions like this:
8884902 [qtp1075738627-4458] WARN o.eclipse.jetty.server.HttpChannel - /upload
java.lang.NullPointerException: null
78884902 [qtp1075738627-4458] WARN o.e.j.u.t.strategy.EatWhatYouKill -
java.lang.IllegalStateException: s=IDLE rs=COMPLETED os=ABORTED is=READY awp=false se=false i=false al=0
at org.eclipse.jetty.server.HttpChannelState.unhandle(HttpChannelState.java:416)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:538)
even though the system seems to be working normally. It's a bit concerning that "normal" operation would include a flood of such logs. I can't find anyone else getting exceptions like this.
This is all on the current version of Jetty, with a Spring Boot 2.3.1 application, using the http2 connector. It happens on a few different URIs in the application with no clear pattern.
Any ideas on this? I don't want to accept having non-stop exceptions as normal behavior of this system.
Looking through the source of HttpChannelState I can see that the exception is formed from:
("s=%s i=%b a=%s",_state,_initial,_async);
But I can't trace much further what this means.
Your usage of Servlet Async Processing or Servlet Async I/O could be the cause.
The output stream being aborted like that is very odd as well.
The origin (in the code) for the 8884902 [qtp1075738627-4458] WARN o.eclipse.jetty.server.HttpChannel - /upload java.lang.NullPointerException: null
is https://github.com/eclipse/jetty.project/blob/jetty-9.4.31.v20200723/jetty-server/src/main/java/org/eclipse/jetty/server/HttpChannel.java#L600
But why it doesn't have a stacktrace is also bizarre.
You should file this as an issue at the Eclipse Jetty issue tracker https://github.com/eclipse/jetty.project/issues and work with us to get to the bottom of your issue.
If you can replicate easily enough that would make things easier to troubleshoot.
Since you are using HTTP2, make sure you upgrade both your version of Java and Eclipse Jetty.
Related
We're currently facing some issues trying to start a Service in Windows, which is an executable file and the output of a compiling process using .NET framework for C++ (Windows\Microsoft.NET\Framework\v2.0.50727).
We are able to compile, start and execute the exact same service in our DEV Environment, which consists of Windows 7 installed in Virtual Box with VisualStudio2005 (it's old software, I know...).
When we do it in our Test environment, we get a timeout error when trying to start the Service (1053: The Service Did Not Respond to the Start or Control Request in a Timely Fashion.). The server is running WindowsServer 2008 R2 Standard. We already tried to change the timeout time, without success. We also compiled the source code using the same Visual Studio 2005 SW and although we were able to compile it successfully we are still getting the same timeout message.
We are currently trying to understand what's objectively causing the different behaviour. The most obvious difference is the windows version, naturally, but since the compilation output appears identical and there are no errors during the compilation process in both environments and both output logs are identical as well we are running low on ideas to identify and validate objective differences. Our latest approach consists in trying to understand if by using Dependency Walker (dependencywalker.com) we are able to identify any issue regarding DLLs (we also checked if there is any corrupt DLL or system file in the environment and there isn't any, using the windows command for it). We're also checking some of the suggestion made on the following post: Error 1053 the service did not respond to the start or control request in a timely fashion.
Any one faced a similar issues? If so, can you suggest any kind of approach to identify the reason why the service isn't staring, other than the ones here mentioned?
Thanks in advance.
We ended up extending the timeout time regarding Service startup in Windows to 10 minutes followed by the necessary restart and we managed to start the service normally and almost immediately, which makes us think that the timeout time was never really an issue here. Although we haven't been able to pinpoint the exact cause we are still inclined to think that it was a Windows/Server related issue.
I'm trying to call any WCF service in code locally which gives me the following exception:
WinHttpException: The group or resource is not in the correct state to perform the requested operation.
Some code example: await service.ReadMultipleAsync(filters.ToArray(), null, 1);. This might not say anything though. The weird thing is that it worked before updating windows 10. This might be a coincidence, but I have absolutely no code changes.
I can also talk directly to the WFC service through some tooling, so it cannot be some sort of IP blocking or firewall. But doing this through code results in the error, both using Kerstel or IIS Express.
Possible relevant packages:
.Net core - 2.2
System.ServiceModel.... - 4.4.0
I'm currently clueless. Any help would be appreciated!
Edit:
A more detailed exception:
System.Net.Http.WinHttpException (8007139F, 5023): The group or resource is not in the correct state to perform the requested operation
at System.Threading.Tasks.RendezvousAwaitable`1.GetResult()
at System.Net.Http.WinHttpHandler.StartRequest(WinHttpRequestState state)
I did a rollback from windows 10 version 1903 to 1803 and it suddenly started working again. Not really a solution but it works. Still no clue on what's wrong. Might be a bug?
Good morning,
I am facing a crash in my application. When the user tries to start it, he waits like a minute and then a std::exception is raised. Really I could not reproduce the bug by myself, but it seems quite a common problem.
The only thing I could track is the following line in syslog:
BUG in libdispatch client: kevent[EVFILT_MACHPORT] monitored resource vanished before the source cancel handler was invoked
Then, I start to google it and I can not find much more...I can only "suppose" that is some problem with GCD (that I do not use afaik, or at least not directly...). What I saw in Internet is that it is related with MacOSX Sierra. But the majority of forum have no answer, just a lot of tries without a unique result. Maybe the only web page that seems a bit clear about a workaround (that I have not tested, and anyway I do not want to use) is this.
So...:
someone has clear what can cause the exception in libdispatch?
someone can give me some good link, official documentation or something?
Is true that can be a bug in Sierra without updates?
Could it be related with the installer of an application?
Someone knows a way to reproduce this exception with a test program?
This libdispatch log message is not fatal, and is almost certainly not related to your crash, which sounds like an abort due to an uncaught C++ exception (without a crashreport/backtrace it is difficult to say anything more). libdispatch does not itself generate any C++ exceptions FWIW.
As to the meaning of that specific log message, it relates to the following section in the dispatch_source_create(3) manpage:
CANCELLATION:
Important: a cancellation handler is required for file descriptor and mach port based sources in order
to safely close the descriptor or destroy the port. Closing the descriptor or port before the cancellation handler has run may result in a race condition: if a new descriptor is allocated with the same
value as the recently closed descriptor while the source's event handler is still running, the event
handler may read/write data to the wrong descriptor.
If you see the EVFILT_MACHPORT "vanished" log message, somebody in your process has violated that API contract and deallocated a machport while a dispatch source was still monitoring it (causing the kernel to generate an EV_VANISHED kevent), see the source code.
I want to test air applications and air libraries using flexmojos 3.9-SNAPSHOT.
However, although flexmojos does indeed has support for air, it tries to run the swf generated by the build using flash player, and as I need to use air native libraries I wanted to run the tests using adl (AIR debug launcher).
To do this, I cloned flexmojos in github.com to this repository (http://github.com/mi007/flexmojos). I then created a class that created an -app.xml for the TestRunner.swf file that was generated and ran:
adl TestRunner-app.xml
However, before the Test ends, it should call the server in the port 13540 to report something. When that happens, I'm getting the following error:
Error #2044: Unhandled securityError:. text=Error #2048: Security sandbox violation: app:/TestRunner.swf cannot load data from 127.0.0.1:13540.
at org.sonatype.flexmojos.unitestingsupport::ControlSocket/connect()[/Users/rafael/p2d/others/flexmojos/flexmojos-testing/flexmojos-unittest-support/src/main/flex/org/sonatype/flexmojos/unitestingsupport/ControlSocket.as:46]
at org.sonatype.flexmojos.unitestingsupport::TestApplication/runTests()[/Users/rafael/p2d/others/flexmojos/flexmojos-testing/flexmojos-unittest-support/src/main/flex/org/sonatype/flexmojos/unitestingsupport/TestApplication.as:52]
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at mx.core::UIComponent/dispatchEvent()[C:\autobuild\galaga\frameworks\projects\framework\src\mx\core\UIComponent.as:9408]
at mx.core::UIComponent/set initialized()[C:\autobuild\galaga\frameworks\projects\framework\src\mx\core\UIComponent.as:1169]
at mx.managers::LayoutManager/doPhasedInstantiation()[C:\autobuild\galaga\frameworks\projects\framework\src\mx\managers\LayoutManager.as:718]
at Function/http://adobe.com/AS3/2006/builtin::apply()
at mx.core::UIComponent/callLaterDispatcher2()[C:\autobuild\galaga\frameworks\projects\framework\src\mx\core\UIComponent.as:8733]
at mx.core::UIComponent/callLaterDispatcher()[C:\autobuild\galaga\frameworks\projects\framework\src\mx\core\UIComponent.as:8673]
I know that it is calling the server before in port 13539 successfully, because it prints the test results on the console. I also know that it is opening port 13540 because I was able to telnet to it. However, for some reason it is unable to connect from the air application.
Given the circunstances, I have the following questions:
1) Is there any good documentation that I can read to understand how this security framework works? The only documentation that I found was terribly confusing.
2) Does anyone has any ideas or hints about what might be happening?
3) I have read somewhere that flexmojos hacks the security framework so that flex applications can open a socket to localhost without problems during tests. Is there any documentation about how this is done?
Thanks,
You've got very close to the answer in your comment...
You need to add a line to a file in ~/Library/Preferences/Macromedia/Flash Player/#Security/FlashPlayerTrust yourself, covering the swf you want to run. You can do this by hand directly (all files in that folder will be processed) or by using the Flash Player Settings Manager.
I am building a sharing-service for maemo5. In the example plugin they are calling ULOG_INFO_L at a lot of places, so I have adopted this for my service as well. The problem is that I can't find where the messages goes.
Reading osso-log.h I should define DEBUG or OSSOLOGCOMPILE, which I do and OSSOLOG_STDOUT or OSSOLOG_SYSLOG. I have tried both settings but can't get anything on syslog or stdout (I have no idea where stdout should end up since I am only calling af-sb-init.sh start), and it's not there anyway :-)
Anyone know where I can find my log?
I found out that when using OSSOLOG_SYSLOG it actually logs to the host machine, not the scratchbox environment.