Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 329622 - error publishing to Apache Geronimo V3.0
Summary: error publishing to Apache Geronimo V3.0
Status: RESOLVED INVALID
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: wst.server (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Angel Vera CLA
QA Contact: Angel Vera CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-06 17:59 EDT by hiperion CLA
Modified: 2010-11-09 15:02 EST (History)
0 users

See Also:

Attachments
log (3.05 KB, text/x-log)
2010-11-09 10:18 EST, hiperion CLA 		no flags Details
View All 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 hiperion CLA 2010-11-06 17:59:30 EDT 
Build Identifier: 20100617-1415

An internal error occurred during: "Publishing to Apache Geronimo v3.0 Server at localhost...".

Reproducible: Always

Steps to Reproduce:
1.Project, Run as, Run on server
2. Choose an existing server, next, Finish
3. The System tries to deploy the project but after starting the server right I get: An internal error occurred during: "Publishing to Apache Geronimo v3.0 Server at localhost...".
net.sf.cglib.core.Signature.<init>(Ljava/lang/String;Lnet/sf/cglib/asm/Type;[Lnet/sf/cglib/asm/Type;)V
Comment 1 Angel Vera CLA 2010-11-08 11:08:13 EST 
Can you check the .log of the workspace and see if there are any more details about the error?
Comment 2 hiperion CLA 2010-11-09 10:18:45 EST 
Created attachment 182721 [details]
log 

Yes, here you have the log.
Comment 3 Angel Vera CLA 2010-11-09 15:02:14 EST 
This looks like an server adopter problem. Try reporting the problem to the provider of the plugin or the server provider itself. 

The error in the .log shows that the server adopter (plugin provider) class GeronimoConnectionFactory is calling some deployment code and later it fails (possibly in the server code) because JMXProxyMethodInterCeptor.getSuperIndex:157 doesn't find a method.