Cannot connect to Foreign JMS of Spazio
Hi all,
I'm trying to connect the OSB with smoe JMS product I've been testing, called Spazio. This product has the ability to transfer files over messaging service (propietery of Spazio, now know as Premieur).
Well, I have a .bindings file. I have the Java code. I start the OSB server, and then weblogic throws the following exception:
####<12:06:17 GMT+02:00 14/02/2011> <Error> <OSB Transform> <eli-dev-01> <admin> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <5cebd471a1c67174:6c3ea6b4:12e23a02793:-7fff-000000000000009b> <1297677977234> <BEA-382515> <Callout to java method "public static void mamram.spazio.files.Main.main(java.lang.String[]) throws java.lang.Exception" resulted in exception: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory
javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.fscontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at mamram.spazio.files.BaseSpazioFile.getFactory(BaseSpazioFile.java:52)
at mamram.spazio.files.BaseSpazioFile.getSession(BaseSpazioFile.java:61)
at mamram.spazio.files.BaseSpazioFile.init(BaseSpazioFile.java:47)
at mamram.spazio.files.BaseSpazioFile.<init>(BaseSpazioFile.java:36)
at mamram.spazio.files.SendFile.<init>(SendFile.java:18)
at mamram.spazio.files.Main.main(Main.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at stages.transform.runtime.JavaCalloutRuntimeStep$1.run(JavaCalloutRuntimeStep.java:173)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at stages.transform.runtime.JavaCalloutRuntimeStep.processMessage(JavaCalloutRuntimeStep.java:195)
at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.ClassNotFoundException: com.sun.jndi.fscontext.RefFSContextFactory
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at com.bea.wli.sb.resources.archive.classloader.HookedJarClassLoader.loadClass(HookedJarClassLoader.java:295)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at mamram.spazio.files.BaseSpazioFile.getFactory(BaseSpazioFile.java:52)
at mamram.spazio.files.BaseSpazioFile.getSession(BaseSpazioFile.java:61)
at mamram.spazio.files.BaseSpazioFile.init(BaseSpazioFile.java:47)
at mamram.spazio.files.BaseSpazioFile.<init>(BaseSpazioFile.java:36)
at mamram.spazio.files.SendFile.<init>(SendFile.java:18)
at mamram.spazio.files.Main.main(Main.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at stages.transform.runtime.JavaCalloutRuntimeStep$1.run(JavaCalloutRuntimeStep.java:173)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at stages.transform.runtime.JavaCalloutRuntimeStep.processMessage(JavaCalloutRuntimeStep.java:195)
at com.bea.wli.sb.pipeline.debug.DebuggerRuntimeStep.processMessage(DebuggerRuntimeStep.java:74)
at com.bea.wli.sb.stages.StageMetadataImpl$WrapperRuntimeStep.processMessage(StageMetadataImpl.java:346)
at com.bea.wli.sb.pipeline.PipelineStage.processMessage(PipelineStage.java:84)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Pipeline.processMessage(Pipeline.java:141)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.PipelineNode.doRequest(PipelineNode.java:55)
at com.bea.wli.sb.pipeline.Node.processMessage(Node.java:67)
at com.bea.wli.sb.pipeline.PipelineContextImpl.execute(PipelineContextImpl.java:922)
at com.bea.wli.sb.pipeline.Router.processMessage(Router.java:214)
at com.bea.wli.sb.pipeline.MessageProcessor.processRequest(MessageProcessor.java:99)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:593)
at com.bea.wli.sb.pipeline.RouterManager$1.run(RouterManager.java:591)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.pipeline.RouterManager.processMessage(RouterManager.java:590)
at com.bea.wli.sb.test.service.ServiceMessageSender.send0(ServiceMessageSender.java:329)
at com.bea.wli.sb.test.service.ServiceMessageSender.access$000(ServiceMessageSender.java:76)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:134)
at com.bea.wli.sb.test.service.ServiceMessageSender$1.run(ServiceMessageSender.java:132)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at com.bea.wli.sb.security.WLSSecurityContextService.runAs(WLSSecurityContextService.java:55)
at com.bea.wli.sb.test.service.ServiceMessageSender.send(ServiceMessageSender.java:137)
at com.bea.wli.sb.test.service.ServiceProcessor.invoke(ServiceProcessor.java:454)
at com.bea.wli.sb.test.TestServiceImpl.invoke(TestServiceImpl.java:172)
at com.bea.wli.sb.test.client.ejb.TestServiceEJBBean.invoke(TestServiceEJBBean.java:167)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl.invoke(TestService_sqr59p_EOImpl.java:353)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.bea.wli.sb.test.client.ejb.TestService_sqr59p_EOImpl_1033_WLStub.invoke(Unknown Source)
at com.bea.alsb.console.test.TestServiceClient.invoke(TestServiceClient.java:174)
at com.bea.alsb.console.test.actions.DefaultRequestAction.invoke(DefaultRequestAction.java:117)
at com.bea.alsb.console.test.actions.DefaultRequestAction.execute(DefaultRequestAction.java:70)
at com.bea.alsb.console.test.actions.ServiceRequestAction.execute(ServiceRequestAction.java:143)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:91)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.processActionPerform(SBConsoleRequestProcessor.java:91)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at com.bea.alsb.console.common.base.SBConsoleRequestProcessor.process(SBConsoleRequestProcessor.java:191)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at com.bea.alsb.console.common.base.SBConsoleActionServlet.doGet(SBConsoleActionServlet.java:49)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1129)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:687)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.StrutsStubImpl.processAction(StrutsStubImpl.java:76)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I'd appreciate some help figuring out why oh why the weblogic doesn't recognize a perfectly common jndi class....
Thanks!
Make sure you have fscontext.jar in the classpath of your weblogic server process.
Similar Messages
-
MDB connecting to Foreign JMS server in WL8.1
Hello,
I have this problem that I am hoping someone can help me with. There is a
MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
Server which is also a WL8.1 running in a remote server. This MDB is
attempting to subscribe to a topic hosted by that foreign server. In the
local WL8.1 I created a Foreign JMS Server via the adminconsole and mapped
the connection factory as well as destinations to the Foreign JMS Server.
The MDB (via its deployment descriptor) only refers to the local JNDI names
of the ConnectionFactory and Topic. Here are the scenarios concerning
security:
1) When security is turned off (user is in group everyone) everything works
fine. Messages published to the foreign Topic are received by the MDB in
the local WL8.1 server and processed.
2) When a security policy is applied to the Topic (via the remote
adminconsole), the MDB in the local server gets a 'permission denied'. I
now have to get around this by defining a principle for the MDB to run as
and to map the credentials of this principle to that of the user in the
remote environment with access permissions to the Topic.
3) When I specify the security identity of my MDB, its JNDI lookup of the
Topic fails with 'not found'.
4) Even when the security policy in the remote server is reverted back to
'everyone' (effectively turning security off) but leaving the MDB running as
the security principle, it still cannot find the Topic.
I hope this is something that people have seen and dealt with before.
Thanks for any and all help anyone can provide. I have also included the
deployment descriptors for this MDB:
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>MDB</ejb-name>
<ejb-class>sample.class.MDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
</message-driven-destination>
<security-identity>
<run-as>
<role-name>OutsideJMSUser</role-name>
</run-as>
</security-identity>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<security-role>
<role-name>OutsideJMSUser</role-name>
</security-role>
</assembly-descriptor>
</ejb-jar>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>MDB</ejb-name>
<message-driven-descriptor>
<pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>ForeignTopic</destination-jndi-name>
<connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
ndi-name>
</message-driven-descriptor>
<jndi-name>MDB</jndi-name>
</weblogic-enterprise-bean>
<security-role-assignment>
<role-name>OutsideJMSUser</role-name>
<principal-name>OutsideJMSUser</principal-name>
</security-role-assignment>
</weblogic-ejb-jar>
Thanks for the suggestion Greg. I have enabled trust between the two
domains and that has certainly cut down the variations of SecurityExceptions
that I get. Now I am consistently only getting a JMSSecurityException with
a access denied to the topic. I believe I have the credential mapped
correctly between the run-as local user and the remote authorized user.
Unfortunately the exception does not specify what username was rejected, it
would have been useful in determining the next debugging step to take.
I think you're right, I should engage the security forum for this. Thanks
again for the help.
"Greg Brail" <[email protected]> wrote in message
news:[email protected]...
> Hmm. The security people (on weblogic.developer.interest.security) might
> have to help you here, too. When you set the "runAs" identity for the MDB,
> it's doing everything, including the JNDI lookup, under that identity. So
if
> that identity is one that's recognized by the remote domain, then you
should
> be OK. One way to make your local identity recognized by the remote domain
> is to make your domains trusted, but you may wish not to do that.
>
> greg
>
> "Steve Chan" <[email protected]> wrote in message
> news:[email protected]...
> > Hello,
> >
> > I have this problem that I am hoping someone can help me with. There is
a
> > MDB deployed in a local WL8.1 that is trying to connect to a Foreign JMS
> > Server which is also a WL8.1 running in a remote server. This MDB is
> > attempting to subscribe to a topic hosted by that foreign server. In
the
> > local WL8.1 I created a Foreign JMS Server via the adminconsole and
mapped
> > the connection factory as well as destinations to the Foreign JMS
Server.
> > The MDB (via its deployment descriptor) only refers to the local JNDI
> names
> > of the ConnectionFactory and Topic. Here are the scenarios concerning
> > security:
> >
> > 1) When security is turned off (user is in group everyone) everything
> works
> > fine. Messages published to the foreign Topic are received by the MDB
in
> > the local WL8.1 server and processed.
> >
> > 2) When a security policy is applied to the Topic (via the remote
> > adminconsole), the MDB in the local server gets a 'permission denied'.
I
> > now have to get around this by defining a principle for the MDB to run
as
> > and to map the credentials of this principle to that of the user in the
> > remote environment with access permissions to the Topic.
> >
> > 3) When I specify the security identity of my MDB, its JNDI lookup of
the
> > Topic fails with 'not found'.
> >
> > 4) Even when the security policy in the remote server is reverted back
to
> > 'everyone' (effectively turning security off) but leaving the MDB
running
> as
> > the security principle, it still cannot find the Topic.
> >
> > I hope this is something that people have seen and dealt with before.
> > Thanks for any and all help anyone can provide. I have also included
the
> > deployment descriptors for this MDB:
> >
> > <ejb-jar>
> > <enterprise-beans>
> > <message-driven>
> > <ejb-name>MDB</ejb-name>
> > <ejb-class>sample.class.MDB</ejb-class>
> > <transaction-type>Container</transaction-type>
> > <message-driven-destination>
> > <destination-type>javax.jms.Topic</destination-type>
> > </message-driven-destination>
> > <security-identity>
> > <run-as>
> > <role-name>OutsideJMSUser</role-name>
> > </run-as>
> > </security-identity>
> > </message-driven>
> > </enterprise-beans>
> >
> > <assembly-descriptor>
> > <security-role>
> > <role-name>OutsideJMSUser</role-name>
> > </security-role>
> > </assembly-descriptor>
> >
> > </ejb-jar>
> >
> > <weblogic-ejb-jar>
> > <weblogic-enterprise-bean>
> > <ejb-name>MDB</ejb-name>
> > <message-driven-descriptor>
> > <pool>
> > <initial-beans-in-free-pool>1</initial-beans-in-free-pool>
> > </pool>
> > <destination-jndi-name>ForeignTopic</destination-jndi-name>
> >
> >
>
<connection-factory-jndi-name>ForeignConnectionFactory</connection-factory-j
> > ndi-name>
> > </message-driven-descriptor>
> > <jndi-name>MDB</jndi-name>
> > </weblogic-enterprise-bean>
> >
> > <security-role-assignment>
> > <role-name>OutsideJMSUser</role-name>
> > <principal-name>OutsideJMSUser</principal-name>
> > </security-role-assignment>
> >
> > </weblogic-ejb-jar>
> >
> >
>
>
-
MDB not connecting to Foreign JMS destination
I'm running WL 9.2 MP3 on Windows machine. I'm deploying a rudimentary MDB congured against as Foreign Service JMS provider against MQ V6.0 with local queue running on the same local machine.
I'm using Maven2 to build all the sub-projects - including my ejb project and enterprise application project. The EAR file deploys successfully without any errors (one minor warning about lack of explicity transactionsi in onMessage() method...). I don't see any errors but my MDB Connection Status is "disconnected" - I've enabled Debug for key sections under default and weblogic sections - still not errors of any kind but it does not connect! What can I do to find the problem?!
Here is my EJB definition:
public class AnotherBean extends GenericMessageDrivenBean implements
MessageDrivenBean, MessageListener {
private static final long serialVersionUID = 1L;
/* When the bean is activated, this method will be invoked
* @see javax.jms.MessageListener#onMessage(javax.jms.Message)
public void onMessage(Message msg) {
System.out.println("\n=========================================");
System.out.println("=> Message received!");
if (msg instanceof TextMessage) {
try {
System.out.println("=> Message: "
+ ((TextMessage) msg).getText());
} catch (JMSException e) {
e.printStackTrace();
// Place the message on to the reply queue (WLReplyQueue)
System.out.println("=========================================");
Here is my ejb-jar.xml:
<ejb-jar
xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/ejb-jar_2_1.xsd"
version="2.1">
<enterprise-beans>
<message-driven>
<ejb-name>AnotherBean</ejb-name>
<ejb-class>com.ibm.myclient.gems.ejb.AnotherBean</ejb-class>
<transaction-type>Container</transaction-type>
<activation-config>
<activation-config-property>
<activation-config-property-name>destinationType</activation-config-property-name>
<activation-config-property-value>javax.jms.Queue</activation-config-property-value>
</activation-config-property>
</activation-config>
</message-driven>
</enterprise-beans>
</ejb-jar>
Here is my weblogic-ejb-jar.xml:
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>AnotherBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>jms/WLReceiverQueue</destination-jndi-name>
<connection-factory-jndi-name>jms/WLReceiverQCF</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
WL JMS module is setup like this:
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schema
Location="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<foreign-server name="MQTestForeignServer">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="ReceiverDetails">
<local-jndi-name>jms/WLReceiverQueue</local-jndi-name>
<remote-jndi-name>MQSenderQueue</remote-jndi-name>
</foreign-destination>
<foreign-destination name="ReplyDetails">
<local-jndi-name>jms/WLReplyQueue</local-jndi-name>
<remote-jndi-name>MQReceiverQueue</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="ReceiverCF">
<local-jndi-name>jms/WLReceiverQCF</local-jndi-name>
<remote-jndi-name>MQSenderQCF</remote-jndi-name>
</foreign-connection-factory>
<foreign-connection-factory name="ReplyCF">
<local-jndi-name>jms/WLReplyQCF</local-jndi-name>
<remote-jndi-name>MQReceiverQCF</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:/ C:/JNDI-Directory</connection-url>
</foreign-server>
</weblogic-jms>Thanks for the tips - I solved the problem. I first recreated my .bindinds file making sure that both QCF objects are in there (it turned out that only ONE of them was there and not the other). Next, I also removed an extra space " " from the URL reference in the Foreign JMS service setup in the console:
was like this initially:
<connection-url>file:/ C:/JNDI-Directory</connection-url>
and I changed it to this - removing single space after first "/":
<connection-url>file:/C:/JNDI-Directory</connection-url>
Restarted the whole thing and it worked! Thanks again. -
ORA-25228 error occurs when Foreign JMS Server connecting to the Oracle AQ
Hi,
I configure of a Foreign JMS Server that uses the Oracle JDBC Driver to connect to the AQ Topic. I use OSB messaging proxy service as a JMS client to connect the Foreign JMS Server. After the launch, I get the following error:
####<Jan 30, 2013 4:51:49 AM MSK> <Error> <EJB> <EPRUSARW0520> <osb_server1> <RequestEJB7826682746890400115XX35047bed.13c85602eea.X7f53> <<anonymous>> <> <0000Jm8w2Es6qI_5xRh8iW1H1sMk0001sD> <1359507109078> <BEA-010079> <An error occurred while attempting to receive a message from JMS for processing by a message-driven bean: oracle.jms.AQjmsException: JMS-120: Dequeue failed
Nested exception: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
The exception is : oracle.jms.AQjmsException: JMS-120: Dequeue failed
at oracle.jms.AQjmsError.throwEx(AQjmsError.java:315)
at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1620)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:1035)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:960)
at oracle.jms.AQjmsConsumer.receiveFromAQ(AQjmsConsumer.java:938)
at oracle.jms.AQjmsConsumer.receive(AQjmsConsumer.java:790)
at weblogic.deployment.jms.WrappedMessageConsumer.receive(WrappedMessageConsumer.java:201)
at weblogic.ejb.container.internal.JMSMessagePoller$1.run(JMSMessagePoller.java:262)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.ejb.container.internal.JMSConnectionPoller.doPrivilegedJMSAction(JMSConnectionPoller.java:2752)
at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:257)
at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:351)
at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:483)
at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:499)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at line 11
ORA-25228: timeout or end-of-fetch during message dequeue from MDM.ALL_NSI
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:397)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:389)
at oracle.jdbc.driver.T4Caqdq.processError(T4Caqdq.java:497)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
at oracle.jdbc.driver.T4Caqdq.doOAQDQ(T4Caqdq.java:183)
at oracle.jdbc.driver.T4CConnection.doDequeue(T4CConnection.java:4704)
at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17863)
at oracle.jdbc.driver.PhysicalConnection.dequeue(PhysicalConnection.java:17949)
at oracle.jdbc.OracleConnectionWrapper.dequeue(OracleConnectionWrapper.java:1624)
at weblogic.jdbc.wrapper.XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
at weblogic.jdbc.wrapper.JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection.dequeue(Unknown Source)
at oracle.jms.AQjmsConsumer.jdbcConnectionDequeueCheck25242(AQjmsConsumer.java:1713)
at oracle.jms.AQjmsConsumer.jdbcDequeue(AQjmsConsumer.java:1295)
... 13 moreHowever, when I put message to AQ topic, the OSB proxy receives and processes it. But SQLException occurs every five seconds and pollute logs.
Request help to resolve this.
Thanks in advance.
Regards
Alexander.Maybe this can help: http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::p11_question_id:4018285967344
-
MDB cannot connect to JMS destination using Foreign Server
Hi everyone,
I have configured foreign jms server in weblogic but when MDB tries to connect to specific queue, it gets the following exception:
I would really appreciate if anyone could help me.
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010096> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination or bind to JCA resource adapter: xcg2/smsInQueue. Connection failed after 2 attempts. The MDB will attempt to reconnect/rebind every 10 seconds. This log message will repeat every 600 seconds until the condition clears.>
<Sep 28, 2012 5:23:34 PM CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: SmsReceiver is unable to connect to the JMS destination: xcg2/smsInQueue. The Error was:
[EJB:011010]The JMS destination with the JNDI name: jmsxcg.out could not be found. Please ensure that the JNDI name in the weblogic-ejb-jar.xml or corresponding annotation is correct, and the JMS destination has been deployed.
javax.naming.InvalidNameException: jmsxcg.out: [LDAP: error code 34 - Invalid DN]; remaining name 'jmsxcg.out' NestedException Message is :jmsxcg.out: [LDAP: error code 34 - Invalid DN]>
MDB annotation looks like this:
@MessageDriven(name="SmsReceiver", mappedName="xcg2/smsInQueue",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue")
@TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)
public class SmsReceiverBean implements MessageListener
weblogic-ejb-jar.xml excerpt:
<weblogic-enterprise-bean>
<ejb-name>SmsReceiver</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<connection-factory-jndi-name>echoQueueConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>600</trans-timeout-seconds>
</transaction-descriptor>
<dispatch-policy>MdbSmsWorkManager</dispatch-policy>
</weblogic-enterprise-bean>
and the configuration of foreign-server:
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/weblogic-jms">
<foreign-server name="serverr">
<sub-deployment-name>Subdeployment</sub-deployment-name>
<foreign-destination name="sms queue>
<local-jndi-name>xcg2/smsInQueue</local-jndi-name>
<remote-jndi-name>jmsxcg.out</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="Connection Factory">
<local-jndi-name>echoQueueConnectionFactory</local-jndi-name>
<remote-jndi-name>QueueConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>com.tibco.tibjms.naming.TibjmsInitialContextFactory</initial-context-factory>
<connection-url>tibjmsnaming://xx.xx.xx.xx:7222</connection-url>
</foreign-server>
</weblogic-jms>
PS. I'm able to connect to the weblogic jndi, get connectionFactory echoQueueConnectionFactory, then lookup queue and grab messages so that's i suspect there is something wrong with configurationHmm - I'm not sure what's going on. Two thoughts --
Thought 1 - According to my (admittedly minimal) research, Tibco is complaining about a syntax error in the lookup name. Perhaps the problem has something to do with your use of a "." in the queue name "jmsxcg.out": WL or Tibco JNDI might be interpreting the "." as a subcontext or some-such. Perhaps try renaming the queue to "jmsxcg_out" throughout (in Tibco and in your Foreign JMS reference).
Thought 2 - It probably won't make a difference, but you might want try specifying the source destination via the "destinationJndiName" config property instead of via "mappedName".
@MessageDriven(
name = "MyMDB",
activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destinationJndiName",
propertyValue = "MyQueue") // Ext. JNDI Name
)HTH,
Tom -
Javax.naming.NameNotFoundException for foreign JMS Connection factory
I have a foreign jms server configured and when I try and test it I get a Name not found exception.
javax.naming.NameNotFoundException: Unable to resolve 'jms.SSLQueueConnectionFactory' Resolved jms [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'jms.SSLQueueConnectionFactory' Resolved jms]; remaining name 'SSLQueueConnectionFactory'
The config.xml looks ok
<ForeignJMSServer
ConnectionURL="ssl://eaid1-jms.ges.symantec.com:7243"
JNDIProperties="" Name="JMS Proxy Dev" Targets="TeamWorksServer">
<ForeignJMSConnectionFactory
LocalJNDIName="jms.SSLQueueConnectionFactory"
Name="MyForeign JMS Connection Factory"
PasswordEncrypted="{3DES}Es94ikW1TZzBFyDp+3/gktRtDaHWI6j/"
RemoteJNDIName="SSLQueueConnectionFactory" Username="weblogicUser"/>
<ForeignJMSDestination LocalJNDIName="jms.WEBLOGIC.TEST.QUEUE"
Name="MyForeign JMS Destination" RemoteJNDIName="WEBLOGIC.TEST.QUEUE"/>
</ForeignJMSServer>
The code i took from the QueueSend example
package com.symantec.utils.jms;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.Hashtable;
import javax.jms.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
/** This example shows how to establish a connection
* and send messages to the JMS queue. The classes in this
* package operate on the same JMS queue. Run the classes together to
* witness messages being sent and received, and to browse the queue
* for messages. The class is used to send messages to the queue.
* @author Copyright (c) 1999-2006 by BEA Systems, Inc. All Rights Reserved.
public class QueueSend
// Defines the JNDI context factory.
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
// Defines the JMS context factory.
public final static String JMS_FACTORY="jms.SSLQueueConnectionFactory";
// Defines the queue.
public final static String QUEUE="WEBLOGIC.TEST.QUEUE";
private QueueConnectionFactory qconFactory;
private QueueConnection qcon;
private QueueSession qsession;
private QueueSender qsender;
private Queue queue;
private TextMessage msg;
* Creates all the necessary objects for sending
* messages to a JMS queue.
* @param ctx JNDI initial context
* @param queueName name of queue
* @exception NamingException if operation cannot be performed
* @exception JMSException if JMS fails to initialize due to internal error
public void init(Context ctx, String queueName)
throws NamingException, JMSException
qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
qcon = qconFactory.createQueueConnection();
qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queue = (Queue) ctx.lookup(queueName);
qsender = qsession.createSender(queue);
msg = qsession.createTextMessage();
qcon.start();
* Sends a message to a JMS queue.
* @param message message to be sent
* @exception JMSException if JMS fails to send message due to internal error
public void send(String message) throws JMSException {
msg.setText(message);
qsender.send(msg);
* Closes JMS objects.
* @exception JMSException if JMS fails to close objects due to internal error
public void close() throws JMSException {
qsender.close();
qsession.close();
qcon.close();
private static void readAndSend(QueueSend qs)throws IOException, JMSException
BufferedReader msgStream = new BufferedReader(new InputStreamReader(System.in));
String line=null;
boolean quitNow = false;
do {
System.out.print("Enter message (\"quit\" to quit): \n");
line = msgStream.readLine();
if (line != null && line.trim().length() != 0) {
qs.send(line);
System.out.println("JMS Message Sent: "+line+"\n");
quitNow = line.equalsIgnoreCase("quit");
} while (! quitNow);
private static InitialContext getInitialContext(String url)
throws NamingException
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, url);
return new InitialContext(env);
/** main() method.
* @param args WebLogic Server URL
* @exception Exception if operation fails
public static void main(String[] args) throws Exception
InitialContext ic = getInitialContext("t3://tus1bpmappdin01.ges.symantec.com:7501");
QueueSend qs = new QueueSend();
qs.init(ic, QUEUE);
readAndSend(qs);
qs.close();
Any suggestions would be appreciated
RegardsI have a foreign jms server configured and when I try and test it I get a Name not found exception.
javax.naming.NameNotFoundException: Unable to resolve 'jms.SSLQueueConnectionFactory' Resolved jms [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'jms.SSLQueueConnectionFactory' Resolved jms]; remaining name 'SSLQueueConnectionFactory'
The config.xml looks ok
<ForeignJMSServer
ConnectionURL="ssl://eaid1-jms.ges.symantec.com:7243"
JNDIProperties="" Name="JMS Proxy Dev" Targets="TeamWorksServer">
<ForeignJMSConnectionFactory
LocalJNDIName="jms.SSLQueueConnectionFactory"
Name="MyForeign JMS Connection Factory"
PasswordEncrypted="{3DES}Es94ikW1TZzBFyDp+3/gktRtDaHWI6j/"
RemoteJNDIName="SSLQueueConnectionFactory" Username="weblogicUser"/>
<ForeignJMSDestination LocalJNDIName="jms.WEBLOGIC.TEST.QUEUE"
Name="MyForeign JMS Destination" RemoteJNDIName="WEBLOGIC.TEST.QUEUE"/>
</ForeignJMSServer>
The code i took from the QueueSend example
package com.symantec.utils.jms;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStreamReader;
import java.util.Hashtable;
import javax.jms.*;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;
/** This example shows how to establish a connection
* and send messages to the JMS queue. The classes in this
* package operate on the same JMS queue. Run the classes together to
* witness messages being sent and received, and to browse the queue
* for messages. The class is used to send messages to the queue.
* @author Copyright (c) 1999-2006 by BEA Systems, Inc. All Rights Reserved.
public class QueueSend
// Defines the JNDI context factory.
public final static String JNDI_FACTORY="weblogic.jndi.WLInitialContextFactory";
// Defines the JMS context factory.
public final static String JMS_FACTORY="jms.SSLQueueConnectionFactory";
// Defines the queue.
public final static String QUEUE="WEBLOGIC.TEST.QUEUE";
private QueueConnectionFactory qconFactory;
private QueueConnection qcon;
private QueueSession qsession;
private QueueSender qsender;
private Queue queue;
private TextMessage msg;
* Creates all the necessary objects for sending
* messages to a JMS queue.
* @param ctx JNDI initial context
* @param queueName name of queue
* @exception NamingException if operation cannot be performed
* @exception JMSException if JMS fails to initialize due to internal error
public void init(Context ctx, String queueName)
throws NamingException, JMSException
qconFactory = (QueueConnectionFactory) ctx.lookup(JMS_FACTORY);
qcon = qconFactory.createQueueConnection();
qsession = qcon.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
queue = (Queue) ctx.lookup(queueName);
qsender = qsession.createSender(queue);
msg = qsession.createTextMessage();
qcon.start();
* Sends a message to a JMS queue.
* @param message message to be sent
* @exception JMSException if JMS fails to send message due to internal error
public void send(String message) throws JMSException {
msg.setText(message);
qsender.send(msg);
* Closes JMS objects.
* @exception JMSException if JMS fails to close objects due to internal error
public void close() throws JMSException {
qsender.close();
qsession.close();
qcon.close();
private static void readAndSend(QueueSend qs)throws IOException, JMSException
BufferedReader msgStream = new BufferedReader(new InputStreamReader(System.in));
String line=null;
boolean quitNow = false;
do {
System.out.print("Enter message (\"quit\" to quit): \n");
line = msgStream.readLine();
if (line != null && line.trim().length() != 0) {
qs.send(line);
System.out.println("JMS Message Sent: "+line+"\n");
quitNow = line.equalsIgnoreCase("quit");
} while (! quitNow);
private static InitialContext getInitialContext(String url)
throws NamingException
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, JNDI_FACTORY);
env.put(Context.PROVIDER_URL, url);
return new InitialContext(env);
/** main() method.
* @param args WebLogic Server URL
* @exception Exception if operation fails
public static void main(String[] args) throws Exception
InitialContext ic = getInitialContext("t3://tus1bpmappdin01.ges.symantec.com:7501");
QueueSend qs = new QueueSend();
qs.init(ic, QUEUE);
readAndSend(qs);
qs.close();
Any suggestions would be appreciated
Regards -
MDB Credential Mapper for connecting to secured foreign JMS - Need WLST
Hello All
Weblogic 10.3.0
I am in a situation where i have the MDB trying to read messages from secure foreign jms . The ejb-jar and weblogic-jar.xml has the right values like
ejb-jar.xml
==========
<assembly-descriptor>
<security-role>
<role-name>admin</role-name>
</security-role>
</assembly-descriptor>
weblogic-ejb-jar.xml
==============
<run-as-principal-name>CFAMJMS</run-as-principal-name>
<security-role-assignment>
<role-name>admin</role-name>
<principal-name>CFAMJMS</principal-name>
</security-role-assignment>
</weblogic-ejb-jar>
If i am correct , to connect to the Secured Foreign JMS Connection - There are couple of steps involved
1) To create a new security wlsuser under myrealm - called CFAMJMS
2) Each MDB deployed as part of the ear file - I need to perform the credential Mapping - Means
EJB Component Credential Mappings - create a WLS user of the name CFAMJMS and supply the Remote JMS User Name and Password .
Today , i perform the setp 2 ) using the Weblogic Admin Console . Need to automate the same using wlst script . Please helpHi,
Similar question was answered in this thread...
JMS integration with Tibco EMS via SSL
Could you please check if your TIBCO EMS is ssl enabled .Login on TIBCO EMS using putty and then type show config and check for the following parameter ssl_server_identity ,ssl_server_key . Go to the path mentioned in these two properties and see if the certificate with .pem is present there.
As you are getting following error in the log
Caused by: javax.jms.JMSSecurityException: Can not initialize SSL client: no trusted certificates are set
In TIBCO we need trusted store .pem certificate to make it ssl enabled.
Cheers,
Vlad
It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts)
https://forums.oracle.com/forums/ann.jspa?annID=893 -
Foreign jms connection factory username and password
I have to connect to TIBCO as the foreign JMS. I have created a foreign JMS server and configured JNDI properties including username and password. I configured a connection factory and specified username and password as well. Finally, I configured foreign destination.
In web.xml and corresponding welogic.xml, I am using the resource-ref with Container authentication.
With the above, I always get the following exception.
javax.jms.JMSSecurityException: Not permitted
at com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:499)
at com.tibco.tibjms.TibjmsSession._createProducer(TibjmsSession.java:697)
at com.tibco.tibjms.TibjmsQueueSession.createSender(TibjmsQueueSession.java:123)
The above code works fine under the following circumstances:
* If I don't use any username and passwords.
* If I pass the username and password to the connection factory when creating the connection. According to the documentation here (http://e-docs.bea.com/wls/docs81/jms/j2ee_components.html#1033768) doing so in an error:(
Any ideas or suggestions?Even though I had configured things in the web.xml and weblogic.xml, I didn't use them. So, instead of using global JNDI, I used java:comp/env JNDI. Once, I used the correct JNDI, the connection is working... I will continue to do further testing.
> I have to connect to TIBCO as the foreign JMS. I
> have created a foreign JMS server and configured JNDI
> properties including username and password. I
> configured a connection factory and specified
> username and password as well. Finally, I configured
> foreign destination.
>
> In web.xml and corresponding welogic.xml, I am using
> the resource-ref with Container authentication.
>
> With the above, I always get the following exception.
>
>
> javax.jms.JMSSecurityException: Not permitted
> at
> t
> com.tibco.tibjms.Tibjmsx.buildException(Tibjmsx.java:4
> 99)
> at
> t
> com.tibco.tibjms.TibjmsSession._createProducer(TibjmsS
> ession.java:697)
> at
> t
> com.tibco.tibjms.TibjmsQueueSession.createSender(Tibjm
> sQueueSession.java:123)
>
> The above code works fine under the following
> circumstances:
> * If I don't use any username and passwords.
> * If I pass the username and password to the
> connection factory when creating the connection.
> According to the documentation here
> e
> (http://e-docs.bea.com/wls/docs81/jms/j2ee_components.
> html#1033768) doing so in an error:(
>
> Any ideas or suggestions? -
Foreign JMS server connection issue.
Hi All,
We are migrating a JMS application from websphere 6.1 to weblogic 10.3. The message queue resides in a TIBCO EMS server.
We are trying to configure the foreign JMS server through JMS Module in the admin console. We are getting the following error will deploying the application.
+<May 4, 2009 12:32:52 AM PDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: TxnMessageSubscriber is unable to connect to the JMS destination: weblogic.bbmdb-txn.jms/system+
module-0-jms.xml. The Error was:
Can not get distribute destination information. The destination JNDI name is weblogic.bbmdb-txn.jms/systemmodule-0-jms.xml, the provider URL is null>
we have provided the connection URL in "JNDI Connection URL" column in the foreign server setup page.
Is there any other thing that need to be configured?I m facing the same problem, we are using Weblogic Server 10.3.
We have defined a cluster on one Weblogic server and have created one managed server in the cluster machine and the other managed server in another machine.
We are using Foreign JMS and I m getting the error as follow:
####<Jun 19, 2009 3:30:53 PM IST> <Warning> <EJB> <iflexpkw513> <Managed1> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1245405653881> <BEA-010061> <The Message-Driven EJB: TestJMSALSB is unable to connect to the JMS destination: fcssi/FCSSI. The Error was:
Can not get distribute destination information. The destination JNDI name is fcssi/FCSSI, the provider URL is null>
Not able to understand what is the problem here...
ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar id="ejb-jar_ID">
<enterprise-beans>
<message-driven>
<ejb-name>TestJMSALSB</ejb-name>
<ejb-class>samplemdb.TestJMSALSB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination id="MessageDrivenDestination_1169302343246">
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
</ejb-jar>
weblogic-ejb-jar.xml :
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar
xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
<weblogic-enterprise-bean>
<ejb-name>TestJMSALSB</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>fcssi/FCSSI</destination-jndi-name>
<connection-factory-jndi-name>iflex/fcssiQCF</connection-factory-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Can anyone provide some help on this..... -
Problem connecting weblogic OSB with IBM websphere via foreign JMS
Hi All,
I am trying to setup Foreign JMS. My configuration doesn’t work.
Could you please let me know if I am missing anything .
All my configuration details are done as specified in this link http://www.oracle.com/technology/products/integration/service-bus/docs/osb-websphere-whitepaper.pdf
Here is what I did.
In OSB sbconsole
OSB business Service ENDPoint URL jms://webspherehost:9082/sampleQueuemanager/sampleQueue
In websphere
Created a queue connection factory and a queue from the webspehere administrator console.
Modified JSMAdmin.config to enable the following…/Java/bin/JMSAdmin.config.
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
PROVIDER_URL=file:/C:/JNDI-Directory
Ran JSMAdmin.bat to bind the JNDI
def qcf(sampleQueuemanager) qmanager(QMGR) HOSTNAME(webspherehost) PORT(1327) TRANSPORT(CLIENT)
def Q(sampleQueue) queue(sampleQueue) qmanager(QMGR) PERSISTENCE(PERS)
InitCtx> dis ctx
JMSADM4089 InitCtx
.bindings java.io.File
bck_.bindings java.io.File
a sampleQueuemanager com.ibm.mq.jms.MQQueueConnectionFactory
a sampleQueue com.ibm.mq.jms.MQQueue
4 Object(s)
0 Context(s)
4 Binding(s), 2 Administered
In weblogic admin console
Created foreign JMS, destination and connection factory as mentioned in the following link.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/jms_modules/foreign_servers/CreateForeignConnectionFactories.html
When I execute business service from OSB sbconsole, this is what I get.
+The invocation resulted in an error: [JMSPool:169803]JNDI lookup of the JMS connection factory sampleQueuemanager failed: javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: HTTP/1.1 400 Bad Request]].+
Thanks
sivaLittle confusing. Are we not supposed to use osb host name and port along with foreign connection factory created in weblogic for OSB BS?.
You said: jms://webspherehost:9082/sampleQueuemanager/sampleQueue
We have to jms://osbhost:port/ForeignQueueManagerInWeblogic/ForeignQueueInWeblogic
Manoj -
Error of Foreign JMS server connecting to durable subscriber topic
Weblogic server domain is trying to connect to the durable topic configured on the other weblogic domain. (Both domain are running on weblogic 9.2 platform)
WLI 9.2 Event generator is TestPinFJ is the MDB which is trying to listen message from Foreign JMS.
Following error we have got when I did following configuration for connecting to durable topic using foreign JMS.
<EJB> <BEA-010061> <The Message-Driven EJB: TestPinFJ is unable to connect to the JMS destination: TestQueue. The Error was:
java.lang.IllegalArgumentException: port out of range:-16>
Detail configuration is as follows:
Foreign JMS : TestFS
General:
JNDI Connection URL: t3://10.20.65.95:9004 TestClient123 (where TestClient123 is the client id for durable subscriber topic )
Destinations:
Local JNDI Name: TestQueue
Remote JNDI Name: TestTopic
Connection Factories :
Local JNDI Name: TestQCF
Remote JNDI Name: TestTCF
My suspect is the JNDI connection URL is incorrect. Please advice how to configure JNDI conn url while connecting to durable topic with client id?hi Hussain,
I am the collegue of the person created this thread.
Thaks for the input. can u please suggest me how do we configure connectionfactory and JSM topic to durable subscription with ClientID.Shoudl th eClientID be same for JMSTopic and ConectionFactory?
In Domain "A" I have created JMS topic with durable subscriber wioth client ID "TestClient123" and created a conenctionfacory with same client ID "TestClient123" .
In Domain "B" i created a foreign JMS connecting to topic in Domain A using connection facatory created in Domain "A" configured as as remoteConnectionFActory.
Also the JNDI Connection URL is : t3://10.20.65.95:9004
"weblogic.jms.common.InvalidClientIDException: Client id, Testclient1, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
Nested exception: weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)".
weblogic.jms.common.InvalidClientIDException: Client id, EAIEXTTestClient123, is in use. The reason for rejection is "The JNDI name weblogic.jms.connection.clientid.TestClient123 was found, and was bound to an object of type weblogic.jms.frontend.FEClientIDSingularAggregatable : FEClientIDSingularAggregatable(SingularAggregatable(<9222810352589496374.1>:1):TestClient123)"
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)"
IS there any chnage i need to make to get this connectivity between Domain A and B working?
Appreciate your help on this. -
Does weblogic automatically pools Foreign JMS Connections ?
I cofigured MQ Series connection factories and queues in my weblogic using Foreign JNDI provider feature.
I am sending messages to MQ using common JMS approach
public void sendMessage(List lnTransactionList) throws JMSException {
XAQueueConnection conn = null;
try {
conn = mqConnectionFactory.createXAQueueConnection("", "");
QueueSession session = conn.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
TextMessage message = session.createTextMessage();
sender.send(message);
} catch (JMSException ex) {
throw ex;
} finally {
conn.close();
I know that by default weblogic does some pooling for JMS connections and sessions.
Does it work for third-party JMS Connections ?
I checked class names for XAQueueConnection, QueueSession, Queue that weblogic returns for my MQ JNDI objects.
All of them are from IBM libraries.
So I think that default pooling doesn`t work in this case.Yes, third party pooling is supported and heavily leveraged. JMS resources are automatically pooled when a JMS connection factory is accessed via a standard EJB or Servlet "resource reference" (it is not enough simply to specify a foreign JMS server mapping). You can verify pooling is working by monitoring the stats on the foreign vendor itself, or by monitoring the pool Stats.
Similar to WebLogic JDBC connection pools, pooled JMS resources still implement all of the public interfaces of a foreign vendor and redirect method invocations on these interfaces to the underlying class. This includes proprietary interfaces.
Doc links:
Pooling/Wrapping/Res-Refs:
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/j2ee.htm#g1329180
FAQ entry on same:
http://download.oracle.com/docs/cd/E15523_01/web.1111/e13727/interop.htm#i1009836
Tom -
Foreign JMS Providers with WebLogic Server does not close connection
Hello All,
We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
context factory to bind MQ.
We found a number of LDAP connections are getting opened by JNDIMapper, but it's
not getting closed.
Can some one give some clue to this ?
Also any suggestion to serve the current purpose is welcome.
Thanks,
Sudarson
What version are you using? "wlsmqseries.zip" does enlisting of MQ JMS
sessions in XA transactions, but WLS 8.1 does that for you out of the box.
If you're using 8.1, it would be better to use the new 8.1 features for
foreign JMS providers.
A place to start is the "Using WebLogic JMS with EJBs and Servlets" section
of the JMS programming documentation for 8.1, and there have been many other
posts on this newsgroup with details. (There also appear to be quite a few
customers using this feature in their own systems, judging from the number
of posts.)
greg
"sudarson" <[email protected]> wrote in message
news:40bf05ea$1@mktnews1...
>
> Reposting the message. Awaiting response from newsgroup or BEA
> Thanks,
> Sudarson
> "sudarson" <[email protected]> wrote:
> >
> >Hello All,
> >
> >We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for
integrating
> >WebLogic Server with MQ so that we can incorporate XA transactions. We
> >use LDAP
> >context factory to bind MQ.
> >
> >We found a number of LDAP connections are getting opened by JNDIMapper,
> >but it's
> >not getting closed.
> >
> >Can some one give some clue to this ?
> >
> >Also any suggestion to serve the current purpose is welcome.
> >
> >Thanks,
> >Sudarson
>
-
Calling Foreign JMS in SOA Suite 11g JMS Adapter
Hi,
Just want to get some guidance in the implementation of Foreign JMS in WebLogic 10.3.
I followed the creation of the Foreign JMS Server using this document:
http://download.oracle.com/docs/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/foreign_servers/CreateForeignServers.html
I am trying to connect to a remote Weblogic 10.3 JMS queue but cannot get pass the JDev wizard stage.
I need to call the foreign JMS via the Fusion 11g JMS Adapter but cannot lookup the destination from the JDev wizard. My composite will produce a message that will end up in the remote queue.
Has anybody got this to work? Is this supported in JMS Adapter? I've read quite a few using MDB to call the Foreign JMS but not JMS Adapter.
Regards,
RobertPlease refer to the following document that shows how to access remote wls jms queues and topics. This is the preferred way when accessing remote wls destinations.
http://download.oracle.com/docs/cd/E17904_01/integration.1111/e10231/adptr_jms.htm#BABJACJA
Thanks
Aman -
ClassNotFoundException for initial-context-factory using foreign JMS p.
Hi,
I am currently working on migrating an application from weblogic 9 to weblogic 10 and I bumped into this issue while MDB connecting to JMS.
[Loaded cz.jaksky.riskscenario.beans.RiskScenarioServiceLocalHome from file:/C:/SVN/app-WLS10-FRESH/app-deploy/servers/myserver/tmp/_WL_user/performance/nyubkw/point-interfaces.jar]
<17-Sep-2012 11:01:27 o'clock CEST> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PerformanceAsyncRequestBean is unable to connect to the JMS destination: wls.AsyncQueue. The Error was:
javax.naming.NoInitialContextException: Cannot instantiate class: cz.jaksky.common.jms.JMSInitialContextFactory [Root exception is java.lang.ClassNotFoundException: cz.jaksky.common.jms.JMSInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:657)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:182)
at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.jms.common.CDS$2.run(CDS.java:486)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:131)
at weblogic.jms.common.CDS.lookupDestination(CDS.java:480)
at weblogic.jms.common.CDS.lookupDDAndCalloutListener(CDS.java:345)
at weblogic.jms.common.CDS.access$100(CDS.java:41)
at weblogic.jms.common.CDS$DDListenerRegistrationTimerListener.timerExpired(CDS.java:193)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)
Caused by: java.lang.ClassNotFoundException: cz.jaksky.common.jms.JMSInitialContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:247)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:654)
... 23 more
I am using foreign JMS provider with provided mapping. Config follows:
ejb-jar.xml:
<enterprise-beans>
<message-driven>
<ejb-name>PortfolioRetrieverAsyncRequestBean</ejb-name>
<ejb-class>cz.jaksky.common.async.AsynchronousRequestMessageBean</ejb-class>
<transaction-type>Bean</transaction-type>
<acknowledge-mode>Auto-acknowledge</acknowledge-mode>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>Durable</subscription-durability>
</message-driven-destination>
<message-selector>
<![CDATA[ Service IN ('PortfolioRetriever')
AND MessageType = 'request'
AND BigBox = FALSE
]]>
</message-selector>
</message-driven>
</enterprise-beans>
weblogic-ejb-jar.xml:
<weblogic-enterprise-bean>
<ejb-name>PortfolioRetrieverAsyncRequestBean</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>64</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>wls.AsyncQueue</destination-jndi-name>
<initial-context-factory>weblogic.jndi.WLInitialContextFactory</initial-context-factory>
<connection-factory-jndi-name>ServiceLocatorAsyncQueueFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<dispatch-policy>PortfolioAsyncQueueWorkManager</dispatch-policy>
</weblogic-enterprise-bean>
jmsconfig-jms.xml
<foreign-server name="TibjmsAsyncServer">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="AsyncQueue.LOCAL.prgdwm355410.7001">
<local-jndi-name>wls.AsyncQueue</local-jndi-name>
<remote-jndi-name>AsyncQueue.LOCAL.prgdwm355410.7001</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="FTQueueConnectionFactory">
<local-jndi-name>ServiceLocatorAsyncQueueFactory</local-jndi-name>
<remote-jndi-name>FTQueueConnectionFactory</remote-jndi-name>
</foreign-connection-factory>
<initial-context-factory>cz.jaksky.common.jms.JMSInitialContextFactory</initial-context-factory>
<connection-url>tcp://JUSD-FTPOIA.jaksky.com:22542,tcp://JUSD-FTPOB.jaksky.com:22543</connection-url>
</foreign-server>
Module containing this MDB is packed as an ear file with following structure:
APP-INF/lib/modules.jar - contains AsynchronousRequestMessageBean class
APP-INF/lib/interface.jar - contains JMSInitialContextFactory (class used for initial-context-factory)
portfolio-async.jar
META-INF/ejb-jar.xml content pasted above
META-INF/webogic-ejb-jar.xml content pasted above
Weblogic system classpath doesn't contain any application sepcific libraries.
This set up was working for weblogic 9 without any problem. I am just wondering what the problem is whether I am faceing class loading issue or JMS configuration issue and how to resolve it.
Edited by: user13047709 on 18-Sep-2012 07:15
Edited by: user13047709 on 18-Sep-2012 07:16Hi,
When working with a non-WebLogic JNDI provider (or a non-WebLogic JMS provider), the non-WebLogic client classes must be made available to the classloader of the calling application in WebLogic Server. This is usually accomplished by adding them to the system classpath.
In your case, WebLogic is looking for a proprietary/foreign JNDI Context Factory class named "cz.jaksky.common.jms.JMSInitialContextFactory", which means you need to make sure that a jar/dir that contains the non-WebLogic class "JMSInitialContextFactory.class" is in the classpath.
The configuration for this should be similar in WL9 and WL10. It could be that your classpath is already setup to reference the foreign class, but it refers to a directory/jar that you haven't setup yet on your WL10 host.
HTH,
Tom
Maybe you are looking for
-
Hp Laserjet 4200, Printer Virus or Software Failure?
Have been using a HP Laserjet 4200/4300 series, very few issues, very good printer. Background: Small office, this printer is attached to my computer but able to be used by 4 other machines on the network. We are using everything from windows ME to
-
Why are my thumbnails suddenly smaller
My daughter, who is 1.5 years old, was hitting the keys on my keyboard and now my thumbnails in IPhoto are too small. I can't figure out how to change them back. They are hard to see now.
-
Sales informations systems issue
Dear Gurus, I have problem in SALES INFO SYSTEMS, unable to generate standard reports like Customer, material wise MCTA,MCTC and MCTE sales orgn wise etc. I maintained Satistics currency in Sales Orgn and maintained Relevant for statistics in Custo
-
Process instruction sheet configuration
Dear Guru's, I am exploring SAP PP PI and not much into it,since it has been few months. I want to know more abt the PI SHEETS, and the way to configure it. Since my client is not using PI sheets, i want to explore this area and want to know more abt
-
My mbp came with Snow Leopard, I upgraded to Lion, but its not in my purchases now.
I have an early 2011 MBP, it came with Snow Leopard preinstalled. I later upgraded to Lion when it was released. I did a clean wipe on the hard drive and a fresh reinstall of Snow Leopard with the intention of re loading Lion also. It's not showing i