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 105584 - AM not configured correctly after first start of AS
Summary: AM not configured correctly after first start of AS
Status: RESOLVED FIXED
Alias: None
Product: installer
Classification: Unclassified
Component: NBI (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: dlipin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-04 15:09 UTC by Andrey Yamkovoy
Modified: 2007-07-02 09:28 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 Andrey Yamkovoy 2007-06-04 15:09:54 UTC
I am not sure it's installer issue, probably it's AM configurator issue. Please
evaluate...

Steps to reproduce:
- Install full bundle.
- Start IDE.
- Start AS from Services TAB.
- Notice that AM not configured correctly when AS started at 1st time (invoke
'Edit' item in the context menu of some of the AM profiles).
- Restart AS.
- Notice that AM configured correctly when AS started at 2nd time.
Comment 1 dlipin 2007-06-05 14:02:20 UTC
Andrey,

There was an issue in our scripts that resulted in wrong application server 
configuraition during its installation. That error is most probably the core of 
such a behaviour.

I mark the issue as fixed. Please reopen it if it is still reproducible in the 
next daily build (when it is available).

Dmitry
Comment 2 Andrey Yamkovoy 2007-06-06 15:43:21 UTC
Still reproducible on the NBI build 0706060000.
Comment 3 dlipin 2007-06-08 10:47:13 UTC
note: I`ve filed an issue 6567469 in bugster against access manager.
Comment 4 Peter Pis 2007-06-25 16:49:00 UTC
Is this issue considered as a stopper for M10? Umbrella issue #106807 has been fixed.
Comment 5 Kirill Sorokin 2007-07-02 09:28:44 UTC
I assume that this might have been fixed with the new build of SJSAM, which is included in M10. Please verify and reopen
as appropriate.