Jk_mod configuration in virtual host

Hi,
I met a strange problem.
Apache has several virtual hosts. Each virtual host has its own configuration file, which is "included" into main httpd.conf .
If I define JkMount directive in virtual host conf file inside <VirtualHost>, it does not work.
If I move it to the httpd.conf at the top level, it works fine.
Could you help me out to launch it on <VirtualHost> level.
Thanks.

Hi there,
I just wanted to clarify my question, has anyone been able to use group authentication using OID to restrict access to websites hosted using AS10g? My website is just plain html, but maybe someone has done something similar by adding a java wrapper to perform the authentication (that seems like overkill to me but maybe there is a more elegant workaround)?
Thanks,
Karen

Similar Messages

How to configure Apache Virtual Hosts?

Hi, I was wondering, how does configure Apache virtual hosts for Mac OS X Client 10.4.5? At this time, I have added
NameVirtualHost *:80
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /Library/WebServer/Documents/janus
ServerName janus.php.test
ErrorLog /private/var/log/httpd/janus.php.com-error_log
CustomLog /private/var/log/httpd/janus.php.com-access_log common
</VirtualHost>
Finally, when I try to use the name in the browser, I get the following error message:
Safari can’t find the server.
Safari can’t open the page “http://janus.php.test/” because it can’t find the server “janus.php.test”.
Well, I must go and thanks in advance.
Peace,
-Conrad

If you want to use the fqdn you defined and can/do not want to register it as a Internet Domain you can add it to the hosts file in /etc/hosts if you are comfortable using terminal and the shell
open a terminal
and use the following commands
cd /etc
sudo vim hosts
(you will be prompted for your password here, enter it and hit return)
in vim scroll to the last line which will look like
::1 localhost
type
i
(you are now in insert mode)
type the following line
192.168.0.15 janus.php.test
(replace the ip address with the ip address of the host in question)
hit Control-C
type
:w (vim will confirm in the last line)
type
:q
you are back at the terminal
test your new hosts file by typing
ping janus.php.test
Hope this helps
Mike

How to configure multiple virtual hosts for the same context root /

Hi,
I am using Glassfish V1 U1 - b14 on Solaris.
I am trying to configure two applications to be mapped to the / root context, each one in its own virtual host.
Two things I have noticed:
1. I have to manually add virtual-hosts="hostId" in domain.xml/application-ref ... looks like just simply deploying the app does not do that although the application is set as default for its particular virtual host. Is this a bug?
2. Although I have set for each virtual host the default web-app correctly, and they both respond fine, I cannot map both of them to the / context. The second application (chronologically deployed) does not respond when called with the / context ....
Any ideas? Is this a bug again?
Regards,
Rares
Message was edited by:
raresp

Wow, that's a shame. All mighty Application Server and two different apps on two different virtual hosts are considered ambiguous to have the same context root definition.... Fair play to Tomcat and 90% of the rest of servlet containers!
In my case I have the same EAR we are planning to deploy to many (up to 30) virtual hosts. Faking different context roots for each deployment will bring unnecessary overheads...
Should I file a bug or feature request?
Thanks again for your answer, although you're basically saying it is not possible I will wait and look a while for a possible solution before bringing this topic to a conclusion.

Configuring a virtual host in Weblogic

Hi,
I created a virtual host in Weblogic but it doesn't work. I followed all of the steps from the Weblogic website.
The default URL for my application works, http://localhost:7001/abc_application but when I try using the new virtual host I get an error,
http://xyz.com:7001/abc_application. I applied the virtual host to my Weblogic Managed Server and also to a deployed application. What else needs to be done outside of Weblogic for this to work?
Sorry for the cross-posting.
Thanks,
Annette

Hi Annette!
Have you modified the hosts file for your machine to add an entry for xyz.com to map back to 127.0.0.1?
What sort of errors are you getting when you try to access the virtual host? Can you post a snippet from your log file?
Apologies if your problem has been solved since posting this message...
<br>
Kevin Powe
http://www.integral-techsolutions.com

Webdav/virtual host configuration problem

Hi folks,
I have a web server behind firewall, which redirects port 80 to my server's internal IP, 192.168.6.222. I did setup 3 virtual domains there:
blogs.domain.com at *
wiki.domain.com at *
dav.domain.com at *
each site has different root and dav site has its own realm set.
I just found that virtual domains are not working and dav.domain.com doesn't work at all. When I switch dav.domain.com to 192.168.6.222, it eats all connections and even for blogs site shows login sheet.
$ httpd -S
Processing config directory: /etc/httpd/sites/*.conf
Processing config file: /etc/httpd/sites/0000any_80blogs.domain.com.conf
Processing config file: /etc/httpd/sites/0001any_80wiki.domain.com.conf
Processing config file: /etc/httpd/sites/0002any_80dav.domain.com.conf
Processing config file: /etc/httpd/sites/virtualhostglobal.conf
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
*:80 is a NameVirtualHost
default server blogs.domain.com (/etc/httpd/sites/0000any_80blogs.domain.co.conf:3)
port 80 namevhost blogs.domain.com (/etc/httpd/sites/0000any_80blogs.domain.co.conf:3)
port 80 namevhost wiki.domain.com (/etc/httpd/sites/0001any_80wiki.domain.com.conf:3)
port 80 namevhost dav.domain.com (/etc/httpd/sites/0002any_80dav.domain.com.conf:3)

Hi Simon
You are not doing anything wrong. Setting up a virtual host has obviously
worked as you can access it. You still have to specify the port number as
it is not running on the standard port 80 that your browser assumes if you
do not explicitly state it.
regards
Nick
"Simon Pierre NOLIN" <[email protected]> wrote in message
news:3be7f4f1$[email protected]..
>
Hi!
I try to configure a virtual host but it doesn't work. I have create it(name=myVirtualHost,
virtual host names=gandalf.foo.com). I assigne it to my managed server(port 5021).
In the managed server i have a web application calls "rings". If i typethe url,
gandalf.foo.com/rings/login : 404 not found error. BUT if i usegandalf.foo.com:5021/rings/login
: it works.
Can someone explain me what i do wrong?
Regards
Simon Pierre NOLIN

Weblogic virtual host configuration

Hi,
Can anyone explain to me what is virtual host.
what is the significance and purpose of the same.
in what scenario should we configure a virtual host.
and what is the benefit of the same.
from the documentation i did not understand the concept.
Thanks in advance.

I think this page is pretty clear. Does this help?
http://download.oracle.com/docs/cd/E14571_01/apirefs.1111/e13952/pagehelp/Corecorevirtualhosttabletitle.html
A virtual host is a set of host names to which WebLogic Server instances (servers) or clusters respond. When you use virtual hosting, you use DNS to specify one or more host names that map to the IP address of a server or cluster. You also specify which Web applications are served by each virtual host.

Apache-weblogic bridge problems with virtual hosting

Hi,
Can we set apache-weblogic bridge where apache webserver is configured
as virtual hosts and each Virtual Host is mapped to a WebLogic server
instance running on separate port ?
Please provide doc or reference or your comments if you have solved this
problem
Thanks
Shriniwas

The above comments notwithstanding, there's one outstanding line in your post that seems crucial:
Also if I type on my browser the name of another secondary (or virtual) domain name in the form http://domain2.com it brings the website hosted under the primary domain which is domain1.com. In case I type http://www.domain2.com than it works as it should and displays the website hosted under this domain name.
As far as Apache is concerned, 'domain2.com' and 'www.domain2.com' are completely separate entities. They have to be otherwise if all domain2.com traffic went to this site you'd never be able to host different sites within the domain (e.g. blogs.domain2.com, wiki.domain2.com, blah.domain2.com, etc.). In other words, there is no automatic relationship between a hostname and sub-records of that hostname.
So what's happening here is Apache is seeing a request for 'domain2.com' which does not match any of its configured virtual hosts, so it handles the request via the default site. If you request www.domain2.com this matches your virtual host configuration so Apache serves the alternate content.
The fix is simple - trivial, even - you just need to tell Apache all the hostnames that match this site - in this case if you've configured the site's primary address as 'www.domain2.com' and you want it to also respond to requests to 'domain2.com' then add 'domain2.com' to the list of Server Aliases in Server Admin.

Virtual Hosts in Apache HTTP Server

How to configure virtual hosts in Apache HTTP Server httpd.conf file.
If I want to access my server with some other name(alias), how can I do this ?
Suggestions in this matter would be highly helpful.
Thanks
Vidhyut Arora

Following is a note explaining how to setup
Virtual hosts.
Hope this helps
Ranga
Note:70647.1
Subject: Apache Server Virtual Hosting
Last Revision Date: 07-JUN-2001
PURPOSE
This document discusses considerations for setting up virtual hosts on an
Apache machine, to include how to get the hostname working and how to
configure Apache.
SCOPE & APPLICATION
The information in this document is intended for those who manage multiple sites
using an Apache machine.
REFERENCES
First published in Apache Week issue 31 (6th September 1996)
Last update 20th September 1998
Using Virtual Hosts
Virtual Hosts let you run multiple independent Web sites on a single host with
a single Apache setup.
One of the most important facilities in Apache is its ability to run virtual
hosts. This is now the essential way to run multiple Web services - each with
different host names and URLs - that appear to be completely separate sites.
This is widely used by ISPs, hosting sites and content providers who need to
manage multiple sites but do not want to buy a new machine for each one.
Picking an IP address
There are two types of virtual hosts: IP-based and non-IP-based. The former is
where each virtual host has its own IP address. You must have a new IP address
for each virtual host you want to set up, either from your existing allocation
or by obtaining more from your service provider. When you have extra IP
addresses, you tell your machine to handle them. On some operating systems, you
can give a single ethernet interface multiple addresses (typically with an
fconfig alias command). On other systems, you must have a different
physical interface for each IP address (typically by buying extra ethernet
cards).
IP addresses are a resource that costs money and are increasingly difficult to
get, so modern browsers can now also use 'non-IP' virtual hosts. This
lets you use the same IP address for multiple host names. When the server
receives an incoming Web connection, it does not know the hostname that was used
in the URL. However, the new HTTP/1.1 specification adds a facility where the
browser must tell the server the hostname it is using, on the Host: header. If
an older browser connects to a non-IP virtual host, it does not send the Host:
header, so the server must respond with a list of possible virtual
hosts. Apache provides some help for configuring a site for both old and new
browsers.
Picking a Hostname and Updating the DNS
Having selected an IP address, the next stage is to update the DNS so that
browsers can convert the hostname into the right address. The DNS is the system
that every machine connected to the internet uses to find the IP address of host
names. If your hostname is not in the DNS, no one can connect to
your server (except by the unfriendly IP address).
If the virtual hostname you are going to use is under your existing domain,
you can just add the record into your own DNS server. If the virtual hostname
is in someone else's domain, you must get them to add it to their DNS
server files. In some cases, you want to use a domain not yet used on the
internet, in which case you must apply for the domain name from the
InterNIC and set up the primary and secondary DNS servers for it, before adding
the entry for your virtual host.
In any of these cases, the entry you need to add to the DNS is an address record
(an A record) pointing to the appropriate IP address. For example, say you want
the domain www.my-dom.com to access your host with IP address 10.1.2.3: you
must add the following line to the DNS zone file for my-dom.com:
www A 10.1.2.3
Now, users can enter http://www.my-dom.com/ as a URL in their browsers and get
to your Web server. However, it will return the same information as if the
machine's original hostname had been used. So, the final stage is to tell Apache
how to respond differently to the different addresses.
How Apache Handles Virtual Hosts
Configuring Apache for virtual hosts is a two-stage process. First, it needs
to be told which IP addresses (and ports) to listen to for incoming Web
connections. By default, Apache listens to port 80 on all IP addresses of the
local machine, and this is often sufficient. If you have a more complex
requirement, such as listening on various port numbers, or only to specific IP
addresses, then the BindAddress or Listen directives can be used.
Second, having accepted an incoming Web connection, the server must be
configured to handle the request differently, depending on what virtual host it
was addressed to. This usually involves configuring Apache to use a different
DocumentRoot.
Telling Apache Which Addresses to Listen To
If you are happy for Apache to listen to all local IP addresses on the port
specified by the Port directive, you can skip this section. However, there are
some cases where you want to use the directives explained here:
- If you have many IP addresses on the machine but only want to run a Web
server on some of them
- If one or more of your virtual hosts is on a different port
- If you want to run multiple copies of the Apache server serving different virtual
hosts
There are two ways of telling Apache what addresses and ports to listen to:
- Use the BindAddress directive to specify a single address or port
- Use the Listen directive to any number of specific addresses or ports
For example, if you run your main server on IP address 10.1.2.3 port 80, and a
virtual host on IP 10.1.2.4 port 8000, you would use:
Listen 10.1.2.3:80
Listen 10.1.2.4:8000
Listen and BindAddress are documented on the Apache site.
Configuring the Virtual Hosts
Having gotten Apache to listen to the appropriate IP addresses and ports, the
final stage is to configure the server to behave differently for requests on
each of the different addresses. This is done using <VirtualHost> sections in
the configuration files, normally in httpd.conf.
A typical (but minimal) virtual host configuration looks like this:
<VirtualHost 10.1.2.3>
DocumentRoot /www/vhost1
ServerName www.my-dom.com
</VirtualHost>
This should be placed in the httpd.conf file. You replace the text
10.1.2.3 with one of your virtual host IP addresses. If you want to specify a
port as well, follow the IP address with a colon and the port number
(example: 10.1.2.4:8000). If omitted, the port defaults to 80.
If no <VirtualHost> sections are given in the configuration files, Apache
treats requests from the different addresses and ports identically. In terms of
setting up virtual hosts, we call the default behavior the main server
configuration. Unless overridden by <VirtualHost> sections, the main server
behaviour is inherited by all the virtual hosts. When configuring virtual
hosts, you must decide what changes to make in each of the virtual
host configurations.
Any directives inside a <VirtualHost> section apply to just that virtual host.
The directives either override the configuration give in the main server, or
supplement it, depending on the directive. For example, the DocumentRoot
directive in a <VirtualHost> section overrides the main server's DocumentRoot,
while AddType supplements the main server's mime types.
Now, when a request arrives, Apache uses the IP address and port it arrived on
to find a matching virtual host configuration. If no virtual host matches the
address and port, it is handled by the main server configuration. If it does
match a virtual host address, Apache uses the configuration of that virtual
server to handle the request.
For the example above, the server configuration used is the same as the
main server, except that the DocumentRoot is /www/vhost1, and the
ServerName is www.my-dom.com. Directives commonly set in <VirtualHost>
sections are DocumentRoot, ServerName, ErrorLog and TransferLog. Directives
that deal with handling requests and resources are valid inside <VirtualHost>
sections. However, some directives are not valid inside <VirtualHost> sections,
including BindAddress, StartSevers, Listen, Group and User.
You can have as many <VirtualHost> sections as you want. You can
leave one or more of your virtual hosts being handled by the main server, or
have a <VirtualHost> for every available address and port, and leave the main
server with no requests to handle.
VirtualHost sections for non-IP Virtual Hosts
Non-IP virtual hosts are configured in a very similar way. The IP address that
the requests arrive on is given in the <VirtualHost> directive, and the
host name is put in the ServerName directive. The difference is that there
(usually) is more than one <VirtualHost> section handling the same IP address.
For Apache to know whether a request arriving on a particular IP
address is supposed to be a name-based requests, the NameVirtualHost directive
addresses for name-based requests. A virtual host can handle more than one
non-IP hostname by using the ServerAlias directive, in addition to the
ServerName.
null

Setting Up a Virtual Host

I need define a virtual host dynamically in my application.
How can i do that in WebLogic Server (Web Server)? Have i command line to do this?
Thank´s

In 6.x, you can use the JMX API to configure a virtual host dynamically.
Check out the docs at http://e-docs.bea.com/wls/docs61/jmx for reference
material.
-- Ian
"jacques" <[email protected]> wrote in message
news:3b6075d8$[email protected]..
>
I need define a virtual host dynamically in my application.
How can i do that in WebLogic Server (Web Server)? Have i command line todo this?
>
Thank´s

Forms Virtual Hosts?

Hi,
Is it possible to use forms with virtual hosts? I have configured a virtual host in apache conf but the new virtual host is never used in forms.
original host
www.oldhost.com
my new virtual host
www.newhost.com
when I write in url www.newhost.com/forms/frmservlet?config=xxx i am always redirected to www.oldhost.com/forms/frmservlet?config=xxx
Thanks
Joao Oliveira

Any can help? Forms team?

Real brain bender: virtual host or omni portlet issue? Take the challenge

We are having problems with a portal page that displays several omni portlets on several tabs. Here's the situation:
The page consists of 5 tabs, each representing a different demographic characteristic. On each tab there are four omni portlets. One omni porlet represents a selection list. The user makes a selection, which triggers an omni portlet event to pass the selection criteria to a page parameter. The other three omni portlets on the tab read the parameter value and retrieve data according to the selected parameter value.
Example: The user selects the Age tab and selects the link representing data for the Central Region. The omni portlet's event populates the page's "region" parameter with the value "Central." The other three portlets on the tab retrieve their respective data where region = 'Central'.
Since all the tabs on the page represent different demographic characteristics, the omni portlets on all the other tabs also perform their queries where region='Central' so that the user will see Central Region data displayed regardless of what tab they navigate to.
Also, when the user navigates to another tab and selects a different region, all the omni portlets on all the tabs perform their respective queries to capture data where region=<selected region>.
The page performs correctly until we configure a virtual host. In that case, when a user makes a selection of a particular county in one tab, the queries are performed but the page displays with a tab in view other than the one where the user made the selection.
Example: the user navigates to the Age tab and selects region='Central'. Then the user navigates to Gender tab and then Living Situation tab, viewing the results on each tab. Now the user returns to Gender tab and selects region='Western.' The portlets perform their queries and the page re-displays with the user on Living Situations tab, rather than Gender tab where the selection was made.
Obviously, we want the user to stay put on the tab in which they make their selection. I think it's a problem with the virtual host configuration. My DBA thinks it's a problem with the way the page is built. Has anyone else run into this kind of thing? Is there a trick to using Virtual Hosts?

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

IP Virtual Host w/SSL serving on port 80 and 443

We have an OS 10.3.8 system and we've configured several virtual hosts using the system admin panel. One IP has several hosts on it. We have a seperate IP with one virtual host on it since it is running SSL. I have it configured for port 443 and I have all the security certificates installed OK. The site operates correctly over HTTPs. If I try to access it with standard HTTP I get a service not available error (which makes sense since server admin sets the config files to port 443 ... not 80).
The only way I can get it to work is to add another virual host in server admin running on that IP at port 80. Unfortunately, that means it will be logged seperately (which I don't really want it to do). What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
Thanks in advance ...
Tom

>The only way I can get it to work is to add another virual host in server admin running on that IP at port 80.
That's correct. That's how you run a site as both HTTP and HTTPS - they're two sites.
> Unfortunately, that means it will be logged seperately
Why? You can set both sites to use the same log file and their hits will be combined in a single file.
> What do I need to change to get a single virtual host on a specific IP to respond correctly to both 443 and 80 using the file layout generated by server admin (I can modify them manually)?
You can't, but if your issue is the logging, my answer above should take care of that.

How to configure virtual hosts and separate tiers

The configuration we require with WLS must:
1) provide virtual hosts that can operate under their own SSL environments (some one way, some two way, with different certs)
2) perform all XML parsing of received message objects in the web layer in order to (a) offload CPU from ejb layer to web layer and (b) prevent any malformed message from penetrating to the ejb layer - reject in the web layer
3) the web tier must be physically separate from the ejb tier - an integrated WLS server is not acceptable for security reasons
4) the ejb layer must be clusterable
5) DNS round robin is sufficient protection for web layer failover
I do not see clearly how to accomplish this configuration using the WLS suite. Would appreciate guidance on this prior to plunking down big dollars for licenses.
Thanks

The configuration we require with WLS must:
1) provide virtual hosts that can operate under their own SSL environments (some one way, some two way, with different certs)
2) perform all XML parsing of received message objects in the web layer in order to (a) offload CPU from ejb layer to web layer and (b) prevent any malformed message from penetrating to the ejb layer - reject in the web layer
3) the web tier must be physically separate from the ejb tier - an integrated WLS server is not acceptable for security reasons
4) the ejb layer must be clusterable
5) DNS round robin is sufficient protection for web layer failover
I do not see clearly how to accomplish this configuration using the WLS suite. Would appreciate guidance on this prior to plunking down big dollars for licenses.
Thanks

Configurations, instances, nodes, virtual hosts, clusters ... oh my!

Perhaps I am being dense, but I am having some trouble wrapping my head around the different "objects" of a SJS web server 7 installation. It is not clear to me how they relate/map to each other and to real processes on the server (logical architecture, mapped to physical architecture).
I had the same difficulty with WebSphere App Server 6 terminology until, with one fell swipe of the Sword of Fundamental Truthiness, a very brilliant instructor cleared it up for me when he said (using WAS6 parlance) "a 'profile' is the on-disk configuration, files etc, of a node. 1 profile = 1 node. The node is the run-time object describe by the profile." Bingo. Everything (nodes, servers, cells, profiles) made sense after that.
I've been through the docs, but it is still not clear to me. Any lucid descriptions would be appreciated. There's configurations, nodes, instances, virtual hosts, listeners, clusters.
Is a cluster a collection of nodes? Or instances? Virtual server vs. instance? A "configuration" is the on-disk configuration/files etc describing a ???" Maybe there is a nice diagram out there someplace that maps all these bits together?
Thanks,
Mark

Thanks all. Like I said, I've read the docs. They are not terribly clear, at least not to me, but maybe I am just being dense. Some detailed diagrams would be useful.
[In the text below, I use leading CAPS to differentiate between generic use of a term and Web Server's use of a term ... instance vs. Instance for example.]
To say "an Instance is a Configuration deployed to a Node" doesn't make any sense to me, since an "Instance" is a configuration item within the Configuration. Maybe it is technically correct
I think I have the following correct:
* A Configuration defines/describes an HTTP service that you wish to provide. It ties together all the elements required to define that service: ports to listen on, SSL or no SSL, document roots, access control and so on.
* You deploy Configurations to Nodes. You define which Nodes to deploy the Configuration to using the Instances tab within the Configuration. The Instance is the run-time representation within a Node of the Configuration (as the Node is the run-time representation within a Cell of the on-disk Profile in WebSphere). You may only have one Instance of a Configuration per available Node. If you have multiple Configurations, you can deploy one Instance of each Configuration to a single Node. An important point here is that Instances really have nothing to do with Virtual Hosts or HTTP Listeners. They are related to Configurations. Configurations have a one-to-(potentially)-many relationship with Instances. Instances within a single Configuration have a one-to-one relationship with Nodes.
* A Listener listens for incoming HTTP requests on a single port. You may have multiple Listeners per Configuration. A Listener forwards incoming HTTP requests to the "appropriate" Virtual Host.
* You can map a single Listener (therefore a single port) onto multiple Virtual Hosts, (Why would you do this?) and of course, multiple Listeners onto a single Virtual Host. Listeners and Virtual Hosts have a many-to-many relationship.
* A virtual host is really the definition of the "real HTTP service", by which I mean it defines the doc root, access controls etc.
I think I have it straight. I apologize if this is amateur. I am hoping to replace all my Apache servers with SJSWS and need to have all my ducks lined up to make the argument for doing so.
Thanks again,
Mark

Virtual Hosts configuration in JServ.conf

I was trying to configure virtual hosts in the Jserv.conf file like this:
NameVirtualHost 138.1.104.151
# directives for vhost1
<VirtualHost 138.1.104.151:10001>
ServerName gsyang-lap.xyz.com
<IfModule mod_jserv.c>
ApJServDefaultHost gsyang-lap.xyz.com
ApJServProperties "C:\ORCL\ias\Apache\Jserv\conf\jserv_1.properties"
ApJServLogFile "C:\ORCL\ias\Apache\Jserv\logs\mod_jserv_1.log"
</IfModule>
</VirtualHost>
# directives for vhost2
<VirtualHost 138.1.104.151:10002>
ServerName gsyang-lap.us.oracle.com
<IfModule mod_jserv.c>
ApJServDefaultHost gsyang-lap.xyz.com
ApJServProperties "C:\ORCL\ias\Apache\Jserv\conf\jserv_2.properties"
ApJServLogFile "C:\ORCL\ias\Apache\Jserv\logs\mod_jserv_2.log"
</IfModule>
</VirtualHost>
After I saved the file and tried to stop/restart the Apache server, I got any warning, saying:"NameVirtualHosts 138.1.104.151 has not virtual hosts". Any idea as to how to fix this problem? Thanks in advance.
Sunny

Hi,
This seems to be a SO error more than an IAS error.
Have you tried stopping the iAS Server and looking for and old process still running?
It may not be a problem with the file open limit, but may be the one it is trying to user is still in use by and old process.
Carlos

Jk_mod configuration in virtual host

Similar Messages

Maybe you are looking for