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!
Related
I tested the Sparklr demo for Spring OAuth 2 on this server Jboss Enterprise 6.1.0 and I get a 404 for /oauth/token. The same war works great on tomcat 8, get a token back no problem.
Do you know how I can fix this server to work with Spring OAuth 2? Or why the same war behaves differently on the two different servers?
Here is the source for the Sparklr demo.
https://github.com/spring-projects/spring-security-oauth/tree/master/samples/oauth2/sparklr
I tried it on the new Jboss EAP 7.10 and Sparklr demo is working great. Fortunately we upgraded the jboss and this fixed it.
If i was using apache tomcat as web server then i can simply take the Jar file and deploy in apache running in windows.
How can i deploy same when using Eureka Server in windows?
Do we have any server installation of Eureka?
Kiran, Each Spring Boot application you developed is standalone application. Whenever application is built embedded tomcat is packed inside the package. So it means it does not require extra effort for you side, just port the application to target machine and double click the application -> it will start its magic.
thus, created package is not suitable for separate running tomcat as it contains unnessary stuff.
If you don't want to deploy on separate tomcat instead of standalone then follow guide
http://docs.spring.io/spring-boot/docs/current/reference/html/howto-traditional-deployment.html
I've developed a spring integration component that is to sit on a server and process messages coming in over an inbound RMI channel do some processing/filtering and then send out some messages over a different RMI channel.
Currently, for testing, I've been running it using a Main class that just loads the context, which sets up the inbound RMI gateway and it's working fine. But I don't think that this is appropriate for a production environment.
What is the best way to deploy this type of project to a server?
If I were working in a .Net I'd be deploying this type of application as a windows service, is that what I should be doing here?
The application that is sending me data is hosted in Tomcat, would it be a good idea to also run this application within the same Tomcat container (Current requirements are for both components to be on the same machine this may change)? And if so how?
I'm currently looking into Spring Boot, am I on the right path?
I think the best would be Spring Boot, as it's made to easily allow running different types of applications. Also, you don't need Tomcat if you can run the same component with a simple Main and not using UI. Spring Boot, also, has a sample using Spring Integration here, so you should be up and running in no time.
I am new to OSGi, and trying to configure Equinox/Felix on Weblogic Server. But nowhere can I find any information of any OSGi container embedded in Weblogic Server. So my questions are-
1. Has anyone configured Equinox or Felix with Weblogic Server? Is it supported?
2. SpringDM supports tomcat and jetty, does it support Weblogic too?
3. Can I deploy a Spring MVC application as a bundle without using SpringDM? OSGi container could be Felix/Equinox; and app server is Weblogic 10.3.3
Appreciate any help/samples/references to understand OSGi support in Weblogic.
Thanks in advance
-dee
please have a look to this question I've raised several months ago: WebLogic and OSGi. I also updated the question. Since version 12.1.2, Weblogic supports OSGi out of the box.
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