Please help me for below issue,
I am working in Upgrade project. WAS server getting upgrade to Websphere 6.1, Java J2EE application we compiled with IBM JDK1.5.
Now we hosted J2EE application in newly installed WAS 6.1. Client application sending Login request and getting login successfully. If client send next request the session is getting destroyed some session values, So I am getting Null pointer exception.
Can any one say, Is there any settings we need to do in websphere server, or we need to do something in application side.
But it is working fine in TOMCAT server
Related
Issue :
Unable to deploy Spring-Boot application in WebLogic Server.
Description
I am new to Spring boot trying to build a proxy application to route the requests to source system but having issues deploying to weblogic-12c. It's a very simple application that exposes a rest service and then redirects the received request to upstream system.
What did I try ?
Tried log4j version in pom.xml and dispatcher-servlet.xml approaches googling, I've also read the issue is b'coz of the data sources but I don't have any persistence logic and don't need a data source to be configured in weblogic.
Below is the error I am seeing, any suggestions are highly appreciated.
ERROR:
Unable to access the selected application.
Message icon - Error java.io.IOException
Message icon - Error weblogic.utils.compiler.ToolFailureException
I deployed my java application on Bluemix. It's a Spring MVC application with some REST controller to expose web services and some jsp page to create a admin panel.
The JSP pages are in the root of web application (not in WEB-INF directory). If I run the application in local on my tomcat server, everything works, the web services and the JSP, but if I deploy on Bluemix i have this error:
Error 403: SRVE0190E: File not found: /admin/index.jsp
It's a strange error because it says "File not found", but it's not a 404 error, but a 403 (Forbidden), so I think it could be some kind of configuration problem...
Thanks
If your application runs on tomcat locally, then you can try using the tomcat buildpack:
cf push <appname> -b java_buildpack -p path/to/file.war
your problem seems related to your application context root, probably the server.xml resulting after application uploading and staging is not enough to manage it.
Generally speaking before submitting an application on Bluemix it should be better trying to deploy it to a local Liberty server first. If you are able run this application locally on your liberty server, package up the server, and then push the package using the related option from cf cli.
Follow this link https://www.ng.bluemix.net/docs/starters/liberty/index.html
to have a complete reference about java liberty runtime on Bluemix and about its options
In weblogic 10.3.5 I get 403--Forbidden after deploy application, but not exceptions or stack-traces in logs, or stdout. Application(spring) deployed on managed server which working on jdk 8. Also, the application is a web application. How do I get an exception?
I am having a problem deploying my spring websocket service in a Wildfly 8.x server.
I have two Java services running in the wildfly server, one of them is working great but the other one (the websocket one), despite is deployed correctly does not stop in the breakpoints. In fact, when I set the breakpoint it seems as if the server was off.
The deployment folder of my wildfly server created the two directories, one of each services.
I am using jdk 1.8 and Maven 3.2.3.
Thanks in advance for any help!
Hi I'm using tomcat and using Waffle for windows authentication. I'm also connecting to an SQL server using the windows credentials too using microsoft's driver. I have a problem that everytime I reload or redeploy the application, i have to restart tomcat. After some googling i've discovered that the dll was already loaded and thus cannot be reloaded.
I really need to redeploy application as i would need to update some functionality and it is very frustrating to ask the administrator to restart tomcat everytime i update the application.
When i was doing the same with glassfish i managed to work around this issue somehow, but cannot manage with tomcat