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 86837 - Exception when trying to access WL 9.1 Server
Summary: Exception when trying to access WL 9.1 Server
Status: RESOLVED WORKSFORME
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P2 blocker (vote)
Assignee: Sherold Dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-10 08:14 UTC by tkellerer
Modified: 2006-12-11 11:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Startup log from WL (5.15 KB, text/plain)
2006-10-10 08:14 UTC, tkellerer
Details
NB log file (19.08 KB, text/plain)
2006-10-10 08:15 UTC, tkellerer
Details
weblogic jar with additional logging (1.28 MB, application/octet-stream)
2006-10-10 15:11 UTC, Sherold Dev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description tkellerer 2006-10-10 08:14:32 UTC
After setting up a new Weblogic Server in 5.5 RC1, I can start the server from
within NB. Once startup is completed an exception is thrown (signalled by the
littel stop sign in the status bar). 

The server cannot be accessed from within NB after that. 

This is not the same as #85454, as the exception is different, and WL and NB are
both running on JDK 1.5 (NB uses 1.5.0_08, whereas WL uses 1.5.0_04 which is
installed during WL installation. I was not able to run WL with non-BEA supplied
JDK.
Comment 1 tkellerer 2006-10-10 08:14:59 UTC
Created attachment 35069 [details]
Startup log from WL
Comment 2 tkellerer 2006-10-10 08:15:27 UTC
Created attachment 35070 [details]
NB log file
Comment 3 Petr Blaha 2006-10-10 09:50:06 UTC
Stepane, can you evaluate the issue? Thanks Petr
Comment 4 Sherold Dev 2006-10-10 15:08:11 UTC
I was not able to reproduce this issue, although I used the same environment as
reported.

Are you sure you have registered the WebLogic server with the correct username
and password? If not it might be the cause of this issue. Can you try to remove
it and register it again?

If this doesn't help, please try to replace the following jar with the one attached:

<nb_home>\enterprise3\modules\org-netbeans-modules-j2ee-weblogic9.jar

and then try to start the server from NetBeans (this jar contains some
additional logging). Once the server is up and running, some more useful info
should appear in the NB message log, please attach it to the issue again.

Thanks
Comment 5 Sherold Dev 2006-10-10 15:11:43 UTC
Created attachment 35079 [details]
weblogic jar with additional logging
Comment 6 tkellerer 2006-10-10 16:42:06 UTC
OK, I retried with a fresh BEA installation and an empty NB userdir and now
starting and stopping seems to work, but I cannot deploy my module. When I do
so, the following appears:

init:
deps-module-jar:
deps-ear-jar:
deps-jar:
library-inclusion-in-archive:
library-inclusion-in-manifest:
compile:
compile-jsps:
Building jar: C:\Daten\NetBeansProjects\BeaTest\dist\BeaTest.war
do-dist:
dist:
Distributing C:\Daten\NetBeansProjects\BeaTest\dist\BeaTest.war to
[examplesServer/server]
Deploying C:\Daten\NetBeansProjects\BeaTest\dist\BeaTest.war
Waiting for server to start the module http://localhost:7001/test...
Applicaton Deployed
<Oct 10, 2006 5:38:53 PM CEST> <Info> <J2EE Deployment SPI> <BEA-260121>
<Initiating start operation for application, BeaTest.war [archive: null], to
examplesServer .> 
java.lang.ClassCastException: org.netbeans.modules.j2ee.weblogic9.WLTargetModuleID
run-deploy:
BUILD SUCCESSFUL (total time: 45 seconds)

There is no messages in NB's log file, even with the attached .jar file
Comment 7 tkellerer 2006-10-10 16:47:34 UTC
I forgot to mention, that there are no exceptions in the WL log files if the
ClassCastException occurs.

WL is set up with a node manager and one managed server (to which I'm actually
trying to deploy and not to [examplesServer/server])
Comment 8 Sherold Dev 2006-10-11 08:27:55 UTC
How do you know that the deployment failed? According to the Ant output log it
seems it completed successfully, see

> BUILD SUCCESSFUL (total time: 45 seconds)
Comment 9 tkellerer 2006-10-11 08:45:43 UTC
The module was not working after that deployment.
 After a restart of WL it seems to work now. 
Comment 10 Sherold Dev 2006-10-11 11:19:43 UTC
So does that mean that you are no longer able to reproduce the issue?

Thanks
Comment 11 Sherold Dev 2006-12-11 11:24:37 UTC
Closing as WORKSFORME.

If you are still experiencing the problem feel free to reopen the issue.