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 212743 - NB Assumptions
Summary: NB Assumptions
Status: RESOLVED INVALID
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WebLogic (show other bugs)
Version: 7.2
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: Petr Hejl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-20 00:00 UTC by ttroy
Modified: 2012-05-23 06:07 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ttroy 2012-05-20 00:00:51 UTC
I have local WebLogic server installed prior to using NetBeans.  I set the password for the weblogic user to something other than the default.  I register the server within NetBeans using the password I set, not the default of welcome1. I then open a web project that deploys to the WebLogic server.  A  dialog tells me that some server libraries need to be installed and I can fix this by right clicking the web project and selecting the option to fix the problem and that a server restart might be needed.  I stop the WebLogic server that I usually start before using NetBeans.  I select the option to fix the missing library (which never told me what was missing, that should be fixed to tell me what it thinks is missing). NetBeans then starts the server, invokes an index page, http://192.168.1.103:7001/index.jsp, which is a WebLogic Server Getting Started page.  At this point, the output window in NetBeans that started the server says that 5 invalid login attempts have been made and the weblogic user has been locked for the next 30 minutes.  Thanks, my admin user is locked out because you assumed the password was welcome1, vs. what I said it is in the server setup. And another thing, you ignored the startWebLogic.cmd on my machine and used your own, thus ignoring my customized settings.  Stop that.  Just run the startWebLogic.cmd and use the password provided. I later realized the NB is starting the examplesServer vs the server I configured in NB.  In addition, you are starting Derby.  Why?  Run only the server I set up.  Why do you assume I am developing against an example server?
Comment 1 Petr Hejl 2012-05-20 07:49:05 UTC
(In reply to comment #0)
> I have local WebLogic server installed prior to using NetBeans.  I set the
> password for the weblogic user to something other than the default.  I register
> the server within NetBeans using the password I set, not the default of
> welcome1. I then open a web project that deploys to the WebLogic server.  A 
> dialog tells me that some server libraries need to be installed and I can fix
> this by right clicking the web project and selecting the option to fix the
> problem and that a server restart might be needed.  I stop the WebLogic server
> that I usually start before using NetBeans.  I select the option to fix the
> missing library (which never told me what was missing, that should be fixed to
> tell me what it thinks is missing). NetBeans then starts the server, invokes an
> index page, http://192.168.1.103:7001/index.jsp, which is a WebLogic Server
> Getting Started page.  At this point, the output window in NetBeans that
> started the server says that 5 invalid login attempts have been made and the
> weblogic user has been locked for the next 30 minutes.  Thanks, my admin user
> is locked out because you assumed the password was welcome1, vs. what I said it
> is in the server setup.
How did you came to conclusion the welcome1 is used? Is it somewhere in console? There is no hardcoded password in nb sources. Are you sure you typed in the password correctly?

> And another thing, you ignored the startWebLogic.cmd on
> my machine and used your own, thus ignoring my customized settings.  Stop > that.
Again, there is no "own" script. Is that something you see in console? We are using startWeblogic.cmd of the domain.

>  Just run the startWebLogic.cmd and use the password provided. I later realized
> the NB is starting the examplesServer vs the server I configured in NB. 
That's strange. We do not care about particular servers. We start the domain by the script as written above.

> In
> addition, you are starting Derby.  Why?  Run only the server I set up.  Why do
> you assume I am developing against an example server?
Again no specific derby code in nb afaik.

Would be good to know the WL version and exact steps to reproduce the issue here, so we can evaulate and fix it. This means step by step instructions for domain creation and registration inside NB.

Thanks.
Comment 2 Petr Hejl 2012-05-20 07:55:29 UTC
I realized that if you registered the wrong domain in the wizard that would be explanation for all the problems you have just described. Are you sure you registered the domain correctly and it is not just example domain registered?
Comment 3 ttroy 2012-05-21 12:55:10 UTC
I see what you mean on setting the domain. I never use domains I don't create so that fact that the examples domain was selected did not register. To fix the domain, I had to remove the server and add it again because the Domain Folder can not be updated.