null pointer exception during testing phase

[Yuri Gurevich]

Hi,

I'm getting the following exception during BG benchmark testing run on cassandra:

Error in Rels
java.lang.NullPointerException
    at edu.usc.bg.workloads.CoreWorkload.relateUsers(CoreWorkload.java:2950)
    at edu.usc.bg.workloads.CoreWorkload.initStatsQueryData(CoreWorkload.java:1002)
    at edu.usc.bg.workloads.CoreWorkload.readInitStatsReqApproachProperty(CoreWorkload.java:745)
    at edu.usc.bg.workloads.CoreWorkload.resetDBInternalStructures(CoreWorkload.java:731)
    at edu.usc.bg.base.Client.initializeDB(Client.java:1725)
    at edu.usc.bg.base.Client.runBG(Client.java:837)
    at edu.usc.bg.BGMainClass.main(BGMainClass.java:41)

I found that actually in the code there is no NULL value check in that particular function (relateUsers).
Please advice.


Thanks,
-Yuri

[Shahram Ghandeharizadeh]

Hi Yuri,

Please provide additional information so that we can help you trouble shoot: 

Does this exception occur when running a workload?  After schema creation and loading of the database? 

Shahram.

--
You received this message because you are subscribed to the Google Groups "BG Social Benchmark" group.
To unsubscribe from this group and stop receiving emails from it, send an email to BG-SocialBenchm...@googlegroups.com.
Visit this group at http://groups.google.com/group/BG-SocialBenchmark.
For more options, visit https://groups.google.com/d/optout.

[Yuri Gurevich]

Hi Shahram,

It happens when I run workload (-t option), after the schema creation and data loading are both completed successfully.

Thanks,
-Yuri

You received this message because you are subscribed to a topic in the Google Groups "BG Social Benchmark" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/BG-SocialBenchmark/xo_3StHnTEY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to BG-SocialBenchm...@googlegroups.com.

[Yuri Gurevich]

To overcome that I had to update BG CoreWorkload code and add a null pointer check in that particular place.

Do you think it is a problem in BG or it just might be an issue with my client implementation?

Thanks,

-Yuri

[Sumita Barahmand]

Hi,

Based on the stack trace you have posted I am assuming you are using the "-p initapproach=querydata" flag. is that correct?

There may be a problem in your client implementation to get the initial state of the data from the database. Can you run your experiment using the "-p initapproach=deterministic" (along with its required parameters) and with removing the null check you added to the code to see if the problem reproduces?

- Sumita

On Wednesday, November 26, 2014 4:05:05 AM UTC-8, Yuri Gurevich wrote:

To overcome that I had to update BG CoreWorkload code and add a null pointer check in that particular place.

Do you think it is a problem in BG or it just might be an issue with my client implementation?

Thanks,

-Yuri

On Mon, Nov 17, 2014 at 11:19 AM, Yuri Gurevich <yuri.g...@gmail.com> wrote:

Hi Shahram,

It happens when I run workload (-t option), after the schema creation and data loading are both completed successfully.

Thanks,
-Yuri

On Nov 16, 2014 5:21 PM, "Shahram Ghandeharizadeh" <shahram.ghandeharizadeh@gmail.com> wrote:

Hi Yuri,

Please provide additional information so that we can help you trouble shoot: 

Does this exception occur when running a workload?  After schema creation and loading of the database? 

Shahram.

On Sun, Nov 16, 2014 at 9:11 AM, Yuri Gurevich <yuri.g...@gmail.com> wrote:

Hi,

I'm getting the following exception during BG benchmark testing run on cassandra:

Error in Rels
java.lang.NullPointerException
    at edu.usc.bg.workloads.CoreWorkload.relateUsers(CoreWorkload.java:2950)
    at edu.usc.bg.workloads.CoreWorkload.initStatsQueryData(CoreWorkload.java:1002)
    at edu.usc.bg.workloads.CoreWorkload.readInitStatsReqApproachProperty(CoreWorkload.java:745)
    at edu.usc.bg.workloads.CoreWorkload.resetDBInternalStructures(CoreWorkload.java:731)
    at edu.usc.bg.base.Client.initializeDB(Client.java:1725)
    at edu.usc.bg.base.Client.runBG(Client.java:837)
    at edu.usc.bg.BGMainClass.main(BGMainClass.java:41)

I found that actually in the code there is no NULL value check in that particular function (relateUsers).
Please advice.


Thanks,
-Yuri

--
You received this message because you are subscribed to the Google Groups "BG Social Benchmark" group.

To unsubscribe from this group and stop receiving emails from it, send an email to BG-SocialBenchmark+unsub...@googlegroups.com.

Visit this group at http://groups.google.com/group/BG-SocialBenchmark.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "BG Social Benchmark" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/BG-SocialBenchmark/xo_3StHnTEY/unsubscribe.

To unsubscribe from this group and all its topics, send an email to BG-SocialBenchmark+unsub...@googlegroups.com.

[Yuri Gurevich]

Hi Sumita,

Your assumption was correct - there was a problem with getting initial statistics in my client implementation.
I've fixed that one and now it seems to work fine also with "-p initapproach=querydata". Thanks a lot!


Regards,
-Yuri

On Saturday, December 13, 2014 8:55:47 AM UTC-5, Sumita Barahmand wrote:

Hi,

Based on the stack trace you have posted I am assuming you are using the "-p initapproach=querydata" flag. is that correct?

There may be a problem in your client implementation to get the initial state of the data from the database. Can you run your experiment using the "-p initapproach=deterministic" (along with its required parameters) and with removing the null check you added to the code to see if the problem reproduces?

- Sumita

On Wednesday, November 26, 2014 4:05:05 AM UTC-8, Yuri Gurevich wrote:

To overcome that I had to update BG CoreWorkload code and add a null pointer check in that particular place.

Do you think it is a problem in BG or it just might be an issue with my client implementation?

Thanks,

-Yuri

On Mon, Nov 17, 2014 at 11:19 AM, Yuri Gurevich <yuri.g...@gmail.com> wrote:

Hi Shahram,

It happens when I run workload (-t option), after the schema creation and data loading are both completed successfully.

Thanks,
-Yuri