I've never run ActiveMQ with the JDBC persistence store, so I can't answer
that question directly, and I don't get the sense that most of the people
on this mailing list have either, so you may not be able to answer that
question other than by trying it. With that being said, I wouldn't expect
it to be that large of a hit.
Tim
On Wed, Mar 9, 2016 at 5:10 PM, alt_alt <alt_...@163.com> wrote:
> Hi Tim,
> Really appreciated for your reply, here is the datasource configuration,
> just the same as the one shown in ActiveMQ webpage.
>
> <bean id="mysql-ds" class="org.apache.commons.dbcp.BasicDataSource"
> destroy-method="close">
> <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
> <property name="url"
> value="jdbc:mysql://
> eanprdactivemq01writer01.eao.abn-iad.ea.com:3306/activemq?relaxAutoCommit=true
> "/>
> <property name="username" value="ACTIVEMQSERVER"/>
> <property name="password" value="${jdbc.password}"/>
> <property name="poolPreparedStatements" value="true"/>
> </bean>
>
> What's the performance impact if I set poolPreparedStatements to false?
>
> Best Regards
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Failed-network-connector-can-not-be-re-established-tp4709054p4709136.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
