For a particular reason i developed a web app in apache tomcat 7.x and now i have to deploy it in weblogic server 10.3.3, in my project i use JSF 2.0 and Primefaces 3.0M2 and every thing works fine under tomcat container, but in WLS i get and error on startup, a FileNotFoundException when loading primefaces-3.0M2.jar!/META-INF/faces-config.xml, but that's not all, some pages does not display and in the logs there's and entry saying: *SEVERE: jsf.cannot_instantiate_behavior_error null*. I was thinking maybe WLS does not load the primefaces' behaviors and i put in my faces-config.xml the content of primefaces' faces-config.xml, but still nothing, any help would be accepted.
Related
I encountered a 404 error while trying to access a Spring Boot web app on Tomcat 10. The war is designed and work OK with embedded Tomcat (thru the cmd: mvn spring-boot:run). An example of invocation is http://localhost:8080/api/tutorials. The war file then is deployed in a normal Tomcat, but 404 error in both cases: http://localhost:8080/api/tutorials or http://localhost:8080/api, but OK if http://localhost:8080 (Tomcat welcome page)
I'm using Windows 10, Tomcat 10. Tomcat port, url...is carefully verified correctly
Could anyone help please, thanks much
The attached is my app deployed on Tomcat (no index.html or so)
enter image description here
I am facing a weird issue and I have no idea what is the cause of the problem. Specifically I am deploying my application (.war file) locally on Oracle WebLogic Server successfully.
When I open my application on the browser everything works fine. Suddenly I noticed that some of the recourses files (mine js,css files as well as libraries files) contains duplicated content as you can see the below picture
I tried open my application on multiple browser but still the problem exists.
I have also deployed the application on Payara server and I am not facing the issue but when I deployed it on WebLogic this issue occurred. So is this an oracle bug? Does someone else faced this problem too ?
Notice: I am using WebLogic 14c but the same issue exist in older versions too(12c).
I have just upgraded our ASP.NET Core 2.2 web application to 3.0. It builds and deploys fine. The problem is when I go to run it from our IIS server. This was running perfectly fine as a Core 2.2 web app, but now fails since upgrading to Core 3.0.
When I launch the web app from the commandline there are no reported errors.
When I launch the application from the browser the Windows logs indicate that the app started correctly.
The app then fails with an HTTP 500 error. Here are the IIS log entries.
We're using Windows Server 2012 R2 with IIS 8.5.9600.16384
The app appears to start correctly but then fails with an HTTP 500 error. Has anyone else seen this or something similar? Any ideas how to diagnose / fix the problem?
UPDATE
I've attached the VS 2019 debugger to the deployed app via the w3wp.exe process and it's not even hitting any of the middleware (I have a breakpoint at Startup() in Startup.cs).
I've tried changing the application pool settings e.g. identity, .NET version but to no avail.
When I launch the site from the web server I get the following error message which doesn't really tell me anything.
I can't see what's causing the problem.
.NET Core 3.0 uses the in-process hosting model by default. You may need to upgrade the .NET Core Hosting Bundle.
You will check web.config "aspNetCore"
<aspNetCore processPath="dotnet" arguments=".\Api.dll" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" />
maybe proccessPath is wrong.
if it doesn't solve problem , write to log step step startup.cs.
Maybe throw error in startup.cs
After investigation and comparison of the build artifacts that the build produces vs the deployed app, I discovered that the appsettings.json was not being deployed. No idea how or when this started failing, but it caused the app to generate an HTTP 500 error message. Our app's Azure ADB2C settings are contained in this file so it was crashing trying to authenticate but couldn't find the authentication settings.
There was no obvious error being generated and everything seemed to be loading fine. It was at the point at which the app was trying to authenticate that it was failing. All working now.
Mono 3.2 MVC4 WebAPI application is running in Debian x64 VPS server. Mono is compiled from source and 4.5 subtree is used.
Application requires Chrome or Safari browser.
After refreshing browser window several times server does not work properly. I tried all known free possibilites:
Apache + mod_mono
After pressing browser refresh button several times server randomly returns 500 error for some pages
and apache error log contains "failed to map path" exception.
I posted it in
https://stackoverflow.com/questions/20356779/how-to-fix-failed-to-map-path-errors-in-mono-mvc4-application
and in
Mono ASP.NET mailing list without any response.
There are number of mono applications in server, maybe mod_mono selects wrong thread or is there some bug in webapi mapping implementation in mono.
Nginx + mono-fastcgi-server4.exe
Holding down F5 key causes 200% CPU usage forever in mono-fastcgi-server4.exe
I posted it in
https://stackoverflow.com/questions/20512978/how-to-limit-mono-197-cpu-usage-in-mono-fastcgi-server
and in
Mono ASP.NET mailing list without any solution.
Is looks like there is bug in mono fastcgi server or it is not compatible with mono 3.2
Using xsp4.exe directly
It causes "server does not return data" in Chrome if browser window is refreshed several times.
I posted this in
https://code.google.com/p/chromium/issues/detail?id=329311
without response.
Maybe xsp4 does not implement http protocol properly.
Havent tried ServiceStack since it cannot used for closed source development which is required. Also application uses also images, css, js files and MVC views which needs also served.
How to create proper server for mono which returns correct data ?
When 500 errors happen, somewhere in the mono class libraries an exception was thrown, you can find out more by using tracing:
mono --trace=E:System.Exception YourApp.exe
This way it's very possible that you find out what is causing the load problems you're seeing in each case (to do this for mono-fastcgi, you would need to add the trace argument in the script that calls mono-fastcgi-server4.exe).
This is with GF 3.1.1 build 12.
I have a JSF 2 web application that uses EclipseLink 2.3.0 as the back end JPA provider. You can see the deployment here.
When I use the admin console to redeploy, it uploads the WAR file just fine, then all hell breaks loose. As soon as someone accesses a page the log fills with exceptions usually related to attempting to do operations on a closed EntityManager. If I let it go on, GlassFish degenerates and pretty much crashes -- I can't get any response anymore on the admin port.
If I do a reload, then it seems to work OK. So my question is, what kind of application can do a redeploy without a reload? Is there something I can do to my application to let do a smooth transition from one version to the next?