cannot start iotmms java app

[#1]

Hi

After redeploying the iotmms java app to the newest version (using "Deploy Message Management Service" of the "Internet of Things Management Cockpit") I cannot start the iotmms java app any more. When I try to (stop and) start the service, after the waiting whell spinns a long time it fails to start. Looking at the logs didn't help me.

The problem might have to do with the fact that there seems to be a broken binding definition which I cannot delete. When I look in the "Bindings" section of the iotmms java app there is an error message stating the following: "Internal Server Error (500) - Unexpected exception in getBindingList() called with application key '{account:'s0001207844trial', application:'iotmms', component:'web'}'". However, when i delete the iotmms app with all bindings (checking the respective flag) and then redeploy and restart the app the same error appears. Has Anybody an idea what I could do?

Thanks for your suggestions,

Patrick

[anton_levin · Accepted solution]

A "myhanaxs" schema is missing in your case. Can you create one with such ID? Afterwards, you will able to see the list of your bindings and continue operating your account/application as usual.

Regards,

Anton

[patrickwenger · Accepted solution]

Hi Anton

This did the trick. Again, thanks a lot for your support and best regards,

Patrick

[Former Member · Accepted solution]

Hi Anton,

I'm having the same problem and the solution provided here is not solving the problem.

Error message is as follows:-

Internal Server Error (500) - Unexpected exception in getBindingList() called with application key '{account:'i054356trial', application:'iotmms', component:'web'}'

Any other suggestions?

Thanks in advance

Bella

[anton_levin · Accepted solution]

Provided solution didn't solve your problem since you have other configuration setup. I have made a request to check what is the corrupted schema ID in your account. You will be notified by mail with the internal ticket updates.

P.S. Failed to subscribe you for notifications. I will give an update here.

[Former Member · Accepted solution]

Hi

I have the same problem.

How did you solve the problem?

Regards,

Mariusz

[anton_levin · Accepted solution]

In order to be able to help, I would need your account ID. Let me know if you do not want to share it here, we will establish another communication channel.

[Former Member · Accepted solution]

Hi Mariusz,

My issue is not yet resolved. Anton is trying to help get the issue resolved.

Bella

[Former Member · Accepted solution]

Hi Anton,

Please can you email (using SAP email address) the internal ticket number?

Thanks

Bella

[Former Member · Accepted solution]

Hi Anton,

Some additional information which may help..

I deployed the .WAR file as per point 1 in

This started the iotmms successfully.

If you redeploy the MMS from the IoT Services Cockpit then this is when the starting process takes very long and eventually times out and fails.

[Former Member · Accepted solution]

Thank you for your answer.

According to the recommendations.

I do not want to publish my ID.

Mariusz

[anton_levin]

Hello Patrick,

may I ask you to start the "iotmms" app in your account so that it reaches that "failing state"? (currently I see that there is no iotmms app in your account). I need all possible logs to be able to open an internal ticket. You do not need to send them. I can grab everything I need from the monitoring tool.

Additionally, for that error message in HCP Cockpit, I would like to ask you to make a screenshot for me and attach it in here.

Thanks,

Anton

[patrickwenger]

Hi Anton

Thanks for your quick replay. I have started the app again and it is in fail-state now. I have also attached the printscreens.

Your help is highly appreciated.

Patrick

[anton_levin]

I have the logs now. Meanwhile, I can suggest a workaround for you since creation of the default schema "<accountID>.iotmms.web" didn't work for some reasons. With that we will also check if creation of the schema works for you in general.

1. Stop your iotmms

2. Go to its Data Source Bindings and delete the <DEFAULT> binding (if any)

3. In your HCP Cockpit -> Databases & Schemas -> click New

4. Give some name i.e. "customiotmmschema", choose "HANA<shared>" as type, Save

5. Return back to iotmms -> Data Source Bindings -> click New Binding -> select your "customiotmmschema"

6. Start iotmms

Let me know if that worked or you also have the same kind of exception for "customiotmmschema"

Regards,

Anton

[patrickwenger]

I've tried the suggested steps. Until step 4 all is ok (although there was no <DEFAULT> binding to delete).

In step 5 I get the following error as soon as I try to save the new binding: Unable to create default binding. At least one binding already exists for application '{account:'s0001207844trial', application:'iotmms', component:'web'}'.

There already seems to be a binding which cannot be deleted via cockpit. Is there some other way to see/delete existing bindings (i.e. some database table entry...)?

Regards,

Patrick

[anton_levin]

Not to my knowledge. An internal ticket is opened, let's give the colleagues some time. Hopefully, a "corrupted" binding will be removed soon. I will keep you updated.

Sorry for the inconvenience,

Anton

[patrickwenger]

Thanks for your response and your upcoming update about this matter. I appreciate your (very quick and helpful) support a lot.

Patrick

[anton_levin]

Hi Patrick,

colleagues ask to try to create a schema with exactly the same name (like corrupted one) -> "s0001207844trial.iotmms.web" in step 4.

Can you reply with the result afterwards?

Investigation is still in progress.

Regards,

Anton

[patrickwenger]

I've tried this already. Unfortunately with the same error.