http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1161

*** shadow/1161 Fri Mar 30 11:11:33 2001
--- shadow/1161.tmp.17776       Fri Mar 30 11:37:10 2001
***************
*** 5,11 ****
  |       Status: NEW                         Version: 1.3                     |
  |   Resolution:                            Platform: PC                      |
  |     Severity: Normal                   OS/Version: Windows NT/2K           |
! |     Priority:                           Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
  |  Assigned To: [EMAIL PROTECTED]                                   |
  |  Reported By: [EMAIL PROTECTED]                                        |
--- 5,11 ----
  |       Status: NEW                         Version: 1.3                     |
  |   Resolution:                            Platform: PC                      |
  |     Severity: Normal                   OS/Version: Windows NT/2K           |
! |     Priority: High                      Component: Optional Tasks          |
  +----------------------------------------------------------------------------+
  |  Assigned To: [EMAIL PROTECTED]                                   |
  |  Reported By: [EMAIL PROTECTED]                                        |
***************
*** 34,37 ****
  2.  WLRun should put attribute-based jvm args BEFORE those directly set with 
  the jvmargs.
  
! (I am using WebLogic 5.1)
--- 34,44 ----
  2.  WLRun should put attribute-based jvm args BEFORE those directly set with 
  the jvmargs.
  
! (I am using WebLogic 5.1)
! 
! ------- Additional Comments From [EMAIL PROTECTED]  2001-03-30 11:37 -------
! There actually seems to be a bug in WebLogic (5.1sp8) where it checks for a 
! policy file in weblogic.system.home, even if java.security.policy is set to 
! find it elsewhere.  If you put any random file in weblogic.system.home and 
name 
! it weblogic.policy, WebLogic will pass this check and use the policy file you 
! told it to with java.security.policy.

Reply via email to