Skip to content
This repository was archived by the owner on Nov 6, 2018. It is now read-only.

NullPointerException while getting list of services has been fixed.#185

Open
irbis wants to merge 1 commit into
fabric8io:masterfrom
irbis:ribbon-discovery-npe
Open

NullPointerException while getting list of services has been fixed.#185
irbis wants to merge 1 commit into
fabric8io:masterfrom
irbis:ribbon-discovery-npe

Conversation

@irbis

@irbis irbis commented Jun 21, 2017

Copy link
Copy Markdown
Contributor

By default KubernetesServerList() initializes with default constructor and then method initWithNiwsConfig(IClientConfig clientConfig) runs.

Default constructor doesn't initialize this.client that leads to NullPointerException in line 67. This has been fixed.

Also, hellohystrix and helloribbon use different keys and looks like this is a reason why ribbon can't find hello-hystrix command.

cc: @iocanel

@irbis

irbis commented Jun 30, 2017

Copy link
Copy Markdown
Contributor Author

Hi @iocanel
Is this pull request is usefull?

Thanks,

@sonata82

Copy link
Copy Markdown

Shouldn't client be initialized in the default empty constructor then?

And I'm not sure, but it the default constructor used anyway?

@irbis

irbis commented Sep 11, 2017

Copy link
Copy Markdown
Contributor Author

It in use. And this leads to NullPointerException.

@iocanel iocanel left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for sending this in and apologies for the long wait.

}

public void initWithNiwsConfig(IClientConfig clientConfig) {
this.client = new DefaultKubernetesClient();

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any guarantees that this method will be called only when the object is constructed using the empty constructor? If not, then it can potentially be an issue.

It would be cleaner if we took care of the problem as part of the default constructor.

@irbis irbis Sep 11, 2017

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As far as I tested this, first default constructor runs, then initWithNiwsConfig(). I didn't see any call to other variants of constructors.

To guarantee from issues why not to add check to null:
if (this.client == null) this.client = new DefaultKubernetesClient();

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we just move the logic to the default constructor? I think that this is the cleanest possible approach.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did it. But it didn't work. I could check why, but I need extra time for this.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only rational explanation I can think of is the default constructor not being used at all. It could use the non-default ones and pass a null instance of the kubernetes-client.

@irbis irbis Sep 11, 2017

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. Give me a couple of days and I'll attach stack trace.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi,
I've checked the code and find out some changes were added after I had created PR. Let's drop my changes.

Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants