Bugs item #764150, was opened at 2003-07-01 19:20
Message generated for change (Comment added) made by gregwilkins
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=764150&group_id=22866

Category: JBossWeb
Group: v3.2
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: Patrick Lai (lc9)
Assigned to: Scott M Stark (starksm)
Summary: Jetty cannot use symbolic links in server/<config>/lib

Initial Comment:
OS: Solaris 2.8
JBoss: 3.2.2RC1
JDK: 
1.4.0_01

Jar files put in server/<config>/lib as symbolic 
links do not seem to be loaded.  Here is how to reproduce the 
problem:

$ cd $JBOSS_HOME/server
$ mkdir 
bug
$ cp -rp default/conf bug/
$ cp -rp default/deploy 
bug/
$ cp -rp default/farm bug/
$ cd bug; mkdir lib; cd 
lib
$ ln -s ../../default/lib/* .
$ cd ..; ../../bin/run.sh -c 
bug

JBoss reports a lot of "bad classpath entry" warning 
during start up, and access to jmx-console results in "HTTP ERROR: 
500 Unable to compile class for JSP An error occurred at line: -1 in the 
jsp file: null ..."

Symbolic links were okay in 3.2.0.

----------------------------------------------------------------------

Comment By: Greg Wilkins (gregwilkins)
Date: 2003-08-04 07:00

Message:
Logged In: YES 
user_id=44062

This problem is due to a cautious response to some security
problems.    Previously Jetty considered that Unix was
immune to unwitting alias problems (eg. ~eight.thr names in
win32) and thus did not check for aliases on unix.  
However, some recent JVMs started ignoring trailing null
characters in file URLs on Unix.  
This caused the problem where JSP source can be seen or
security constraints bypassed by appendind %00 on the end of
a URL.

Jetty could have explicitly checked for this case, but it
would then be vulnerable if JVMs again changed to add a new
alias case.   So currently Jetty is checking for aliases all
the time.
Unfortunately this catched simlink as well, as there is no
way to tell the difference between a user symlink and OS/JVM
alias for a file.

Unfortunately Jetty uses the same resource code for loading
libraries as it does for serving resources.  Thus the Jetty
classloader no longer accepts symlinks.

We will have to parameterize the resource layer so that it
can selectively ignore aliases.   This will be coming soon.



  

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-07-04 11:16

Message:
Logged In: YES 
user_id=175228

Ok, I was actually using the jboss-3.2.2RC1_tomcat-4.1.24
bundle rather than jboss-3.2.2RC1 which includes Jetty. When
testing this proceedure with jboss-3.2.2RC1 I do see the
indicated failures.

----------------------------------------------------------------------

Comment By: Patrick Lai (lc9)
Date: 2003-07-04 07:39

Message:
Logged In: YES 
user_id=804134

Just to provide more information, these are the first the warning 
messages I see when JBoss starts:

23:51:48,260 INFO  
[MainDeployer] Starting deployment of package: 
file:/home/plai/local/jboss-
3.2.2RC1/server/bug/deploy/jms/jbossmq-httpil.sar/jbossmq-
httpil.war/
23:51:50,629 INFO  [jbossweb] Registered 
jboss.web:Jetty=0,JBossWebApplicationContext=0,context=/jbossmq-
httpil
23:51:50,706 INFO  [jbossweb] Checking Resource 
aliases
23:51:52,204 WARN  
[JBossWebApplicationContext#/jbossmq-httpil] bad classpath entry: 
file:/home/plai/local/jboss-
3.2.2RC1/server/bug/lib/jboss.jar
23:51:52,205 WARN  
[JBossWebApplicationContext#/jbossmq-httpil] bad classpath entry: 
file:/home/plai/local/jboss-
3.2.2RC1/server/bug/lib/jsse.jar
23:51:52,206 WARN  
[JBossWebApplicationContext#/jbossmq-httpil] bad classpath entry: 
file:/home/plai/local/jboss-
3.2.2RC1/server/bug/lib/jbossha.jar
...

I believe they 
come from org.jboss.jetty.JBossWebApplicationContext.

----------------------------------------------------------------------

Comment By: Scott M Stark (starksm)
Date: 2003-07-04 03:11

Message:
Logged In: YES 
user_id=175228

I followed these proceedures verbatim on a RH9 linux system
runing 1.4.1_02 and the server starts fine and the
jmx-console is accessible. I don't see how it could be a
system/vm issue since you said this worked with 3.2.0.

20:09:37,199 INFO  [MainDeployer] Deployed package:
file:/home/starksm/JBoss/Releases/jboss-3.2.2RC1/server/bug/conf/jboss-service.xml
20:09:37,202 INFO  [Server] JBoss (MX MicroKernel) [3.2.2RC1
(build: CVSTag=JBoss_3_2_2_RC1 date=200306060938)] Started
in 19s:663ms

[EMAIL PROTECTED] server]$ ls -l bug/lib/
total 0
lrwxrwxrwx    1 starksm  starksm        32 Jul  3 20:08
activation.jar -> ../../default/lib/activation.jar
lrwxrwxrwx    1 starksm  starksm        25 Jul  3 20:08
ant.jar -> ../../default/lib/ant.jar
lrwxrwxrwx    1 starksm  starksm        39 Jul  3 20:08
autonumber-plugin.jar -> ../../default/lib/autonumber-plugin.jar
lrwxrwxrwx    1 starksm  starksm        26 Jul  3 20:08
bcel.jar -> ../../default/lib/bcel.jar
lrwxrwxrwx    1 starksm  starksm        43 Jul  3 20:08
bindingservice-plugin.jar ->
../../default/lib/bindingservice-plugin.jar
lrwxrwxrwx    1 starksm  starksm        36 Jul  3 20:08
bsh-core-1.2b7.jar -> ../../default/lib/bsh-core-1.2b7.jar
lrwxrwxrwx    1 starksm  starksm        34 Jul  3 20:08
bsh-deployer.jar -> ../../default/lib/bsh-deployer.jar
lrwxrwxrwx    1 starksm  starksm        28 Jul  3 20:08
hsqldb.jar -> ../../default/lib/hsqldb.jar
lrwxrwxrwx    1 starksm  starksm        35 Jul  3 20:08
hsqldb-plugin.jar -> ../../default/lib/hsqldb-plugin.jar
lrwxrwxrwx    1 starksm  starksm        35 Jul  3 20:08
javax.servlet.jar -> ../../default/lib/javax.servlet.jar
lrwxrwxrwx    1 starksm  starksm        47 Jul  3 20:08
jboss-common-jdbc-wrapper.jar ->
../../default/lib/jboss-common-jdbc-wrapper.jar
lrwxrwxrwx    1 starksm  starksm        29 Jul  3 20:08
jbossha.jar -> ../../default/lib/jbossha.jar
lrwxrwxrwx    1 starksm  starksm        39 Jul  3 20:08
jbossha-singleton.jar -> ../../default/lib/jbossha-singleton.jar
lrwxrwxrwx    1 starksm  starksm        32 Jul  3 20:08
jboss-j2ee.jar -> ../../default/lib/jboss-j2ee.jar
lrwxrwxrwx    1 starksm  starksm        32 Jul  3 20:08
jboss-jaas.jar -> ../../default/lib/jboss-jaas.jar
lrwxrwxrwx    1 starksm  starksm        27 Jul  3 20:08
jboss.jar -> ../../default/lib/jboss.jar
lrwxrwxrwx    1 starksm  starksm        33 Jul  3 20:08
jboss-jsr77.jar -> ../../default/lib/jboss-jsr77.jar
lrwxrwxrwx    1 starksm  starksm        38 Jul  3 20:08
jboss-management.jar -> ../../default/lib/jboss-management.jar
lrwxrwxrwx    1 starksm  starksm        29 Jul  3 20:08
jbossmq.jar -> ../../default/lib/jbossmq.jar
lrwxrwxrwx    1 starksm  starksm        29 Jul  3 20:08
jbosssx.jar -> ../../default/lib/jbosssx.jar
lrwxrwxrwx    1 starksm  starksm        39 Jul  3 20:08
jboss-transaction.jar -> ../../default/lib/jboss-transaction.jar
lrwxrwxrwx    1 starksm  starksm        27 Jul  3 20:08
jcert.jar -> ../../default/lib/jcert.jar
lrwxrwxrwx    1 starksm  starksm        40 Jul  3 20:08
jmx-adaptor-plugin.jar ->
../../default/lib/jmx-adaptor-plugin.jar
lrwxrwxrwx    1 starksm  starksm        26 Jul  3 20:08
jnet.jar -> ../../default/lib/jnet.jar
lrwxrwxrwx    1 starksm  starksm        31 Jul  3 20:08
jnpserver.jar -> ../../default/lib/jnpserver.jar
lrwxrwxrwx    1 starksm  starksm        33 Jul  3 20:08
jpl-pattern.jar -> ../../default/lib/jpl-pattern.jar
lrwxrwxrwx    1 starksm  starksm        30 Jul  3 20:08
jpl-util.jar -> ../../default/lib/jpl-util.jar
lrwxrwxrwx    1 starksm  starksm        26 Jul  3 20:08
jsse.jar -> ../../default/lib/jsse.jar
lrwxrwxrwx    1 starksm  starksm        25 Jul  3 20:08
jts.jar -> ../../default/lib/jts.jar
lrwxrwxrwx    1 starksm  starksm        27 Jul  3 20:08
log4j.jar -> ../../default/lib/log4j.jar
lrwxrwxrwx    1 starksm  starksm        26 Jul  3 20:08
mail.jar -> ../../default/lib/mail.jar
lrwxrwxrwx    1 starksm  starksm        33 Jul  3 20:08
mail-plugin.jar -> ../../default/lib/mail-plugin.jar
lrwxrwxrwx    1 starksm  starksm        39 Jul  3 20:08
properties-plugin.jar -> ../../default/lib/properties-plugin.jar
lrwxrwxrwx    1 starksm  starksm        46 Jul  3 20:08
scheduler-plugin-example.jar ->
../../default/lib/scheduler-plugin-example.jar
lrwxrwxrwx    1 starksm  starksm        38 Jul  3 20:08
scheduler-plugin.jar -> ../../default/lib/scheduler-plugin.jar
lrwxrwxrwx    1 starksm  starksm        34 Jul  3 20:08
snmp-support.jar -> ../../default/lib/snmp-support.jar
lrwxrwxrwx    1 starksm  starksm        27 Jul  3 20:08
tyrex.jar -> ../../default/lib/tyrex.jar
lrwxrwxrwx    1 starksm  starksm        27 Jul  3 20:08
xalan.jar -> ../../default/lib/xalan.jar


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=376685&aid=764150&group_id=22866


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to