Fwd: I can't build in MacOS

[Altan Özlü]

ah i’ve found it’s jdk.tracePinnedThreads not jdk.tracePinning


> İleti başlangıcı:
> 
> Kimden: Altan Özlü <sevendrofleneux at icloud.com>
> Konu: İlet: I can't build in MacOS
> Tarih: 16 Nisan 2019 22:12:48 GMT+3
> Kime: loom-dev at openjdk.java.net
> 
> I have a code which trying to connect with jdbc and it can only process 8 fiber at the time I’ve tried using  -Djdk.tracePinning=full but i didn’t get any error or something even with a synchronised block.
> 
> Connection connection = DriverManager.getConnection(mysqlUrl);
> PreparedStatement statement = connection.prepareStatement("select SLEEP(1);");
> System.out.println(connection);
> ResultSet rs = statement.executeQuery();
> if (rs.next()) {
>     System.out.println(rs.getInt(1));
> }
> 
> 
> 
>> İleti başlangıcı:
>> 
>> Kimden: Alan Bateman <Alan.Bateman at oracle.com <mailto:Alan.Bateman at oracle.com>>
>> Konu: Ynt: Fwd: I can't build in MacOS
>> Tarih: 16 Nisan 2019 18:38:18 GMT+3
>> Kime: Altan Özlü <sevendrofleneux at icloud.com <mailto:sevendrofleneux at icloud.com>>, loom-dev at openjdk.java.net <mailto:loom-dev at openjdk.java.net>
>> 
>> On 15/04/2019 22:20, Altan Özlü wrote:
>>> I get this error with building default branch too now i use java-next’s loom binaries and they work fine.
>>> I’m using Mojave btw and i have a question does normal sockets blocking scheduler ?
>> I think you are asking if blocking socket operations pin the carrier thread. At this time, the following (potentially blocking) operations are "fiber friendly" and will free up the carrier thread for other tasks when the operation doesn't complete immediately:
>> 
>> Socket: read, write, close
>> ServerSocket: accept, close
>> SocketChannel: read, write
>> ServerSocketChanne: accept
>> DatagramChannel: read, receive, write, send
>> Pipe.SourceChannel: read
>> Pipe.SinkChannel: write
>> 
>> Absent from the list is DatagramSocket.receive that we'll get to at some point. The close method of the network channels also needs a bit of work (trivial, just not done yet).
>> 
>> If you are using a library that does the socket I/O then you might run into issues with synchronization in the library. Running with -Djdk.tracePinning=full is a useful to track down many of the issues.
>> 
>> -Alan
>