[
https://issues.apache.org/jira/browse/AMQ-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14270859#comment-14270859
]
N Gorisse commented on AMQ-5509:
--------------------------------
That's fantastic, but that is a locking exception, I mean no write rights.
Let's say we have a /var/log/somewhere for which user 'user' has no read or
write rights, so it can't create a /var/log/somewhere/activemq-data folder.
That's our behavior and we do not get any exception (or log).
Thanks for your test!
> Broker quits silently when no access to activemq-data folder
> ------------------------------------------------------------
>
> Key: AMQ-5509
> URL: https://issues.apache.org/jira/browse/AMQ-5509
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 1.5
> Environment: Ubuntu 12.02
> Reporter: N Gorisse
> Priority: Trivial
> Fix For: 5.10.1
>
>
> When I startup the broker by code, there is a silent exit when the folder
> could not be accessed (by user rights). It's generally not pleasent behavior
> when something doesn't work without saying why imhu. In any case it took us
> several times an hour or two to figure out what was happening. Thanks for
> fixing!
> brokerService = new BrokerService();
> brokerService.setBrokerName(brokerName);
> brokerService.addConnector("tcp://" + host + ":" + port);
> brokerService.setSchedulerSupport(true);
> if (dataDirectory != null) {
> // In 5.10.0 this must be done before setting the
> persistence
> // adapter...
> brokerService.setDataDirectory(dataDirectory);
> }
> // Allow JMX monitoring
> brokerService.setUseJmx(true);
> ManagementContext managementContext = new ManagementContext();
> managementContext.setConnectorPort(port + 10000);
> managementContext.setRmiServerPort(port + 20000);
> brokerService.setManagementContext(managementContext);
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
