You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Niclas Hedhman <ni...@hedhman.org> on 2022/06/15 16:18:38 UTC

Major problem

Hi,
(perhaps this is a dev@ issue more than a users@ issue)

I have had a Pulsar system running for ~5 months and have had no 
problems.

Today I updated my application that uses Pulsar, and everything stopped 
working. I naturally assumed that the problem was in my application. And 
after a lot of debugging I realized that it was Pulsar not delivering 
messages.

"Maybe ran out of memory, let's restart. Oh well, why not upgrade to new 
version at the same time."

And that failed, I got this "IllegalAccessError" and I thought, that the 
new version 2.10.0 required something special/new that I have not 
investigated, so go back to 2.9.1 and I still had the exception (see 
below). And I now think that this was the problem all the while...but 
how? No idea.

Any pointers to what can cause this in 2.9.1 and/or 2.10.0 is most 
welcome.

BTW, running Java 11 on Debian 11.

Thanks
Niclas


java.lang.IllegalAccessError: Update to non-static final field 
org.apache.pulsar.policies.data.loadbalancer.ResourceUsage.usage 
attempted from a different class 
(org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared) than the 
field's declaring class
         at 
org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared.getSystemResourceUsage(LoadManagerShared.java:220) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.updateLocalBrokerData(ModularLoadManagerImpl.java:915) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.start(ModularLoadManagerImpl.java:876) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerWrapper.start(ModularLoadManagerWrapper.java:102) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.broker.PulsarService.startLoadManagementService(PulsarService.java:1022) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.broker.PulsarService.start(PulsarService.java:737) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.PulsarBrokerStarter$BrokerStarter.start(PulsarBrokerStarter.java:273) 
~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
         at 
org.apache.pulsar.PulsarBrokerStarter.main(PulsarBrokerStarter.java:350) 
[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]

Re: Major problem

Posted by Niclas Hedhman <ni...@hedhman.org>.
On 2022-06-15 20:03, Matteo Merli wrote:
> Hi Niclas,
> 
> can you provide the output of
> 
> `pulsar-admin topics stats $TOPIC`

Answer on users@ brought me back to a stable situation and issue is 
resolved.

Thanks
Niclas

Re: Major problem

Posted by Matteo Merli <ma...@gmail.com>.
Hi Niclas,

can you provide the output of

`pulsar-admin topics stats $TOPIC`


--
Matteo Merli
<ma...@gmail.com>

On Wed, Jun 15, 2022 at 9:18 AM Niclas Hedhman <ni...@hedhman.org> wrote:
>
> Hi,
> (perhaps this is a dev@ issue more than a users@ issue)
>
> I have had a Pulsar system running for ~5 months and have had no
> problems.
>
> Today I updated my application that uses Pulsar, and everything stopped
> working. I naturally assumed that the problem was in my application. And
> after a lot of debugging I realized that it was Pulsar not delivering
> messages.
>
> "Maybe ran out of memory, let's restart. Oh well, why not upgrade to new
> version at the same time."
>
> And that failed, I got this "IllegalAccessError" and I thought, that the
> new version 2.10.0 required something special/new that I have not
> investigated, so go back to 2.9.1 and I still had the exception (see
> below). And I now think that this was the problem all the while...but
> how? No idea.
>
> Any pointers to what can cause this in 2.9.1 and/or 2.10.0 is most
> welcome.
>
> BTW, running Java 11 on Debian 11.
>
> Thanks
> Niclas
>
>
> java.lang.IllegalAccessError: Update to non-static final field
> org.apache.pulsar.policies.data.loadbalancer.ResourceUsage.usage
> attempted from a different class
> (org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared) than the
> field's declaring class
>          at
> org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared.getSystemResourceUsage(LoadManagerShared.java:220)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.updateLocalBrokerData(ModularLoadManagerImpl.java:915)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.start(ModularLoadManagerImpl.java:876)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerWrapper.start(ModularLoadManagerWrapper.java:102)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.broker.PulsarService.startLoadManagementService(PulsarService.java:1022)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:737)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.PulsarBrokerStarter$BrokerStarter.start(PulsarBrokerStarter.java:273)
> ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
>          at
> org.apache.pulsar.PulsarBrokerStarter.main(PulsarBrokerStarter.java:350)
> [org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]