You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Black & White (JIRA)" <ji...@apache.org> on 2016/01/12 11:42:39 UTC

[jira] [Comment Edited] (DERBY-6853) Shutdown Derby Network Server after local ip change

    [ https://issues.apache.org/jira/browse/DERBY-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093695#comment-15093695 ] 

Black & White edited comment on DERBY-6853 at 1/12/16 10:42 AM:
----------------------------------------------------------------

[~rhillegas]
1) Network Adapter is standart Ethernet Adapter "Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller"
2) I go to Network Connections, enter Properties of my network adapter and change TCP/IPv4 IP address.

[~bpendleton]
1) Right. If i reverse my ip to old value, i can shutdown the Derby without any problem. I have already doing this for shutdown. Problem is if standart user change the ip of the system while Derby Network Server Up, i can't kill old Network Server programaticly.

Also if i start the server with;
{code}java -jar derbyrun.jar server start -h 0.0.0.0{code}

I can shutdown the derby with below command (system ip change or not)
{code}java -jar derbyrun.jar server shutdown -h localhost{code}

But this start method listen connections from all network adapter. I am not thinking use this method for security reasons. I should give exact network adapter for listen the connections.




was (Author: lacrymae):
[~rhillegas]
1) Network Adapter is standart Ethernet Adapter "Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller"
2) I go to Network Connections, enter Properties of my network adapter and change TCP/IPv4 IP address.

[~bpendleton]
1) Right. If i reverse my ip to old value, i can shutdown the Derby without any problem. I have already doing this for shutdown. Problem is if standart user change the ip of the system while Derby Network Server Up, i can't kill old Network Server programaticly.






> 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)