Yes, It is my fault. Thanks!
Kristian Waagan-4 wrote:
>
> Hi,
>
> I think this is expected behavior, because you don't close the statement.
> From [1] (* added by me):
> "Auto-commit mode means that when a statement is completed, the method
> /commit/ is called on that statement automaticall
I found that derby do not auto commit data change on my computer, even I set
auto commit to true explicitly. nothing written to database, unless I call
commit().
java version "1.6.0_19"
Java(TM) SE Runtime Environment (build 1.6.0_19-b04)
Java HotSpot(TM) Client VM (build 16.2-b04, mixed mode, sh
>Maybe there is a problem on you machine, or maybe it is a bug in Derby.
>It would be helpful if you could do what Bryan suggested - obtain the
>stack trace from the Java process when it is hanging.
>Besides from what Bryan mentioned, you can also use jstack (or visualvm)
>to do this.
jstack me
Bryan Pendleton-3 wrote:
>
> I'm not sure why the block occurred, but when you specified the IP
> address for your server to listen on, all connection requests must be
> made to that IP address.
>
Sorry, I'm busy in working these days.
I make a test at office, It blocking always. I waited for
Bryan Pendleton-3 wrote:
>
> I'm not sure why the block occurred, but when you specified the IP
> address for your server to listen on, all connection requests must be
> made to that IP address.
>
Surprising, I did a test at home, and it is very favorable. I don't know
what happened.
I will ma
Sorry, my english is poor, I try to explain that problem I reached.
I write a program using SAF, and I want to start derby server for my
purpose, then I wrote:
@Action
public void startServer() {
try {
PrintWriter pw = new PrintWriter(System.out);
InetAddress ia = InetAddress.
