#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 by , 15 years ago
comment:3 by , 15 years ago
Yes, but in code after uri/url manipulations uri authority from "" became null -> and here is exception
comment:4 by , 15 years ago
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 by , 15 years ago
| Milestone: | → 1.0.1 |
|---|
comment:6 by , 15 years ago
Might work after the patch for Weblogic using the "zip" scheme in r13700. Please test in failing environment.
comment:7 by , 15 years ago
| Keywords: | needs-test analysis added |
|---|---|
| Milestone: | 1.0.1 → 1.1.0 |
| Owner: | changed from to |
| Status: | new → assigned |
comment:8 by , 15 years ago
| Owner: | changed from to |
|---|
comment:9 by , 14 years ago
| Owner: | changed from to |
|---|
comment:10 by , 14 years ago
| Owner: | changed from to |
|---|
comment:11 by , 14 years ago
| 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 by , 14 years ago
| 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.