-
1. Re: Problem with Unresponsive EPR
marklittle Sep 6, 2007 9:52 AM (in response to claudio_br)Try upgrading to 4.2GA please.
-
2. Re: Problem with Unresponsive EPR
claudio_br Sep 6, 2007 8:40 PM (in response to claudio_br)In 4.2G.A the problem was resolved.
Thanks Mark! -
3. Re: Problem with Unresponsive EPR
marklittle Sep 7, 2007 4:23 AM (in response to claudio_br)Glad to help.
-
4. Re: Problem with Unresponsive EPR
claudio_br Oct 3, 2007 2:56 PM (in response to claudio_br)The problem appear in Jboss 4.2.GA.
In my log:2007-10-03 00:17:08,218 INFO [com.buscape.esb.CepEsb] addCep( ----------------- Cep -> Id: 'null' Cep: '27275260' Logradouro: 'RETIRO' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' null ----------------- ,false) 2007-10-03 00:17:13,218 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address jms://localhost/queue/cep_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > 2007-10-03 00:17:13,235 INFO [com.buscape.esb.CepEsb] addCep( ----------------- Cep -> Id: 'null' Cep: '27275260' Logradouro: 'RETIRO' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' null ----------------- ,false) 2007-10-03 00:17:13,270 WARN [com.buscape.esb.CepEsb] com.buscape.generico.BusinessException: cep:Cep com número já existente ----------------- Cep -> Id: 'null' Cep: '27275260' Logradouro: 'RETIRO' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' null ----------------- com.buscape.generico.BusinessException: cep:Cep com número já existente ----------------- Cep -> Id: 'null' Cep: '27275260' Logradouro: 'RETIRO' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' null ----------------- at com.buscape.cep.facade.CepFACADEBean.isValido(CepFACADEBean.java:302) at com.buscape.cep.facade.CepFACADEBean.persiste(CepFACADEBean.java:80) at sun.reflect.GeneratedMethodAccessor605.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:112) at org.jboss.ejb3.interceptor.InvocationContextImpl.proceed(InvocationContextImpl.java:166) at org.jboss.ejb3.interceptor.EJB3InterceptorsInterceptor.invoke(EJB3InterceptorsInterceptor.java:63) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:76) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:77) at org.jboss.ejb3.security.Ejb3AuthenticationInterceptor.invoke(Ejb3AuthenticationInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:46) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:106) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:278) at org.jboss.ejb3.remoting.IsLocalInterceptor.invokeLocal(IsLocalInterceptor.java:79) at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:70) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:103) at $Proxy280.persiste(Unknown Source) at com.buscape.esb.CepEsb.addCep(CepEsb.java:139) at com.buscape.esb.CepEsb.executar(CepEsb.java:88) at sun.reflect.GeneratedMethodAccessor565.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 2007-10-03 00:17:13,271 WARN [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Unexpected exception caught while processing the action pipeline org.jboss.soa.esb.actions.ActionProcessingFaultException: com.buscape.generico.BusinessException: cep:Cep com número já existente ----------------- Cep -> Id: 'null' Cep: '27275260' Logradouro: 'RETIRO' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' null ----------------- at com.buscape.esb.CepEsb.executar(CepEsb.java:104) at sun.reflect.GeneratedMethodAccessor565.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.processMethods(ActionProcessorMethodInfo.java:102) at org.jboss.soa.esb.listeners.message.OverriddenActionLifecycleProcessor.process(OverriddenActionLifecycleProcessor.java:74) at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:265) at org.jboss.soa.esb.listeners.message.MessageAwareListener$1.run(MessageAwareListener.java:297) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) 2007-10-03 00:17:18,235 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address jms://localhost/queue/cep_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > 2007-10-03 00:17:18,259 WARN [org.jboss.soa.esb.client.ServiceInvoker] Unexpected exception during attempted message delivery over Courier for EPR [EPR: PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> >] for Service [JBossESB-Internal:DeadLetterService]. java.lang.NullPointerException 2007-10-03 00:17:18,259 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > 2007-10-03 00:17:18,260 WARN [com.buscape.webservice.CepWS] org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to Service [JBossESB-Internal:DeadLetterService]. Check for errors. org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to Service [JBossESB-Internal:DeadLetterService]. Check for errors. at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:262) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:185) at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:219) at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:165) at com.buscape.webservice.CepWS.enviarEsb(CepWS.java:55) at com.buscape.webservice.CepWS.addCep(CepWS.java:198) at sun.reflect.GeneratedMethodAccessor604.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.wsf.spi.invocation.InvocationHandlerJSE.invoke(InvocationHandlerJSE.java:74) at org.jboss.wsf.stack.jbws.ServiceLifecycleInvocationHandler.invoke(ServiceLifecycleInvocationHandler.java:59) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:206) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:396) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:260) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:177) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110) at org.jboss.wsf.spi.invocation.EndpointServlet.service(EndpointServlet.java:72) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) 2007-10-03 00:17:18,357 INFO [com.buscape.esb.CepEsb] addCep( ----------------- Cep -> Id: 'null' Cep: '27273575' Logradouro: 'Rua Resende' SiglaPais: 'br' UnidadeFederativa -> Id: '9' Sigla: 'RJ' Nome: 'Rio de Janeiro ' Cidade -> Id: '9541' Nome: 'Volta Redonda' CoordenanadaXY -> CoordenadaX: '-44.104167' CoordenadaY: '-22.523056' ----------------- ,false) 2007-10-03 00:17:23,358 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address jms://localhost/queue/cep_esb/>, <wsa:ReferenceProperties jbossesb:java.naming.factory.initial : org.jnp.interfaces.NamingContextFactory/>, <wsa:ReferenceProperties jbossesb:java.naming.provider.url : localhost/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > 2007-10-03 00:17:23,374 WARN [org.jboss.soa.esb.client.ServiceInvoker] Unexpected exception during attempted message delivery over Courier for EPR [EPR: PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> >] for Service [JBossESB-Internal:DeadLetterService]. java.lang.NullPointerException 2007-10-03 00:17:23,375 INFO [org.jboss.soa.esb.client.ServiceInvoker] Unresponsive EPR: EPR: PortReference < <wsa:Address jms://localhost/queue/DeadMessageQueue/>, <wsa:ReferenceProperties jbossesb:destination-type : queue/>, <wsa:ReferenceProperties jbossesb:specification-version : 1.1/>, <wsa:ReferenceProperties jbossesb:connection-factory : ConnectionFactory/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/jms/> > 2007-10-03 00:17:23,375 WARN [com.buscape.webservice.CepWS] org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to Service [JBossESB-Internal:DeadLetterService]. Check for errors. org.jboss.soa.esb.listeners.message.MessageDeliverException: Failed to deliver message to Service [JBossESB-Internal:DeadLetterService]. Check for errors. at org.jboss.soa.esb.client.ServiceInvoker.post(ServiceInvoker.java:262) at org.jboss.soa.esb.client.ServiceInvoker.deliverAsync(ServiceInvoker.java:185) at org.jboss.soa.esb.client.ServiceInvoker.deliverToDeadLetterService(ServiceInvoker.java:219) at org.jboss.soa.esb.client.ServiceInvoker.deliverSync(ServiceInvoker.java:165) at com.buscape.webservice.CepWS.enviarEsb(CepWS.java:55) at com.buscape.webservice.CepWS.addCep(CepWS.java:198) at sun.reflect.GeneratedMethodAccessor604.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.wsf.spi.invocation.InvocationHandlerJSE.invoke(InvocationHandlerJSE.java:74) at org.jboss.wsf.stack.jbws.ServiceLifecycleInvocationHandler.invoke(ServiceLifecycleInvocationHandler.java:59) at org.jboss.ws.core.server.ServiceEndpointInvoker.invoke(ServiceEndpointInvoker.java:206) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest(RequestHandlerImpl.java:396) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:260) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost(RequestHandlerImpl.java:177) at org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:110) at org.jboss.wsf.spi.invocation.EndpointServlet.service(EndpointServlet.java:72) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:179) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595)
In the first addCep I get Unresponsive EPR. The ESB automaticly rerun addCep (with cep=27275260) and I get a BusinessException. In all next calls (example: with cep=27273575) I get MessageDeliverException: Failed to deliver message to Service
Where is the problem?
Thanks -
5. Re: Problem with Unresponsive EPR
claudio_br Oct 4, 2007 12:48 PM (in response to claudio_br)I changed my code to update the reference of ServiceInvoker always that I get MessageDeliverException. But this didn´t work.
I still get Unresponsive EPR.
Please, help me! -
6. Re: Problem with Unresponsive EPR
claudio_br Oct 4, 2007 2:17 PM (in response to claudio_br)Why do I get Unresponsive EPR after some hours of processing?
-
7. Re: Problem with Unresponsive EPR
kconner Oct 5, 2007 4:59 AM (in response to claudio_br)Can you send me your server.log file?
-
8. Re: Problem with Unresponsive EPR
claudio_br Oct 5, 2007 10:52 AM (in response to claudio_br)Hi Kevin
I sent the server.log to your email.
Please, help me.
Thanks -
9. Re: Problem with Unresponsive EPR
claudio_br Oct 8, 2007 9:06 AM (in response to claudio_br)Hi Kevin,
I added the action "org.jboss.soa.esb.actions.SystemPrintln" at end of pipeline.
I am running again my application.
When the problem to occurs I wil send to you the server.log.
Thanks! -
10. Re: Problem with Unresponsive EPR
beve Oct 8, 2007 9:16 AM (in response to claudio_br)Hi Claudio,
just a thought as I seem to recall have a similar problem while back. This had to do with old EPRs in the juddi database. Perhaps it would be worth checking if you havn't already.
What I'm thinking is that the DeadLetterService has more then one EPR in the db, one of which might be "outdated".
Regards,
Daniel -
11. Re: Problem with Unresponsive EPR
kconner Oct 8, 2007 9:58 AM (in response to claudio_br)Hiya Claudio.
Great, let me know how it goes. -
12. Re: Problem with Unresponsive EPR
kconner Oct 8, 2007 10:01 AM (in response to claudio_br)For the record, the logs Claudio sent showed that the original service (not the DLS) was unresponsive so we are trying to work out why this could be.
They also showed that the message was redelivered as expected. -
13. Re: Problem with Unresponsive EPR
beve Oct 8, 2007 10:07 AM (in response to claudio_br)Ah, well that still sounds like the problem we were having. We had some old ERPs that had not been removed. The old EPRs had invalid values for our connection factory which was previously clustered.
Perhaps they are getting redelivered because of the roundrobin policy and a correct EPR is being used...
Kevin, do you think this could be the cause or am I way off:)
Thanks,
Daniel -
14. Re: Problem with Unresponsive EPR
kconner Oct 8, 2007 10:31 AM (in response to claudio_br)Hiya Daniel.
I think that there might be two issues here and the second may well be what you are describing. :)