Hello,

Never mind. I "fixed" the problem by reconfiguring from scratch my API
manager and only my API manager with the following documentation [1]

Regards,

Thomas

[1]
https://docs.wso2.com/display/AM210/Configuring+WSO2+Identity+Server+as+a+Key+Manager#ConfiguringWSO2IdentityServerasaKeyManager-Step5-ConfiguretheAPIManager

2017-11-08 10:29 GMT+01:00 Thomas LEGRAND <[email protected]>:

> Hello,
>
> I stopped the instance of the API manager to remove the h2 database file (
> <WSO2_APIM_DIRECTORY>/repository/database/WSO2CARBON_DB.h2.db). I
> restarted the instance with -Dsetup to make it create the data model. Then
> I stop and I start again. No sign of the error I had during the startup. So
> that works.
>
> However, I always have the problem concerning the APIs which do not appear
> in the list on the publisher of the API manager. When I check in the
> database, I can see them in the table AM_API.
>
> Both of my AM and IS point to the same schema/tables (see the joined
> master-datasources.xml).
>
> They have the same registry.xml, too (see the joined registry.xml)
>
> Can you help me?
>
> Regards,
>
> Thomas
>
> 2017-11-07 19:15 GMT+01:00 Bhathiya Jayasekara <[email protected]>:
>
>> Hi Thomas,
>>
>> Please attach complete log files and registry.xml files of both servers.
>>
>> Thanks,
>> Bhathiya
>>
>> On Tue, Nov 7, 2017 at 9:43 PM, Thomas LEGRAND <
>> [email protected]> wrote:
>>
>>> Hello,
>>>
>>> I have my API manager which is configured to use the Identity Server as
>>> Key Manager. But, on the API manager publisher, when I create a new API
>>> from a swagger file or using the assistant (for the worldbank tuto), I
>>> don't see any of my API in the list. However, I can see that XML files are
>>> created via the log of the API manager :
>>>
>>> TID: [-1234] [] [2017-11-07 17:04:39,159]  INFO
>>>> {org.apache.synapse.rest.API} -  Initializing API: admin--WorldBank:v1.0.0
>>>> {org.apache.synapse.rest.API}
>>>>
>>>
>>> But nothing on my screen:
>>>
>>> [image: Images intégrées 1]
>>>
>>> I am connected as admin (the default user) and I can't even bind my API
>>> to an application on the API manager store :/
>>>
>>> I double-checked the configuration but I can see an error at the startup
>>> of the API manager :
>>>
>>> TID: [-1234] [] [2017-11-07 17:04:02,197] ERROR
>>> {org.wso2.carbon.registry.core.internal.RegistryCoreServiceComponent}
>>> -  Unable to create fixed remote mounts. {org.wso2.carbon.regi
>>> stry.core.internal.RegistryCoreServiceComponent}
>>> org.wso2.carbon.registry.core.exceptions.RegistryException: An
>>> exception occurred while executing handler chain. null
>>>         at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.d
>>> elete(HandlerManager.java:2649)
>>>         at org.wso2.carbon.registry.core.jdbc.handlers.UserDefinedHandl
>>> erManager.delete(UserDefinedHandlerManager.java:215)
>>> Caused by: java.lang.NullPointerException
>>>         at org.wso2.carbon.registry.core.jdbc.handlers.builtin.MountHan
>>> dler.delete(MountHandler.java:490)
>>>         at org.wso2.carbon.registry.core.jdbc.handlers.HandlerManager.d
>>> elete(HandlerManager.java:2627)
>>>         ... 50 more
>>>
>>> - Do you have any idea why this error occurs?
>>> - Is this error linked to the fact I can't see my newly created APIs?
>>> - CAn you help me, please?
>>>
>>> Regards,
>>>
>>> Thomas
>>>
>>> _______________________________________________
>>> Dev mailing list
>>> [email protected]
>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>
>>>
>>
>>
>> --
>> *Bhathiya Jayasekara*
>> *Associate Technical Lead,*
>> *WSO2 inc., http://wso2.com <http://wso2.com>*
>>
>> *Phone: +94715478185 <+94%2071%20547%208185>*
>> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
>> <http://www.linkedin.com/in/bhathiyaj>*
>> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
>> *Blog: http://movingaheadblog.blogspot.com
>> <http://movingaheadblog.blogspot.com/>*
>>
>
>
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to