Hi Dinusha, Yeah, you could create public JIRA for the improvement also document it.
@adding 'Shadsha' as she was struggling to get it connect FYI: Shadsha please communicate with Dinusha to get more details if you still can't connect On Fri, Aug 14, 2015 at 3:00 PM, Dinusha Senanayaka <dinu...@wso2.com> wrote: > Hi Dushan, > > I was running JBoss with port offset. Reverting back to default port > solved the issue. There should be some client property in ESB side to tell > the remote connection port of JBoss server. Not sure what it is though. > > Regards, > Dinusha. > > On Fri, Aug 14, 2015 at 5:45 PM, Dushan Abeyruwan <dus...@wso2.com> wrote: > >> Hi Dinusha, >> There has been lot's of class loader issues when comes to EJBMediator >> connection to JBoss, have shared the artifacts archived [1], we have to >> have jboss client (osgied) to be placed in ESB, anyway did you check by >> writing a simple JAVA client to invoke those services ? >> >> if with ESB we still getting above mentioned issue, we could try to add >> following parameter to synapse.properties under bean you have defined >> synapse.beanstalks.jack.jboss.naming.client.ejb.context=true >> >> anyway, shall we first check the java client ? >> >> [1] >> https://drive.google.com/drive/u/0/folders/0BxjKaX2u7UlUZXRaVURnWkxMcHc >> [2] >> http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling >> >> On Fri, Aug 14, 2015 at 7:50 AM, Dinusha Senanayaka <dinu...@wso2.com> >> wrote: >> >>> Forgot to send the exception >>> >>> org.apache.synapse.SynapseException: Error while invoking >>> 'getClosestStore' method via reflection. >>> at >>> org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:79) >>> at >>> org.apache.synapse.mediators.bean.enterprise.EJBMediator.mediate(EJBMediator.java:132) >>> at >>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:77) >>> at >>> org.apache.synapse.mediators.AbstractListMediator.mediate(AbstractListMediator.java:47) >>> at >>> org.apache.synapse.mediators.base.SequenceMediator.mediate(SequenceMediator.java:131) >>> at >>> org.apache.synapse.core.axis2.ProxyServiceMessageReceiver.receive(ProxyServiceMessageReceiver.java:166) >>> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:180) >>> at >>> org.apache.synapse.transport.passthru.ServerWorker.processEntityEnclosingRequest(ServerWorker.java:411) >>> at >>> org.apache.synapse.transport.passthru.ServerWorker.run(ServerWorker.java:183) >>> at >>> org.apache.axis2.transport.base.threads.NativeWorkerPool$1.run(NativeWorkerPool.java:172) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >>> at java.lang.Thread.run(Thread.java:722) >>> Caused by: java.lang.reflect.InvocationTargetException >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.lang.reflect.Method.invoke(Method.java:601) >>> at >>> org.apache.synapse.mediators.bean.BeanUtils.invokeInstanceMethod(BeanUtils.java:74) >>> ... 12 more >>> Caused by: java.lang.IllegalStateException: No EJB receiver available >>> for handling [appName:,modulename:EJBDemo,distinctname:] combination for >>> invocation context org.jboss.ejb.client.EJBClientInvocationContext@5d5f1834 >>> at >>> org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:584) >>> at >>> org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:119) >>> at >>> org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:181) >>> at >>> org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136) >>> at >>> org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121) >>> at >>> org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104) >>> at $Proxy17.getClosestStore(Unknown Source) >>> >>> On Fri, Aug 14, 2015 at 5:14 PM, Dinusha Senanayaka <dinu...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> I'm trying EJB sample given in [1], [2]. But getting following >>>> exception while invoking the proxy. Found this [3] which is reported >>>> earlier, but for me issue comes continuously not intermittent. Also [4] >>>> seems to be related. but not sure how to set this property with ESB. >>>> >>>> Appreciate any help to sort this. >>>> >>>> [1] >>>> http://wso2.com/library/articles/2012/06/ejb-mediator-action-wso2-esb-450/ >>>> [2] http://www.dushantech.com/2012/06/syntaxhighlighter.html >>>> [3] https://wso2.org/jira/browse/ESBJAVA-1487 >>>> [4] >>>> http://stackoverflow.com/questions/11975396/no-ejb-receiver-available-for-handling >>>> >>>> >>>> Regards, >>>> Dinusha. >>>> >>>> >>>> -- >>>> Dinusha Dilrukshi >>>> Associate Technical Lead >>>> WSO2 Inc.: http://wso2.com/ >>>> Mobile: +94725255071 >>>> Blog: http://dinushasblog.blogspot.com/ >>>> >>> >>> >>> >>> -- >>> Dinusha Dilrukshi >>> Associate Technical Lead >>> WSO2 Inc.: http://wso2.com/ >>> Mobile: +94725255071 >>> Blog: http://dinushasblog.blogspot.com/ >>> >> >> >> >> -- >> Dushan Abeyruwan | Technical Lead >> Technical Support-Bloomington US >> PMC Member Apache Synpase >> WSO2 Inc. http://wso2.com/ >> Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* >> Mobile:(001)812-391-7441 >> >> > > > -- > Dinusha Dilrukshi > Associate Technical Lead > WSO2 Inc.: http://wso2.com/ > Mobile: +94725255071 > Blog: http://dinushasblog.blogspot.com/ > -- Dushan Abeyruwan | Technical Lead Technical Support-Bloomington US PMC Member Apache Synpase WSO2 Inc. http://wso2.com/ Blog:*http://www.dushantech.com/ <http://www.dushantech.com/>* Mobile:(001)812-391-7441
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
