re: Couldn't read web-site config file...
You didn't mention your orion/config/server.xml file. There must be an entry in server.xml which specifies the location of your web.xml file. It would look something like: You may also need another line in this same server.xml file, like this: Then, your orion/config/default-web-site.xml file should probably have the following line: which, assuming orion is running on your local machine, would allow you to access your index.jsp file as: http://localhost/webstuff/index.jsp Hope this helps... -Dale
[Fwd: Orion 1.4.8 page reload stalls]
I am forwarding this on to the group per Mark's request... Additionally, Mark - yes! I have noticed too that the stall occurs *after* the contents have been sent to the browser - almost as hough the content length was set to be longer than the real content length. I've never seen this with any previous versions, and I agree that it is a serious problem - although since it worked before, I would guess that it wouldn't be a very difficult problem for the Orion team to fix, who have, in my opinion, done an incredible job with this product so far. -Dale Hello. I'm replying directly to you because I do not subscribe to the Orion list. Would you be so kind as to add this to the list? I have had the same problem with Orion. I've noticed a few more things: The stalls are always in regard to POST requests. The stalls occur after the request has been committed. I put in statements that print to the standard output once a JSP page has been finished. The stall is happening *after* the page contents have been sent to the browser. This is a very serious problem. -mark Mark Meuer Software Engineer Life Navigator, Inc. http://www.lifenavigator.com mailto:[EMAIL PROTECTED]
Orion 1.4.8 page reload stalls
Hi, I recently upgraded to version Orion 1.4.8 from version 1.4.5, and discovered that when a page (jsp) initially loads and displays, the message bar at the bottom of the browser window (Netscape) indicates that it is still trying to download something, while the indicated transfer rate drops and eventually stalls - and then, after perhaps 8 to 10 seconds, the hourlgass goes away. Clicking the browser's 'Reload' button after the page has completely loaded, results in a blank browser window, while the message bar at the bottom indicates "(stalled)", and after about 10 seconds, the page re-appears. This is not unique to just one project - it happens on every project under Orion. None of the previous versions of Orion exhibited this problem. I switched hoping that the problem with PostFileInputStream has been fixed, and happily it has. However, this current problem would almost make a site unusable. Sorry if this has already been addressed in the group. Any help would be greatly appreciated. Thanks, Dale
Re: Anyone using Orion/Apache w/ many virt. hosts?
Robert Krueger wrote: Are you talking name based or ip based vhosts? what magnus explained was that it was a problem with name based hosts sharing one ip address and port. for ip base hosts he gave you a solution. you're saying that it does work with name based hosts sharing ip and port with apache? Robert, Well, I guess I don't know if I'm talking name-based or IP-based. I use the "virtual-hosts" parameter of the web-site.xml file to specify the domains of interest, such as www.domain1.com, www.domain2.com, www.domain3.com, with the dns server mapping each of these domains to the same IP address, which in turn is running Orion. I'm a programmer working at an ISP, and although I don't manage the Apache servers here, I do know that they have one Apache server with five certificates installed, and only one network adatper. From that, I'm understanding that the server is using only one IP address, on one port (well, two actually I guess, one for http, and one for https), and yet the server selects the cert which is appropriate for the site. Sorry if I'm being dense about this, but I obviously am just not 'getting' it. -Dale
Re: 1.3.8 on NT causing Dr. Watson
Vidur Dhanda wrote: > Hello, > > Has anyone else experienced erratic java.exe (JDK1.3) failures while > running 1.3.8 on a NT4.0SP6a box. All of a sudden I have started > getting Dr Watson while running orion. I can't detect any pattern -- it > can crash while it is doing nothing and when there is heavy load on the > server. > > My configuration: JDK1.3, Orion 1.3.8, NTWS4.0SP6a, 384MB, AMD K6. > > Vidur Vidur, I can't comment about jdk/orion under NT, but ... For what it's worth, here's what I've noticed while running Sun's jdk1.3 under Linux: When Orion is started, there are about a dozen jdk1.3 processess that start up simultaneously! Under jdk1.2.2, there was only one. As I modify the server.xml file - adding or dropping sites, the number of jdk1.3 instances increases dramatically. If I kill the first jdk1.3 instance started, they all terminate. Under jdk1.2.2, I've never noticed any additional processes start up. I don't know what these processes are doing, or why this happens, but it's just something that I've noticed, and the fact that the number of processes rapidly increases is pretty alarming. So... I went back to jdk1.2.2 for now, and that works fine. I'd suggest that maybe you can check out the number of processes running under NT, and see if perhaps you're experiencing something similar. -Dale
Re: Anyone using Orion/Apache w/ many virt. hosts?
Mike Cannon-Brookes wrote: > I run Orion with 15 virtual hosts (don't know why 50 would be any > different). > > Use Orion exclusively, it's really only a little leap not really a big one. > There was a discussion a while back about what you needed in Apache, net > result: there's nothing that can't be done in Orion ;) > > Mike > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Keith Elliott > > Sent: Tuesday, October 03, 2000 8:23 AM > > To: Orion-Interest > > Subject: Anyone using Orion/Apache w/ many virt. hosts? > > > > > > Hi, > > > > I'm new to Orion and have been searching through the > > mailing list archives. But, I'm still left with a > > couple questions: > > > > 1. Is anyone using Orion with Apache and 50 or more > > Apache virtual hosts? > > > > 2. Is anyone using only Orion with 50 or more virtual > > hosts? > > > > 3. What is the best choice? Like many companies, we > > have a large number of legacy virtual hosts on Apache. > > We are migrating to the J2EE framework and currently > > selecting an app server for our needs. > > > > Thanks for your time and thougths! > > > > Keith Elliott > > NuRelm Internet Solutions > > www.nurelm.com > > Austin, Texas, USA > > > > __ > > Do You Yahoo!? > > Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! > > http://photos.yahoo.com/ > > Mike, I know that running SSL on multiple virtual-host sites works well with Apache. However, have you tried to do the same with Orion? By that, I don't mean one SSL certificate shared by multiple hosts - I mean multiple certificates, each of which is specific to a virtual host. I've tried for a long time to get that scenario to work, yet the best I can do is to have Orion recognize and share only one certificate among *all* of the virtual-hosts. That's not particularly useful. I'm to the point of placing just the SSL pages of all the sites on Apache, and using Orion only for the non-SSL part of the virtual-host sites. I was told by someone that this was an https limitation and not an Orion limitation, but it works on Apache, JavaWebServer, and IIS just fine. Any suggestions or ideas? Thanks! -Dale
Re: SSL w/ virtual domains really possible?
Magnus Stenman wrote: > - Original Message - > From: "Dale M. Boresz" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Saturday, September 30, 2000 5:15 AM > Subject: SSL w/ virtual domains really possible? > > > > I don't have any problem getting SSL to work. The problem is that with > > multiple certs and multiple virtual domains, all domains continue to use > > the same single cert - that one being the last one imported into the > > keystore. I don't understand by what mechanism the virtual domain is > > associated with a particular cert. > > > HTTPS is HTTP on top of SSL. The 'on top of' part is the important thing > here. The client first connects on the socket level and negotiates the > secure connection. This includes identifying which certificate the server > uses etc. When this is done the client sends the HTTP request, this includes > the host (site) that it wants to access. Hence it is impossible to use > different certs for virtual hosts using the same IP and port. This is a > HTTPS limitation, not Orion limitation. > > As for posting to this forum; as Karl already said: it is an unsupported > user to user forum. That does not prevent it from being useful of course, a > lot of users get helped in here. We will write up a short document on OI > guidelines since the current info doesnt seem to suffice. It will also be > covering stuff like not posting attachments to the list (use a link instead) > and so on. > > Even if you do mail info@ you cannot rely on getting a response unless > you're a customer (which use support@ and specify their customer info etc). > It depends on how tight a schedule we're on, and these days it's pretty > tight. We're expanding with a support staff soon hopefully but even then > paying customers have to be prioritized, which I'm sure you understand. > > Have a nice day! > > /Magnus Stenman, the Orion team Magnus, Thanks very much for the response, and I apologize for trying to flag you down via the group. I understand the tight schedule you guys must be under, and that responses must be prioritized. Thanks again, -Dale
SSL w/ virtual domains really possible?
This is my fourth posting, and still no response from the Orion team. The question remains: When using virtual domains, and multiple certificates - how do I get the correct certificate associated with the appropriate domain??? All certs in same keystore? Each cert in a separate keystore? Separate secure-web-site.xml file for each site? I don't have any problem getting SSL to work. The problem is that with multiple certs and multiple virtual domains, all domains continue to use the same single cert - that one being the last one imported into the keystore. I don't understand by what mechanism the virtual domain is associated with a particular cert. I've been through the three-step SSL How-To, and it does NOT address this issue - nor does any other part of the documentation. I can't believe that SSL can work on only one site under Orion, and I'm sure that I'm just missing a line or two in a configuration file, but I've spent almost 40 hours trying to 'guess' the right way - without success. Orion team - P-l-e-a-s-e address this. I can't be the only one trying to get more than one virtual domain SSL site running under Orion. Thank you. -Dale
SSL certs for multiple virtual domains
Karl, I've been struggling for the last four days to get Orion to associate the correct certificates with the appropriate virtual sites, and have been completely unsuccessful. No problem in establishing a secure connection - but it's not using the correct certificate. By what mechanism does Orion associate a certificate with a virtual site??? This must be what I'm missing, but I can't find any reference to it in the documentation. Thanks for any assistance. -Dale
Re: Associating SSL certs with appropriate site
"Van Dooren, Damian" wrote: > You should be using two different files for your keystores, on for CompnayA > and one for CompanyB. > > > -Original Message- > > From: Dale M. Boresz [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, September 27, 2000 8:03 AM > > To: Orion-Interest > > Subject: Associating SSL certs with appropriate site > > > > > > To any SSL guru's: > > > > I have two (servlet/jsp) web sites set up (CompanyA and > > CompanyB), with > > each site capable of being accessed normally and via SSL. I have a > > certificate for each site, and both certificates are contained in a > > common "keystore". I am unable to persuade the Orion server > > to associate > > the correct SSL certificate with the appropriate site. When I > > attempt to > > access either site via SSL, I always get the certificate for > > CompanyB - > > which was the last one imported into the keystore. (I don't know if > > that's significant or not.) > > > > The locations of significant files: > > > > CompanyA is at: > > orion/applications/CompA/CompA-web/WEB-INF/web-site.xml > > orion/applications/CompA/CompA-web/WEB-INF/secure-web-site.xml > > > > CompanyB is at: > > orion/applications/CompB/CompB-web/WEB-INF/web-site.xml > > orion/applications/CompB/CompB-web/WEB-INF/secure-web-site.xml > > > > The Keystore is at: > > orion/keystore > > (The CN for each certificate matched the domain name of each site - > > i.e. www.companya.com, and www.companyb.com) > > > > Orion configuration file: > > orion/config/server.xml > > > > The file contents (minus the dtd header info): > > CompanyA web-site.xml: > > > virtual-hosts="www.companya.com"> > >> shared="true" /> > > > >> root="/CompA/CompA-web" > > /> > > > > > > CompanyA secure-web-site.xml: > > > virtual-hosts="www.companya.com"> > >> shared="true" /> > > > >> root="/CompA/CompA-web" > > /> > >> keystore-password="123456" > > /> > > > > > > (CompanyB files look the same - except CompA is CompB etc.) > > > > Orion server.xml configuration file: > > > application-directory="../applications" > > deployment-directory="../application-deployments"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >> path="../applications/CompA/CompA-web/WEB-INF/web-site.xml" > > /> > >> path="../applications/CompA/CompA-web/WEB-INF/secure-web-site.xml" /> > > > > > >> path="../applications/CompB/CompB-web/WEB-INF/web-site.xml" > > /> > >> path="../applications/CompB/CompB-web/WEB-INF/secure-web-site.xml" /> > > > > > > > > When I attempt to access either https://www.companya.com or > > https://www.companyb.com, I gain access to the appropriate site, BUT > > always using the certificate for www.companyb.com. > > > > Thanks in advance for any help or insight into what I am doing wrong! > > > > -Dale > > > > Damian, Thanks for your reply, however that was actually the way I had tried it originally. However, I did try something new... I used a separate keystore for each company as you suggested, and took it a step further by assigning each keystore a different password. Unfortunately - same result. I DID notice though, that the certificate that gets used seems to be the one which has it's "secure-web-site.xml" reference listed first in the server.xml file. If I swap the order, then it changes over to using the other certificate. This is extremely frustrating. It's seems like this should be a very fundamental and common scenario, yet I've found NO mention of it in any of Orion's (very meager) documentation. Thanks for your response. -Dale
Associating SSL certs with appropriate site
To any SSL guru's: I have two (servlet/jsp) web sites set up (CompanyA and CompanyB), with each site capable of being accessed normally and via SSL. I have a certificate for each site, and both certificates are contained in a common "keystore". I am unable to persuade the Orion server to associate the correct SSL certificate with the appropriate site. When I attempt to access either site via SSL, I always get the certificate for CompanyB - which was the last one imported into the keystore. (I don't know if that's significant or not.) The locations of significant files: CompanyA is at: orion/applications/CompA/CompA-web/WEB-INF/web-site.xml orion/applications/CompA/CompA-web/WEB-INF/secure-web-site.xml CompanyB is at: orion/applications/CompB/CompB-web/WEB-INF/web-site.xml orion/applications/CompB/CompB-web/WEB-INF/secure-web-site.xml The Keystore is at: orion/keystore (The CN for each certificate matched the domain name of each site - i.e. www.companya.com, and www.companyb.com) Orion configuration file: orion/config/server.xml The file contents (minus the dtd header info): CompanyA web-site.xml: CompanyA secure-web-site.xml: (CompanyB files look the same - except CompA is CompB etc.) Orion server.xml configuration file: When I attempt to access either https://www.companya.com or https://www.companyb.com, I gain access to the appropriate site, BUT always using the certificate for www.companyb.com. Thanks in advance for any help or insight into what I am doing wrong! -Dale
