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 103155 - Secured web services not working on AS running on JDK 1.5
Summary: Secured web services not working on AS running on JDK 1.5
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Identity (show other bugs)
Version: 6.x
Hardware: Sun All
: P2 blocker (vote)
Assignee: Peter Liu
Keywords: RELNOTE
: 102818 (view as bug list)
Depends on:
Reported: 2007-05-02 16:15 UTC by Andrey Yamkovoy
Modified: 2008-07-11 19:47 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Yamkovoy 2007-05-02 16:15:11 UTC
If Application Server was started on JDK 1.5 then secured web services not
working at all. In this case not secured web services working fine.

This issue is reproducible on Solaris and Linux but not reproducible on Windows.

The errors and symptoms are the same as for issue 102818 but I created the
separate issue because MacOS use JDK from another vendor.

Steps to reproduce:
1. Start AS on JDK 1.5.
   - stop AS.
   - change JDK in file "<AppServer>/config/asenv.conf".
   - change JDK in file "<AppServer>/imq/etc/imqenv.conf".
   - start AS.
2. Deploy App with secured WS.
3. Deploy App with secured WSC.
4. Run servlet which invokes secured WS operation.
5. Notice that secured web services not working (you will see exception).

In my opinion this issue is not a stopper for M9 but should be added to Release
Comment 1 Bob May 2007-05-03 16:02:50 UTC
Summary for RN
If you started the Application Server with JDK 1.5 on either the Solaris or
Linux platforms, the IDE's secured web services feature does not work
Comment 2 Annette Wegscheider 2007-05-03 18:15:29 UTC
Added to M9 release notes with summary provided by bmay
Comment 3 tonybeckham 2007-05-29 16:51:59 UTC
*** Issue 102818 has been marked as a duplicate of this issue. ***
Comment 4 Peter Liu 2007-06-05 01:04:08 UTC
Here is the corresponding bug in bugster filed against AM:
Comment 5 Srividhya Narayanan 2007-06-22 19:34:33 UTC
The required fix from AM doesn't come until 6/27 into the SDK build. This means the Identity will not be able to have
this fix until beta1. Marking the target milestone for beta1.

The workaround is to use JDK 1.6 for now. Lowering the priority to reflect that we have a workaround.
Comment 6 Peter Liu 2007-06-22 20:07:33 UTC
We should still try to verify if this is fixed in the latest bits. According to the AM team, the workaround for this
issue is included in the latest bits.

Comment 7 Peter Liu 2007-07-05 19:04:57 UTC
This issue has been fixed in the AM bits bundled with M10 as verified by Tony.

Comment 8 tonybeckham 2008-07-11 19:47:51 UTC