You're unlikely to get any support on LevelDB from this mailing list, which
is why we were forced to deprecate LevelDB. Your best path forward is to
grab the source code and a debugger and step through the code in question.
Or switch to KahaDB if you're not interested in learning the LevelDB source
code. Sorry.

Tim

On Jan 19, 2017 7:29 AM, "39db246" <abay.ge...@gmail.com> wrote:

> Hi everyone
> I faced with problem
> LevelDB implementation Slave trying to connect to the master but faced with
> some issues. Lookig like some loop
>
>
> 2017-01-19 16:33:27,246 | INFO  | Slave has disconnected:
> c09ad27f-f9ff-455a-adfd-a5d23176f59a |
> org.apache.activemq.leveldb.replicated.MasterLevelDBStore |
> hawtdispatch-DEFAULT-2
> 2017-01-19 16:33:27,831 | WARN  | Store update waiting on 1 replica(s) to
> catch up to log position 110996648517.  |
> org.apache.activemq.leveldb.replicated.MasterLevelDBStore | ActiveMQ
> BrokerService[AMQBroker] Task-1
> 2017-01-19 16:33:28,387 | INFO  | Slave has connected:
> c09ad27f-f9ff-455a-adfd-a5d23176f59a |
> org.apache.activemq.leveldb.replicated.MasterLevelDBStore |
> hawtdispatch-DEFAULT-2
> 2017-01-19 16:33:28,390 | WARN  | Unexpected session error:
> java.io.IOException: Connection reset by peer |
> org.apache.activemq.leveldb.replicated.MasterLevelDBStore |
> hawtdispatch-DEFAULT-2
>
>
>
> 2017-01-19 15:59:06,927 | INFO  | Using the pure java LevelDB
> implementation. | org.apache.activemq.leveldb.LevelDBClient |
> hawtdispatch-DEFAULT-1 2017-01-19 15:59:06,928 | INFO  | Attaching to
> master: tcp://server1:61619 |
> org.apache.activemq.leveldb.replicated.SlaveLevelDBStore |
> hawtdispatch-DEFAULT-1 2017-01-19
> 15:59:07,081 | WARN  | Unexpected session error:
> java.net.ProtocolException:
> Maximum protocol buffer length exeeded |
> org.apache.activemq.leveldb.replicated.SlaveLevelDBStore | haw
>
>
>   <broker xmlns="http://activemq.apache.org/schema/core";
> brokerName="AMQBroker" dataDirectory="${activemq.data}">
>
>         <destinationPolicy>
>             <policyMap>
>               <policyEntries>
>                 <policyEntry topic=">" >
>
>                   <pendingMessageLimitStrategy>
>                     <constantPendingMessageLimitStrategy limit="1000"/>
>                   </pendingMessageLimitStrategy>
>                 </policyEntry>
>               </policyEntries>
>             </policyMap>
>         </destinationPolicy>
>
>
>         <managementContext>
>             <managementContext createConnector="false"/>
>         </managementContext>
>
>
>         <persistenceAdapter>
>                 <replicatedLevelDB
>                         directory="${activemq.data}/hub"
>                         replicas="3"
>                         zkSessionTimeout="10s"
>                         zkAddress="server01:2181,
> server02:2181,server03:2181"
>                         hostname="server01"
>                         zkPath="/activmq"
>                         weight="15"/>
>         </persistenceAdapter>
>
>           <systemUsage>
>             <systemUsage>
>                 <memoryUsage>
>                     <memoryUsage percentOfJvmHeap="70" />
>                 </memoryUsage>
>                 <storeUsage>
>                     <storeUsage limit="200 gb"/>
>                 </storeUsage>
>                 <tempUsage>
>                     <tempUsage limit="50 gb"/>
>                 </tempUsage>
>             </systemUsage>
>         </systemUsage>
>
>
>         <transportConnectors>
>
>             <transportConnector name="openwire"
> uri="tcp://0.0.0.0:61616?maximumConnections=1000&amp;
> wireFormat.maxFrameSize=104857600"/>
>         </transportConnectors>
>
>
>         <shutdownHooks>
>             <bean xmlns="http://www.springframework.org/schema/beans";
> class="org.apache.activemq.hooks.SpringContextHook" />
>         </shutdownHooks>
>
>     </broker>
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.
> nabble.com/LevelDb-implementation-Maximum-protocol-buffer-length-
> exeeded-tp4721207.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>

Reply via email to