Re: Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

[Brian O'Shea]

Looking at jconsole (connected to the running Qpid broker), it appears that
it exposes a Map under java.lang -> Runtime -> Attributes ->
SystemProperties.  Is this something that I can depend on always being
available?  This is Qpid version 7.0.6, which no longer supports management
over JMX, but will this attribute always be accessible over JMX?

Thanks,
Brian O'Shea
Salesforce



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

[Brian O'Shea]

Hello Qpid maintainers,

My organization uses Qpid, and we occasionally deploy configuration changes
that we track using a build number that we generate internally.  We would
like to find a way to expose this build number so that our application can
access it to see what "build" the Qpid broker is (this is not the Qpid
version number, and only has meaning to our organization).  Ideally we would
access it via the REST API, but I realize that this might not be feasible. 
Can you think of a way that I can store this build number in the broker
somehow that can be accessed remotely?

Thanks.  Let me know if you need clarification.

Brian O'Shea
Salesforce




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

High memory utilization with Java version of Qpid 7.0.6

[Brian O'Shea]

Hello Qpid Community,

I am seeing some strange memory utilization patterns when running the Java
implementation of Qpid, version 7.0.6 on Linux (Ubuntu 16.04).  I ran some
tests for the application that I am working on that uses Qpid, which
enqueues about 50 messages.  I see this very high memory usage by Qpid while
running these tests (see attached image).

My Qpid memory properties are set to the following:

# Java heap settings
qpid.java.min.memory = 3072m
qpid.java.max.memory = 3072m

qpid.java.direct.memory  = 9216m
qpid.flow_to_disk_threshold = 6606029

Several of our tests fail, but if I re-run them all, different ones will
pass and fail, so I suspect it is related to when the memory utilization is
high.  In production, we enqueue many more messages (millions per day), so I
am concerned that with this version of Qpid and/or with this combination of
memory settings, it may not scale.  Can you help me compute the optimal
memory settings for this application?  Let me know if you need to know
anything else about the way that we will be using Qpid.

Thanks,
Brian




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Qpid 7.0.6 not listening on HTTPS port at startup

[Brian O'Shea]

Thanks Keith and Alex,

That was the problem.  I have added the keystores section to the config, and
now it starts up, listening on the HTTPS port.

I also removed the old JMX properties to avoid confusion, although I don't
think those were causing problems (they were probably just ignored)).  I am
now doing some memory utilization and performance testing, and will post
another thread with my findings.  I am seeing some unusual behavior, but I
might not have the right ratio of direct memory to heap memory, and might
not have set the flow-to-disk threshold correctly.

Thanks for your help.

Regards,
Brian



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Qpid 7.0.6 not listening on HTTPS port at startup

[Brian O'Shea]

Hello Qpid Community,

I am trying to configure the Java Qpid broker (version 7.0.6) on Linux
(Ubuntu 16.04) using OpenJDK 1.8.0 u162.  When I start the broker, it is not
listening on the HTTPS port that I specified in the JSON configuration file. 
It is listening on the HTTP and AMPQ ports that I have configured.  I've
attached our JSON configuration file for reference.


/home/boshea/blt/tools/Linux/jdk/openjdk1.8.0_162_x64/bin/java -server
-Xms500m -Xmx1024m -XX:MaxDirectMemorySize=250m -XX:+UseParallelOldGC
-XX:+HeapDumpOnOutOfMemoryError -verbose:gc -XX:+PrintGCDetails
-XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps
-XX:+PrintGCApplicationConcurrentTime -XX:+PrintGCApplicationStoppedTime
-XX:-TraceClassUnloading
-Xloggc:/home/boshea/blt/app/main/core/sfdc/qpid/logs/jvmgc.log
-DPNAME=QPBRKR -DQPID_HOME=/home/boshea/blt/tools/qpid/v7.0.6
-DQPID_WORK=/home/boshea/blt/app/main/core/sfdc/qpid
-Dqpid.logfile.name=/home/boshea/blt/app/main/core/sfdc/qpid/logs/main.sfdc.localhost.qpid.broker.gmt.log
-Dqpid.logging.level=WARN -Djava.rmi.server.hostname=127.0.0.1
-Dqpid.flow_to_disk_threshold=209715200 -Dqpid.amqp_port=5672
-Dqpid.http_port=5673 -Dqpid.https_port=5675 -Dqpid.rmi_port=8999
-Dqpid.jmx_port=9099 -Dqpid.virtualhost_name=test
-Dqpid.virtualhost_type=BDB -classpath
/home/boshea/blt/app/main/core/build/ManifestJars/manifest-classpath_MAIN.qpid-start-java-java_4876430406122862138.jar
org.apache.qpid.server.Main -sp
/home/boshea/blt/app/main/core/sfdc/qpid/etc/sfdc-broker-configuration.json
[Broker] BRK-1006 : Using configuration :
/home/boshea/blt/app/main/core/sfdc/qpid/etc/sfdc-broker-configuration.json
[Broker] BRK-1001 : Startup : Version: 7.0.6 Build:
bda3e6d2254b1634256cf4e0d4eff4da549d3ed8
[Broker] BRK-1010 : Platform : JVM : Azul Systems, Inc. version:
1.8.0_162-b01 OS : Linux version: 4.4.0-137-generic arch: amd64 cores: 16
[Broker] BRK-1011 : Maximum Memory : Heap : 954,728,448 bytes Direct :
262,144,000 bytes
[Broker] BRK-1017 : Process : PID : 31324
[Broker] BRK-1002 : Starting : Listening on TCP port 5672
[Broker] MNG-1001 : Web Management Startup
[Broker] MNG-1002 : Starting : HTTP : Listening on TCP port 5673
[Broker] MNG-1004 : Web Management Ready
[Broker] BRK-1004 : Qpid Broker Ready


sfdc-broker-configuration.json
 
 



--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Converting Qpid Broker configuration from older versions to new

[Brian O'Shea]

Hello,

I am in the process of upgrading the Qpid Broker version that my
organization is using from 0.32 to 7.0.6.  I know this is quite a big jump. 
A former employee already did some of the work to upgrade to 6.0.5, but we
never finished the upgrade before he left, and now we want to upgrade to
7.0.6.  I mention this because we don't have adequate testing around the
configuration for 6.0.5, so the most well-known, stable configuration that
we have is for 0.32.

Do you provide tools for converting the JSON configuration from older
versions to newer versions?

Thanks,
Brian O'Shea




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: Building Qpid broker 7.0.6 Java version with OpenJDK 1.8.0_162_x64 fails in BDB Link Store Plug-in tests

[Brian O'Shea]

Thank you for your responses, Rob and Alex.
We are using the Zulu OpenJDK from Azul:
https://www.azul.com/products/zulu-enterprise/
This is the JVM that I am using:
$ ./java -showversionopenjdk version "1.8.0_172"OpenJDK Runtime Environment
(Zulu 8.30.0.2-linux64) (build 1.8.0_172-b01)OpenJDK 64-Bit Server VM (Zulu
8.30.0.2-linux64) (build 25.172-b01, mixed mode)




--
Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

Building Qpid broker 7.0.6 Java version with OpenJDK 1.8.0_162_x64 fails in BDB Link Store Plug-in tests

[Brian O'Shea]

Hello Qpid developers,

I am trying to build the Qpid broker version 7.0.6 Java version, and it is
failing the BDB Link Store Plug-in tests.  I am building on an Intel 64-bit
system running Ubuntu Linux 16.04 with OpenJDK 1.8.0_162_x64.  I have
searched for the errors that I am seeing but can't find anything.  We are
transitioning to OpenJDK and so I would like to be able to use it to build
and run the Qpid broker.  Can you provide any advice on how to build this
successfully?

Thank you and regards,
Brian O'Shea

When I build with the Oracle JDK of the same version it builds successfully
and all tests pass.  Here is the error that I am getting:

Running org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTestTests
run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0.625 sec <<<
FAILURE! - in
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTesttestOpenAndLoad(org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest)
 
Time elapsed: 0.331 sec  <<< ERROR!java.lang.IllegalStateException: Could
not access Zing management bean. Make sure -XX:+UseZingMXBeans was
specified.  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Caused
by: java.lang.ClassNotFoundException:
com.azul.zing.management.ManagementFactory  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)testSaveLink(org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest)
 
Time elapsed: 0.006 sec  <<< ERROR!java.lang.IllegalStateException: Could
not access Zing management bean. Make sure -XX:+UseZingMXBeans was
specified.  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Caused
by: java.lang.ClassNotFoundException:
com.azul.zing.management.ManagementFactory  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)testClose(org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest)
 
Time elapsed: 0.004 sec  <<< ERROR!java.lang.IllegalStateException: Could
not access Zing management bean. Make sure -XX:+UseZingMXBeans was
specified.  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Caused
by: java.lang.ClassNotFoundException:
com.azul.zing.management.ManagementFactory  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)testDeleteLink(org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest)
 
Time elapsed: 0.01 sec  <<< ERROR!java.lang.IllegalStateException: Could not
access Zing management bean. Make sure -XX:+UseZingMXBeans was specified.   
at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Caused
by: java.lang.ClassNotFoundException:
com.azul.zing.management.ManagementFactory  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)testDelete(org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest)
 
Time elapsed: 0.007 sec  <<< ERROR!java.lang.IllegalStateException: Could
not access Zing management bean. Make sure -XX:+UseZingMXBeans was
specified.  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Caused
by: java.lang.ClassNotFoundException:
com.azul.zing.management.ManagementFactory  at
org.apache.qpid.server.protocol.v1_0.store.bdb.BDBLinkStoreTest.createLinkStore(BDBLinkStoreTest.java:68)Results
:Tests in error:  
BDBLinkStoreTest>QpidTestCase.run:165->LinkStoreTestCase.setUp:55->createLinkStore:68
» IllegalState 
BDBLinkStoreTest>QpidTestCase.run:165->LinkStoreTestCase.setUp:55->createLinkStore:68
» IllegalState 
BDBLinkStoreTest>QpidTestCase.run:165->LinkStoreTestCase.setUp:55->createLinkStore:68
» IllegalState 
BDBLinkStoreTest>QpidTestCase.run:165->LinkStoreTestCase.setUp:55->createLinkStore:68
» IllegalState 
BDBLinkStoreTest>QpidTestCase.run:165->LinkStoreTestCase.setUp:55->createLinkStore:68
» IllegalStateTests run: 5, Failures: 0, Errors: 5, Skipped: 0[INFO]
[INFO]
Reactor Summary:[INFO] [INFO] Apache Qpid Broker-J Parent
 SUCCESS [  1.945 s][INFO] Apache Qpid Broker-J Code
Generation ... SUCCESS [  1.593 s][INFO] Apache Qpid Broker-J
Test Utilities  SUCCESS [  0.270 s][INFO] Apache Qpid
Broker-J Core .. SUCCESS [ 51.180 s][INFO] Apache
Qpid Broker-J LogBack Logging Plug-in ... SUCCESS [  4.200 s][INFO]
Apache Qpid Broker-J Access Control Plug-in  SUCCESS [  3.223
s][INFO] Apache Qpid Broker-J AMQP 0-10 Protocol Plug-in  SUCCESS [ 
4.107 s][INFO] Apache Qpid Broker-J AM