search

laurent-simon / storage-at-desk

Automatically exported from code.google.com/p/storage-at-desk
0 stars 0 forks source link

Error On Reconnect #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Start up services
2. Connect with iSCSI initiator 
3. Try to format drive, requests fail
4. Try to reconnect

What is the expected output? What do you see instead?

The connection is accepted but the new TargetThread is never executed by
the ExecutorService threadPool

Perhaps there is a problem with threadPool or blocking withing
TargetThread's run() method.

Original issue reported on code.google.com by tommy.mu...@gmail.com on 29 Mar 2009 at 7:30

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
86639 15:34:17,800 [pool-1-thread-1] DEBUG storageserver.TargetThread  - Disk 
data
array number is 1, length is 65536
86639 15:34:17,800 [pool-1-thread-1] DEBUG storageserver.TargetThread  - data 
length
262144 response len 65584
86640 15:34:17,801 [pool-1-thread-1] DEBUG storageserver.TargetThread  - after
padding response len 65584
86640 15:34:17,801 [pool-1-thread-1] DEBUG storageserver.TargetThread  - 
Sending READ
DATA RESPONSE: [B@1c56c60
java.io.IOException: Connection reset by peer
    at sun.nio.ch.FileDispatcher.write0(Native Method)
    at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:29)
    at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:104)
    at sun.nio.ch.IOUtil.write(IOUtil.java:75)
    at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:334)
    at
edu.virginia.cs.storagedesk.storageserver.TargetThread.executeSCSICommand(Target
Thread.java:784)
    at edu.virginia.cs.storagedesk.storageserver.TargetThread.execute(TargetThread.java:191)
    at edu.virginia.cs.storagedesk.storageserver.TargetThread.run(TargetThread.java:124)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:619)
86757 15:34:17,918 [main      ] INFO  storageserver.TargetThread  - Connection
accepted on port 3260(local IP /172.27.43.236:3260, remote IP 
/172.27.43.48:1535)
Executer running: false
86759 15:34:17,920 [pool-1-thread-1] DEBUG storageserver.TargetThread  - Target
thread runs

Original comment by tommy.mu...@gmail.com on 29 Mar 2009 at 8:19

GoogleCodeExporter commented 8 years ago 
My mistake:

"Executor running: false" should actually read "Executor shutdown: false"

This means that the executor is still accepting threads, but I believe that it 
may
not be starting them properly still.

Original comment by tommy.mu...@gmail.com on 29 Mar 2009 at 8:30

GoogleCodeExporter commented 8 years ago 
This only happens on "connection reset by peer" error.

Original comment by tommy.mu...@gmail.com on 29 Mar 2009 at 8:31

GoogleCodeExporter commented 8 years ago 
Have not been able to reproduce in a while.  This was originally when 
everything was 
on Ubuntu virtual machine on OSX and being connected to from Alex's XP machine. 

Possible causes:

threading deadlocks in StorageServer
version of iSCSI Initiator
disk formatting software (3rd party was originally used, not the one built in 
to xp)

Original comment by tommy.mu...@gmail.com on 23 Apr 2009 at 8:53