Re: question on certificate use - resending with attachment descriptions in case they get stripped out again. If this doesnt work I will resend the email when I get home

2014-10-02 Thread Ognjen Blagojevic

Ray,

On 1.10.2014 21:05, ray.d...@usbank.com wrote:

Loaded the website and let the error popup happen once, then I install
the certificate it prompts about (to my truststore).


If you mean that you imported CA-signed certificate to your Java 
keystore where your private key is already stored, using keytool, then, 
everything should be Ok.


If you have done something else, please explain what.

-Ognjen

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Tomcat 8.0.14 - doesn§t start from Netbeans 8.0.1 IDE

2014-10-02 Thread Mitev, Mitko
Hi,

I have just encountered the following issue:
I installed Tomcat 8.0.14 on my PC ( Win 7) and integrated it to Netbeans 8.0.1
I tried to start Tomcat from Netbeans IDE and I’ve got the following error:
'127.0.0.1' is not recognized as an internal or external command,
operable program or batch file.

I have been using Netbeans and Tomcat for many years and I have never 
encountered such problem. The previous version - Tomcat 8.0.12 – works fine in 
my environment.

Any hints?
Mitko Mitev
RD CZ 32 Team Lead
Unify, s.r.o.
Bidláky 20, budova Mediahall
639 00 Brno
 
Tel,: +420 266 061 251
Fax: +420 266 066 251
Mobil: +420 724 754 090
mailto: mitko.mi...@unify.commailto:mitko.mi...@unify.com
www.unify.com/czwww.siemens-enterprise.com
Follow us [Social_media_icons] http://www.unify.com/us/about/social-media.aspx

Unify s.r.o., zapsaná v obchodním rejstříku vedeném Městským soudem v Praze, 
oddíl C, vložka 117991
Sídlo:  Průmyslová 1306/7,  102 00 Praha 10 – Hostivař, IČ: 27599523, DIČ: 
CZ27599523
Jednatelé:  Jan Lerche  a  Ing. Tomáš Hájek
Bankovní spojení:  UniCredit Bank Czech Republic a.s., Nám. Republiky 3a/2090,  
110 05  Praha 1,
č.ú. CZK: 513686001/2700,  č.ú. EUR: 513686028/2700

POZOR!
Důležité upozornění: Tato zpráva i její případné přílohy jsou důvěrného 
charakteru, mohou obsahovat obchodní tajemství a být chráněny před zveřejněním. 
Pokud jste zprávu obdrželi omylem, kontaktujte prosím odesílatele a předmětnou 
zprávu i s přílohami ihned ze svého systému vymažte. Jakékoli změny, 
přeposílání či jiné aktivity související s informacemi v této zprávě, nejsou 
dovoleny jiným osobám, než kterým je zpráva určena.
Important Note!
This e-mail and any attachment are confidential and may contain trade secrets 
and may also be legally privileged or otherwise protected from disclosure. If 
you have received it in error, please notify the sender immediately by e-mail 
and then delete this e-mail and any attachment from your system. Any review, 
retransmission, dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than the intended 
recipient is prohibited.



Re: tomcat 8 depends on URL.setURLStreamHandlerFactory method

2014-10-02 Thread Johan Compagner
thx mark,

that seems to work, at least i do get further but i bomb into the next issue
that is in this code of StandardRoot

protected void startInternal() throws LifecycleException {
String docBase = context.getDocBase();

File f = new File(docBase);
if (!f.isAbsolute()) {
f = new File(((Host)context.getParent()).getAppBaseFile(),
f.getName());
}


The problem here is that docBase for us is not absolute, but is a relative,
(which is why there is a test there)
The problem is that f.getName() is used there. Because that only gives pack
the last part of the filename
So if the name was something like:

dir1/dir2

then only dir2 is returned and of course appbase (which is mostly
tomcat\webapps) + dir2 is not an actual dir

For us the doc base is: ../../plugins so it ends up in webapps\plugins
which is not correct it needs to go 2 dirs up..

So the current code only works for a docbase that is a single name that has
to be in the appbase folder.
I think it would be better to just use the docBase string as is instead of
using f.getName(), but there could be a reason that tomcat needs this ?

Johan


On 1 October 2014 20:44, Mark Thomas ma...@apache.org wrote:

 On 01/10/2014 16:59, Johan Compagner wrote:
  Hi,
 
  we have tomcat completely as an OSGI plugin project:
 
 
 https://github.com/Servoy/servoy-eclipse-tomcat/tree/master/org.apache.tomcat
 
  so that we can start it from our eclipse application and also dynamically
  add servlets and filters from all kinds of plugins (so everything is osgi
  based)
 
  Our app uses websockets quite heavily so  i thought lets update now to
 the
  latest 8 that has a lot of improvements in this area.
 
  Problem is that in StandardRoot
 
 
 https://apache.googlesource.com/tomcat/+/defeda9492a54194ea56e4a8220069608a7aa8f0/java/org/apache/catalina/webresources/StandardRoot.java
 
  there is a line:
 
  TomcatURLStreamHandlerFactory.register();
 
  in the internalInit
 
  this tries to call URL.setURLStreamHandlerFactory(this);
  in the constructor of that TomcatURLStreamHandlerFactory class
 
  but this is in eclipse or i guess in an osgi environment not really
 possible
  because that is already set so now it bombs out with factory al ready
 set
  error
 
  Is there any workaround for this or is there any way to improve tomcat 8
 so
  that it places nicer inside an osgi container like eclipse?

 You need to call the static disable() method before you start Tomcat.
 That will stop Tomcat trying to register the factory.

 If you want to be able to use WAR URLs (necessary to support web
 applications that are packaged as WARs and *not* unpacked) then you'll
 need to register the WarURLStreamHandler with whatever factory you have
 configured.

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 
Johan Compagner
Servoy


Re: Client authentication for specific path

2014-10-02 Thread Nathan Quirynen
On 01/10/14 18:50, Cédric Couralet wrote:
 2014-10-01 18:16 GMT+02:00 Nathan Quirynen nat...@pensionarchitects.be:
 On 01/10/14 18:08, Christopher Schultz wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Nathan,

 On 10/1/14 10:02 AM, Nathan Quirynen wrote:
 Hi Tomcat users,

 A current application has client authentication configured in the
 SSL Connector (server.xml):

 Connector port=8443 ... clientAuth=true
 keystoreFile=.keystore keystorePass=...
 truststoreFile=.truststore truststorePass=... /

 And the CA root certificates have been added to the truststore.

 This way it asks for a client certificate in any case, which works
 and is fine for this application. For a new application the use
 case is a bit different. I only need client authentication for a
 specific defined path (for example: /secured/*). After some
 research I found this was possible with defining this on
 application level in the web.xml file. So I changed my
 configuration to:

 server.xml:

 Connector port=8443 ... clientAuth=false
 keystoreFile=.keystore keystorePass=...
 truststoreFile=.truststore truststorePass=... /

 web.xml:

 security-constraint web-resource-collection
 web-resource-nameSecureconn/web-resource-name
 url-pattern/secured/*/url-pattern
 http-methodGET/http-method /web-resource-collection
 auth-constraint role-namesecureconn/role-name
 /auth-constraint /security-constraint login-config
 auth-methodCLIENT-CERT/auth-method
 realm-nameSecureconn/realm-name /login-config
 security-role role-namesecureconn/role-name /security-role


 In this case it actually only asks for client authentication when
 going to for example secured/home page. But I'm getting a 401
 message code.

 What am I missing to get people authenticated based on the CA root
 certificates that are in the configured truststore? Is it even
 possible what I am trying?
 What happens if you change clientAuth=false to clientAuth=want?

 Hey Chris,

 If I change it to want I still get the same error:

 HTTP Status 401 - Cannot authenticate with the provided credentials




 This is because when you use the CLIENT-CERT auth-method, Tomcat add
 the SSLAuthenticator to the context (your app) which validate the cert
 on the realm.

 By default, that realm is the UserDatabaseRealm which stores
 credentials in tomcat-users.xml.

 So several choices for you, add all the certificates DN in that file
 with the right roles, or change the realm for something more suited to
 your need.

 Aside, you can also define which certificate attribute will be
 resolved to search for the principal, in
 X509UsernameRetrieverClassName
 (http://tomcat.apache.org/tomcat-6.0-doc/config/realm.html)

 Cédric

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


With

add all the certificates DN in that file
with the right roles

you mean all the client certificates? Because that's not an option
(there's millions of client certificates).

I'm still not sure how I'm supposed to configure a realm to my needs.
When I search for tutorials all I get is people using tomcat-users.xml
and adding 1 client certificate...

Nathan

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Client authentication for specific path

2014-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Nathan,

On 10/1/14 12:16 PM, Nathan Quirynen wrote:
 On 01/10/14 18:08, Christopher Schultz wrote: Nathan,
 
 On 10/1/14 10:02 AM, Nathan Quirynen wrote:
 Hi Tomcat users,
 
 A current application has client authentication configured in
 the SSL Connector (server.xml):
 
 Connector port=8443 ... clientAuth=true 
 keystoreFile=.keystore keystorePass=... 
 truststoreFile=.truststore truststorePass=... /
 
 And the CA root certificates have been added to the
 truststore.
 
 This way it asks for a client certificate in any case, which
 works and is fine for this application. For a new application
 the use case is a bit different. I only need client
 authentication for a specific defined path (for example:
 /secured/*). After some research I found this was possible
 with defining this on application level in the web.xml file.
 So I changed my configuration to:
 
 server.xml:
 
 Connector port=8443 ... clientAuth=false 
 keystoreFile=.keystore keystorePass=... 
 truststoreFile=.truststore truststorePass=... /
 
 web.xml:
 
 security-constraint web-resource-collection 
 web-resource-nameSecureconn/web-resource-name 
 url-pattern/secured/*/url-pattern 
 http-methodGET/http-method /web-resource-collection 
 auth-constraint role-namesecureconn/role-name 
 /auth-constraint /security-constraint login-config 
 auth-methodCLIENT-CERT/auth-method 
 realm-nameSecureconn/realm-name /login-config 
 security-role role-namesecureconn/role-name
 /security-role
 
 
 In this case it actually only asks for client authentication
 when going to for example secured/home page. But I'm
 getting a 401 message code.
 
 What am I missing to get people authenticated based on the CA
 root certificates that are in the configured truststore? Is
 it even possible what I am trying?
 What happens if you change clientAuth=false to
 clientAuth=want?
 
 -chris
 
 -

 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 Hey Chris,
 
 If I change it to want I still get the same error:
 
 HTTP Status 401 - Cannot authenticate with the provided
 credentials

So just to be sure, the only difference between the application you
have that is working and the one that is not working is that you have
a different url-pattern in your web.xml?

Generally speaking, Tomcat will authenticate the client certificate
just using the configuration at the Connector level. Using
CLIENT-CERT in the application is used for application credentials --
such as establishing roles to be used with role-based permissions.

Do you intend to use role-based permissions and all that other stuff,
or do you just want to make sure that the client has a valid certificate?

If you just want to make sure that the certificate is valid, then you
want to use clientAuth=want and remove the configuration you have
from web.xml. Next, you will need to write a Filter that grabs the
X509 certificate from the request and does manual checking.

You might be able to get some help from a series of posts I wrote a
few years ago about manually-handling X509 certificates:
http://markmail.org/message/kzxsamuiu6bldjmv

Hope that helps,
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJULYSZAAoJEBzwKT+lPKRYorwP/1GT+aPdAK5Vu2piCp+4ZDXQ
kGm42DzD0FBM8oKI2vgPj/hvOTEYC+e7EndxxUbhaSoek0O71hlEeWfnhrCt3lNs
xKHBhwXHeVwxOkSHsjZKfzHqoJgHhMBBVU5rQHQ1mwIT71bayNSYVuG/QRZFffoM
lef1YTql+jt+LOgfJauD/yozYG2fblEMMEcUWfBtpruEFVns6Vu2m5vwKwn7si2K
13SjiqoULIOf6FkiKXiCewXACq98KLbjo21m5SkUNDgFiE6wWquOX/uyQBBP8n+p
B2H6b6YlQAj1KOBtH+yd+0vnW6BwjI9ZxHDfT7t8Ii1zBwUDFj3QZOJ5RXFwteQR
cFjJXxmRliD/EuEfjZuHD5U9d51Eq44RU6p3/8cuIg90gx8fPYBULJimXRX6v4ca
EdTmqnJyxZeh2WoNAY2k+24OxwwxKSZUErxm0biBAy/wcqT1O1ePkaCI6YQx1Vkj
TnHxleVWvr2FpZDp1apmTcgzP0gBnD6fOG8ltf8Nqe/Ax4l6nhdK3Q19YLTt2Q2z
IKX7oUOYru0GNuICtsNYz0EprzdMxnv28v3SBYLSfHln9J5WWtfBeOlKxMPmP0Fg
ZJG/X/zUUC2IxDNe6u7ZdZr/vqxDLyZxc74ugiVIxveutzrXOHdxnPRIzbEXjYIC
umadSoe7yZwlcEAAQFG/
=bMuo
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Gibran Castillo
I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
 here /Library/Tomcat/Home.  Home is a symbolic link that will always point
to the current version Tomcat directory, in this case
/Library/Tomcat/apache-tomcat-8.0.12

In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
following:
  role rolename=manager-gui/
  user username=“admin” password=password” roles=manager-gui”/

When I start tomcat with the out of the box setup everything looks good
except that is throwing an exception regarding user
*username=“admin”* password=adminpw”
roles=manager-gui”/, see below... I am not sure what is going on, this is
suppose to work out of the box

Using CATALINA_BASE:   /Library/Tomcat/Home

Using CATALINA_HOME:   /Library/Tomcat/Home

Using CATALINA_TMPDIR: /Library/Tomcat/Home/temp

Using JRE_HOME:
/Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home

Using CLASSPATH:
/Library/Tomcat/Home/bin/bootstrap.jar:/Library/Tomcat/Home/bin/tomcat-juli.jar


.../Home/logs/catalina.2014-10-02.log

02-Oct-2014 12:19:44.120 INFO [main]
org.apache.catalina.core.AprLifecycleListener.init The APR based Apache
Tomcat Native library which allows optimal performance in production
environments was not found on the java.library.path:
/Users/gibranecastillo/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.

02-Oct-2014 12:19:44.551 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[http-nio-8080]

02-Oct-2014 12:19:44.670 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read

02-Oct-2014 12:19:44.676 INFO [main]
org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
[ajp-nio-8009]

02-Oct-2014 12:19:44.683 INFO [main]
org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
selector for servlet write/read

02-Oct-2014 12:19:44.684 INFO [main]
org.apache.catalina.startup.Catalina.load Initialization processed in 1236
ms

*02-Oct-2014 12:19:44.726 SEVERE [main]
org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
line 37 column 18: Open quote is expected for attribute {1} associated
with an  element type  username.*

* org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
quote is expected for attribute {1} associated with an  element type
username.*

at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)

at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)

at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)

at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)

at
com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)

at
com.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(XMLScanner.java:829)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1546)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1318)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2770)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)

at
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)

at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)

at
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)

at
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)

at
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)

at
com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648)

at
org.apache.tomcat.util.digester.Digester.parse(Digester.java:1476)

at
org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:430)

at
org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:102)

at
org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:94)

at
javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:321)

at org.apache.naming.NamingContext.lookup(NamingContext.java:841)

at org.apache.naming.NamingContext.lookup(NamingContext.java:152)

at

Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Daniel Mikusa
On Thu, Oct 2, 2014 at 2:16 PM, Gibran Castillo gibran.e.casti...@gmail.com
 wrote:

 I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
  here /Library/Tomcat/Home.  Home is a symbolic link that will always point
 to the current version Tomcat directory, in this case
 /Library/Tomcat/apache-tomcat-8.0.12

 In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
 following:
   role rolename=manager-gui/
   user username=“admin” password=password” roles=manager-gui”/


Did you copy and paste this from somewhere?  If so, try deleting it and
manually typing, especially the quote characters.

Dan



 When I start tomcat with the out of the box setup everything looks good
 except that is throwing an exception regarding user
 *username=“admin”* password=adminpw”
 roles=manager-gui”/, see below... I am not sure what is going on, this is
 suppose to work out of the box

 Using CATALINA_BASE:   /Library/Tomcat/Home

 Using CATALINA_HOME:   /Library/Tomcat/Home

 Using CATALINA_TMPDIR: /Library/Tomcat/Home/temp

 Using JRE_HOME:
 /Library/Java/JavaVirtualMachines/jdk1.7.0_60.jdk/Contents/Home

 Using CLASSPATH:

 /Library/Tomcat/Home/bin/bootstrap.jar:/Library/Tomcat/Home/bin/tomcat-juli.jar


 .../Home/logs/catalina.2014-10-02.log

 02-Oct-2014 12:19:44.120 INFO [main]
 org.apache.catalina.core.AprLifecycleListener.init The APR based Apache
 Tomcat Native library which allows optimal performance in production
 environments was not found on the java.library.path:

 /Users/gibranecastillo/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:.

 02-Oct-2014 12:19:44.551 INFO [main]
 org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
 [http-nio-8080]

 02-Oct-2014 12:19:44.670 INFO [main]
 org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
 selector for servlet write/read

 02-Oct-2014 12:19:44.676 INFO [main]
 org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler
 [ajp-nio-8009]

 02-Oct-2014 12:19:44.683 INFO [main]
 org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared
 selector for servlet write/read

 02-Oct-2014 12:19:44.684 INFO [main]
 org.apache.catalina.startup.Catalina.load Initialization processed in 1236
 ms

 *02-Oct-2014 12:19:44.726 SEVERE [main]
 org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
 line 37 column 18: Open quote is expected for attribute {1} associated
 with an  element type  username.*

 * org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
 quote is expected for attribute {1} associated with an  element type
 username.*

 at

 com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)

 at

 com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)

 at

 com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:441)

 at

 com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:368)

 at

 com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1436)

 at

 com.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(XMLScanner.java:829)

 at

 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(XMLDocumentFragmentScannerImpl.java:1546)

 at

 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:1318)

 at

 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2770)

 at

 com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)

 at

 com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)

 at

 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)

 at

 com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)

 at

 com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)

 at

 com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)

 at

 com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:648)

 at
 org.apache.tomcat.util.digester.Digester.parse(Digester.java:1476)

 at

 org.apache.catalina.users.MemoryUserDatabase.open(MemoryUserDatabase.java:430)

 at

 org.apache.catalina.users.MemoryUserDatabaseFactory.getObjectInstance(MemoryUserDatabaseFactory.java:102)

 at

 org.apache.naming.factory.FactoryBase.getObjectInstance(FactoryBase.java:94)


Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Konstantin Kolinko
2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com:
 I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
  here /Library/Tomcat/Home.  Home is a symbolic link that will always point
 to the current version Tomcat directory, in this case
 /Library/Tomcat/apache-tomcat-8.0.12

 In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
 following:
   role rolename=manager-gui/
   user username=“admin” password=password” roles=manager-gui”/

 When I start tomcat with the out of the box setup everything looks good
 except that is throwing an exception regarding user
 *username=“admin”*   (...)

The quote character before a in admin is not the straight quote
character expected in XML files,  but left quote character ( ` `) as
inserted by text processors...



 *02-Oct-2014 12:19:44.726 SEVERE [main]
 org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
 line 37 column 18: Open quote is expected for attribute {1} associated
 with an  element type  username.*

 * org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
 quote is expected for attribute {1} associated with an  element type
 username.*

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Gibran Castillo
Tomcat did not like the double quotes use by TextEdit.app so I use the ones
that were in the commented out section of tomcat-users.xml  I was able to
authenticate

On Thu, Oct 2, 2014 at 2:24 PM, Konstantin Kolinko knst.koli...@gmail.com
wrote:

 2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com:
  I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
   here /Library/Tomcat/Home.  Home is a symbolic link that will always
 point
  to the current version Tomcat directory, in this case
  /Library/Tomcat/apache-tomcat-8.0.12
 
  In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
  following:
role rolename=manager-gui/
user username=“admin” password=password” roles=manager-gui”/
 
  When I start tomcat with the out of the box setup everything looks good
  except that is throwing an exception regarding user
  *username=“admin”*   (...)

 The quote character before a in admin is not the straight quote
 character expected in XML files,  but left quote character ( ` `) as
 inserted by text processors...



  *02-Oct-2014 12:19:44.726 SEVERE [main]
  org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
  line 37 column 18: Open quote is expected for attribute {1} associated
  with an  element type  username.*
 
  * org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
  quote is expected for attribute {1} associated with an  element type
  username.*

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread André Warnier

Konstantin Kolinko wrote:

2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com:

I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
 here /Library/Tomcat/Home.  Home is a symbolic link that will always point
to the current version Tomcat directory, in this case
/Library/Tomcat/apache-tomcat-8.0.12

In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
following:
  role rolename=manager-gui/
  user username=“admin” password=password” roles=manager-gui”/

When I start tomcat with the out of the box setup everything looks good
except that is throwing an exception regarding user
*username=“admin”*   (...)


The quote character before a in admin is not the straight quote
character expected in XML files,  but left quote character ( ` `) as
inserted by text processors...


 +1
Also the one at the end of admin and the one at the end of manager-gui look 
suspicious.





*02-Oct-2014 12:19:44.726 SEVERE [main]
org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
line 37 column 18: Open quote is expected for attribute {1} associated
with an  element type  username.*

* org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
quote is expected for attribute {1} associated with an  element type
username.*


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org





-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: tomcat 8 depends on URL.setURLStreamHandlerFactory method

2014-10-02 Thread Mark Thomas
On 02/10/2014 15:24, Johan Compagner wrote:
 thx mark,
 
 that seems to work, at least i do get further but i bomb into the next issue
 that is in this code of StandardRoot
 
 protected void startInternal() throws LifecycleException {
 String docBase = context.getDocBase();
 
 File f = new File(docBase);
 if (!f.isAbsolute()) {
 f = new File(((Host)context.getParent()).getAppBaseFile(),
 f.getName());
 }
 
 
 The problem here is that docBase for us is not absolute, but is a relative,
 (which is why there is a test there)
 The problem is that f.getName() is used there. Because that only gives pack
 the last part of the filename
 So if the name was something like:
 
 dir1/dir2
 
 then only dir2 is returned and of course appbase (which is mostly
 tomcat\webapps) + dir2 is not an actual dir
 
 For us the doc base is: ../../plugins so it ends up in webapps\plugins
 which is not correct it needs to go 2 dirs up..
 
 So the current code only works for a docbase that is a single name that has
 to be in the appbase folder.
 I think it would be better to just use the docBase string as is instead of
 using f.getName(), but there could be a reason that tomcat needs this ?

Nope. It is a bug. It has been fixed in 8.0.x for 8.0.15 onwards.

Mark


 
 Johan
 
 
 On 1 October 2014 20:44, Mark Thomas ma...@apache.org wrote:
 
 On 01/10/2014 16:59, Johan Compagner wrote:
 Hi,

 we have tomcat completely as an OSGI plugin project:


 https://github.com/Servoy/servoy-eclipse-tomcat/tree/master/org.apache.tomcat

 so that we can start it from our eclipse application and also dynamically
 add servlets and filters from all kinds of plugins (so everything is osgi
 based)

 Our app uses websockets quite heavily so  i thought lets update now to
 the
 latest 8 that has a lot of improvements in this area.

 Problem is that in StandardRoot


 https://apache.googlesource.com/tomcat/+/defeda9492a54194ea56e4a8220069608a7aa8f0/java/org/apache/catalina/webresources/StandardRoot.java

 there is a line:

 TomcatURLStreamHandlerFactory.register();

 in the internalInit

 this tries to call URL.setURLStreamHandlerFactory(this);
 in the constructor of that TomcatURLStreamHandlerFactory class

 but this is in eclipse or i guess in an osgi environment not really
 possible
 because that is already set so now it bombs out with factory al ready
 set
 error

 Is there any workaround for this or is there any way to improve tomcat 8
 so
 that it places nicer inside an osgi container like eclipse?

 You need to call the static disable() method before you start Tomcat.
 That will stop Tomcat trying to register the factory.

 If you want to be able to use WAR URLs (necessary to support web
 applications that are packaged as WARs and *not* unpacked) then you'll
 need to register the WarURLStreamHandler with whatever factory you have
 configured.

 Mark


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org


 
 


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Gibran Castillo
This solved it, thank you guys

On Thu, Oct 2, 2014 at 2:33 PM, André Warnier a...@ice-sa.com wrote:

 Konstantin Kolinko wrote:

 2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com:

 I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
  here /Library/Tomcat/Home.  Home is a symbolic link that will always
 point
 to the current version Tomcat directory, in this case
 /Library/Tomcat/apache-tomcat-8.0.12

 In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
 following:
   role rolename=manager-gui/
   user username=“admin” password=password” roles=manager-gui”/

 When I start tomcat with the out of the box setup everything looks good
 except that is throwing an exception regarding user
 *username=“admin”*   (...)


 The quote character before a in admin is not the straight quote
 character expected in XML files,  but left quote character ( ` `) as
 inserted by text processors...

   +1
 Also the one at the end of admin and the one at the end of manager-gui
 look suspicious.




  *02-Oct-2014 12:19:44.726 SEVERE [main]
 org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
 line 37 column 18: Open quote is expected for attribute {1} associated
 with an  element type  username.*

 * org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
 quote is expected for attribute {1} associated with an  element type
 username.*


 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread André Warnier

Gibran Castillo wrote:

Tomcat did not like the double quotes use by TextEdit.app so I use the ones
that were in the commented out section of tomcat-users.xml  I was able to
authenticate


Oh my..
It is not Tomcat which does not like your quotes, it is XML.
These quotes are not valid characters to delimit attribute values *in XML*.
You will have the same problem with any XML file that you edit with that editor : you will 
generate XML that is not well formed and thus invalid.

And that will crash any program which reads your XML files.
Use another editor, this one is not suitable for editing XML files.



On Thu, Oct 2, 2014 at 2:24 PM, Konstantin Kolinko knst.koli...@gmail.com
wrote:


2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com:

I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
 here /Library/Tomcat/Home.  Home is a symbolic link that will always

point

to the current version Tomcat directory, in this case
/Library/Tomcat/apache-tomcat-8.0.12

In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
following:
  role rolename=manager-gui/
  user username=“admin” password=password” roles=manager-gui”/

When I start tomcat with the out of the box setup everything looks good
except that is throwing an exception regarding user
*username=“admin”*   (...)

The quote character before a in admin is not the straight quote
character expected in XML files,  but left quote character ( ` `) as
inserted by text processors...




*02-Oct-2014 12:19:44.726 SEVERE [main]
org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error at
line 37 column 18: Open quote is expected for attribute {1} associated
with an  element type  username.*

* org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
quote is expected for attribute {1} associated with an  element type
username.*

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org








-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

2014-10-02 Thread Gibran Castillo
I deployed donow62 Spring MVC app into Tomcat by placing donow62.xml file
in $CATALINA_HOME/conf/Catalina/localhost

The contents of donow62.xml are as follow:
Context
docBase=/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website
reloadable=true/

They basically point to the website directory in the spring mvc project in
my eclipse workspace.

I looked at the Tomcat logs and it says donow62 deployed successfully.  In
the Tomcat Web Application Manager I can see /donow62 listed there.

When I clicked on /donow62 it sends me to this URL
http://localhost:8080/donow62/ but instead of getting expected result and
the web page, I get HTTP Status 500 [see web browser log below]

My Spring MVC donow62 app is using JSTL and it is in the classpath.
Using Eclipse on the donow62 project I created User Libraries that
reference all the dependencies for donow62.  The SERVLET user library has
 el-api.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/el-api.jar
 jasper.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper.jar
 jasper-el.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper-el.jar
 jsp-api.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/jsp-api.jar
 servlet-api.jar -
/Library/Tomcat/apache-tomcat-8.0.12/lib/servlet-api.jar
 javax-servlet.jsp.jstl-1.2.1.jar -
/Users/gibranecastillo/Documents/java/servlet/javax-servlet.jsp.jstl-1.2.1.jar


The exception is basically saying that the donow62 app is missing the JSTL
dependency, the jar, any suggestions on how fix this are welcome.


HTTP Status 500 - The absolute uri: http://java.sun.com/jsp/jstl/core
cannot be resolved in either web.xml or the jar files deployed with this
application

*type* Exception report

*message* *The absolute uri: http://java.sun.com/jsp/jstl/core
http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or
the jar files deployed with this application*

*description* *The server encountered an internal error that prevented it
from fulfilling this request.*

*exception*

org.apache.jasper.JasperException: The absolute uri:
http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml
or the jar files deployed with this application

org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:56)

org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:278)

org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:76)

org.apache.jasper.compiler.TagLibraryInfoImpl.generateTldResourcePath(TagLibraryInfoImpl.java:242)

org.apache.jasper.compiler.TagLibraryInfoImpl.init(TagLibraryInfoImpl.java:124)
org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:411)
org.apache.jasper.compiler.Parser.parseDirective(Parser.java:469)
org.apache.jasper.compiler.Parser.parseElements(Parser.java:1428)
org.apache.jasper.compiler.Parser.parse(Parser.java:139)

org.apache.jasper.compiler.ParserController.doParse(ParserController.java:227)

org.apache.jasper.compiler.ParserController.parse(ParserController.java:100)
org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:199)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:356)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:336)
org.apache.jasper.compiler.Compiler.compile(Compiler.java:323)

org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:564)

org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:391)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:335)
javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

*note* *The full stack trace of the root cause is available in the Apache
Tomcat/8.0.12 logs.*
--
Apache Tomcat/8.0.12

-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Re: Open quote is expected for attribute {1} associated with an element type username

2014-10-02 Thread Gibran Castillo
Thank you for clarifying, the XML was not well formed

On Thu, Oct 2, 2014 at 3:50 PM, André Warnier a...@ice-sa.com wrote:

 Gibran Castillo wrote:

 Tomcat did not like the double quotes use by TextEdit.app so I use the
 ones
 that were in the commented out section of tomcat-users.xml  I was able to
 authenticate


 Oh my..
 It is not Tomcat which does not like your quotes, it is XML.
 These quotes are not valid characters to delimit attribute values *in XML*.
 You will have the same problem with any XML file that you edit with that
 editor : you will generate XML that is not well formed and thus invalid.
 And that will crash any program which reads your XML files.
 Use another editor, this one is not suitable for editing XML files.


 On Thu, Oct 2, 2014 at 2:24 PM, Konstantin Kolinko 
 knst.koli...@gmail.com
 wrote:

  2014-10-02 22:16 GMT+04:00 Gibran Castillo gibran.e.casti...@gmail.com
 :

 I installed Tomcat 8.0.12 in my MacBook OS X 10.9.5
  here /Library/Tomcat/Home.  Home is a symbolic link that will always

 point

 to the current version Tomcat directory, in this case
 /Library/Tomcat/apache-tomcat-8.0.12

 In the /Library/Tomcat/Home/conf/tomcat-users.xml file I added the
 following:
   role rolename=manager-gui/
   user username=“admin” password=password” roles=manager-gui”/

 When I start tomcat with the out of the box setup everything looks good
 except that is throwing an exception regarding user
 *username=“admin”*   (...)

 The quote character before a in admin is not the straight quote
 character expected in XML files,  but left quote character ( ` `) as
 inserted by text processors...



  *02-Oct-2014 12:19:44.726 SEVERE [main]
 org.apache.tomcat.util.digester.Digester.fatalError Parse Fatal Error
 at
 line 37 column 18: Open quote is expected for attribute {1} associated
 with an  element type  username.*

 * org.xml.sax.SAXParseException; lineNumber: 37; columnNumber: 18; Open
 quote is expected for attribute {1} associated with an  element type
 username.*

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org






 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Re: [OT] Forward TLS connection information from AWS ELB - httpd - Tomcat

2014-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

All,

On 10/1/14 10:26 AM, Christopher Schultz wrote:
 I'm interested in using AWS ELB for SSL termination but allowing
 the client's TLS connection information to be forwarded all the
 way through the chain to Tomcat.
 
 The setup looks like this:
 
 ELB /\ /  \ /\ w0w1 /  \   / \ t0  t1 t0  t1
 
 (t0 and t1 are repeated because otherwise the diagram would be
 even more difficult to read).
 
 w0 and w1 are running Apache httpd, t0 and t1 are running Tomcat.
 The client's connection is TLS terminated at ELB and whether the 
 connections between ELB/wx/tx are encrypted should be immaterial.
 I'm using mod_jk from httpd - Tomcat.
 
 ELB provides the following HTTP headers to wx: X-Forwarded-For
 (client's IP) X-Forwarded-Port443 X-Forwarded-Proto   https
 
 Unfortunately, it looks like I can't get things like the cipher 
 default, etc. but I'm okay with that for the time being.
 
 I'm wondering two things:
 
 1. How can I get Apache httpd to trust that the connection is
 encrypted? I want to be able to use RequireSSL for certain
 resources and have httpd trust that the connection coming from the
 ELB is in fact secure.
 
 2. How can I use that connection information to tell mod_jk that
 things are to be trusted as well?
 
 For #2, I might just be able to use SetEnv to set 
 REMOTE_ADDR=X-Forwarded-For, but I'm not sure how to say yes, this
 is encrypted. Should I set up a separate VirtualHost on a
 different (non-80) port that is configured only for ELB connections
 and then force SSL to on regardless of the actual incoming
 connections?
 
 That would allow me to use port 80 for regular web traffic and
 not have to worry about proper checking to make sure that the
 connection was in fact coming from the ELB and not directly into
 the web server.

I have some information for those wanting to do this.

Here is a write-up someone did for how to get Apache to log things
appropriately when using AWS ELB:
http://knowledgevoid.com/blog/2012/01/13/logging-the-correct-ip-address-using-apache-2-2-x-and-amazons-elastic-load-balancer/

Here are the two configurations I was able to get working and a few
notes about them.

I would highly recommend that anyone using ELB set up an ELB-only
VirtualHost that only handles requests being proxied through the ELB.
This will protect you against some misconfigurations, etc. that might
allow remote users to get access to resources they should not, or be
able to forge certain parts of the request.

Something like this:

VirtualHost *:81
  (remaining configuration)
/VirtualHost

Remember that you will have to Listen 81 somewhere.

If you have httpd 2.4, then you have mod_remoteip out of the box.
That's nice:

# Trust AWS ELB's X-Forwarded-For header
# This will set REMOTE_ADDR to the client's real IP
RemoteIPHeader X-Forwarded-For
RemoteIPInternalProxy 10.0.0.0/8

# Handle ELB requests; maintain client information
SetEnvIf X-Forwarded-Proto https HTTPS=On
SetEnvIf X-Forwarded-Port (.*) JK_LOCAL_PORT=$1

That last SetEnvIf is nearly entirely useless (because nobody really
cares about users' port numbers), but I put it in there for completeness.

Also, mod_remoteip will adjust the value of the REMOTE_ADDR
environment variable -- which is visible to CGI-style programs as well
as mod_jk/Tomcat/etc. but *it will not work in log files* if you use
%h as your remote-ip log format. You will have to use %a instead.
On AWS Linux, the httpd package comes with both combined and
common log formats defined using %h so you'll have to change those
to %a.

If you have httpd 2.2. instead, you'll have to do things a bit
differently (unless you want to use the back-port of mod_remoteip for
httpd 2.2):

# Handle ELB requests; maintain client information
SetEnvIf X-Forwarded-Proto https HTTPS=On
SetEnvIf X-Forwarded-For (.*) REMOTE_ADDR=$1 JK_REMOTE_ADDR=$1
SetEnvIf X-Forwarded-Port (.*) JK_LOCAL_PORT=$1
Location /
  Order deny,allow
  Deny from all
  Allow from 10.0.0.0/8
/Location

If you want to log properly, I think the best thing to do is change
%h (or %a) in your log formats to %{X-Forwarded-For}i or, if you
want to be super-correct, you want to do something like this:

# The following line has been split over multiple lines.
# httpd doesn't support this; it's for email readability only
SetEnvIf X-Forwarded-For \
^.*?(\d{1,3}+\.\d{1,3}+\.\d{1,3}+\.\d{1,3}+) \
XFFCLIENTIP=$1
LogFormat ... %{XFFCLIENTIP}e ... format-name
CustomLog access_log format-name

This won't get you the right client IP address in error.log, though.
I'm not exactly sure how to do that. Apparently, setting REMOTE_ADDR
is only useful for CGI-style interaction and has no effect on how
httpd does logging, etc.

It also seems that you cannot re-define a LogFormat. I tried
re-defining my combined log format in a VirtualHost and it did not
work. Using a different LogFormat 

Re: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

2014-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gibran,

On 10/2/14 3:59 PM, Gibran Castillo wrote:
 I deployed donow62 Spring MVC app into Tomcat by placing
 donow62.xml file in $CATALINA_HOME/conf/Catalina/localhost
 
 The contents of donow62.xml are as follow: Context 
 docBase=/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website

 
reloadable=true/
 
 They basically point to the website directory in the spring mvc
 project in my eclipse workspace.

What is the directory structure of .../donow62/website?

 I looked at the Tomcat logs and it says donow62 deployed
 successfully.  In the Tomcat Web Application Manager I can see
 /donow62 listed there.
 
 When I clicked on /donow62 it sends me to this URL 
 http://localhost:8080/donow62/ but instead of getting expected
 result and the web page, I get HTTP Status 500 [see web browser log
 below]
 
 My Spring MVC donow62 app is using JSTL and it is in the
 classpath. Using Eclipse on the donow62 project I created User
 Libraries that reference all the dependencies for donow62.  The
 SERVLET user library has  el-api.jar -
 /Library/Tomcat/apache-tomcat-8.0.12/lib/el-api.jar  jasper.jar -
 /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper.jar 
 jasper-el.jar -
 /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper-el.jar 
 jsp-api.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/jsp-api.jar 
  servlet-api.jar - 
 /Library/Tomcat/apache-tomcat-8.0.12/lib/servlet-api.jar 
 javax-servlet.jsp.jstl-1.2.1.jar - 
 /Users/gibranecastillo/Documents/java/servlet/javax-servlet.jsp.jstl-1.2.1.jar


 
The exception is basically saying that the donow62 app is missing the JSTL
 dependency, the jar, any suggestions on how fix this are welcome.

Is the JSTL JAR file in
/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website/WEB-INF/lib?
If not, you aren't actually using it.

Although I don't do it myself, Eclipse is pretty good at deploying web
applications to Tomcat itself: you shouldn't have to even create your
own context.xml file and fill it with data.

If you want to do everything manually (believe me, I understand), then
you'll need to make sure that your Eclipse project successfully builds
to a WAR-like structure which contains, among other things, a WEB-INF/
directory and all of the things that should be in there (like
lib/*.jar). If you don't do that, then you won't really be deploying a
web application... you'll effectively be mapping a directory on the
disk into a URL space and getting no other benefits.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJULbGLAAoJEBzwKT+lPKRYQ04P/AsAB5jVCEh4zH56W6zLSsui
NYOffS3QnNgVzpwh/JV+WOyCMXwrkuWNRSGlBnsniUM4Z5HrzebfYJm1EdsG2FsP
2KKeGltiLAXXHKj/10Lxh8Rv1Q+wFx4pTjwJIJmy0qwyS8mamzhhDY1DRalwQsuA
tbsrgw76v57ljjL7+99+RjZGnhoL6CNdjyOFTwArLMnsebD8WBIDf8hv1sS5HqQV
E/OkmXOxk3fSj7LzPMGH2X4QE1jxKcUTUUnESqU32vJ1xkMdBDVul64ihbh6CaT5
chmI+x6bsLT8CgOGwISlydVTG60BTV9mMpXW9TJ02unlB8wAsR7t9192wmhs/Qmz
ReyIlUJDnlHO5c0B7KmjQjlDWDjwpexef//W+AHFuWr5UMJO7hdIh0m0VUdb3Bv+
qqM18HH0q9t3TlvWvp89jvAhGqSOeYBGO+NU97kEwmlxq3Hu6+W3Fqf4TR6SjlEZ
MnlY3IO1ZMhpnWZuIfV/ff3YkF1EFqGToF7v//mxi8SufASxqIaPl9k5x8C4AkyN
VORR/zrAm370aemg7fUNOGfW8OBSO0KsJdDlW961ZwEWC8AuZpLlrm/sNtVZpc2T
Lqa9/njB6sKbfqOiUGtyvx6UWIYHguR4th86bV8jvUX/K85hOJQJRH/C5626oKsH
WTuwkQf5zzGoXbVFKD/t
=QaZn
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

2014-10-02 Thread Gibran Castillo
To fix the problem I put the .jar files in tomcat's lib directory and it
works best way to do this is like you said to put the *.jar files in
the WEB-INF/lib directory, build the project as WAR and deploy the war file
in Tomcat Where do I place the .war file in Tomcat?  in the
'webapps' directory?

On Thu, Oct 2, 2014 at 4:11 PM, Christopher Schultz 
ch...@christopherschultz.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Gibran,

 On 10/2/14 3:59 PM, Gibran Castillo wrote:
  I deployed donow62 Spring MVC app into Tomcat by placing
  donow62.xml file in $CATALINA_HOME/conf/Catalina/localhost
 
  The contents of donow62.xml are as follow: Context
 
 docBase=/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website
 
 
 reloadable=true/
 
  They basically point to the website directory in the spring mvc
  project in my eclipse workspace.

 What is the directory structure of .../donow62/website?

  I looked at the Tomcat logs and it says donow62 deployed
  successfully.  In the Tomcat Web Application Manager I can see
  /donow62 listed there.
 
  When I clicked on /donow62 it sends me to this URL
  http://localhost:8080/donow62/ but instead of getting expected
  result and the web page, I get HTTP Status 500 [see web browser log
  below]
 
  My Spring MVC donow62 app is using JSTL and it is in the
  classpath. Using Eclipse on the donow62 project I created User
  Libraries that reference all the dependencies for donow62.  The
  SERVLET user library has  el-api.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/el-api.jar  jasper.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper.jar 
  jasper-el.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper-el.jar 
  jsp-api.jar - /Library/Tomcat/apache-tomcat-8.0.12/lib/jsp-api.jar
   servlet-api.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/servlet-api.jar 
  javax-servlet.jsp.jstl-1.2.1.jar -
 
 /Users/gibranecastillo/Documents/java/servlet/javax-servlet.jsp.jstl-1.2.1.jar
 
 
 
 The exception is basically saying that the donow62 app is missing the JSTL
  dependency, the jar, any suggestions on how fix this are welcome.

 Is the JSTL JAR file in

 /Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website/WEB-INF/lib?
 If not, you aren't actually using it.

 Although I don't do it myself, Eclipse is pretty good at deploying web
 applications to Tomcat itself: you shouldn't have to even create your
 own context.xml file and fill it with data.

 If you want to do everything manually (believe me, I understand), then
 you'll need to make sure that your Eclipse project successfully builds
 to a WAR-like structure which contains, among other things, a WEB-INF/
 directory and all of the things that should be in there (like
 lib/*.jar). If you don't do that, then you won't really be deploying a
 web application... you'll effectively be mapping a directory on the
 disk into a URL space and getting no other benefits.

 - -chris
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1
 Comment: GPGTools - http://gpgtools.org

 iQIcBAEBCAAGBQJULbGLAAoJEBzwKT+lPKRYQ04P/AsAB5jVCEh4zH56W6zLSsui
 NYOffS3QnNgVzpwh/JV+WOyCMXwrkuWNRSGlBnsniUM4Z5HrzebfYJm1EdsG2FsP
 2KKeGltiLAXXHKj/10Lxh8Rv1Q+wFx4pTjwJIJmy0qwyS8mamzhhDY1DRalwQsuA
 tbsrgw76v57ljjL7+99+RjZGnhoL6CNdjyOFTwArLMnsebD8WBIDf8hv1sS5HqQV
 E/OkmXOxk3fSj7LzPMGH2X4QE1jxKcUTUUnESqU32vJ1xkMdBDVul64ihbh6CaT5
 chmI+x6bsLT8CgOGwISlydVTG60BTV9mMpXW9TJ02unlB8wAsR7t9192wmhs/Qmz
 ReyIlUJDnlHO5c0B7KmjQjlDWDjwpexef//W+AHFuWr5UMJO7hdIh0m0VUdb3Bv+
 qqM18HH0q9t3TlvWvp89jvAhGqSOeYBGO+NU97kEwmlxq3Hu6+W3Fqf4TR6SjlEZ
 MnlY3IO1ZMhpnWZuIfV/ff3YkF1EFqGToF7v//mxi8SufASxqIaPl9k5x8C4AkyN
 VORR/zrAm370aemg7fUNOGfW8OBSO0KsJdDlW961ZwEWC8AuZpLlrm/sNtVZpc2T
 Lqa9/njB6sKbfqOiUGtyvx6UWIYHguR4th86bV8jvUX/K85hOJQJRH/C5626oKsH
 WTuwkQf5zzGoXbVFKD/t
 =QaZn
 -END PGP SIGNATURE-

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Re: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

2014-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Gibran,

On 10/2/14 5:04 PM, Gibran Castillo wrote:
 To fix the problem I put the .jar files in tomcat's lib directory
 and it works best way to do this is like you said to put the
 *.jar files in the WEB-INF/lib directory, build the project as WAR
 and deploy the war file in Tomcat Where do I place the .war
 file in Tomcat?  in the 'webapps' directory?

Yes, you would put the WAR file into Tomcat's webapps/ directory. If
you do that, you won't need the separate donow62.xml file.

- -chris

 On Thu, Oct 2, 2014 at 4:11 PM, Christopher Schultz  
 ch...@christopherschultz.net wrote:
 
 Gibran,
 
 On 10/2/14 3:59 PM, Gibran Castillo wrote:
 I deployed donow62 Spring MVC app into Tomcat by placing 
 donow62.xml file in $CATALINA_HOME/conf/Catalina/localhost
 
 The contents of donow62.xml are as follow: Context
 
 docBase=/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website



 
reloadable=true/
 
 They basically point to the website directory in the spring
 mvc project in my eclipse workspace.
 
 What is the directory structure of .../donow62/website?
 
 I looked at the Tomcat logs and it says donow62 deployed 
 successfully.  In the Tomcat Web Application Manager I can
 see /donow62 listed there.
 
 When I clicked on /donow62 it sends me to this URL 
 http://localhost:8080/donow62/ but instead of getting
 expected result and the web page, I get HTTP Status 500 [see
 web browser log below]
 
 My Spring MVC donow62 app is using JSTL and it is in the 
 classpath. Using Eclipse on the donow62 project I created
 User Libraries that reference all the dependencies for
 donow62.  The SERVLET user library has  el-api.jar - 
 /Library/Tomcat/apache-tomcat-8.0.12/lib/el-api.jar 
 jasper.jar - 
 /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper.jar  
 jasper-el.jar - 
 /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper-el.jar  
 jsp-api.jar -
 /Library/Tomcat/apache-tomcat-8.0.12/lib/jsp-api.jar 
 servlet-api.jar - 
 /Library/Tomcat/apache-tomcat-8.0.12/lib/servlet-api.jar  
 javax-servlet.jsp.jstl-1.2.1.jar -
 
 /Users/gibranecastillo/Documents/java/servlet/javax-servlet.jsp.jstl-1.2.1.jar




 
The exception is basically saying that the donow62 app is missing the JSTL
 dependency, the jar, any suggestions on how fix this are
 welcome.
 
 Is the JSTL JAR file in
 
 /Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website/WEB-INF/lib?

 
If not, you aren't actually using it.
 
 Although I don't do it myself, Eclipse is pretty good at deploying
 web applications to Tomcat itself: you shouldn't have to even
 create your own context.xml file and fill it with data.
 
 If you want to do everything manually (believe me, I understand),
 then you'll need to make sure that your Eclipse project
 successfully builds to a WAR-like structure which contains, among
 other things, a WEB-INF/ directory and all of the things that
 should be in there (like lib/*.jar). If you don't do that, then you
 won't really be deploying a web application... you'll effectively
 be mapping a directory on the disk into a URL space and getting no
 other benefits.
 
 -chris
 
 -

 
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJULcAeAAoJEBzwKT+lPKRY1+cQAMY1dP2G+IjwFLciEUkWRUZ0
AS9MmQZT6QJ4EtnAjBeby3Uv8So9XzWu4ZKYjUT4QLPntXFswnnkVNW3DKHNXxhq
uxHYLBhaZRTDYmHpkuNHdH5nX8Cil5wy7ToXqBPmTnY/DxDghjU6Vlzb19oWpkVM
HyM8Ky2CnGqoKtr0fTw8hOzpsi/2F9mgMM7j+cuWmMQoMKpAho8pc5UuBCSU55wG
JJgaTGf0UNsm9X6M4YB/ccsprskdJ1LEp8xou7uOi6geMCJ57sXDlTBSQAelXgyR
YrlH7vVE0rs1+8bdLnrMTK+eTNOTWgNFxEpH8gzsOy3J5PbfZPYN2SRL+r1Fmomx
QdjF7K1gRfCLBwG4fJuilkpwjPkUpFlCv4RFFrr6ZQjf1DSNzZgZ+9+LFgZ8Sxzb
ACXGFErutuFDYBod/HLXYwwX4LrlZ3KlAHV5C9MNQHQzJao33batHIak9S856yiv
ND/Xqm5V0IgTPEcjDwHGMV5/lkCJHJKzJBrbchBDJt7uR4tyvulCet508rmz6fVe
mGcK6jvd1Wi/6nOTULycv0Ufk55dHl/K8nBUi7xUYFz22Yo0cHmXtkcwnvAswmT2
cqjM2/Ypu4GPT4nGk8Txcick5rI+4Z42U00hn3h0mp0w75Wn7n3cAoiMWGyIn6s8
WRSSlu7KeT+EDzmINuko
=Knbb
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: The absolute uri: http://java.sun.com/jsp/jstl/core cannot be resolved in either web.xml or the jar files deployed with this application

2014-10-02 Thread Gibran Castillo
Ok, thanks

On Thu, Oct 2, 2014 at 5:14 PM, Christopher Schultz 
ch...@christopherschultz.net wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Gibran,

 On 10/2/14 5:04 PM, Gibran Castillo wrote:
  To fix the problem I put the .jar files in tomcat's lib directory
  and it works best way to do this is like you said to put the
  *.jar files in the WEB-INF/lib directory, build the project as WAR
  and deploy the war file in Tomcat Where do I place the .war
  file in Tomcat?  in the 'webapps' directory?

 Yes, you would put the WAR file into Tomcat's webapps/ directory. If
 you do that, you won't need the separate donow62.xml file.

 - -chris

  On Thu, Oct 2, 2014 at 4:11 PM, Christopher Schultz 
  ch...@christopherschultz.net wrote:
 
  Gibran,
 
  On 10/2/14 3:59 PM, Gibran Castillo wrote:
  I deployed donow62 Spring MVC app into Tomcat by placing
  donow62.xml file in $CATALINA_HOME/conf/Catalina/localhost
 
  The contents of donow62.xml are as follow: Context
 
 
 docBase=/Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website
 
 
 
 
 reloadable=true/
 
  They basically point to the website directory in the spring
  mvc project in my eclipse workspace.
 
  What is the directory structure of .../donow62/website?
 
  I looked at the Tomcat logs and it says donow62 deployed
  successfully.  In the Tomcat Web Application Manager I can
  see /donow62 listed there.
 
  When I clicked on /donow62 it sends me to this URL
  http://localhost:8080/donow62/ but instead of getting
  expected result and the web page, I get HTTP Status 500 [see
  web browser log below]
 
  My Spring MVC donow62 app is using JSTL and it is in the
  classpath. Using Eclipse on the donow62 project I created
  User Libraries that reference all the dependencies for
  donow62.  The SERVLET user library has  el-api.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/el-api.jar 
  jasper.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper.jar 
  jasper-el.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/jasper-el.jar 
  jsp-api.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/jsp-api.jar 
  servlet-api.jar -
  /Library/Tomcat/apache-tomcat-8.0.12/lib/servlet-api.jar 
  javax-servlet.jsp.jstl-1.2.1.jar -
 
 
 /Users/gibranecastillo/Documents/java/servlet/javax-servlet.jsp.jstl-1.2.1.jar
 
 
 
 
 
 The exception is basically saying that the donow62 app is missing the JSTL
  dependency, the jar, any suggestions on how fix this are
  welcome.
 
  Is the JSTL JAR file in
 
 
 /Users/gibranecastillo/Documents/workspace/CollegeLife/donow62/website/WEB-INF/lib?
 
 
 If not, you aren't actually using it.
 
  Although I don't do it myself, Eclipse is pretty good at deploying
  web applications to Tomcat itself: you shouldn't have to even
  create your own context.xml file and fill it with data.
 
  If you want to do everything manually (believe me, I understand),
  then you'll need to make sure that your Eclipse project
  successfully builds to a WAR-like structure which contains, among
  other things, a WEB-INF/ directory and all of the things that
  should be in there (like lib/*.jar). If you don't do that, then you
  won't really be deploying a web application... you'll effectively
  be mapping a directory on the disk into a URL space and getting no
  other benefits.
 
  -chris
 
  -
 
 
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
  For additional commands, e-mail: users-h...@tomcat.apache.org
 
 
 
 
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v1
 Comment: GPGTools - http://gpgtools.org

 iQIcBAEBCAAGBQJULcAeAAoJEBzwKT+lPKRY1+cQAMY1dP2G+IjwFLciEUkWRUZ0
 AS9MmQZT6QJ4EtnAjBeby3Uv8So9XzWu4ZKYjUT4QLPntXFswnnkVNW3DKHNXxhq
 uxHYLBhaZRTDYmHpkuNHdH5nX8Cil5wy7ToXqBPmTnY/DxDghjU6Vlzb19oWpkVM
 HyM8Ky2CnGqoKtr0fTw8hOzpsi/2F9mgMM7j+cuWmMQoMKpAho8pc5UuBCSU55wG
 JJgaTGf0UNsm9X6M4YB/ccsprskdJ1LEp8xou7uOi6geMCJ57sXDlTBSQAelXgyR
 YrlH7vVE0rs1+8bdLnrMTK+eTNOTWgNFxEpH8gzsOy3J5PbfZPYN2SRL+r1Fmomx
 QdjF7K1gRfCLBwG4fJuilkpwjPkUpFlCv4RFFrr6ZQjf1DSNzZgZ+9+LFgZ8Sxzb
 ACXGFErutuFDYBod/HLXYwwX4LrlZ3KlAHV5C9MNQHQzJao33batHIak9S856yiv
 ND/Xqm5V0IgTPEcjDwHGMV5/lkCJHJKzJBrbchBDJt7uR4tyvulCet508rmz6fVe
 mGcK6jvd1Wi/6nOTULycv0Ufk55dHl/K8nBUi7xUYFz22Yo0cHmXtkcwnvAswmT2
 cqjM2/Ypu4GPT4nGk8Txcick5rI+4Z42U00hn3h0mp0w75Wn7n3cAoiMWGyIn6s8
 WRSSlu7KeT+EDzmINuko
 =Knbb
 -END PGP SIGNATURE-

 -
 To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: users-h...@tomcat.apache.org




-- 


Thank you,
 *Gibran E Castillo*
*iOS 7:  434.713.8095*


Struts 2 /Glassfish to Tomcat migration

2014-10-02 Thread Kiran Badi
I am migration my glassfish struts 2 based application to Tomcat 7.055.

I am coming across 2 issues, first one is below exception while starting
Tomcat

java.lang.UnsatisfiedLinkError: C:\Apache Software
Foundation\apache-tomcat-7.0.55\bin\tcnative-1.dll: Can't load IA 64-bit
.dll on a AMD 64-bit platform

these are java information,

Using CATALINA_BASE:   C:\Apache Software Foundation\apache-tomcat-7.0.55
Using CATALINA_HOME:   C:\Apache Software Foundation\apache-tomcat-7.0.55
Using CATALINA_TMPDIR: C:\Apache Software
Foundation\apache-tomcat-7.0.55\temp
Using JRE_HOME:C:\Program Files\Java\jdk1.7.0_13


Though the server starts and I can access the home page,
but it seems like struts.xml file is getting ignored and i am getting 404
for all jsp which are under web-inf.

Is their any migration guide from glassfish 4x to Tomcat ?

I was thinking that copying struts.xml to config directory and setting
dispatcher servlet should be sufficient.I am missing anything here.


Re: Struts 2 /Glassfish to Tomcat migration

2014-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Kiran,

On 10/2/14 9:59 PM, Kiran Badi wrote:
 I am migration my glassfish struts 2 based application to Tomcat
 7.055.
 
 I am coming across 2 issues, first one is below exception while
 starting Tomcat
 
 java.lang.UnsatisfiedLinkError: C:\Apache Software 
 Foundation\apache-tomcat-7.0.55\bin\tcnative-1.dll: Can't load IA
 64-bit .dll on a AMD 64-bit platform

You have the IA-64 library in your path, and you need the x86-64
library instead. How did you install Tomcat? If you used the binary
installer, it should have correctly detected your architecture and
used the correct library. If you installed it manually, you should
have a selection of tcnative .dll files. fine the x86-64 one and use that.

 these are java information,
 
 Using CATALINA_BASE:   C:\Apache Software
 Foundation\apache-tomcat-7.0.55 Using CATALINA_HOME:   C:\Apache
 Software Foundation\apache-tomcat-7.0.55 Using CATALINA_TMPDIR:
 C:\Apache Software Foundation\apache-tomcat-7.0.55\temp Using
 JRE_HOME:C:\Program Files\Java\jdk1.7.0_13
 
 Though the server starts and I can access the home page, but it
 seems like struts.xml file is getting ignored and i am getting 404 
 for all jsp which are under web-inf.

The inability to start the APR connector won't have any effect on this.

How are you trying to access your .jsp files within WEB-INF? Via a
direct URL or some kind of internal forward from another URL?

 Is their any migration guide from glassfish 4x to Tomcat ?

You shouldn't have to do too much to migrate, as long as you don't
have anything GlassFish-specific in your webapp. You should be able to
take your existing WAR file and drop it into Tomcat's webapps/
directory. That should get you 90% of the way. If you use JNDI-based
resources, you'll have additional configuration, but I won't get into
that unless you actually need it.

 I was thinking that copying struts.xml to config directory and
 setting dispatcher servlet should be sufficient. I am missing
 anything here.

What is config directory and how did you set [the] dispatcher servlet?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org

iQIcBAEBCAAGBQJULgw0AAoJEBzwKT+lPKRYoI8P/2N1QNVZK1ZfvPqNNY2sALE0
4obJMM/vKtzDsKrJmJ+kaTfSAt1Cnd6fOP3VCFUYrfkKGWUjOfTczxN6c2RgvJbV
R8Y9nwUhevgb2Y36slZ2Kda6g2XmxH5WR8PU/qEF8qRu+ZM7BSkKAkfUz+lrbrC2
a4MD02LmiQXaXEyxsFzOcW+Ig9iMUi4gpCA5hJw9SJtObedeW9rfQDrNJVpMd559
FFUdGE6hz2/+3JcTV+gYutYrS0sGuPrTL/WA+X7OYTdPheU6R9JmiK8OmLBA6COg
aNBT6k/Bm29NgTQVAXATkomI7fBCV3HRYlIH7eA1oZgMPgSKf6PTdrfKaAvZZfz0
qxXl9dD7gXgssNN59CxxDu2xHlYv11RMN/vlVodpdWWHWkttetigpQi1wL3dDfJd
uBzi8vl8DXVcs+44sZ+lPNa07VjHRxR8zElqTppQ9f500ozQN+5j18LYtOKefoOZ
HmQ1lhs721hN5XzWP1xQRZGFNVg1fb0tBFVf/n2TT3n9DhiQhXpy029xKYkUBa9q
Ch2iFzQN1HbLimBVuUlKx2fDjy8P6BWUfN0I1T9kSPLwZwtSZy8V0JuSuaOdkNby
kQ6PQBV5CMQNdMNcNE5rIDUA66YyLOMXMYnN/pQaT5JIoeTJL0b2jVNweFGcdukp
ANyaJNqtL6SuIS7DUmvE
=QXr1
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org