This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 119979 - SERVER : When starting up Sun App Server 9, receive exception from jbi component
Summary: SERVER : When starting up Sun App Server 9, receive exception from jbi component
Status: RESOLVED WONTFIX
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 9 (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Nitya Doraisamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-25 01:40 UTC by dziants
Modified: 2007-10-31 22:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Log file with jbi exception (29.99 KB, application/octet-stream)
2007-10-25 01:42 UTC, dziants 		Details
Also attaching jvm log (12.08 KB, application/octet-stream)
2007-10-25 01:44 UTC, dziants 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dziants 2007-10-25 01:40:24 UTC 
When starting up Sun App Server 9, receive exception from jbi component.

Log file is attached.

Section from log is quoted here:
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
[#|2007-10-25T02:08:32.750+0200|WARNING|sun-
appserver9.1|javax.enterprise.system.stream.err|_ThreadID=11;_ThreadName=pool-1-thread-2;_RequestID=ff5d71ab-7b0b-49d8-
97ab-32d93d43b5af;|com.sun.appserv.server.ServerLifecycleException: java.lang.LinkageError: loader constraint 
violation in interface itable initialization: when resolving 
method "com.sun.jbi.framework.EnvironmentContext.getComponentManager()Lcom/sun/jbi/ComponentManager;" the class loader 
(instance of java/net/URLClassLoader) of the current class, com/sun/jbi/framework/EnvironmentContext, and the class 
loader (instance of java/net/URLClassLoader) for interface com/sun/jbi/EnvironmentContext have different Class objects 
for the type com/sun/jbi/ComponentManager used in the signature
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Comment 1 dziants 2007-10-25 01:42:46 UTC 
Created attachment 51638 [details]
Log file with jbi exception
Comment 2 dziants 2007-10-25 01:44:38 UTC 
Created attachment 51639 [details]
Also attaching jvm log
Comment 3 Petr Hejl 2007-10-25 14:50:43 UTC 
Maybe this bug should be filed against the glassfish itself - I don't see any nb related code.
Comment 4 Nitya Doraisamy 2007-10-31 03:01:11 UTC 
Filed issue against server. Please add yourself to the cc list of GlassFish issue
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3824
Comment 5 Nitya Doraisamy 2007-10-31 18:28:01 UTC 
Also, are you starting the appserver from NetBeans? Do you see the exception in server.log if you start the server from
asadmin?
Comment 6 dziants 2007-10-31 21:32:43 UTC 
It happens also when starting the server from asadmin and netbeans is not running.
I see now why the bug was moved to glassfish (#3824), and tracking done there.

Is there anyway of formally reassigning it here to glassfish tracking, or should the resolution just be marked as 
WONTFIX with this note?
Comment 7 Nitya Doraisamy 2007-10-31 22:28:31 UTC 
No. There is no formal way of reassigning it here to glassfish tracking. Will prefix 'SERVER' to summary and mark as WONTFIX