Tomcat 7 with SpringMVC, missing "Server startup" success message - spring-mvc

Up until recently my catalina.log used to report the following:
Mar 19, 2015 4:49:20 PM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring FrameworkServlet 'dispatcher1'
Mar 19, 2015 4:49:20 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-9080"]
Mar 19, 2015 4:49:20 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 53209 ms
which I look for during an automated deployment to know whether my servlet started OK. Recently, I no longer get this message in catalina.out. However:
there are no startup errors
logging is working
the server seems to be working perfectly, AFAICT (responds to all requests)
kill -3 doesn't show anything helpful that I can see
So,
What might have caused the "Server startup" message to stop being printed (and yet the server to accept connections)?
In (annotation based) Spring MVC, there a good place where I can place a hook and output a custom "servlet startup success" message?

The "standard out" may no longer be going to catalina.out. What's in your log4j property file? And what are you using to start Tomcat?
You could impelement a ServletContextListener to be aware of when the Servlet based application is ready to accept requests.
http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextListener.html#contextInitialized(javax.servlet.ServletContextEvent)

Related

Disable lifetime application logging from a BackgroundService in .NET 7

I want to remove messages such as "Application started. Hosting environment: Production; Content root path: ..." or "Application is shutting down" from my .NET 7 windows service.
I tried to mess with the Logging json object in the appsetting.json file to disable logs from Microsoft but it didn't work... I also tried to add builder.ClearProviders() and builder.UseConsoleLifetime(x => x.SuppressStatusMessages = true) but I get an error 1053 when starting the service.
Is there a solution to not print out these messages?

SingalR Client Return Error 405 Method is not allowed

I'm using SignalR for communication between my backend server and winform client.
Well I tried to start the hub connection between those 2 but I got error from the client.
It throw exception 405 Method is not allowed.
It said:
{
StatusCode: 405,
ReasonPhrase: 'Method Not Allowed',
Version: 1.1,
Content: System.Net.Http.StreamContent,
Headers: \r\ n {
\
r\ n Date: Tue, 27 Dec 2022 06: 42: 18 GMT\ r\ n Server: Kestrel\ r\ n Content - Length: 0\ r\ n Content - Type: text / plain\ r\ n
}
}
It did some research about this error and tried everything from enable Cors, add useSignalr... which I'm already did. Anyone having the same issue?
About the package: I'm using Microsoft.AspNet.SignalR.Core 2.4.3 on Server, Microsoft.AspNet.SignalR.Client 2.4.3 on Client.
This is my Service try the hubconnection:
My Service with the hub connection
405 Code
I tried to enable Cors, using the same version on server and client for SignalR, use differ packages.
I was excepting that it will hit my Hub on my server but no.
I authored the link Jason referenced and I think that link does apply if you are trying to run .NET 4.x (client/server) with .NET CORE 6 (client/server). They don't mix and cannot be used together.
However, from your scenario it looks like you are running - "Microsoft.AspNet.SignalR.Core 2.4.3 on Server" and "Microsoft.AspNet.SignalR.Client 2.4.3"
Which are fine for a .NET 4.7/8 server. 1 issue I see here is "Content: System.Net.Http.StreamContent," will not work because this version does not support streaming (.NET CORE 6/7 does).
Your overall problem may be resolved by checking to see if you can or have .NET 4.7/8 on your server. According to this you should be able to have both but everything will still run in IIS (meaning .NET CORE 6/7 apps must as well in their own app pool).
Hopefully one of these help you resolve your issue.

How do you do server side rendering with eureka and springMVC

I am trying to create a set of springMVC microservices with server side rendering using JSPs. My springMVC apps are having controllers that returns model objects to JSP's that does the view.
My JSP's are in "META-INF/resources/WEB-INF/jsp/" folder. When I run the Springboot application it works without any issue and my model gets displayed properly in the browser.
However when I use eureka with zuul to do service registry and go through a common app service, I am getting the following error
This application has no explicit mapping for /error, so you are seeing this as a fallback.
Wed Aug 24 23:30:25 IST 2016
There was an unexpected error (type=Internal Server Error, status=500).
GENERAL
And in the console it states
com.netflix.zuul.exception.ZuulException: Forwarding error
at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.handleException(RibbonRoutingFilter.java:158) ~[spring-cloud-netflix-core-1.1.5.RELEASE.jar!/:1.1.5.RELEASE]
at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.forward(RibbonRoutingFilter.java:133) ~[spring-cloud-netflix-core-1.1.5.RELEASE.jar!/:1.1.5.RELEASE]
at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.run(RibbonRoutingFilter.java:79) ~[spring-cloud-netflix-core-1.1.5.RELEASE.jar!/:1.1.5.RELEASE]
at com.netflix.zuul.ZuulFilter.runFilter(ZuulFilter.java:112) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.FilterProcessor.processZuulFilter(FilterProcessor.java:197) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.FilterProcessor.runFilters(FilterProcessor.java:161) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.FilterProcessor.route(FilterProcessor.java:120) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.ZuulRunner.route(ZuulRunner.java:96) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.http.ZuulServlet.route(ZuulServlet.java:116) ~[zuul-core-1.1.0.jar!/:1.1.0]
at com.netflix.zuul.http.ZuulServlet.service(ZuulServlet.java:81) ~[zuul-core-1.1.0.jar!/:1.1.0]
Any idea why I am getting this. I think this is due to the way that I might be having the JSP's (view) rendered.
thanks for the quick response. I found this to be a an issue with my understanding of zuul routes. Once I corrected the routes everything worked properly through eureka.

push notification not receiving in an iphone device

I followed all the steps mentioned in this link, https://developer.ibm.com/mobilefirstplatform/documentation/getting-started-6-3/notifications/push-notifications-hybrid-applications/ and I am able to successfully sent push notifications for android phones. But iPhone is not receiving any notification.
I have properly added APNS certificates and 2195, 2196 ports are opened.
In mobilefirst console, push notification section showing my iphone received 10 messages from event sources. When I looked the tomcat logs it showing following warning
Nov 05, 2015 3:48:48 PM com.worklight.gadgets.serving.ClientConfigProfileServlet piggybackConfigProfile
WARNING: com.worklight.core.messages:could not piggyback configprofile due to invalid or incomplete headers sent from client
Nov 05, 2015 3:48:48 PM com.ibm.pushworks.server.notification.Mediator run()
SEVERE: FPWSE1067E: An Exception occurred in the mediator.
java.lang.RuntimeException: Not yet implemented
at com.ibm.pushworks.server.notification.Mediator.updateDeviceSubscriptionByToken(Mediator.java:130)
at com.ibm.pushworks.server.notification.gcm.GCMMediator.updateDeviceSubsciption(GCMMediator.java:172)
at com.ibm.pushworks.server.notification.gcm.GCMSender.sendAndVerify(GCMSender.java:169)
at com.ibm.pushworks.server.notification.gcm.GCMMediator.sendOrWait(GCMMediator.java:139)
at com.ibm.pushworks.server.notification.gcm.GCMMediator.sendNotification(GCMMediator.java:128)
at com.ibm.pushworks.server.notification.Mediator$2.run(Mediator.java:87)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
Is above warning is the clue for the issue? If so what I'm missing? Any suggestions will help.
This was recently resolved.
Visit IBM Fix Central and download the latest iFix for your MobileFirst Platform Foundation release. Use the updated Studio/CLI package to re-build your application.

How to solve error "connection:closed" in SharePoint2010?

Hi , when i deleted site under mysite collection the webapplication
doesnot work and i had this error
HTTP/1.1 200 OK Server: Microsoft-IIS/7.5 Date: Fri, 13 Dec 2013
07:03:54 GMT Connection: close
When I checked the log file I had this :
From Microsoft support page
Cause
This is caused by insufficient permissions for the search service account on the SharePoint Server. Verify that no group policies have been set on the local user groups 'WSS_WPG' and 'WSS_ADMIN_WPG'.
Resolution
Check the system event log for group policy changes that may have occurred around the same time as the search errors. Determine if any group policies have altered permissions on 'WSS_WPG', or WSS_ADMIN_WPG groups
From the folder %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\14\bin run the Psconfig command-line tool for SharePoint Products as follows:
Psconfig -cmd secureresources

Resources