Hi Nuwan, Thanks for your assistance today debugging this issue. As we have now identified it is a bug, the fix will be tested with ticket [1].
[1] https://wso2.org/jira/browse/APIMANAGER-4290 Cheers, Pubudu. Pubudu D.P Senior Software Engineer - QA Team | WSO2 inc. Mobile : +94775464547 On Tue, Dec 1, 2015 at 9:57 AM, Nuwan Dias <[email protected]> wrote: > Hi Pubudu, > > The reason for the publishing failure is an authentication failure. The > Publisher fails to authenticate with the Gateway to access its admin > services. Could the admin passwords changed inconsistently? > > The Exception on the Gateway is not related to the error on publisher. Its > an issue related to svn dep-sync. I'm not sure what that is. > > Although these have occurred when you tried to move to Oracle from MySQL, > none of the errors are DB specific. There aren't any SQL related error logs > in the traces you've attached. My guess is that they have been introduced > during the migration process from MySQL to Oracle. > > If we cannot get this figured out soon can we sit together and have a > look? It would make things fast. > > Thanks, > NuwanD. > > On Mon, Nov 30, 2015 at 11:45 PM, Pubudu Priyashan <[email protected]> > wrote: > >> Also, gateway worker nodes have given the attached exception after >> the server was started. >> >> Pubudu D.P >> Senior Software Engineer - QA Team | WSO2 inc. >> Mobile : +94775464547 >> >> On Mon, Nov 30, 2015 at 11:35 PM, Pubudu Priyashan <[email protected]> >> wrote: >> >>> Hi API-M team, >>> >>> We've been experiencing the attached exception in publisher node while >>> trying to point the dep-sync svn location to a new folder path. We got rid >>> of the same issue in mysql setup. But for Oracle 12c we are unable fix it >>> with the same set of steps. Please find the steps we followed below. >>> >>> 1. Drop DBs and re-create the same DBs (apim, um, reg, stats) >>> 2. Delete H2 dbs from all nodes ($home/repository/databases) >>> 3. Delete $home/repository/deployment/server folder and replace the same >>> from a fresh pack >>> 4. Create a new svn folder and point it on carbon.xml in gateway manager >>> and both gateway worker nodes. >>> 5. Make sure there are no .svn folders within the file structure of >>> gateway manager and gateway workers >>> 6. Start all the nodes with -Dsetup >>> >>> This sequence worked for mysql, but for Oracle 12c set up, attached >>> exception keeps appearing on publisher node when trying to publish an api >>> from publisher to store. On UI it's giving attached error message. Could >>> you please point out if we are missing something or could it be an issue >>> related to Oracle db? >>> >>> Cheers, >>> Pubudu D.P >>> Senior Software Engineer - QA Team | WSO2 inc. >>> Mobile : +94775464547 >>> >> >> > > > -- > Nuwan Dias > > Technical Lead - WSO2, Inc. http://wso2.com > email : [email protected] > Phone : +94 777 775 729 >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
