Uses of Class
org.apache.qpid.protonj2.engine.exceptions.EngineStateException
Package
Description
-
Uses of EngineStateException in org.apache.qpid.protonj2.engine
Modifier and TypeMethodDescriptionEngine.engineFailed
(Throwable cause) Transition theEngine
to a failed state if not already closed or closing.Modifier and TypeMethodDescriptiondefault void
Engine.accept
(ProtonBuffer input) Provide data input for this Engine from some external source.Engine.ingest
(ProtonBuffer input) Provide data input for this Engine from some external source.Connection.negotiate()
If not already negotiated this method initiates the AMQP protocol negotiation phase of the connection process sending theAMQPHeader
to the remote peer.Connection.negotiate
(EventHandler<AMQPHeader> remoteAMQPHeaderHandler) If not already negotiated this method initiates the AMQP protocol negotiation phase of the connection process sending theAMQPHeader
to the remote peer.Endpoint.open()
Open the end point locally, sending the Open performative immediately if possible or holding it until SASL negotiations or the AMQP header exchange and other required performative exchanges has completed.Engine.start()
Starts the engine and returns theConnection
instance that is bound to this Engine.long
Connection.tick
(long current) Performs a tick operation on the connection which checks that Connection Idle timeout processing is run.long
Engine.tick
(long currentTime) Prompt the engine to perform idle-timeout/heartbeat handling, and return an absolute deadline in milliseconds that tick must again be called by/at, based on the provided current time in milliseconds, to ensure the periodic work is carried out as necessary.Convenience method which is the same as callingEngine.tickAuto(Scheduler)
.Engine.tickAuto
(ScheduledExecutorService executor) Allows the engine to manage idle timeout processing by providing it the single threaded executor context where all transport work is done which ensures singled threaded access while removing the need for the client library or server application to manage calls to theEngine.tick(long)
methods.Allows the engine to manage idle timeout processing by providing it the single threaded executor context where all transport work is done which ensures singled threaded access while removing the need for the client library or server application to manage calls to theEngine.tick(long)
methods. -
Uses of EngineStateException in org.apache.qpid.protonj2.engine.exceptions
Modifier and TypeClassDescriptionfinal class
Thrown from Engine API methods that attempted an operation what would have resulted in a write of data or other state modification after the engine has entered the the failed state.final class
Thrown when a read or write operation is attempted on the engine before it has been properly started.final class
Exception indicating that the engine is not currently accepting input of datafinal class
Exception thrown when an option is performed on a closed engine.class
Thrown when an API method has been called which cannot be allowed to proceed due to the engine having already been started and doesn't allow modification to the resource in question after that point. -
Uses of EngineStateException in org.apache.qpid.protonj2.engine.impl
Modifier and TypeMethodDescriptionProtonEngine.ingest
(ProtonBuffer input) ProtonConnection.open()
ProtonSession.open()
ProtonTransactionController.open()
ProtonTransactionManager.open()
void
ProtonEngine.registerSaslDriver
(EngineSaslDriver saslDriver) Allows for registration of a customEngineSaslDriver
that will convey SASL state and configuration for this engine.ProtonEngine.start()
long
ProtonEngine.tick
(long currentTime) ProtonEngine.tickAuto
(ScheduledExecutorService executor) -
Uses of EngineStateException in org.apache.qpid.protonj2.engine.sasl
Modifier and TypeMethodDescriptionSaslServerContext.sendChallenge
(ProtonBuffer challenge) Sends the SASL challenge defined by the SASL mechanism that is in use during this SASL negotiation.default SaslClientContext
SaslClientContext.sendChosenMechanism
(String mechanism, String host, ProtonBuffer initialResponse) Sends a response to the SASL server indicating the chosen mechanism for this client and the host name that this client is identifying itself as.SaslClientContext.sendChosenMechanism
(Symbol mechanism, String host, ProtonBuffer initialResponse) Sends a response to the SASL server indicating the chosen mechanism for this client and the host name that this client is identifying itself as.default SaslServerContext
SaslServerContext.sendMechanisms
(String[] mechanisms) Sends the set of supported mechanisms to the SASL client from which it must choose and return one mechanism which will then be the basis for the SASL authentication negotiation.SaslServerContext.sendMechanisms
(Symbol[] mechanisms) Sends the set of supported mechanisms to the SASL client from which it must choose and return one mechanism which will then be the basis for the SASL authentication negotiation.SaslServerContext.sendOutcome
(SaslOutcome outcome, ProtonBuffer additional) Sends a response to a server side challenge that comprises the challenge / response exchange for the chosen SASL mechanism.SaslClientContext.sendResponse
(ProtonBuffer response) Sends a response to a server side challenge that comprises the challenge / response exchange for the chosen SASL mechanism.SaslClientContext.sendSASLHeader()
Sends the AMQP Header indicating the desire for SASL negotiations to be commenced on this connection.