Re: Qpid 7.0.6 not listening on HTTPS port at startup

2018-10-10 Thread 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

Re: Qpid 7.0.6 not listening on HTTPS port at startup

2018-10-10 Thread Oleksandr Rudyy 
Hi Brian,

It does not look to me that https port is declared in broker
configuration. Could you please verify that  https port declaration is
present in 
/home/boshea/blt/app/main/core/sfdc/qpid/etc/sfdc-broker-configuration.json?

I noticed that you started Broker with Qpid legacy jvm settings for
rmi and jmx ports:  -Dqpid.rmi_port=8999 -Dqpid.jmx_port=9099 .
The JMX support was disabled in 6.0 and completely removed in 6.1. You
can use REST API to manage the broker.

Kind Regards,
Alex


On Wed, 10 Oct 2018 at 01:29, Brian O'Shea  wrote:
>
> 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
>

-
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

2018-10-10 Thread Keith W 
Hello Brian

Check the log file (default location ${QPID_WORK}/log/qpid.log).
You'll probably see that the port has gone into an ERRORed state,
owing to the lack of a keystore object called "Selfsigned", which is
absent from your configuration file.  I suggest setting up the Broker
using the Console (or REST API) and comparing with the configuration
you are trying to craft by hand.

Keith.
On Wed, 10 Oct 2018 at 01:29, Brian O'Shea  wrote:
>
> 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
>

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