[
https://issues.apache.org/jira/browse/DERBY-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095556#comment-15095556
]
Rick Hillegas commented on DERBY-6853:
--------------------------------------
It sounds as though you are asking for a new Network Server api. Can you
provide an example of how you would like this api to behave? Are there other
products which you can suggest as models for how should Derby should respond to
an ip change?
Thanks,
-Rick
> 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)
