I am using STS with tomcat 6 but I am not able to add tomcat 7. I have tried to remove all servers and add them again but still the problem persists. It says
cannot create a server of the selected type
What can be the cause?
Related
I am unable to create a Spring Starter Project with STS 3.9.4. I see the following error.
I tried the following approaches:
I looked at proxy settings in STS and set the "Active Provider" to manual. The help -> dashboard successfully rendered implying that it was able to tunnel through the proxy but the spring-starter-project was still failing.
I cleared the local password storage but still ran into the same issue.
I tried various settings of the "Active Provider" and the errors for the Spring Starter Project varied implying that it was definitely using the proxy settings in STS but was failing for some reason.
After some digging I found this in Java SE release notes:
Disable Basic authentication for HTTPS tunneling
I realized immediately that I had upgraded the version of JDK a few days ago. I believe I had Java SE 8 u45 prior to the upgrade. I had upgraded it to Java SE 8 u111 and the above change was causing the issue.
I added the following line in STS.ini and it solved the problem.
-Djdk.http.auth.tunneling.disabledSchemes=""
I have a Spring MVC 4 application deployed in tomcat. It works fine. I have to clone this app to have several applications with same behaviour but different configurations: database instance and folders for file management. Each for different customers. When I deploy de original application to Linux Tomcat it works fine (https://hostname:8443/app1).
Then I change the db connection settings (database name, username, and folders to manage some generated files) and change the name of the artefact to customername. But when I get into the application, it shows the login page right, but when login into the app, I'm getting the following error:
Status HTTP 500 - Request processing failed; nested exception is org.apache.tiles.request.render.CannotRenderException: java.io.IOException: JSPException including path '/WEB-INF/layout/header.jsp'
javax.servlet.ServletException: File [/WEB-INF/layout/header.jsp] not found
when accessing to https://hostname:8443/customername, which it's part of tiles template. Files exist in the deployed application, It's able to reach the login page, so it seems to be resolved the tiles config, but I don't know why is not able to reach the jsp files. It's working fine in local windows without secure Tomcat (port 8080).
EDITED
If I change the name of customername.war to app1.war it's working fine. Anybody knows where the war file keep a reference to the base application app1? It seems that there a reference to app1 in somewhere that makes that If I change the application name (artifact id) it does not reference to customername path.
Seems that it's a context root issue. I have changed it in STS (Project > Properties > Web Project Settings > Context root), deployed on Tomcat but still not working. It's supposed that only with changing the war file name, the context root of the application should be updated, but it's not working.
Upgrading Tomcat from 8.0 to 8.5.5 solves the issue. I don't know why, but there's an issue in 8.0 because no way to force context root for an application, not context.xml application file neither other configuration.
Just upgrade to 8.5.5 and deploy applications without context issue.
BR
I've developed a camel route in a Fuse Project using blueprint, now I would like to deploy the route in the Fuse Server.
I'm not sure if this is a problem but the blueprint.xml returns me this error
White spaces are required between publicId and systemId at line 1
I've tried deploying the project following some guides online: tried to use drag and drop function in jboss dev studio dragging the project folder into server window but nothing happened.
Also tried use maven building and deploying as a maven project via osgi:install but it returns me this error :
Error executing command: Error installing bundles: Unable to start bundle file:/home/pajarittu/jboss_workspace/prova_sub/target/camel-subscribe-1.0.0-SNAPSHOT.jar: Unresolved constraint in bundle camel-subscribe [293]: Unable to resolve 293.0: missing requirement [293.0] osgi.wiring.package; (osgi.wiring.package=org.json)`
Do you know how to solve this problems or different ways to deploy the service? thanks in advance for the the answers.
First of all I recommend looking at this blog post:
http://lhein.blogspot.de/2014/07/improved-server-adapters-for-jboss-fuse.html
I described there how the deployment works now in tooling.
Then you should also make sure that if you choose Fuse 6.1 you can't use Java 8 to run it. I think the last error you posted exactly is caused by this. (I could be wrong though ;) )
Finally Claus is right. If you want to run Camel on Fuse runtime you should make sure you installed all the needed features / camel components in order to sucessfully run your routes.
Hope that helps,
Lars
You can take a look at an example which used camel , REST and camel route is deployed on JBOSS fuse 6.1
https://github.com/TheMaheshBiradar/fuse-middlware-services
.
I want to use Spring Insight with Tomcat 6. I cant use TC server because of reasons beyond my control. So I am looking at integrating Spring Insight with Tomcat 6. Has any one worked on this before or can any one point me to any documentation.
Thanks,
Anuj
Insight Developer (the free product) comes in two form, packaged with tc Server Developer and packaged with STS. Neither option will provide an easy mechanism for installing Insight into Tomcat. I'm not saying that it can't be done, there is just no simple way to do it.
If you really want to run Insight on Tomcat then you are going to need to do some work. Here are the rough steps that you'll need to do.
Download vFabric tc Server Developer
Create a vFabric tc Server instance which has Insight enabled.
Download the latest Apache Tomcat 6.0.x or 7.0.x
Copy the following files & folders from the tc Server instance w/Insight
bin/setenv.sh
bin/insight-bootstrap-tcserver-1.8.3.RELEASE.jar
insight
lib/*
webapps/insight.war
Edit conf/server.xml and add the following Valve to the Engine block.
<Valve className="com.springsource.insight.collection.tcserver.request.HttpRequestOperationCollectionValve"/>
Edit conf/context.xml and add the following before the closing Context tag.
<Loader loaderClass="com.springsource.insight.collection.tcserver.ltw.TomcatWeavingInsightClassLoader" />
<Listener className="com.springsource.insight.collection.tcserver.lifecycle.ApplicationLifecycleCollectionListener" />
Start the Tomcat instance.
Alternatively, Insight Operations (a paid product) makes this much easier and offers an installer that allows you to easily and quickly add the Insight Agent into different containers, including ASF Tomcat. Here's a link to the documentation.
http://pubs.vmware.com/vfabric51/topic/com.vmware.vfabric.tc-server.2.7/operations/install-agents.html
I think this instruction can be helpful for you http://blog.jelastic.com/2012/11/28/application-monitoring-in-the-cloud-with-spring-insight/
Actually in this tutorial Tomcat is a cloud instance, but I guess it is suitable for local installation too.
I downloaded vfacbric-tc-server-2.9.6 and followed the instructions mentioned by Daniel Mikusa to set up insight on tomcat 7. Unfortunately tomcat was not able to find the classes HttpRequestOperationCollectionValve, TomcatWeavingInsightClassLoader and ApplicationLifecycleCollectionListener in the jars provided. After struggling 2 days adding new jars containing these classes and getting class clash., finally I figured out that just removing the configuration in server.xml and context.xml are sufficient to get insight working on tomcat.
So, all you need to setup insight on tomcat are the steps 1 to 4 and 7 in his answer. I'm copying the same for the ease of others
Download vFabric tc Server Developer
Create a vFabric tc Server instance which has Insight enabled.
Download the latest Apache Tomcat 6.0.x or 7.0.x
Copy the following files & folders from the tc Server instance w/Insight
bin/setenv.sh
bin/insight-bootstrap-tcserver-1.8.3.RELEASE.jar
insight
lib/*
webapps/insight.war
Start the Tomcat instance.
I am trying to follow the updated instructions provided by "nagamanojv". I am able to start http://localhost:8080/insight/ on Tomcat 6, but I do not see any applications. I have deployed one of my web applications on the same tomcat instance. Let me know if I am missing anything.
we have a WAR packaged web application which works on a development machine. It consists of Java EE 5 + Seam 2.2.1 + Hibernate 3.3.1. It uses an Oracle 10g XE database and runs on the latest Tomcat 6 using JDK 1.6.0_24. The system is a 64bit Windows 7 Pro and uses Firefox 6.
Now, we tried to migrate the application to Oracle WebLogic 10.3.5. We followed the Seam manual for specifying the datasource, deploying the JSF lib and configuring the necessary xml-Files. In parallel to that, we verified that a newly seam-gen generated application using the same datasource and having the xml files configured as stated works fine.
But if we try our own application on WebLogic, allthough the deployment works fine, when trying to open the web application in the browser, it shows that endless redirection occured. We don't see any stacktrace or log error, even when configuring log4j in WebLogic. When analyzing the request with Firebug, we see the get request to "login.seam" and then 20 times a get request for "error.seam" (or "debug.seam when setting debug mode) with the response "302 Moved Temporarily".
I worked on that all week now, trying to compare all configurations and couldn't solve it - so I hope to get any ideas what could cause that problem and how to solve it!
I could pin down the problem to starting a transaction on the JTA persistence context.
I still don't understand why I didn't see any log message or stacktrace and why this also happens on the debug/error page (that's why the endless redirect occured).
I ended up using RESOURCE_LOCAL so far, but I'm not sure if this is the right thing to do.
The alternative is disabling the seam transaction setting, but then it didn't work together with the development build which still runs on Tomcat.