Setup Virtual Host w/HTML Calendar v8.5.3

[Latesha Williams]

Per the MM HTML Calendar setup documentation. . .

The previous version of the HTML Calendar (i.e. v7.x Java Client)
installed itself into the mmwebclient directory of the Apache Tomcat
webapps directory. In version 8.5.x, the HTML Calendar is no longer
installed there. The files are installed in a different directory, which

is specified during the installation. The Apache Tomcat webapps director
y
contains an XML file that references the "new HTML Calendar directory."

In order to setup a virtual host to hide the port number from being
displayed in the URL, in version MM 7.x the appBase and docBase parameter
s
(in server.xml Host definition) referenced the mmwebclient directory unde
r
webapps. In v8.5.3, when I setup appBase and docBase to reference
the "new HTML Calendar directory," I get the following errors when typing

the URL:

http://<virtual-host-name>/context

"There was an unhandled error condition. Please try again. If this proble
m
persists, please contact your network administrator.

Administrator diagnostic information: Failure logged on 19 Dec 2006
14:38:12,509 as incident 10,001; the original exception text is:
javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot

find bean under name database
The server log has more information on this error."

When I check the log file catalina.out, the following errors:

"ERROR [main] SessionManager - Error locating configuration parameter
mm_config_file javax.naming.NameNotFoundException: Name mm_config_file is

not bound in this Context"

Has anyone else run into this problem? We prefer running Apache Tomcat a
s
a standalone server, hiding the port numbers from the URL. Any advice is

appreciated. We are running version Apache Tomcat v5.5.20.


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Rich Trouton]

What platform are you running Tomcat on? Also, when I ran into Tomcat
problems earlier this year, PeopleCube told me at that point that
they were supporting Tomcat 5.5.9 and no higher. I actually had to
downgrade my Tomcat 5.5 install from .17 to .9.

Thanks,
Rich


On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:

> Per the MM HTML Calendar setup documentation. . .
>
> The previous version of the HTML Calendar (i.e. v7.x Java Client)
> installed itself into the mmwebclient directory of the Apache Tomcat
> webapps directory. In version 8.5.x, the HTML Calendar is no longer
> installed there. The files are installed in a different directory,
> which
>
> is specified during the installation. The Apache Tomcat webapps
> director
> y
> contains an XML file that references the "new HTML Calendar
> directory."
>
> In order to setup a virtual host to hide the port number from being
> displayed in the URL, in version MM 7.x the appBase and docBase
> parameter
> s
> (in server.xml Host definition) referenced the mmwebclient
> directory unde
> r
> webapps. In v8.5.3, when I setup appBase and docBase to reference
> the "new HTML Calendar directory," I get the following errors when
> typing
>
> the URL:
>
> http://<virtual-host-name>/context
>
> "There was an unhandled error condition. Please try again. If this
> proble
> m
> persists, please contact your network administrator.
>
> Administrator diagnostic information: Failure logged on 19 Dec 2006
> 14:38:12,509 as incident 10,001; the original exception text is:
> javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot
>
> find bean under name database
> The server log has more information on this error."
>
> When I check the log file catalina.out, the following errors:
>
> "ERROR [main] SessionManager - Error locating configuration parameter
> mm_config_file javax.naming.NameNotFoundException: Name
> mm_config_file is
>
> not bound in this Context"
>
> Has anyone else run into this problem? We prefer running Apache
> Tomcat a
> s
> a standalone server, hiding the port numbers from the URL. Any
> advice is
>
> appreciated. We are running version Apache Tomcat v5.5.20.
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
>

---

Rich Trouton (Contractor)
LAN Support
***@mail.nih.gov
-----------------------------------------------------------
National Human Genome Research Institute
National Institutes of Health — Bethesda, MD

Office number:
[phone]

NHGRI LAN Support number:
[phone]

The best way to get in touch with me is through email.




* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Latesha Williams]

Red Hat Linux Enterprise v4 w/Sun Java JDK 1.5.0_09

Rich Trouton wrote:
> What platform are you running Tomcat on? Also, when I ran into Tomcat
> problems earlier this year, PeopleCube told me at that point that they
> were supporting Tomcat 5.5.9 and no higher. I actually had to downgrade
> my Tomcat 5.5 install from .17 to .9.
>
> Thanks,
> Rich
>
>
> On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
>
>> Per the MM HTML Calendar setup documentation. . .
>>
>> The previous version of the HTML Calendar (i.e. v7.x Java Client)
>> installed itself into the mmwebclient directory of the Apache Tomcat
>> webapps directory. In version 8.5.x, the HTML Calendar is no longer
>> installed there. The files are installed in a different directory, which
>>
>> is specified during the installation. The Apache Tomcat webapps director
>> y
>> contains an XML file that references the "new HTML Calendar directory."
>>
>> In order to setup a virtual host to hide the port number from being
>> displayed in the URL, in version MM 7.x the appBase and docBase parameter
>> s
>> (in server.xml Host definition) referenced the mmwebclient directory unde
>> r
>> webapps. In v8.5.3, when I setup appBase and docBase to reference
>> the "new HTML Calendar directory," I get the following errors when typing
>>
>> the URL:
>>
>> http://<virtual-host-name>/context
>>
>> "There was an unhandled error condition. Please try again. If this proble
>> m
>> persists, please contact your network administrator.
>>
>> Administrator diagnostic information: Failure logged on 19 Dec 2006
>> 14:38:12,509 as incident 10,001; the original exception text is:
>> javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot
>>
>> find bean under name database
>> The server log has more information on this error."
>>
>> When I check the log file catalina.out, the following errors:
>>
>> "ERROR [main] SessionManager - Error locating configuration parameter
>> mm_config_file javax.naming.NameNotFoundException: Name mm_config_file is
>>
>> not bound in this Context"
>>
>> Has anyone else run into this problem? We prefer running Apache Tomcat a
>> s
>> a standalone server, hiding the port numbers from the URL. Any advice is
>>
>> appreciated. We are running version Apache Tomcat v5.5.20.
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>>
>
> ---
>
>
> Rich Trouton (Contractor)
>
> LAN Support
>
> ***@mail.nih.gov <mailto:***@mail.nih.gov>
>
> -----------------------------------------------------------
>
> National Human Genome Research Institute
>
> National Institutes of Health — Bethesda, MD
>
>
> Office number:
>
> [phone]
>
>
> NHGRI LAN Support number:
>
> [phone]
>
>
> The best way to get in touch with me is through email.
>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>

--
Latesha Williams
Applications Support, Information Technology
American Museum of Natural History
212.769.5947 (Office)
917.837.2460 (Cell)


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Latesha Williams]

We can launch the MM HTML Calendar successfully, as follows:

http://<hostname>:8080/context

I have two questions about your previous problems:

(1) Were you getting a similar errors after configuring a virtual host?

(2) Did the problem go away once you downgraded to v5.5.9?

-L


Rich Trouton wrote:
> What platform are you running Tomcat on? Also, when I ran into Tomcat
> problems earlier this year, PeopleCube told me at that point that they
> were supporting Tomcat 5.5.9 and no higher. I actually had to downgrade
> my Tomcat 5.5 install from .17 to .9.
>
> Thanks,
> Rich
>
>
> On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
>
>> Per the MM HTML Calendar setup documentation. . .
>>
>> The previous version of the HTML Calendar (i.e. v7.x Java Client)
>> installed itself into the mmwebclient directory of the Apache Tomcat
>> webapps directory. In version 8.5.x, the HTML Calendar is no longer
>> installed there. The files are installed in a different directory, which
>>
>> is specified during the installation. The Apache Tomcat webapps director
>> y
>> contains an XML file that references the "new HTML Calendar directory."
>>
>> In order to setup a virtual host to hide the port number from being
>> displayed in the URL, in version MM 7.x the appBase and docBase parameter
>> s
>> (in server.xml Host definition) referenced the mmwebclient directory unde
>> r
>> webapps. In v8.5.3, when I setup appBase and docBase to reference
>> the "new HTML Calendar directory," I get the following errors when typing
>>
>> the URL:
>>
>> http://<virtual-host-name>/context
>>
>> "There was an unhandled error condition. Please try again. If this proble
>> m
>> persists, please contact your network administrator.
>>
>> Administrator diagnostic information: Failure logged on 19 Dec 2006
>> 14:38:12,509 as incident 10,001; the original exception text is:
>> javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot
>>
>> find bean under name database
>> The server log has more information on this error."
>>
>> When I check the log file catalina.out, the following errors:
>>
>> "ERROR [main] SessionManager - Error locating configuration parameter
>> mm_config_file javax.naming.NameNotFoundException: Name mm_config_file is
>>
>> not bound in this Context"
>>
>> Has anyone else run into this problem? We prefer running Apache Tomcat a
>> s
>> a standalone server, hiding the port numbers from the URL. Any advice is
>>
>> appreciated. We are running version Apache Tomcat v5.5.20.
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>>
>
> ---
>
>
> Rich Trouton (Contractor)
>
> LAN Support
>
> ***@mail.nih.gov <mailto:***@mail.nih.gov>
>
> -----------------------------------------------------------
>
> National Human Genome Research Institute
>
> National Institutes of Health — Bethesda, MD
>
>
> Office number:
>
> [phone]
>
>
> NHGRI LAN Support number:
>
> [phone]
>
>
> The best way to get in touch with me is through email.
>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>

--
Latesha Williams
Applications Support, Information Technology
American Museum of Natural History
212.769.5947 (Office)
917.837.2460 (Cell)


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Rich Trouton]

I didn't wind up configuring a virtual host. I tried, but in the end
I wasn't successful and it was decided that it didn't matter as much
as long as I was able to set up a redirect on the web server to point
to the right URL if people entered the URL without the port numbers.
My Tomcat problems did go away after I downgraded to 5.5.9.

Thanks,
Rich


On Dec 19, 2006, at 3:11 PM, Latesha Williams wrote:

> We can launch the MM HTML Calendar successfully, as follows:
>
> http://<hostname>:8080/context
>
> I have two questions about your previous problems:
>
> (1) Were you getting a similar errors after configuring a virtual
> host?
>
> (2) Did the problem go away once you downgraded to v5.5.9?
>
> -L
>
>
> Rich Trouton wrote:
> > What platform are you running Tomcat on? Also, when I ran into
> Tomcat
> > problems earlier this year, PeopleCube told me at that point that
> they
> > were supporting Tomcat 5.5.9 and no higher. I actually had to
> downgrade
> > my Tomcat 5.5 install from .17 to .9.
> >
> > Thanks,
> > Rich
> >
> >
> > On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
> >
> >> Per the MM HTML Calendar setup documentation. . .
> >>
> >> The previous version of the HTML Calendar (i.e. v7.x Java Client)
> >> installed itself into the mmwebclient directory of the Apache
> Tomcat
> >> webapps directory. In version 8.5.x, the HTML Calendar is no
> longer
> >> installed there. The files are installed in a different
> directory, which
> >>
> >> is specified during the installation. The Apache Tomcat webapps
> director
> >> y
> >> contains an XML file that references the "new HTML Calendar
> directory."
> >>
> >> In order to setup a virtual host to hide the port number from being
> >> displayed in the URL, in version MM 7.x the appBase and docBase
> parameter
> >> s
> >> (in server.xml Host definition) referenced the mmwebclient
> directory unde
> >> r
> >> webapps. In v8.5.3, when I setup appBase and docBase to reference
> >> the "new HTML Calendar directory," I get the following errors
> when typing
> >>
> >> the URL:
> >>
> >> http://<virtual-host-name>/context
> >>
> >> "There was an unhandled error condition. Please try again. If
> this proble
> >> m
> >> persists, please contact your network administrator.
> >>
> >> Administrator diagnostic information: Failure logged on 19 Dec 2006
> >> 14:38:12,509 as incident 10,001; the original exception text is:
> >> javax.servlet.ServletException: javax.servlet.jsp.JspException:
> Cannot
> >>
> >> find bean under name database
> >> The server log has more information on this error."
> >>
> >> When I check the log file catalina.out, the following errors:
> >>
> >> "ERROR [main] SessionManager - Error locating configuration
> parameter
> >> mm_config_file javax.naming.NameNotFoundException: Name
> mm_config_file is
> >>
> >> not bound in this Context"
> >>
> >> Has anyone else run into this problem? We prefer running Apache
> Tomcat a
> >> s
> >> a standalone server, hiding the port numbers from the URL. Any
> advice is
> >>
> >> appreciated. We are running version Apache Tomcat v5.5.20.
> >>
> >>
> >> * MMXP-TALK Web Page:
> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
> >>
> >
> > ---
> >
> >
> > Rich Trouton (Contractor)
> >
> > LAN Support
> >
> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
> >
> > -----------------------------------------------------------
> >
> > National Human Genome Research Institute
> >
> > National Institutes of Health — Bethesda, MD
> >
> >
> > Office number:
> >
> > [phone]
> >
> >
> > NHGRI LAN Support number:
> >
> > [phone]
> >
> >
> > The best way to get in touch with me is through email.
> >
> >
> >
> > * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
> >
>
> --
> Latesha Williams
> Applications Support, Information Technology
> American Museum of Natural History
> 212.769.5947 (Office)
> 917.837.2460 (Cell)
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
>

---

Rich Trouton (Contractor)
LAN Support
***@mail.nih.gov
-----------------------------------------------------------
National Human Genome Research Institute
National Institutes of Health — Bethesda, MD

Office number:
[phone]

NHGRI LAN Support number:
[phone]

The best way to get in touch with me is through email.




* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Latesha Williams]

That sounds like a better option than downgrading. We tested the HTML
client with no problems except for items found under "Tips and Known
Issues" in the release notes. Did you refer to the article #3543 on
People Cube support site for the redirect? If so, how did you go about
setting up the redirect if Apache Tomcat default page is precompiled and
cannot be edited? I am not a web developer, but can get one involved if
necessary (I'd rather avoid this to keep it simple.) Please advise.


Rich Trouton wrote:
> I didn't wind up configuring a virtual host. I tried, but in the end I
> wasn't successful and it was decided that it didn't matter as much as
> long as I was able to set up a redirect on the web server to point to
> the right URL if people entered the URL without the port numbers. My
> Tomcat problems did go away after I downgraded to 5.5.9.
>
> Thanks,
> Rich
>
>
> On Dec 19, 2006, at 3:11 PM, Latesha Williams wrote:
>
>> We can launch the MM HTML Calendar successfully, as follows:
>>
>> http://<hostname>:8080/context
>>
>> I have two questions about your previous problems:
>>
>> (1) Were you getting a similar errors after configuring a virtual host?
>>
>> (2) Did the problem go away once you downgraded to v5.5.9?
>>
>> -L
>>
>>
>> Rich Trouton wrote:
>> > What platform are you running Tomcat on? Also, when I ran into Tomcat
>> > problems earlier this year, PeopleCube told me at that point that they
>> > were supporting Tomcat 5.5.9 and no higher. I actually had to downgrade
>> > my Tomcat 5.5 install from .17 to .9.
>> >
>> > Thanks,
>> > Rich
>> >
>> >
>> > On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
>> >
>> >> Per the MM HTML Calendar setup documentation. . .
>> >>
>> >> The previous version of the HTML Calendar (i.e. v7.x Java Client)
>> >> installed itself into the mmwebclient directory of the Apache Tomcat
>> >> webapps directory. In version 8.5.x, the HTML Calendar is no longer
>> >> installed there. The files are installed in a different directory,
>> which
>> >>
>> >> is specified during the installation. The Apache Tomcat webapps
>> director
>> >> y
>> >> contains an XML file that references the "new HTML Calendar directory."
>> >>
>> >> In order to setup a virtual host to hide the port number from being
>> >> displayed in the URL, in version MM 7.x the appBase and docBase
>> parameter
>> >> s
>> >> (in server.xml Host definition) referenced the mmwebclient
>> directory unde
>> >> r
>> >> webapps. In v8.5.3, when I setup appBase and docBase to reference
>> >> the "new HTML Calendar directory," I get the following errors when
>> typing
>> >>
>> >> the URL:
>> >>
>> >> http://<virtual-host-name>/context
>> >>
>> >> "There was an unhandled error condition. Please try again. If this
>> proble
>> >> m
>> >> persists, please contact your network administrator.
>> >>
>> >> Administrator diagnostic information: Failure logged on 19 Dec 2006
>> >> 14:38:12,509 as incident 10,001; the original exception text is:
>> >> javax.servlet.ServletException: javax.servlet.jsp.JspException: Cannot
>> >>
>> >> find bean under name database
>> >> The server log has more information on this error."
>> >>
>> >> When I check the log file catalina.out, the following errors:
>> >>
>> >> "ERROR [main] SessionManager - Error locating configuration parameter
>> >> mm_config_file javax.naming.NameNotFoundException: Name
>> mm_config_file is
>> >>
>> >> not bound in this Context"
>> >>
>> >> Has anyone else run into this problem? We prefer running Apache
>> Tomcat a
>> >> s
>> >> a standalone server, hiding the port numbers from the URL. Any
>> advice is
>> >>
>> >> appreciated. We are running version Apache Tomcat v5.5.20.
>> >>
>> >>
>> >> * MMXP-TALK Web Page:
>> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >>
>> >
>> > ---
>> >
>> >
>> > Rich Trouton (Contractor)
>> >
>> > LAN Support
>> >
>> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
>> <mailto:***@mail.nih.gov>
>> >
>> > -----------------------------------------------------------
>> >
>> > National Human Genome Research Institute
>> >
>> > National Institutes of Health — Bethesda, MD
>> >
>> >
>> > Office number:
>> >
>> > [phone]
>> >
>> >
>> > NHGRI LAN Support number:
>> >
>> > [phone]
>> >
>> >
>> > The best way to get in touch with me is through email.
>> >
>> >
>> >
>> > * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >
>>
>> --
>> Latesha Williams
>> Applications Support, Information Technology
>> American Museum of Natural History
>> 212.769.5947 (Office)
>> 917.837.2460 (Cell)
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>>
>
> ---
>
>
> Rich Trouton (Contractor)
>
> LAN Support
>
> ***@mail.nih.gov <mailto:***@mail.nih.gov>
>
> -----------------------------------------------------------
>
> National Human Genome Research Institute
>
> National Institutes of Health — Bethesda, MD
>
>
> Office number:
>
> [phone]
>
>
> NHGRI LAN Support number:
>
> [phone]
>
>
> The best way to get in touch with me is through email.
>
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>

--
Latesha Williams
Applications Support, Information Technology
American Museum of Natural History
212.769.5947 (Office)
917.837.2460 (Cell)


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Rich Trouton]

I used Apache for the redirect, as I've got both Tomcat 5.5.9 and a
regular Apache webserver running on my Meeting Maker server.
Basically, if Apache sees a request for http://server.name/
mmwebclient, https://server.name/mmwebclient, http://server.name/
mmwebclient/, or https://server.name/mmwebclient/, it redirects the
request to https://server.name:8443/mmwebclient

Thanks,
Rich

On Dec 19, 2006, at 3:58 PM, Latesha Williams wrote:

> That sounds like a better option than downgrading. We tested the HTML
> client with no problems except for items found under "Tips and Known
> Issues" in the release notes. Did you refer to the article #3543 on
> People Cube support site for the redirect? If so, how did you go
> about
> setting up the redirect if Apache Tomcat default page is
> precompiled and
> cannot be edited? I am not a web developer, but can get one
> involved if
> necessary (I'd rather avoid this to keep it simple.) Please advise.
>
>
> Rich Trouton wrote:
> > I didn't wind up configuring a virtual host. I tried, but in the
> end I
> > wasn't successful and it was decided that it didn't matter as
> much as
> > long as I was able to set up a redirect on the web server to
> point to
> > the right URL if people entered the URL without the port numbers. My
> > Tomcat problems did go away after I downgraded to 5.5.9.
> >
> > Thanks,
> > Rich
> >
> >
> > On Dec 19, 2006, at 3:11 PM, Latesha Williams wrote:
> >
> >> We can launch the MM HTML Calendar successfully, as follows:
> >>
> >> http://<hostname>:8080/context
> >>
> >> I have two questions about your previous problems:
> >>
> >> (1) Were you getting a similar errors after configuring a
> virtual host?
> >>
> >> (2) Did the problem go away once you downgraded to v5.5.9?
> >>
> >> -L
> >>
> >>
> >> Rich Trouton wrote:
> >> > What platform are you running Tomcat on? Also, when I ran into
> Tomcat
> >> > problems earlier this year, PeopleCube told me at that point
> that they
> >> > were supporting Tomcat 5.5.9 and no higher. I actually had to
> downgrade
> >> > my Tomcat 5.5 install from .17 to .9.
> >> >
> >> > Thanks,
> >> > Rich
> >> >
> >> >
> >> > On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
> >> >
> >> >> Per the MM HTML Calendar setup documentation. . .
> >> >>
> >> >> The previous version of the HTML Calendar (i.e. v7.x Java
> Client)
> >> >> installed itself into the mmwebclient directory of the Apache
> Tomcat
> >> >> webapps directory. In version 8.5.x, the HTML Calendar is no
> longer
> >> >> installed there. The files are installed in a different
> directory,
> >> which
> >> >>
> >> >> is specified during the installation. The Apache Tomcat webapps
> >> director
> >> >> y
> >> >> contains an XML file that references the "new HTML Calendar
> directory."
> >> >>
> >> >> In order to setup a virtual host to hide the port number from
> being
> >> >> displayed in the URL, in version MM 7.x the appBase and docBase
> >> parameter
> >> >> s
> >> >> (in server.xml Host definition) referenced the mmwebclient
> >> directory unde
> >> >> r
> >> >> webapps. In v8.5.3, when I setup appBase and docBase to
> reference
> >> >> the "new HTML Calendar directory," I get the following errors
> when
> >> typing
> >> >>
> >> >> the URL:
> >> >>
> >> >> http://<virtual-host-name>/context
> >> >>
> >> >> "There was an unhandled error condition. Please try again. If
> this
> >> proble
> >> >> m
> >> >> persists, please contact your network administrator.
> >> >>
> >> >> Administrator diagnostic information: Failure logged on 19
> Dec 2006
> >> >> 14:38:12,509 as incident 10,001; the original exception text is:
> >> >> javax.servlet.ServletException:
> javax.servlet.jsp.JspException: Cannot
> >> >>
> >> >> find bean under name database
> >> >> The server log has more information on this error."
> >> >>
> >> >> When I check the log file catalina.out, the following errors:
> >> >>
> >> >> "ERROR [main] SessionManager - Error locating configuration
> parameter
> >> >> mm_config_file javax.naming.NameNotFoundException: Name
> >> mm_config_file is
> >> >>
> >> >> not bound in this Context"
> >> >>
> >> >> Has anyone else run into this problem? We prefer running Apache
> >> Tomcat a
> >> >> s
> >> >> a standalone server, hiding the port numbers from the URL. Any
> >> advice is
> >> >>
> >> >> appreciated. We are running version Apache Tomcat v5.5.20.
> >> >>
> >> >>
> >> >> * MMXP-TALK Web Page:
> >> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
> >> >>
> >> >
> >> > ---
> >> >
> >> >
> >> > Rich Trouton (Contractor)
> >> >
> >> > LAN Support
> >> >
> >> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
> >> <mailto:***@mail.nih.gov>
> >> >
> >> > -----------------------------------------------------------
> >> >
> >> > National Human Genome Research Institute
> >> >
> >> > National Institutes of Health — Bethesda, MD
> >> >
> >> >
> >> > Office number:
> >> >
> >> > [phone]
> >> >
> >> >
> >> > NHGRI LAN Support number:
> >> >
> >> > [phone]
> >> >
> >> >
> >> > The best way to get in touch with me is through email.
> >> >
> >> >
> >> >
> >> > * MMXP-TALK Web Page:
> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
> >> >
> >>
> >> --
> >> Latesha Williams
> >> Applications Support, Information Technology
> >> American Museum of Natural History
> >> 212.769.5947 (Office)
> >> 917.837.2460 (Cell)
> >>
> >>
> >> * MMXP-TALK Web Page:
> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
> >>
> >
> > ---
> >
> >
> > Rich Trouton (Contractor)
> >
> > LAN Support
> >
> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
> >
> > -----------------------------------------------------------
> >
> > National Human Genome Research Institute
> >
> > National Institutes of Health — Bethesda, MD
> >
> >
> > Office number:
> >
> > [phone]
> >
> >
> > NHGRI LAN Support number:
> >
> > [phone]
> >
> >
> > The best way to get in touch with me is through email.
> >
> >
> >
> > * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
> >
>
> --
> Latesha Williams
> Applications Support, Information Technology
> American Museum of Natural History
> 212.769.5947 (Office)
> 917.837.2460 (Cell)
>
>
> * MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-
> TALK.HTML
>

---

Rich Trouton (Contractor)
LAN Support
***@mail.nih.gov
-----------------------------------------------------------
National Human Genome Research Institute
National Institutes of Health — Bethesda, MD

Office number:
[phone]

NHGRI LAN Support number:
[phone]

The best way to get in touch with me is through email.




* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

[Latesha Williams]

Gotcha. Thanks.

Rich Trouton wrote:
> I used Apache for the redirect, as I've got both Tomcat 5.5.9 and a
> regular Apache webserver running on my Meeting Maker server. Basically,
> if Apache sees a request for http://server.name/mmwebclient,
> https://server.name/mmwebclient, http://server.name/mmwebclient/, or
> https://server.name/mmwebclient/, it redirects the request to
> https://server.name:8443/mmwebclient
>
> Thanks,
> Rich
>
> On Dec 19, 2006, at 3:58 PM, Latesha Williams wrote:
>
>> That sounds like a better option than downgrading. We tested the HTML
>> client with no problems except for items found under "Tips and Known
>> Issues" in the release notes. Did you refer to the article #3543 on
>> People Cube support site for the redirect? If so, how did you go about
>> setting up the redirect if Apache Tomcat default page is precompiled and
>> cannot be edited? I am not a web developer, but can get one involved if
>> necessary (I'd rather avoid this to keep it simple.) Please advise.
>>
>>
>> Rich Trouton wrote:
>> > I didn't wind up configuring a virtual host. I tried, but in the end I
>> > wasn't successful and it was decided that it didn't matter as much as
>> > long as I was able to set up a redirect on the web server to point to
>> > the right URL if people entered the URL without the port numbers. My
>> > Tomcat problems did go away after I downgraded to 5.5.9.
>> >
>> > Thanks,
>> > Rich
>> >
>> >
>> > On Dec 19, 2006, at 3:11 PM, Latesha Williams wrote:
>> >
>> >> We can launch the MM HTML Calendar successfully, as follows:
>> >>
>> >> http://<hostname>:8080/context
>> >>
>> >> I have two questions about your previous problems:
>> >>
>> >> (1) Were you getting a similar errors after configuring a virtual
>> host?
>> >>
>> >> (2) Did the problem go away once you downgraded to v5.5.9?
>> >>
>> >> -L
>> >>
>> >>
>> >> Rich Trouton wrote:
>> >> > What platform are you running Tomcat on? Also, when I ran into
>> Tomcat
>> >> > problems earlier this year, PeopleCube told me at that point that
>> they
>> >> > were supporting Tomcat 5.5.9 and no higher. I actually had to
>> downgrade
>> >> > my Tomcat 5.5 install from .17 to .9.
>> >> >
>> >> > Thanks,
>> >> > Rich
>> >> >
>> >> >
>> >> > On Dec 19, 2006, at 2:49 PM, Latesha Williams wrote:
>> >> >
>> >> >> Per the MM HTML Calendar setup documentation. . .
>> >> >>
>> >> >> The previous version of the HTML Calendar (i.e. v7.x Java Client)
>> >> >> installed itself into the mmwebclient directory of the Apache
>> Tomcat
>> >> >> webapps directory. In version 8.5.x, the HTML Calendar is no
>> longer
>> >> >> installed there. The files are installed in a different directory,
>> >> which
>> >> >>
>> >> >> is specified during the installation. The Apache Tomcat webapps
>> >> director
>> >> >> y
>> >> >> contains an XML file that references the "new HTML Calendar
>> directory."
>> >> >>
>> >> >> In order to setup a virtual host to hide the port number from being
>> >> >> displayed in the URL, in version MM 7.x the appBase and docBase
>> >> parameter
>> >> >> s
>> >> >> (in server.xml Host definition) referenced the mmwebclient
>> >> directory unde
>> >> >> r
>> >> >> webapps. In v8.5.3, when I setup appBase and docBase to reference
>> >> >> the "new HTML Calendar directory," I get the following errors when
>> >> typing
>> >> >>
>> >> >> the URL:
>> >> >>
>> >> >> http://<virtual-host-name>/context
>> >> >>
>> >> >> "There was an unhandled error condition. Please try again. If this
>> >> proble
>> >> >> m
>> >> >> persists, please contact your network administrator.
>> >> >>
>> >> >> Administrator diagnostic information: Failure logged on 19 Dec 2006
>> >> >> 14:38:12,509 as incident 10,001; the original exception text is:
>> >> >> javax.servlet.ServletException: javax.servlet.jsp.JspException:
>> Cannot
>> >> >>
>> >> >> find bean under name database
>> >> >> The server log has more information on this error."
>> >> >>
>> >> >> When I check the log file catalina.out, the following errors:
>> >> >>
>> >> >> "ERROR [main] SessionManager - Error locating configuration
>> parameter
>> >> >> mm_config_file javax.naming.NameNotFoundException: Name
>> >> mm_config_file is
>> >> >>
>> >> >> not bound in this Context"
>> >> >>
>> >> >> Has anyone else run into this problem? We prefer running Apache
>> >> Tomcat a
>> >> >> s
>> >> >> a standalone server, hiding the port numbers from the URL. Any
>> >> advice is
>> >> >>
>> >> >> appreciated. We are running version Apache Tomcat v5.5.20.
>> >> >>
>> >> >>
>> >> >> * MMXP-TALK Web Page:
>> >> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >> >>
>> >> >
>> >> > ---
>> >> >
>> >> >
>> >> > Rich Trouton (Contractor)
>> >> >
>> >> > LAN Support
>> >> >
>> >> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
>> >> <mailto:***@mail.nih.gov>
>> >> >
>> >> > -----------------------------------------------------------
>> >> >
>> >> > National Human Genome Research Institute
>> >> >
>> >> > National Institutes of Health — Bethesda, MD
>> >> >
>> >> >
>> >> > Office number:
>> >> >
>> >> > [phone]
>> >> >
>> >> >
>> >> > NHGRI LAN Support number:
>> >> >
>> >> > [phone]
>> >> >
>> >> >
>> >> > The best way to get in touch with me is through email.
>> >> >
>> >> >
>> >> >
>> >> > * MMXP-TALK Web Page:
>> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >> >
>> >>
>> >> --
>> >> Latesha Williams
>> >> Applications Support, Information Technology
>> >> American Museum of Natural History
>> >> 212.769.5947 (Office)
>> >> 917.837.2460 (Cell)
>> >>
>> >>
>> >> * MMXP-TALK Web Page:
>> >> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >>
>> >
>> > ---
>> >
>> >
>> > Rich Trouton (Contractor)
>> >
>> > LAN Support
>> >
>> > ***@mail.nih.gov <mailto:***@mail.nih.gov>
>> >
>> > -----------------------------------------------------------
>> >
>> > National Human Genome Research Institute
>> >
>> > National Institutes of Health — Bethesda, MD
>> >
>> >
>> > Office number:
>> >
>> > [phone]
>> >
>> >
>> > NHGRI LAN Support number:
>> >
>> > [phone]
>> >
>> >
>> > The best way to get in touch with me is through email.
>> >
>> >
>> >
>> > * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>> >
>>
>> --
>> Latesha Williams
>> Applications Support, Information Technology
>> American Museum of Natural History
>> 212.769.5947 (Office)
>> 917.837.2460 (Cell)
>>
>>
>> * MMXP-TALK Web Page:
>> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML
>>
>
> ---
>
> Rich Trouton (Contractor)
> LAN Support
> ***@mail.nih.gov
> -----------------------------------------------------------
> National Human Genome Research Institute
> National Institutes of Health — Bethesda, MD
>
> Office number:
> [phone]
>
> NHGRI LAN Support number:
> [phone]
>
> The best way to get in touch with me is through email.
>
>
>
>
> * MMXP-TALK Web Page:
> http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML

--
Latesha Williams
Applications Support, Information Technology
American Museum of Natural History
212.769.5947 (Office)
917.837.2460 (Cell)


* MMXP-TALK Web Page: http://WWW.LISTSERV.Emory.Edu/Archives/MMXP-TALK.HTML