/*
* DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
*
* under the terms of the GNU General Public License version 2 only, as
* published by the Free Software Foundation.
*
* This code is distributed in the hope that it will be useful, but WITHOUT
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
* version 2 for more details (a copy is included in the LICENSE file that
* accompanied this code).
*
* You should have received a copy of the GNU General Public License version
* 2 along with this work; if not, write to the Free Software Foundation,
* Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
*
* Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
* or visit www.oracle.com if you need additional information or have any
* questions.
*/
/* @test
@bug 4156625
@summary Socket.setSoTimeout(T) can cause incorrect delay of T
under green threads
@author Tom Rodriguez
*/
/*
* This program depends a bit on the particular behaviour of the green
* threads scheduler to produce the problem, but given that the underlying
* bug a green threads bug, I think that's OK.
*/
static long timeWritten;
static int port;
byte[] b = new byte[12];
t.start();
// set a 5 second timeout on the socket
s.setSoTimeout(5000);
s.close();
// this sequence should complete fairly quickly and if it
// takes something resembling the the SoTimeout value then
// we are probably incorrectly blocking and not waking up
if (waited > 2000) {
}
}
public void run() {
try {
byte[] b = new byte[12];
s.close();
} catch (Exception e) {
e.printStackTrace();
}
}
}