#173 closed defect (fixed)
Cannot initialize ABCL within .ear
Reported by: | https://me.yahoo.com/a/KvgfiPIMkNAd1zTHUTfXlVJkp92K#3d978 | Owned by: | Mark Evenson |
---|---|---|---|
Priority: | blocker | Milestone: | 1.1.0 |
Component: | interpreter | Version: | 0.27 |
Keywords: | needs-test | Cc: | |
Parent Tickets: |
Description
Exception is
java.lang.Error: ABCL Debug.assertTrue() assertion failed!
at org.armedbear.lisp.Debug.assertTrue(Debug.java:46)
at org.armedbear.lisp.Pathname.init(Pathname.java:404)
at org.armedbear.lisp.Pathname.<init>(Pathname.java:217)
at org.armedbear.lisp.Site.init(Site.java:60)
at org.armedbear.lisp.Site.getLispHome(Site.java:74)
Truncated. see log file for complete stacktrace
ABCL is initialized from .ear and tries to load boot.lisp
on URL zip:/opt/was/.........abcl-0.27.0.jar!/......../boot.lisp
Change History (12)
comment:1 Changed 13 years ago by
comment:3 Changed 13 years ago by
Yes, but in code after uri/url manipulations uri authority from "" became null -> and here is exception
comment:4 Changed 13 years ago by
uri is
zip:C:/Oracle/Middleware/user_projects/domains/evb-head/servers/AdminServer/tmp/_WL_user/evb-app/vn9chc/war/WEB-INF/lib/abcl-0.27.0.jar!/org/armedbear/lisp/boot.lisp
comment:5 Changed 13 years ago by
Milestone: | → 1.0.1 |
---|
comment:6 Changed 13 years ago by
Might work after the patch for Weblogic using the "zip" scheme in r13700. Please test in failing environment.
comment:7 Changed 13 years ago by
Keywords: | needs-test analysis added |
---|---|
Milestone: | 1.0.1 → 1.1.0 |
Owner: | changed from ehuelsmann to ehuelsman |
Status: | new → assigned |
comment:8 Changed 13 years ago by
Owner: | changed from ehuelsman to ehuelsmann |
---|
comment:9 Changed 12 years ago by
Owner: | changed from ehuelsmann to unassigned |
---|
comment:10 Changed 12 years ago by
Owner: | changed from unassigned to Mark Evenson |
---|
comment:11 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
ABCL runs fine under current Weblogic 10.3.
Exceptions for PATHNAME-URL with the schema 'zip' have been added to the class loading infrastructure that allow me to run Armed Bear in all Weblogic containers currently support commercially by ORCL.
(need reference to commit)
comment:12 Changed 12 years ago by
Keywords: | analysis removed |
---|
On which application server?
In general, the classpath scanning system which is part of the Spring framework might be a good source of inspiration on how to deal with idiosyncratic classloaders on various application servers. I'm afraid that issues like this are only solvable by a lot of special casing.