I installed Apache Tomcat 7. During the install, it asks if I want to do a full install or if I want to install just the web service. I chose to install the full package (Tomcat and a web service). When it finished, I had a windows service I could start. I could then view/use the web-based tomcat admin panel.
I shut down the service and re-ran the installer to setup an additional web service. I will have a couple dozen web apps to setup. During the install, I selected the "Web Service Only" so I could install the additional web app without installing Tomcat again. The installation finished OK.
I checked the installation folders and see both of my web services setup in the webapps folder. I start the tomcat service OK. When I attempt to view the web-based admin panel for either web service .. the originally installed web service and the second web service, tomcat seems to hang. When I attempt to shutdown the service, it doesn't shutdown properly and displays the windows error "unable to shutdown service". Eventually I can kill the process.
What could be causing this issue? I'm new to Tomcat on Windows so I apologize if I did not provide enough information. The web-based admin panel DOES work when I have a single webapp. When I have two or more webapps, the admin panel quits working (hangs).
Any ideas?
If you have Tomcat install a separate service for each web application, then you should be able to control each of them separately. They will be running separate JVMs, separate Tomcat services, etc.
If you had instead intended to have a single service with multiple applications deployed on it, then it appears that you may have made a mistake and configured multiple services instead.
From the command-line, you can launch the Tomcat service manager and specify exactly which of the Windows Services you'd like to control. For example:
C:\path\to\tomcat> tomcat8w.exe //ES//MyService
(Where MyService is the name you gave to your Windows Service when you configured it.)
You can find more information on Tomcat's Windows Service Documentation.
Related
Can you run the SQL Server 2014 Master Data Services Configuration manager on windows 8.1 pro and not on a server like Windows server R2?
If so please help it tells me "The required .svc handler mappings are not installed in IIS." but I have checked and everything in the windows features under IIS is selected
The answer was a simple google search away.
You can run it on Windows 8.1 Pro.
Take a look at this link for several troubleshooting help:
SVC_Handler_mapping_error_in_MDS_Configuration_Manager
SVC Handler mapping error in MDS Configuration Manager
When you configure Master Data Services in the MDS Configuration
Manager, you may encounter an error indicating that the required .svc
handler mappings are not installed in IIS.
Before creating an MDS web application, you must correct the following
errors:
Internet Information Services (IIS) is not configured on this server.
The required .svc handler mappings are not installed in IIS.
This can occur in one of the following instances: IIS may be missing the necessary .svc Handler Mappings. Visit IIS Manager from
the start menu. If you have a default website listed, click the site,
and click Handler Mappers icon. In the list, sort by Path column.
notice if *.svc is listed or not. If it is already listed, this error
may a false positive, but if it is not, you may need to install the
*.svc path mappers in Step 2 & 3 below.
Depending on the IIS version, there are different ways to get the
Service Mappers installed. For .Net 4.0, the mappers may need to be
installed by installing HTTP activation in .Net Framework 4.6 Advanced
Services. From the start menu search or control panel, find the item
Turn Windows Features Off or On. then in the tree of Windows Features
find .Net Framework 4.6 > WCF Services > HTTP Activation
On earlier Windows versions where .Net Framework 4.0 does not come
preinstalled, when you add or install IIS features after .NET 4 was
installed, you may encounter this error. To fix this issue, open a
command prompt and go to the .NET directory (for example
%windir%\Microsoft.NET\Framework64\v4.0.30319). Run the command:
aspnet_regiis -i.
You may encounter this error as a false positive or false negative
when there is an existing IIS website(s) already existing in your IIS
server, but you select a different Web site to host MDS, or when you
select a Web site other than the first Web site listed. This can
happen in following two ways: Service handlers are not installed on
the first Web site that MDS is not attached to, but are installed on
another Web site that MDS is attached to. MDS will post an error
because it looks at the first Web site, not the second Web site. This
is a false negative, in that the error message indicates that the
handler mappings are not made, whereas they actually are. In this
case, you can ignore the error and proceed. Service handlers are
installed on the first Web site that MDS is not attached to, but are
not installed on another Web site that MDS is attached to. MDS will
not post an error because it looks at the first Web site, not the
second Web site. This is a false positive, because the lack of handler
mappings will cause MDS not to work. You should install the handler
mappings for the Web site that you are attaching MDS to.
This has to be a pretty simple task. I have an Azure Cloud Service that works just fine with HTTP and HTTPS. Now I want to create a net.tcp connection to the cloud service. The first thing I discover is that net.tcp is not supported by IIS Express. That's fine. So I try switching to regular IIS and all I get when I try to run the application is a 404 error. If I was building an WCF Web Application, I would get a form that allows me to select (and build) the virtual directory for the application, but there's no analog for this in the Cloud Service.
I can take a fresh 'Cloud Service' project build using visual studio, make no changes to it except change IIS Express to IIS. When I launch it, I get a 404 error in the web browser.
Does anyone have a working example of tcp.net (with IIS Express or standard IIS) in a Cloud Service?
This video by the Azure team is a great overview and cleared up a lot of conceptual issues I had. An Azure Cloud Service is a container around one or more virtual machines. The virtual machines basically come in two flavors: Web Role and Worker Role. What threw me is the description that the Worker Role was intended for background processes: not true. A Web Role is basically a VM with IIS, a Worker Role is basically a VM without IIS. Since the off-the-shelf IIS doesn't have net.tcp installed, you have to jump through hoops in order to get the protocol installed. Instead, the Worker Role can be used as a self-hosted web service. If you want the performance and throughput of TCP, this appears to be the direction to go.
I have an MVC 3 application and WCF service to be deployed in IIS 8.5 installed on Windows Server. I have checked all the prerequisites installed for IIS 8.5. After the deployment when I try to access the .svc files, I get "This page can't be displayed".
The have verified the below conditions.
APP POOL:
1.) The app pool is set to "Integrated" mode and targetted to V4.0.
2.) Identity is set to "ApplicationPoolIdentity" and enabled 32 bit
applications.
BINDINGS:
1.) Provided a different port"88" and ip address is configured.
PERMISSIONS:
1.) Full access has been provided for the below mentioned users.
a.) IUSR
b.) IIS_IUSRS
c.) DefaultAppPool(This is the app pool that has
been assigned).
I am struck with this, Please let me know for anything that needs to be included.
Do you have HTTP Activation checked for WCF Service under IIS features. If not you need to enable that from server manager add roles/features wizard. Please refer to the image attached.
I'm developing a Web App with Dache, Thanks the author for the fantastic library.
Unfortunately, I have a big problem with it.
In previous version of 1.5.6, it was worse. but in 1.5.6 it's better but still I get The following exception:
There are no reachable cache hosts available. Verify your client settings and ensure that all cache hosts can be successfully communicated with from this client.
In developing, I get the exception after 2 or 3 times build, and I have to restart cache service and stop IIS Express to remove the exception.
In the web app after some hours the clients disconnect from cache service. and I have to restart the cache service and web sites to remove the exception.
I hosted dache on windows service.
I think the problem is for comunications between dache host and dache clients.
So, Is it possible to host dache cache on IIS like a WCF service instead of windows service?
You can host Dache in your own process using the Nuget package. More information available on the Dache wiki:
I have to do some maintenance on a WCF service that is hosted in a managed windows service.
In the old deployed version I can enter: http://localhost:9091. It shows a page with info about the hosted WCF service (with a C# and VB example).
When I get the sources from TFS and reinstall with the MSI, the same http://localhost:9091 gives a 404.
What could be wrong ?
Could be lots of things. Try these for a start:
Installed msi on wrong port
web site / app pool not runnig
the configuration in web.config does not match the new location
Web site not marked as asp.net 2.0
IIS not configured to recognise svc files
The last 3 are the most probable. Check the event log for more details.
Here are a few more based on the comment:
is the service started
is the port blocked on the new machine
the configuration in web.config does not match the new location
Perhaps that port is meant to be the port of the ASP.NET Development Server. Is the service started? Open the solution in Visual Studio, right-click the service and choose "View in browser". That will have the side-effect of starting the service.