| #************************************************************** | |
| # | |
| # Licensed to the Apache Software Foundation (ASF) under one | |
| # or more contributor license agreements. See the NOTICE file | |
| # distributed with this work for additional information | |
| # regarding copyright ownership. The ASF licenses this file | |
| # to you under the Apache License, Version 2.0 (the | |
| # "License"); you may not use this file except in compliance | |
| # with the License. You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, | |
| # software distributed under the License is distributed on an | |
| # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY | |
| # KIND, either express or implied. See the License for the | |
| # specific language governing permissions and limitations | |
| # under the License. | |
| # | |
| #************************************************************** | |
| Test that a Java URP bridge started in a native process uses the same thread | |
| pool as a C++ URP bridge. This test currently only works on Linux Intel. | |
| There are two processes involved. The client starts as a native process. It | |
| first loads a Java component (Relay) via the in-process JNI bridge, which in | |
| turn starts to accept incoming URP connections. The native part of the client | |
| then connects to the server, retrieves a thread-local token from it, and checks | |
| the token for correctness. The server simply waits for a connection from the | |
| native part of the client, creates a connection to the Java part of the client, | |
| and routes all requests from the native part of the client to the Java part of | |
| the client. The Java part of the client in turn uses the in-process JNI bridge | |
| to obtain the thread-local token. |