Running the Proxy Server

Contents

Steps to Run the Proxy Server
Using STREAMBASE_JVM_ARGS for sbproxy Performance
Related Topics

Note

This topic describes the behavior of the StreamBase Proxy Server before StreamBase release 7.1.3, when the Proxy Server handled both SSL and LDAP authentication. Starting with release 7.1.3, the LDAP authentication feature was moved into StreamBase Server itself. See Using LDAP Authentication.

Steps to Run the Proxy Server

The StreamBase sbproxy server runs separately from the sbd server. Use the proxy server to provide security for StreamBase client access using SSL and LDAP, as described in Using the Proxy Server.

To run a StreamBase client and server with the proxy server, follow these general steps:

  1. Start the sbd server.

  2. Start the proxy server by using the sbproxy command, as described in sbproxy.

  3. Start the client application.

Notes

  • Use the -f option to point to the sbd server configuration file where you have defined the <security> element.

  • To stop the proxy server, kill its process.

  • JVM tuning options can be supplied to the proxy server by setting the STREAMBASE_JVM_ARGS environment variable as described in the next section.

Using STREAMBASE_JVM_ARGS for sbproxy Performance

The proxy server uses any JVM parameters set with the STREAMBASE_JVM_ARGS environment variable. The default settings maximize the number of clients and throughput, at the expense of increased latency. In general, settings that you adjust to decrease latency will reduce the maximum number of clients and throughput. This section lists the parameters you can use to adjust performance while running the proxy server.

-Dcom.streambase.sb.proxy.use-acceptor-thread-pool=true

Use a thread pool for socket acceptor. Using a thread pool should increase overall throughput but will increase latency. If false, will spawn a thread for each request. Default is true.

-Dcom.streambase.sb.proxy.acceptor-processing-threads=n

Number of threads dedicated to the Socket Acceptor, if acceptor threads are enabled. Default is the number of processors on the system.

-Dcom.streambase.sb.proxy.max-threads=-1

Approximate maximum number of concurrent threads that will be spawned for each thread type (IOService and Filters). Default is no maximum.

-Dcom.streambase.sb.proxy.use-request-thread-pool=true

Use a thread pool for requests. Using this should increase overall throughput but will increase latency. Default is true.

-Dcom.streambase.sb.proxy.use-response-thread-pool=true

Use a thread pool for responses. Default is true. Use should increase overall throughput but will increase latency.

-Dcom.streambase.sb.proxy.max-buffer-size=NNN

Maximum buffer size that the proxy will hold until it stalls the client or server during reads. Default is 10 Mb.

-Dcom.streambase.sb.proxy.socket-receive-buffer-size=-1

Size of the buffer that the proxy server reads from the socket. By default, the setting is the system default.

Related Topics