You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Tim <na...@gmail.com> on 2019/05/27 06:37:01 UTC
Artemis startup issues
Dear Team.
We are facing issues with starting of artemis after adding the below stanzas
<blockOnNonDurableSend>true</blockOnNonDurableSend>
<block-On-NonDurable-Send>true</block-On-NonDurable-Send>
<blockOnDurableSend>true</blockOnDurableSend>
<BlockOnAcknowledge>true</BlockOnAcknowledge>
<journal-sync-transactional>true</journal-sync-transactional>
<journal-sync-non-transactional>true</journal-sync-non-transactional>
We are getting the below error, kindly assist
2019-05-27 13:11:12,022 ERROR [org.apache.activemq.artemis.core.client]
AMQ214019: Invalid configuration: org.xml.sax.SAXParseException;
cvc-complex-type.2.4.a: Invalid content was found starting with element
'blockOnNonDurableSend'. One of
'{"urn:activemq:core":system-property-prefix,
"urn:activemq:core":internal-naming-prefix,
"urn:activemq:core":amqp-use-core-subscription-naming,
"urn:activemq:core":resolve-protocols, "urn:activemq:core":journal-datasync,
"urn:activemq:core":scheduled-thread-pool-max-size,
"urn:activemq:core":thread-pool-max-size,
"urn:activemq:core":graceful-shutdown-enabled,
"urn:activemq:core":graceful-shutdown-timeout,
"urn:activemq:core":security-enabled,
"urn:activemq:core":security-invalidation-interval,
"urn:activemq:core":journal-lock-acquisition-timeout,
"urn:activemq:core":wild-card-routing-enabled,
"urn:activemq:core":management-address,
"urn:activemq:core":management-notification-address,
"urn:activemq:core":cluster-user, "urn:activemq:core":cluster-password,
"urn:activemq:core":password-codec, "urn:activemq:core":mask-password,
"urn:activemq:core":log-delegate-factory-class-name,
"urn:activemq:core":jmx-management-enabled, "urn:activemq:core":jmx-domain,
"urn:activemq:core":jmx-use-broker-name,
"urn:activemq:core":message-counter-enabled,
"urn:activemq:core":message-counter-sample-period,
"urn:activemq:core":message-counter-max-day-history,
"urn:activemq:core":connection-ttl-override,
"urn:activemq:core":connection-ttl-check-interval,
"urn:activemq:core":configuration-file-refresh-period,
"urn:activemq:core":async-connection-execution-enabled,
"urn:activemq:core":transaction-timeout,
"urn:activemq:core":transaction-timeout-scan-period,
"urn:activemq:core":message-expiry-scan-period,
"urn:activemq:core":message-expiry-thread-priority,
"urn:activemq:core":id-cache-size, "urn:activemq:core":persist-id-cache,
"urn:activemq:core":remoting-incoming-interceptors,
"urn:activemq:core":remoting-outgoing-interceptors,
"urn:activemq:core":persist-delivery-count-before-delivery,
"urn:activemq:core":populate-validated-user, "urn:activemq:core":connectors,
"urn:activemq:core":acceptors, "urn:activemq:core":broadcast-groups,
"urn:activemq:core":discovery-groups, "urn:activemq:core":diverts,
"urn:activemq:core":queues, "urn:activemq:core":bridges,
"urn:activemq:core":ha-policy, "urn:activemq:core":cluster-connections,
"urn:activemq:core":grouping-handler, "urn:activemq:core":paging-directory,
"urn:activemq:core":bindings-directory,
"urn:activemq:core":create-bindings-dir,
"urn:activemq:core":page-max-concurrent-io,
"urn:activemq:core":journal-directory,
"urn:activemq:core":create-journal-dir, "urn:activemq:core":journal-type,
"urn:activemq:core":journal-buffer-timeout,
"urn:activemq:core":journal-buffer-size,
"urn:activemq:core":journal-sync-transactional,
"urn:activemq:core":journal-sync-non-transactional,
"urn:activemq:core":log-journal-write-rate,
"urn:activemq:core":journal-file-size,
"urn:activemq:core":journal-min-files,
"urn:activemq:core":journal-pool-files,
"urn:activemq:core":journal-compact-percentage,
"urn:activemq:core":journal-compact-min-files,
"urn:activemq:core":journal-max-io,
"urn:activemq:core":journal-file-open-timeout,
"urn:activemq:core":server-dump-interval,
"urn:activemq:core":global-max-size, "urn:activemq:core":max-disk-usage,
"urn:activemq:core":disk-scan-period,
"urn:activemq:core":memory-warning-threshold,
"urn:activemq:core":memory-measure-interval,
"urn:activemq:core":large-messages-directory, "urn:activemq:core":store,
"urn:activemq:core":critical-analyzer,
"urn:activemq:core":critical-analyzer-timeout,
"urn:activemq:core":critical-analyzer-check-period,
"urn:activemq:core":critical-analyzer-policy,
"urn:activemq:core":security-settings, "urn:activemq:core":broker-plugins,
"urn:activemq:core":address-settings,
"urn:activemq:core":resource-limit-settings,
"urn:activemq:core":connector-services, "urn:activemq:core":addresses,
"urn:activemq:core":network-check-list,
"urn:activemq:core":network-check-URL-list,
"urn:activemq:core":network-check-period,
"urn:activemq:core":network-check-timeout,
"urn:activemq:core":network-check-NIC,
"urn:activemq:core":network-check-ping-command,
"urn:activemq:core":network-check-ping6-command,
"urn:activemq:core":wildcard-addresses}' is expected.
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
[rt.jar:1.8.0_161]
at
com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
[rt.jar:1.8.0_161]
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
[rt.jar:1.8.0_161]
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
[rt.jar:1.8.0_161]
at
com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
[rt.jar:1.8.0_161]
at
com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:453)
[rt.jar:1
Thanks
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis startup issues
Posted by Justin Bertram <jb...@apache.org>.
Whether you're using shared-store or replication durable messages should
already be persisted in such a way as to eliminate the possibility of loss.
If you're seeing message loss during fail-over either your expectation of
high availability is illegitimate (e.g. you expect non-durable messages to
be highly available) or there is a bug. In either case, a test case which
reproduces the problem you're seeing or at the very least a full
explanation of your use-case and the steps leading up to the "loss" is in
order here. Can you provide these details?
Justin
On Mon, May 27, 2019 at 12:39 PM GedupuriRamesh <ra...@gmail.com>
wrote:
> Dear Justin,
>
> We have live-backup mechanism... we see some message loss during fail-over
> from live to backup server. so we want to setup this parameters and see if
> the message loss still present.
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>
Re: Artemis startup issues
Posted by GedupuriRamesh <ra...@gmail.com>.
Dear Justin,
We have live-backup mechanism... we see some message loss during fail-over
from live to backup server. so we want to setup this parameters and see if
the message loss still present.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Re: Artemis startup issues
Posted by Justin Bertram <jb...@apache.org>.
The error message is pretty clear, in my opinion. It's saying that
"blockOnNonDurableSend" is not a valid name for an XML configuration
element, and that you should use one of the names listed. That's all
correct. In fact, "block-On-NonDurable-Send," "blockOnDurableSend," and
"BlockOnAcknowledge" are all invalid for XML config. These setting are
client-side only and are set via the core client API or via the connection
URL, e.g.:
tcp://host:61616?blockOnNonDurableSend=true;blockOnDurableSend=true;blockOnAcknowledge=true
The default values work in most cases. Is there a specific reason why you
want to change these?
Justin
On Mon, May 27, 2019 at 1:37 AM Tim <na...@gmail.com> wrote:
> Dear Team.
>
> We are facing issues with starting of artemis after adding the below
> stanzas
>
> <blockOnNonDurableSend>true</blockOnNonDurableSend>
> <block-On-NonDurable-Send>true</block-On-NonDurable-Send>
>
> <blockOnDurableSend>true</blockOnDurableSend>
>
> <BlockOnAcknowledge>true</BlockOnAcknowledge>
> <journal-sync-transactional>true</journal-sync-transactional>
> <journal-sync-non-transactional>true</journal-sync-non-transactional>
>
> We are getting the below error, kindly assist
>
> 2019-05-27 13:11:12,022 ERROR [org.apache.activemq.artemis.core.client]
> AMQ214019: Invalid configuration: org.xml.sax.SAXParseException;
> cvc-complex-type.2.4.a: Invalid content was found starting with element
> 'blockOnNonDurableSend'. One of
> '{"urn:activemq:core":system-property-prefix,
> "urn:activemq:core":internal-naming-prefix,
> "urn:activemq:core":amqp-use-core-subscription-naming,
> "urn:activemq:core":resolve-protocols,
> "urn:activemq:core":journal-datasync,
> "urn:activemq:core":scheduled-thread-pool-max-size,
> "urn:activemq:core":thread-pool-max-size,
> "urn:activemq:core":graceful-shutdown-enabled,
> "urn:activemq:core":graceful-shutdown-timeout,
> "urn:activemq:core":security-enabled,
> "urn:activemq:core":security-invalidation-interval,
> "urn:activemq:core":journal-lock-acquisition-timeout,
> "urn:activemq:core":wild-card-routing-enabled,
> "urn:activemq:core":management-address,
> "urn:activemq:core":management-notification-address,
> "urn:activemq:core":cluster-user, "urn:activemq:core":cluster-password,
> "urn:activemq:core":password-codec, "urn:activemq:core":mask-password,
> "urn:activemq:core":log-delegate-factory-class-name,
> "urn:activemq:core":jmx-management-enabled, "urn:activemq:core":jmx-domain,
> "urn:activemq:core":jmx-use-broker-name,
> "urn:activemq:core":message-counter-enabled,
> "urn:activemq:core":message-counter-sample-period,
> "urn:activemq:core":message-counter-max-day-history,
> "urn:activemq:core":connection-ttl-override,
> "urn:activemq:core":connection-ttl-check-interval,
> "urn:activemq:core":configuration-file-refresh-period,
> "urn:activemq:core":async-connection-execution-enabled,
> "urn:activemq:core":transaction-timeout,
> "urn:activemq:core":transaction-timeout-scan-period,
> "urn:activemq:core":message-expiry-scan-period,
> "urn:activemq:core":message-expiry-thread-priority,
> "urn:activemq:core":id-cache-size, "urn:activemq:core":persist-id-cache,
> "urn:activemq:core":remoting-incoming-interceptors,
> "urn:activemq:core":remoting-outgoing-interceptors,
> "urn:activemq:core":persist-delivery-count-before-delivery,
> "urn:activemq:core":populate-validated-user,
> "urn:activemq:core":connectors,
> "urn:activemq:core":acceptors, "urn:activemq:core":broadcast-groups,
> "urn:activemq:core":discovery-groups, "urn:activemq:core":diverts,
> "urn:activemq:core":queues, "urn:activemq:core":bridges,
> "urn:activemq:core":ha-policy, "urn:activemq:core":cluster-connections,
> "urn:activemq:core":grouping-handler, "urn:activemq:core":paging-directory,
> "urn:activemq:core":bindings-directory,
> "urn:activemq:core":create-bindings-dir,
> "urn:activemq:core":page-max-concurrent-io,
> "urn:activemq:core":journal-directory,
> "urn:activemq:core":create-journal-dir, "urn:activemq:core":journal-type,
> "urn:activemq:core":journal-buffer-timeout,
> "urn:activemq:core":journal-buffer-size,
> "urn:activemq:core":journal-sync-transactional,
> "urn:activemq:core":journal-sync-non-transactional,
> "urn:activemq:core":log-journal-write-rate,
> "urn:activemq:core":journal-file-size,
> "urn:activemq:core":journal-min-files,
> "urn:activemq:core":journal-pool-files,
> "urn:activemq:core":journal-compact-percentage,
> "urn:activemq:core":journal-compact-min-files,
> "urn:activemq:core":journal-max-io,
> "urn:activemq:core":journal-file-open-timeout,
> "urn:activemq:core":server-dump-interval,
> "urn:activemq:core":global-max-size, "urn:activemq:core":max-disk-usage,
> "urn:activemq:core":disk-scan-period,
> "urn:activemq:core":memory-warning-threshold,
> "urn:activemq:core":memory-measure-interval,
> "urn:activemq:core":large-messages-directory, "urn:activemq:core":store,
> "urn:activemq:core":critical-analyzer,
> "urn:activemq:core":critical-analyzer-timeout,
> "urn:activemq:core":critical-analyzer-check-period,
> "urn:activemq:core":critical-analyzer-policy,
> "urn:activemq:core":security-settings, "urn:activemq:core":broker-plugins,
> "urn:activemq:core":address-settings,
> "urn:activemq:core":resource-limit-settings,
> "urn:activemq:core":connector-services, "urn:activemq:core":addresses,
> "urn:activemq:core":network-check-list,
> "urn:activemq:core":network-check-URL-list,
> "urn:activemq:core":network-check-period,
> "urn:activemq:core":network-check-timeout,
> "urn:activemq:core":network-check-NIC,
> "urn:activemq:core":network-check-ping-command,
> "urn:activemq:core":network-check-ping6-command,
> "urn:activemq:core":wildcard-addresses}' is expected.
> at
>
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:203)
> [rt.jar:1.8.0_161]
> at
>
> com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:134)
> [rt.jar:1.8.0_161]
> at
>
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:396)
> [rt.jar:1.8.0_161]
> at
>
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
> [rt.jar:1.8.0_161]
> at
>
> com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:284)
> [rt.jar:1.8.0_161]
> at
>
> com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(XMLSchemaValidator.java:453)
> [rt.jar:1
>
> Thanks
>
>
>
>
> --
> Sent from:
> http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
>