diff options
| author | Keith Wall <kwall@apache.org> | 2011-10-16 17:46:18 +0000 |
|---|---|---|
| committer | Keith Wall <kwall@apache.org> | 2011-10-16 17:46:18 +0000 |
| commit | f0be669bb60a6a089894f24e33c858eaae9a2c59 (patch) | |
| tree | eeaefd43d4eada96db0b28875bba0c3b0576fb72 /qpid/doc/book/src/Qpid-Java-FAQ.xml | |
| parent | 1b467a05de64157ebf031c3128b49c234366851e (diff) | |
| download | qpid-python-f0be669bb60a6a089894f24e33c858eaae9a2c59.tar.gz | |
QPID-3516: Docbook recent changes to Java client system properties
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk@1184883 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid/doc/book/src/Qpid-Java-FAQ.xml')
| -rw-r--r-- | qpid/doc/book/src/Qpid-Java-FAQ.xml | 54 |
1 files changed, 0 insertions, 54 deletions
diff --git a/qpid/doc/book/src/Qpid-Java-FAQ.xml b/qpid/doc/book/src/Qpid-Java-FAQ.xml index 7a28703774..2144d3a533 100644 --- a/qpid/doc/book/src/Qpid-Java-FAQ.xml +++ b/qpid/doc/book/src/Qpid-Java-FAQ.xml @@ -736,35 +736,6 @@ amqj.logging.level </para> <!--h3--></section> - <section role="h3" id="QpidJavaFAQ-HowdoIuseanInVMBrokerformyowntests-3F"><title> - How do I - use an InVM Broker for my own tests? - </title> - - <para> - I would take a look at the testPassiveTTL in - <ulink url="https://svn.apache.org/repos/asf/qpid/trunk/qpid/java/systests/src/main/java/org/apache/qpid/server/queue/TimeToLiveTest.java">TimeToLiveTest.java</ulink> - </para><para> - The setUp and tearDown methods show how to correctly start up a - broker for InVM testing. If you write your tests using a file for - the JNDI you can then very easily swap between running your tests - InVM and against a real broker. - </para><para> - See our <xref linkend="How-to-Use-JNDI"/> on how to confgure it - </para><para> - Basically though you just need to set two System Properites: - </para><para> - java.naming.factory.initial = - org.apache.qpid.jndi.PropertiesFileInitialContextFactory - java.naming.provider.url = <your JNDI file> - </para><para> - and call getInitialContext() in your code. - </para><para> - You will of course need to have the broker libraries on your - class path for this to run. - </para> -<!--h3--></section> - <section role="h3" id="QpidJavaFAQ-HowcanIinspectthecontentsofmyMessageStore-3F"><title> How can I inspect the contents of my MessageStore? @@ -907,31 +878,6 @@ java.lang.NullPointerException </para> <!--h3--></section> - <section role="h3" id="QpidJavaFAQ-Clientkeepsthrowing-27Serverdidnotrespondinatimelyfashion-27-5Cerrorcode408-3ARequestTimeout-5C."><title> - Client keeps throwing 'Server did not respond in a timely - fashion' [error code 408: Request Timeout]. - </title> - - <para> - Certain operations wait for a response from the Server. One such - operations is commit. If the server does not respond to the - commit request within a set time a Request Timeout [error code: - 408] exception is thrown (Server did not respond in a timely - fashion). This is to ensure that a server that has hung does not - cause the client process to be come unresponsive. - </para><para> - However, it is possible that the server just needs a long time to - process a give request. For example, sending a large persistent - message when using a persistent store will take some time to a) - Transfer accross the network and b) to be fully written to disk. - </para><para> - These situations require that the default timeout value be - increased. A cilent <xref linkend="qpid_System-Properties"/> 'amqj.default_syncwrite_timeout' can be set - on the client to increase the wait time. The default in 0.5 is - 30000 (30s). - </para> -<!--h3--></section> - <section role="h3" id="QpidJavaFAQ-CanauseTCPKEEPALIVEorAMQPheartbeatingtokeepmyconnectionopen-3F"><title> Can a use TCP_KEEPALIVE or AMQP heartbeating to keep my connection open? |
