|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
Glassfish
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
|
If you type incorrect password or user name, the connection to Glassfish (9.0) is failed and obviously no module is deployed.
But if you click "Run" button again you will get dalog with error message saying the next: address : port is already in use.
Java.exe process keeps being in memory (in can be prooved by Task Manager). This procees has to be killed before next deployment attempts.
|
|
Description
|
If you type incorrect password or user name, the connection to Glassfish (9.0) is failed and obviously no module is deployed.
But if you click "Run" button again you will get dalog with error message saying the next: address : port is already in use.
Java.exe process keeps being in memory (in can be prooved by Task Manager). This procees has to be killed before next deployment attempts. |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Open
Critical
Glassfish server keeps loading in memory in case of failed attempt to connect
