Getting error in OSB service

Question

Hi All,
I am facing a peculiar error in OSB. I have an application running in OSB. When I redeployed the application it took more than 10 mins to activate the changes which is not at all expected. Also when I deleted the the application and again deployed it it is taking same more than 10 mins to get activated. When I examibed the log file I got the following error
####<02-Jan-2013 15:13:15 o'clock GMT> <Error> <OSB Kernel> <ukncsaviv679> <DEV_ukncsaviv679_OSB1> <[ACTIVE] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-024B9E71CAB3239C1D6A> <0000Jjvoh700fpG5yzG7yW1Gt4^i00001Z> <1357139595820> <BEA-382016> <Failed to instantiate router for service ProxyService ProcessAgencyMasterProcessMessageEbizRqABCSImplV1/proxySvc/process_Provider_PS: com.bea.wli.sb.management.BrokerManagementException: The configurations for the proxy service is in flux.
com.bea.wli.sb.management.BrokerManagementException: The configurations for the proxy service is in flux.
     at com.bea.wli.sb.pipeline.RouterContext.getInstance(RouterContext.java:178)
     at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:579)
     at com.bea.wli.sb.transports.TransportManagerImpl.receiveMessage(TransportManagerImpl.java:383)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:415)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl$4.run(JCATransportInboundOperationBindingServiceImpl.java:413)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.security.Security.runAs(Security.java:61)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.sendMessage(JCATransportInboundOperationBindingServiceImpl.java:413)
     at com.bea.wli.sb.transports.jca.binding.JCATransportInboundOperationBindingServiceImpl.invokeOneWay(JCATransportInboundOperationBindingServiceImpl.java:126)
     at com.bea.wli.sb.transports.jca.binding.JCAInboundRequestListener.post(JCAInboundRequestListener.java:39)
     at oracle.tip.adapter.sa.impl.inbound.JCAInboundListenerImpl.onMessage(JCAInboundListenerImpl.java:178)
     at oracle.tip.adapter.fw.jca.messageinflow.MessageEndpointImpl.onMessage(MessageEndpointImpl.java:507)
     at oracle.tip.adapter.db.InboundWork.onMessageImmediately(InboundWork.java:2094)
     at oracle.tip.adapter.db.InboundWork.onMessageDirectly(InboundWork.java:2043)
     at oracle.tip.adapter.db.InboundWork.onMessage(InboundWork.java:1923)
     at oracle.tip.adapter.db.InboundWork.transactionalUnitDirectly(InboundWork.java:1633)
     at oracle.tip.adapter.db.InboundWork.transactionalUnit(InboundWork.java:1582)
     at oracle.tip.adapter.db.InboundWork.runOnce(InboundWork.java:825)
     at oracle.tip.adapter.db.InboundWork.run(InboundWork.java:620)
     at oracle.tip.adapter.db.inbound.InboundWorkWrapper.run(InboundWorkWrapper.java:43)
     at weblogic.work.ContextWrap.run(ContextWrap.java:41)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:545)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
Can anyone please tell me what can be the proper reason for this?
Thanks in Advance!!

Answer 1

Roshni,
This exception has nothing to do with the delayed deployment. You will only see this exception when messages are arriving for the proxy service which is getting deployed. Which means you are changing the proxy configuration and activating the changes at the same time when few messages are being received by the proxy. So this exception is expected one.
As far as deployment time is concerned, definitely 10 mins is a huge time but deployment time varies on the basis of multiple factors -
1. Size of OSB repository (if you have huge projects deployed then deployment time may be more)
2. Deployment during peak load time (if you are doing the deployment when server is handling lot of messages then deployment may be delayed)
3. Available CPU and memory during deployment time
To figure out the root cause, you may take thread dumps of OSB servers during deployment and figure out that where the deployment process is getting stuck. You may also consider raising SR to support.
You may also try to redeploy after deleting the files under directory $MW_Home/user_projects/domains/<domain_name>/osb/config/sessions and restarting all the managed servers and admin server to see if it helps.
Regards,
Anuj