[
https://issues.apache.org/jira/browse/DERBY-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093089#comment-15093089
]
Bryan Pendleton commented on DERBY-6853:
----------------------------------------
Two possibilities:
1) Change your IP address back to its previous value, then perform the normal
Network Server shutdown command
2) Leave your IP address alone, and use an operating system command, such as
'kill' (on Linux/Mac) or Task Manager 'Stop Process' (on Windows) to terminate
the java process that is running the Derby Network Server.
> Shutdown Derby Network Server after local ip change
> ---------------------------------------------------
>
> Key: DERBY-6853
> URL: https://issues.apache.org/jira/browse/DERBY-6853
> Project: Derby
> Issue Type: Bug
> Components: Network Server
> Affects Versions: 10.12.1.1
> Environment: Microsoft Windows 7
> Reporter: Black & White
> Priority: Blocker
>
> I have some problem shutdown the Derby Engine.
> h4. Server Start;
> {code}
> java -jar derbyrun.jar server start -h 10.90.232.20
> {code}
> I have started Derby Network Server wiht above cmd command. And I have stop
> the Network Server with below command.
> h4. Server Stop;
> {code}
> java -jar derbyrun.jar server shutdown -h 10.90.232.20
> {code}
> But if i change ip of current network adapter manually +while server up+, i
> don't kill the current listening network server. Because Network Server
> started on different ip before.
> h4. Also i have tried;
> {code}
> java -jar derbyrun.jar server shutdown -h 0.0.0.0
> java -jar derbyrun.jar server shutdown -h localhost
> {code}
> But did not help. I can't reach old started Network Server. So it stuck and
> JVM don't allow start new Derby Network Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
