Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the agent work with JRE under security mode #37

Closed
junoyoon opened this issue Mar 8, 2014 · 1 comment
Closed

Make the agent work with JRE under security mode #37

junoyoon opened this issue Mar 8, 2014 · 1 comment
Labels
enhancement
Milestone
3.3.1

Comments

@junoyoon
Copy link
Contributor

junoyoon commented Mar 8, 2014

nGrinder 3.3 only works with JDK not JRE under the security mode. It's because SecurityManager tries to resolve the JAVA_HOME and JAVA_HOME can be only available with JDK. In the NGrinderSecurityManager JAVA_HOME is used to resolve the jre location. However jre location can be resolved with System.getProperty("java.home"), then we might not need to resolve JAVA_HOME explicitly.
junoyoon added a commit that referenced this issue Mar 8, 2014
@junoyoon
#37 Make the JRE path resolved by the java.home property.
855fe03
junoyoon added a commit that referenced this issue Mar 23, 2014
@junoyoon
#37 Make the target host field 1024 varchar
3f45c5a
@junoyoon junoyoon added this to the 3.3.1 milestone Apr 10, 2014
@junoyoon
Copy link
Contributor Author

Fixed.

lopiter pushed a commit that referenced this issue Jun 20, 2017
@junoyoon
Merge pull request #37 from paas/feature/add-preauth-filter
aece9a5 
Reviewed By: JunHo Yoon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
3.3.1
Development

No branches or pull requests
1 participant
@junoyoon