I really lost the way here, i'm trying to deploy a springboot application, when I try to upload .war file in a weblogic 12c returns BEA-160228 with error message in title here is my pom.xml:
https://bitbucket.org/snippets/CPernillo/6eg5oe
I've tried a lot of solutions that I found on forums even here in stack but nothing seems to work for me like disable spring-boot-starter-logging (as you can see in pom.xml), add a weblogic.xml to my webapp/WEB-INF folder (here it is):
https://bitbucket.org/snippets/CPernillo/yed5oA
Please stack-experts, help me and thanks in advance.
Update 1
This project has sucessfully deployed in a dev server, without changing anything, the problem is production server.
Fixed!
I Answer only if in future somebody have to pass this bad luck:
Java versions in both weblogic where diferent, spring 2.0.3.REALEASE only supports java 8, so, production server has jdk 7, client's sysadmins gonna have a long night migrating all old projects to jdk 8.
Related
I've just created a fresh web application in Netbeans. Project builds fine. However, once I hit run Tomcat starts up fine, but no browser window opens.
If I go under Services > Apache Tomcat or TomEE > Web Applications I can see 'Please wait...' where my project name should be.
Why isn't Tomcat running my project. If I go to localhost/port I can see that Tomcat is running fine but the project is stuck on 'Please wait...'.
I'm using Tomcat 9, Java 16, Java EE 8 Web, Netbeans 12, and Maven Compiler 3.1. If anything else is need to help then please leave comment or message me and I'll get right back
I can't seem to see any issue in the server logs either. What is the issue?
'Please Wait': https://i.stack.imgur.com/y3AOI.png
Server Log: https://i.stack.imgur.com/LT1dU.png
Can't embed images as I don't have enough rep.
Thanks
Not sure how to close the question so I'll answer it myself in case others run into same issue. Problem was simply that the version of Netbeans (12.0 LTS) I was using wasn't compatible with JDK 16 as #skomisa mentioned in a comment. Thanks.
Payara server not boot after a power failure.
how I can fix and save payaradomain, I have many configurations there.
domain1 works well.
Check for a domain.xml.bak file in the same directory as the domain.xml. You may be able to overwrite the corrupted domain.xml with the autogenerated backup.
This link describes it more for an older version of GlassFish in the "backup" section:
http://docs.oracle.com/cd/E19798-01/821-1753/abhar/index.html
I am using glassfish server.. the application was running smoothly but all of sudden i started getting this message.
build-impl.xml:1073:
Could any suggest me on how to solve this problem
Have you upgrade you netbeans or glassfish recently?
This problem happens sometime when you performed an upgrade with the netbeans IDE or some modules of it.
If you did, you had better try to create a new project or re-install the application in the glassfish again. This may help.
By the way, could you please provide some detailed information so that we can perform some further investigation.
well i don't think it is the good solution however i did not find any other option then the one i have mentioned below to solve this problem.
I uninstalled the GlassFish Server and installed latest version i.e. 4.0 ( You can install the same version, it should work) and then i removed the project from netbeans Projects list. I again created a new project and copied all the required files from the previous project. It worked. The application is now deployed in GlassFish Server 4.0.
However this solution to me is like formatting computer when you cannot solve the problem raised in your PC. If someone could tell me the reason and the way to solve the problem mention above i would be very thankful.
Anyways thanks to Mr lowitty for the suggestion.
So here's where I'm at:
I've installed the Apache Tomcat Server successfully.
I've configured the JAVA_HOME path successfully, and created a /common/lib directory (as opposed to plain /lib) to get around an issue with NetBeans recognising recent versions of Tomcat.
If I select GlassFish 4.0 as my server, instead of Tomcat, everything's fine -- but I don't want GlassFish 4.0 as my server, as I'm working through a book on Java WebApps and don't want to run into intractable problems further down the line.
When I select Tomcat as my server, I run into the problem that the dropdown menu to select my "Java EE Version" decides it doesn't want to give me any options at all.
Has anyone experienced this problem before, or can anyone offer a rough guess as to what my problem might be?
Thanks in advance!
EDIT: Update - it's not a problem with the JDK classpath of Tomcat. Tomcat works fine on the .jsp files it came bundled with.
I had the similar problem with Tomcat 8. But after downloading Tomcat 7.0.47 I can now choose from Java EE 5 and 6. Hope that helps.
Googled everything, but can't find solution for my problem.
When i'm trying to deploy my project to Tomcat, i have such errors in Tomcat log:
SEVERE: Error configuring application listener of class com.sun.faces.config.ConfigureListener
java.lang.NoClassDefFoundError: javax/servlet/ServletRequestListener
I tried to deploy it from fresh Netbeans 6.8 to fresh Tomcat 6.0.26, but the problem is still there.
Servlet-api.jar is in the tomcat/lib folder. Tried to replace it with the newest, but problem is still there.
No compilation errors. Everything is correct.
Problem started suddenly. No code changes, no new jars added.
Help?
UPD: contents of WEB-INF/lib:
hibernate3.jar
hibernate-testing.jar
quartz-1.7.2.jar
quartz-all-1.7.2
servlet-api-2.5-20081211
java.lang.NoClassDefFoundError: javax/servlet/ServletRequestListener
The javax.servlet.ServletRequestListener is newly introduced since Servlet 2.4 API. That your environment cannot seem to find it can be caused by two things:
Either the web.xml is declared as Servlet 2.3 or older which forces the server to Servlet 2.3 compliance mode, or the server in question doesn't support Servlet 2.4 at all.
Classpath is really, really messed up. You should never put/change/remove libraries in JRE/lib, JRE/lib/ext or Tomcat/lib without understanding what you're doing. You should never put appserver-specific libraries in Webapp/WEB-INF/lib because that doesn't make any sense.
To fix 1, ensure that your web.xml is declared as at least Servlet 2.4. Preferably the newest which the server can support. Tomcat 6.0 supports Servlet 2.5, so declare web.xml accordingly.
To fix 2, cleanup the classpath of all pollution. Invest some more time to learn more about the phenomeon "classpath". Handle it with care.
Tomcat doesn't ship with JSF libraries, so you have to include those in WEB-INF/lib. From the listing above it is obvious that your are missing those. For JSF2 go here.
Moreover you do not need servlet-api in WEB-INF/lib, it is a provided library.