You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Ashutosh Jadhav (JIRA)" <ji...@apache.org> on 2018/12/25 13:33:00 UTC

[jira] [Created] (FINCN-107) Unable to create deposit product instance

Ashutosh Jadhav created FINCN-107:
-------------------------------------

             Summary: Unable to create deposit product instance
                 Key: FINCN-107
                 URL: https://issues.apache.org/jira/browse/FINCN-107
             Project: Fineract Cloud Native
          Issue Type: Bug
          Components: fineract-cn-command, fineract-cn-demo-server, fineract-cn-deposit-account-management
            Reporter: Ashutosh Jadhav


Hi

 

While creating a new deposit product instance for a customer/member via "Manage member deposit accounts" screen in fineract-cn-fims-web-app using fineract-cn-demo-server.

I just get a message on frontend screen that "Deposit account is going to be saved". But new account is not available. 

While checking the deposit.log at backend following is my observation -

Async command to create new deposit product instance is not working.

Logs of first called to First call before cache or cache entry for CreateProductInstanceCommand is created - 
{quote}
 18:38:05.188 [async-processor-1] DEBUG command-logger - CommandBus::dispatch-async called.
 18:38:05.188 [async-processor-1] DEBUG command-logger - CommandBus::storeCommand called.
 18:38:05.204 [async-processor-1] INFO cassandra-logger - Create new mapping mapper for tenant [playground] and type [CommandSource].
 18:38:05.223 [async-processor-1] DEBUG command-logger - CommandBus::findCommandHandler called for CreateProductInstanceCommand.
 18:38:05.232 [async-processor-1] DEBUG command-logger - CommandBus::findCommandHandler added method for CreateProductInstanceCommand.
 18:38:05.267 [async-processor-1] INFO o.s.c.a.AnnotationConfigApplicationContext - Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@23952a7a: startup date [Tue Dec 25 18:38:05 IST 2018]; parent: org.springframework.boot.context.embedded.AnnotationConfigEmbeddedWebApplicationContext@5bfbf16f
 18:38:05.304 [async-processor-1] INFO o.s.b.f.a.AutowiredAnnotationBeanPostProcessor - JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
 18:38:05.525 [qtp1681303515-21] INFO anubis-logger - Tenant token for user depositmanager1, with key timestamp 2018-12-16T12_41_11 authenticated successfully.
 18:38:05.526 [qtp1681303515-21] DEBUG anubis-logger - Authorizing access to /instances based on permission: ApplicationPermission

{servletPathSegmentMatchers='/instances', allowedOperation=READ}

18:38:05.528 [async-processor-1] INFO c.n.config.ChainedDynamicProperty - Flipping property: accounting-v1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647
 18:38:05.619 [async-processor-1] INFO c.n.u.c.ShutdownEnabledTimer - Shutdown hook installed for: NFLoadBalancer-PingTimer-accounting-v1
 18:38:05.629 [async-processor-1] INFO c.n.loadbalancer.BaseLoadBalancer - Client:accounting-v1 instantiated a LoadBalancer:DynamicServerListLoadBalancer:\{NFLoadBalancer:name=accounting-v1,current list of Servers=[],Load balancer stats=Zone stats: {},Server stats: []}ServerList:null
 18:38:05.638 [async-processor-1] INFO c.n.l.DynamicServerListLoadBalancer - Using serverListUpdater PollingServerListUpdater
 18:38:05.680 [async-processor-1] INFO c.n.config.ChainedDynamicProperty - Flipping property: accounting-v1.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647
 18:38:05.683 [async-processor-1] INFO c.n.l.DynamicServerListLoadBalancer - DynamicServerListLoadBalancer for client accounting-v1 initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=accounting-v1,current list of Servers=[localhost:2025],Load balancer stats=Zone stats:

{defaultzone=[Zone:defaultzone; Instance count:1; Active connections count: 0; Circuit breaker tripped count: 0; Active connections per server: 0.0;] },Server stats: [[Server:localhost:2025; Zone:defaultZone; Total Requests:0; Successive connection failure:0; Total blackout seconds:0; Last connection made:Thu Jan 01 05:30:00 IST 1970; First connection made: Thu Jan 01 05:30:00 IST 1970; Active Connections:0; total failure count in last (1000) msecs:0; average resp time:0.0; 90 percentile resp time:0.0; 95 percentile resp time:0.0; min resp time:0.0; max resp time:0.0; stddev resp time:0.0] ]}

ServerList:org.springframework.cloud.netflix.ribbon.eureka.DomainExtractingServerList@7d6cf5ab
 18:38:06.039 [async-processor-1] WARN command-logger - Error while processing command. NotFoundException: no details available
 18:38:06.039 [async-processor-1] DEBUG command-logger - CommandBus::updateCommandSource called.
 ```
{quote}
After the entry for CreateProductInstanceCommand is available in cachec and no call to add CreateProductInstanceCommand.
{quote}```java
 18:46:24.637 [async-processor-2] DEBUG command-logger - CommandBus::dispatch-async called.
 18:46:24.638 [async-processor-2] DEBUG command-logger - CommandBus::storeCommand called.
 18:46:24.639 [async-processor-2] DEBUG command-logger - CommandBus::findCommandHandler called for CreateProductInstanceCommand.
 18:46:24.700 [async-processor-2] WARN command-logger - Error while processing command. NotFoundException: no details available
 18:46:24.700 [async-processor-2] DEBUG command-logger - CommandBus::updateCommandSource called.
 18:46:24.971 [qtp1681303515-21] INFO anubis-logger - Tenant token for user depositmanager1, with key timestamp 2018-12-16T12_41_11 authenticated successfully.
 18:46:24.972 [qtp1681303515-21] DEBUG anubis-logger - Authorizing access to /instances based on permission: ApplicationPermission

{servletPathSegmentMatchers='/instances/*', allowedOperation=READ}

```
{quote}
 I checked in database - 
{quote}select count(*) from playground.shed_product_instances;
{quote}
The count is 0.

 

Can you please look into this issue and fix it?

 

Best

Ashutosh

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)