You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/12/09 20:02:02 UTC

[GitHub] [pulsar] dlsprague opened a new issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

dlsprague opened a new issue #8884:
URL: https://github.com/apache/pulsar/issues/8884


   User upgraded pulsar java client to 2.6.2 due to security vulnerabilities found in lower versions.  Was able to produce messages fine in 2.5.0 and 2.6.0, but after upgrade getting following error:
   
   [2020-12-08 09:43:28.837] [AlarmCreate][org.apache.pulsar.client.impl.ProducerImpl] WARN - [persistent://i18v/fault-alarmupdate/Apollo-Fault-AlarmUpdate-1sec-partition-0] [xxx-aws-us-xxxx-1-101050-61003] error while create opSendMsg by batch message container
   java.lang.NullPointerException: null
   at org.apache.pulsar.shade.io.netty.util.Recycler.recycle(Recycler.java:180) ~[pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.common.api.proto.PulsarApi$MessageMetadata$Builder.recycle(PulsarApi.java:4571) ~[pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.client.impl.BatchMessageContainerImpl.getCompressedBatchMetadataAndPayload(BatchMessageContainerImpl.java:121) ~[pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.client.impl.BatchMessageContainerImpl.createOpSendMsg(BatchMessageContainerImpl.java:176) ~[pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.client.impl.ProducerImpl.batchMessageAndSend(ProducerImpl.java:1565) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.client.impl.ProducerImpl.access$500(ProducerImpl.java:89) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.client.impl.ProducerImpl$2.run(ProducerImpl.java:1524) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.shade.io.netty.util.HashedWheelTimer$HashedWheelTimeout.expire(HashedWheelTimer.java:672) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.shade.io.netty.util.HashedWheelTimer$HashedWheelBucket.expireTimeouts(HashedWheelTimer.java:747) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.shade.io.netty.util.HashedWheelTimer$Worker.run(HashedWheelTimer.java:472) [pulsar-client-2.6.2.jar:2.6.2]
   at org.apache.pulsar.shade.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [pulsar-client-2.6.2.jar:2.6.2]
   at java.lang.Thread.run(Thread.java:748) [?:1.8.0_202]
   
   Error seems to suggest message size over limit but have sent very small messages for testing and still fails. 
   
   Pulsar broker is at version 2.6.0.  Could this be a compatibility issue with client at a higher version?  
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-754252503


   We turned off encryption on the topics namespace and connecting and producing was then successful.   so problem with the upgrade specific to encryption in our case.  


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-744567290


   Also some additional info as I tried to produce a message.  (it failed because I wasnt using encryptiom).  Thought maybe some of these settings would help.
   11:08:11.281 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ProducerStatsRecorderImpl - Starting Pulsar producer perf with config: {
     "topicName" : "persistent://i18v/fault-alarmupdate/Apollo-Fault-AlarmUpdate-1sec-partition-0",
     "producerName" : null,
     "sendTimeoutMs" : 30000,
     "blockIfQueueFull" : false,
     "maxPendingMessages" : 1000,
     "maxPendingMessagesAcrossPartitions" : 50000,
     "messageRoutingMode" : "RoundRobinPartition",
     "hashingScheme" : "JavaStringHash",
     "cryptoFailureAction" : "FAIL",
     "batchingMaxPublishDelayMicros" : 1000,
     "batchingPartitionSwitchFrequencyByPublishDelay" : 10,
     "batchingMaxMessages" : 1000,
     "batchingMaxBytes" : 131072,
     "batchingEnabled" : true,
     "chunkingEnabled" : false,
     "compressionType" : "NONE",
     "initialSequenceId" : null,
     "autoUpdatePartitions" : true,
     "multiSchema" : true,
     "properties" : { }
   }
   11:08:11.290 [pulsar-client-io-1-1] INFO  org.apache.pulsar.client.impl.ProducerStatsRecorderImpl - Pulsar client config: {
     "serviceUrl" : "pulsar+ssl://localhost:6651/",
     "authPluginClassName" : null,
     "authParams" : null,
     "authParamMap" : null,
     "operationTimeoutMs" : 30000,
     "statsIntervalSeconds" : 60,
     "numIoThreads" : 1,
     "numListenerThreads" : 1,
     "connectionsPerBroker" : 1,
     "useTcpNoDelay" : true,
     "useTls" : true,
     "tlsTrustCertsFilePath" : "/VMB/apache-pulsar-2.6.0/certs/combined.ca.pem",
     "tlsAllowInsecureConnection" : false,
     "tlsHostnameVerificationEnable" : false,
     "concurrentLookupRequest" : 5000,
     "maxLookupRequest" : 50000,
     "maxLookupRedirects" : 20,
     "maxNumberOfRejectedRequestPerConnection" : 50,
     "keepAliveIntervalSeconds" : 30,
     "connectionTimeoutMs" : 10000,
     "requestTimeoutMs" : 60000,
     "initialBackoffIntervalNanos" : 100000000,
     "maxBackoffIntervalNanos" : 60000000000,
     "listenerName" : null,
     "useKeyStoreTls" : false,
     "sslProvider" : null,
     "tlsTrustStoreType" : "JKS",
     "tlsTrustStorePath" : null,
     "tlsTrustStorePassword" : null,
     "tlsCiphers" : [ ],
     "tlsProtocols" : [ ],
     "proxyServiceUrl" : null,
     "proxyProtocol" : null
   }
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-744676001


   The message size limit is set at the broker level.  Because we batch on broker side, we did testing by commenting out .bathcingMaxPublishDelay(3, TimeUnit.MILLISECONDS) but it still gave message  error while create opSendMsg by batch message container.  It was clarified that this is also occurring in 2.5.2, 2.6.0, 2.6.2 and 2.7.0.  Problem does not occur in 2.5.0.  User is encrypting and batching, but as mentioned, stopped batching on client side for testing and it still produced error.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747185423


   Sorry, I did not reply in time. I still cannot reproduce. Now there are too many factors. I am not sure which one is different from what you set: encryption, message size, client version, etc.
   Can you try to turn off some factors, such as: turn off the message size limit, will it appear? Turn off encryption, will it appear?
   Or, provide a piece of code that can definitely be reproduced?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-754919031


   Also, just to verify with your successful testing, what client version were you using?   2.6.2 or newer?  Thank you.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747615024


   Hi Thank you very much..  Yes, I will pass that information on and see if
   it helps..   I appreciate it!
   
   On Thu, Dec 17, 2020 at 12:27 PM Kai <no...@github.com> wrote:
   
   > Hey @dlsprague
   > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dlsprague&d=DwMCaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=CTPxRMwBt64kr_5Ub7TH_GCQDIXgtotELZbBMQznbiI&m=tC4MAHGePW28VxFlA1m2Svot7fwmTwO_hZ-9jWVV5A4&s=vLv_bLs5j2o_t64hhLDv8cLZ8xn2Hht7AaeN-o_iInI&e=>!
   > My team was seeing an identical issue when using client version 2.5.2,
   > where sending a message would trigger that stacktrace regardless of what or
   > how we sent it. We think that it was due to some weird transitive
   > dependencies, where the project was using
   > org.apache.pulsar:pulsar-client-original:2.5.2, but was also pulling in a
   > transitive dependency that used org.apache.pulsar:pulsar-client:2.4.0. By
   > upgrading the transitive dependency so that they were both using the
   > client-original:2.5.2 package, the error went away. Hopefully your
   > project has a similar issue and can benefit from a similar fix.
   >
   > We've definitely had a lot of headaches due to mismatched dependencies..
   >
   > —
   > You are receiving this because you were mentioned.
   > Reply to this email directly, view it on GitHub
   > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_apache_pulsar_issues_8884-23issuecomment-2D747583508&d=DwMCaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=CTPxRMwBt64kr_5Ub7TH_GCQDIXgtotELZbBMQznbiI&m=tC4MAHGePW28VxFlA1m2Svot7fwmTwO_hZ-9jWVV5A4&s=G19ENJsHJMMSn8ctF6qv_FMlsTMjYA8rQrcHK-eQjwE&e=>,
   > or unsubscribe
   > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ASB53NIP3REDCGCQKGRKX7LSVI5PTANCNFSM4UT7S66Q&d=DwMCaQ&c=udBTRvFvXC5Dhqg7UHpJlPps3mZ3LRxpb6__0PomBTQ&r=CTPxRMwBt64kr_5Ub7TH_GCQDIXgtotELZbBMQznbiI&m=tC4MAHGePW28VxFlA1m2Svot7fwmTwO_hZ-9jWVV5A4&s=4T9jV4Qg1CLf49ner_q3f9iEb_fnY_-4qpCJquXRuCU&e=>
   > .
   >
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747537259


   HI a test was performed on a topic not using encryption and it was successful.  Adding encrpytion and it failed.  I am asking developer for code that is failing to provide.  
   
   Thank you


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] sijie commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
sijie commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-755836286


   @dlsprague Can you create a separate Github issue for the vulnerability issue?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-748838263


   I used the complete code you provided, and the certificate used the one used in org.apache.pulsar.client.TlsProducerConsumerTest. The unit test passed normally.
   
   https://github.com/315157973/pulsar/blob/67eb4b81b554b94fb3b51b0a96acd50d7bacceb9/bouncy-castle/bcfips-include-test/src/test/java/org/apache/pulsar/client/TlsProducerConsumerTest.java#L147


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague closed issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague closed issue #8884:
URL: https://github.com/apache/pulsar/issues/8884


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747721467


   developer says snakeyaml 1.2.4 dependency is causing a twist lock.  Unfortunately he is not able to upgrade that individually or change that manually.    How are you able to upgrade the dependencies embedded in client?
   
   ![image (3)](https://user-images.githubusercontent.com/75750837/102547165-c633a200-4086-11eb-8b85-68eced333b04.png)
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-744566122


   Looking for the rest of the info requested.  User did attempt to use client 2.7.0 but got same exception.  


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-755398576


   Can I please request a call concerning this issue?  Just to review, our broker is on 2.6.0, user is attempting to use 2.6.2 to alleviate some security vulnerabilities but with encryption turned on he gets Null pointer exception. Works ok with encryption off.  Looks like same code has been tested above and was successful.  Unsure what we need to do to resolve on our end.    Thank you so much!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-744565840


   Here is how producer sends message. 
   package com.vz.apollo.alarmdbupdates;
   ​
   import java.io.IOException;
   import java.nio.file.Files;
   import java.nio.file.Paths;
   import java.util.Map;
   ​
   import org.apache.pulsar.client.api.CryptoKeyReader;
   import org.apache.pulsar.client.api.EncryptionKeyInfo;
   import org.slf4j.Logger;
   import org.slf4j.LoggerFactory;
   ​
   public class RawFileKeyReader implements CryptoKeyReader {
   	protected final Logger logger = LoggerFactory.getLogger(this.getClass());
   	String publicKeyFile = "";
   	String privateKeyFile = "";
   	
   	public RawFileKeyReader(String pubKeyFile, String privKeyFile) {
   		publicKeyFile = pubKeyFile;
   		privateKeyFile = privKeyFile;
   	}
   ​
   	@Override
   	public EncryptionKeyInfo getPublicKey(String keyName, Map<String, String> keyMeta) {
   		EncryptionKeyInfo keyInfo = new EncryptionKeyInfo();
   		try {
   			keyInfo.setKey(Files.readAllBytes(Paths.get(publicKeyFile)));                
   		} catch (IOException e) {
   			logger.info("ERROR: Failed to read public key from file " + publicKeyFile);
   			e.printStackTrace();
   		}
   		return keyInfo;
   	}
   ​
   	@Override
   	public EncryptionKeyInfo getPrivateKey(String keyName, Map<String, String> keyMeta) {
   		EncryptionKeyInfo keyInfo = new EncryptionKeyInfo();
   		try {
   			keyInfo.setKey(Files.readAllBytes(Paths.get(privateKeyFile)));
   		} catch (IOException e) {
   			logger.info("ERROR: Failed to read private key from file " + privateKeyFile);
   			e.printStackTrace();
   		}
   		return keyInfo;
   	}
   }
   
   
   _producer_java_client = pulsarClient.newProducer().topic(_topic_java_client).batchingMaxPublishDelay(3, TimeUnit.MILLISECONDS)
       				.cryptoKeyReader(new RawFileKeyReader(publicKey,privateKey))
       				.addEncryptionKey(publicKey)
       				.sendTimeout(10, TimeUnit.SECONDS).blockIfQueueFull(true)
       				.create();
   above is the code used for encryption of the messages


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747622815


   Attaching the sample failing code for further review.  
   [Downloads.zip](https://github.com/apache/pulsar/files/5711477/Downloads.zip)
   
   
   
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743245313


   I will see what the problem is


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-755617182


   thank you.   Update to the issue: 
   It is now successful using a different dependency which is bouncy castle and the connection is working with encryption enabled.  However, there are black duck security vulnerabilities being reported.
   
   Using 2.6.2 client Bouncy castle jar file, an inner jar of pulsar client  has some internal transitive dependencies with 1.6.0 version  of bouncy castle which is causing the HIGH vulnerabilities.
   
   Using 2.7.0  High vulnerability is removed but it has  1 CRITICAL vulnerability with the  new  transitive dependency jar (bcprov-ext-jdk15on-1.66.jar
   
   ![image262_1](https://user-images.githubusercontent.com/75750837/103815154-ef65a380-5030-11eb-9590-eafa6ff86d4e.png)
   ![image262_2](https://user-images.githubusercontent.com/75750837/103815168-f4c2ee00-5030-11eb-9bb7-7457a5c1ea56.png)
   ![image270_2](https://user-images.githubusercontent.com/75750837/103815175-f68cb180-5030-11eb-8cb6-34a11898dfa7.png)
   ![image270_1](https://user-images.githubusercontent.com/75750837/103815181-f7bdde80-5030-11eb-8909-6db13251aa45.png)
   
   What can we do to resolve this vulverability?  
   
   Thanks again.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-755416112


   > Can I please request a call concerning this issue?  Just to review, our broker is on 2.6.0, user is attempting to use 2.6.2 to alleviate some security vulnerabilities but with encryption turned on he gets Null pointer exception. Works ok with encryption off.  Looks like same code has been tested above and was successful.  Unsure what we need to do to resolve on our end.    Thank you so much!
   
   
   Tried 2.6.2, 2.6.0, and 2.7.0.  I will add 2.6.x unit tests to my code repository.  It is possible that the encrypted package of the client conflicts with the encrypted package in your business code.  You can try to use the shade version of the client.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747058919


   Is there something else we can do to test?    We attempted to turn off the batching on client producer since batching is done on broker side thinking that would help, but we still got same message.  Is there something else we should try.  Will be furloughed the 2 last weeks of December, hoping to try something before then.  Thanks so much!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 edited a comment on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 edited a comment on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743688366


   Hello, could you provide more information?
   Such as your producer creation parameters、 How does the producer send the message、More client and broker error logs、Is the message size limit set at the broker level or the topic level?...
   
   I use the latest broker and 2.6.2 client locally, and this problem cannot be reproduced temporarily.
   It does not seem to be caused by the topic-level message size limit.
   When the message size limit is exceeded, the producer of 2.6.2 cannot successfully produce until it times out. The 2.7.0 producer will throw an exception.
   @dlsprague 
   
   > Error seems to suggest message size over limit but have sent very small messages for testing and still fails.
   
   Your messages are sent in batches. A single message is small. Will the entire batch of messages be large?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743279109


   Thank you so much!


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 edited a comment on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 edited a comment on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743688366


   Hello, could you provide more information?
   Such as your producer creation parameters、 How does the producer send the message?、More client and broker error logs...
   
   I use the latest broker and 2.6.2 client locally, and this problem cannot be reproduced temporarily.
   It does not seem to be caused by the message size limit.
   When the message size limit is exceeded, the producer of 2.6.2 cannot successfully produce until it times out. The 2.7.0 producer will throw an exception.
   @dlsprague 
   
   > Error seems to suggest message size over limit but have sent very small messages for testing and still fails.
   
   Your messages are sent in batches. A single message is small. Will the entire batch of messages be large?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743688366


   Hello, could you provide more information?
   Such as your producer creation parameters、 How does the producer send the message?
   
   I use the latest broker and 2.6.2 client locally, and this problem cannot be reproduced temporarily.
   It does not seem to be caused by the message size limit.
   When the message size limit is exceeded, the producer of 2.6.2 cannot successfully produce until it times out. The 2.7.0 producer will throw an exception.
   @dlsprague 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] 315157973 edited a comment on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
315157973 edited a comment on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-743688366


   Hello, could you provide more information?
   Such as your producer creation parameters、 How does the producer send the message、More client and broker error logs、Is the message size limit set at the broker level or the topic level?...
   
   I use the latest broker and 2.6.2 client locally, and this problem cannot be reproduced temporarily.
   It does not seem to be caused by the message size limit.
   When the message size limit is exceeded, the producer of 2.6.2 cannot successfully produce until it times out. The 2.7.0 producer will throw an exception.
   @dlsprague 
   
   > Error seems to suggest message size over limit but have sent very small messages for testing and still fails.
   
   Your messages are sent in batches. A single message is small. Will the entire batch of messages be large?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-756765315


   Opened issue #9151 for security vulnerabilities.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] klevy-toast commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
klevy-toast commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-747583508


   Hey @dlsprague! My team was seeing an identical issue when using client version 2.5.2, where sending a message would trigger that stacktrace regardless of what or how we sent it. We think that it was due to some weird transitive dependencies, where the project was using `org.apache.pulsar:pulsar-client-original:2.5.2`, but was also pulling in a transitive dependency that used `org.apache.pulsar:pulsar-client:2.4.0`. By upgrading the transitive dependency so that they were both using the `client-original:2.5.2` package, the error went away. Hopefully your project has a similar issue and can benefit from a similar fix.
   
   We've definitely had a lot of headaches due to mismatched dependencies..


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague closed issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague closed issue #8884:
URL: https://github.com/apache/pulsar/issues/8884


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] dlsprague commented on issue #8884: After upgrade pulsar client version to 2.6.2, getting the Null pointer exception while publishing a message

Posted by GitBox <gi...@apache.org>.
dlsprague commented on issue #8884:
URL: https://github.com/apache/pulsar/issues/8884#issuecomment-756765315


   Opened issue #9151 for security vulnerabilities.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org