JMS Topic Write throws JMSClientException:055143: Destinati must be a queue
Hi,
1) created JMS Server
2) created JMS module
3) Created JMS Topic, created Subdeployment and associated queue to the subdeployment
4) Created JMS Queue and associated Queue to the subdeployment
5) created connection factory and associated connection factory to the subdeployment
6) Created JMS Adapter connection pool.
7) Associated JMS Adapter connection pool and connection factory.
8) Redeployed JMS Adapter.
In my BPEL process i consumed JMS Adapter as a partner link.
If I try to write in JMS queue created above, BPEL process works fine.
But if I try to write in JMS Topic, i am getting following exception
Any solution for the following.
===============================================================
ERRJMS_ERR_CR_QUEUE_PROD.
ERRJMS_ERR_CR_QUEUE_PROD.
Unable to create Queue producer due to JMSException.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:711)
at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:642)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:180)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:337)
at oracle.tip.adapter.jms.WLSJmsInvoker.invoke(WLSJmsInvoker.java:109)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:166)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:140)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.executeJcaInteraction(JCAInteractionInvoker.java:311)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeJcaReference(JCAInteractionInvoker.java:548)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAInteractionInvoker.invokeAsyncJcaReference(JCAInteractionInvoker.java:508)
at oracle.integration.platform.blocks.adapter.fw.jca.cci.JCAEndpointInteraction.performAsynchronousInteraction(JCAEndpointInteraction.java:491)
at oracle.integration.platform.blocks.adapter.AdapterReference.post(AdapterReference.java:247)
at oracle.integration.platform.blocks.mesh.AsynchronousMessageHandler.doPost(AsynchronousMessageHandler.java:142)
at oracle.integration.platform.blocks.mesh.MessageRouter.post(MessageRouter.java:197)
at oracle.integration.platform.blocks.mesh.MeshImpl.post(MeshImpl.java:214)
at sun.reflect.GeneratedMethodAccessor937.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at oracle.integration.platform.metrics.PhaseEventAspect.invoke(PhaseEventAspect.java:71)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy293.post(Unknown Source)
at oracle.fabric.CubeServiceEngine.postToMesh(CubeServiceEngine.java:806)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:258)
at com.collaxa.cube.engine.ext.common.InvokeHandler.__invoke(InvokeHandler.java:1059)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handleNormalInvoke(InvokeHandler.java:586)
at com.collaxa.cube.engine.ext.common.InvokeHandler.handle(InvokeHandler.java:130)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:74)
at com.collaxa.cube.engine.ext.bpel.common.wmp.BaseBPELActivityWMP.perform(BaseBPELActivityWMP.java:158)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:2543)
at com.collaxa.cube.engine.CubeEngine._handleWorkItem(CubeEngine.java:1165)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1071)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:73)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:220)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:328)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4430)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:4361)
at com.collaxa.cube.engine.CubeEngine._createAndInvoke(CubeEngine.java:698)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:555)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:673)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:293)
at sun.reflect.GeneratedMethodAccessor1034.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.jee.intercept.MethodInvocationInvocationContext.proceed(MethodInvocationInvocationContext.java:104)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor$1.run(JpsAbsInterceptor.java:94)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.runJaasMode(JpsAbsInterceptor.java:81)
at oracle.security.jps.ee.ejb.JpsAbsInterceptor.intercept(JpsAbsInterceptor.java:112)
at oracle.security.jps.ee.ejb.JpsInterceptor.intercept(JpsInterceptor.java:105)
at sun.reflect.GeneratedMethodAccessor900.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.jee.intercept.JeeInterceptorInterceptor.invoke(JeeInterceptorInterceptor.java:69)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy276.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:39)
at com.collaxa.cube.engine.ejb.impl.bpel.BPELDeliveryBean_5k948i_ICubeDeliveryLocalBeanImpl.handleInvoke(Unknown Source)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:35)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:140)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.process(BaseDispatchTask.java:88)
at com.collaxa.cube.engine.dispatch.BaseDispatchTask.run(BaseDispatchTask.java:64)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: weblogic.jms.common.InvalidDestinationException: [JMSClientExceptions:055143]Destination must be a queue, PocJmsModule!PocJmsTopic
at weblogic.jms.common.Destination.checkDestinationType(Destination.java:112)
at weblogic.jms.client.JMSSession.setupJMSProducer(JMSSession.java:2830)
at weblogic.jms.client.JMSSession.createProducer(JMSSession.java:2858)
at weblogic.jms.client.JMSSession.createSender(JMSSession.java:2605)
at oracle.tip.adapter.jms.JMS.JMSConnection.createProducer(JMSConnection.java:698)
... 87 more
[2011-07-19T06:56:33.927-04:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool-4.thread-3] [userId: <anonymous>] [ecid: 4c1276542546757f:14f086aa:131000ef8b1:-8000-00000000001abc77,0:1:100079473] [APP: soa-infra] [composite_name: JMSQueueWrite_Composite] [component_name: queueWrite_bpel] [component_instance_id: 103412] JCABinding=> [default/JMSQueueWrite_Composite!1.0*soa_c000666f-6301-48aa-805d-d92a5e62a021.TopicWriteJMSAdapter]:Produce_Message One-way operation Produce_Message() failed
[2011-07-19T06:56:33.929-04:00] [soa_server1] [ERROR] [] [oracle.soa.adapter] [tid: orabpel.invoke.pool-4.thread-1] [userId: <anonymous>] [ecid: 4c1276542546757f:14f086aa:131000ef8b1:-8000-00000000001abc76,0:1:100079475] [APP: soa-infra] [composite_name: JMSQueueWrite_Composite] [component_name: queueWrite_bpel] [component_instance_id: 103413] JCABinding=> JMSQueueWrite_Composite:TopicWriteJMSAdapter [ Produce_Message_ptt::Produce_Message(opaque) ] Could not invoke operation 'Produce_Message' against the 'JMS Adapter' due to: [[
BINDING.JCA-12137
===============================================================
Thanks
Ajay
6) Created JMS Adapter connection pool.Did you set IsTopic attribute here for the outbound connection pool to true...
Instead of creating custom connection pools, easiest approach would be to use eis/wls/Queue as the jndi name in the partner Link for queues and eis/wls/Topic for topics.
Similar Messages
-
How to resolve JMSExceptions:045032 when creating a JMS Topic
I am using Weblogic 12c (12.1.1.0). I have created a new managed server. I have created a JMS server targeted to the new managed server. I have created a JMS module targeted to the new managed server. I have created a JMS Subdeployment which targets both the new managed server and the new JMS server. I've created a JMS connection factory which targets the JMS Subdeployment.
Now everything I've done so far has worked fine. No problems. The problem happens when I try to create a JMS Topic. I select to create a new regular Topic; I target the new JMS Subdeployment, and after selecting the Subdeployment Weblogic refreshes the page and shows the JMS server. So this all seems OK. When I try to finish and create the JMS Topic, I get the following error: [JMSExceptions:045032]While attempting to create destination [TOPIC_NAME] in module [MODULE_NAME] the JMS server [MANAGED_SERVER_NAME] could not be found.
Any thoughts on this? I've googled around but haven't found anything useful.I replicated this at my end. This is caused by Subdeployment target to both the new managed server and the new JMS server.
Please try creating a new Subdeployment and target it to JMS Server only, as described in the document below.
https://docs.oracle.com/cd/E24329_01/web.1211/e24385/best_practice.htm#JMSAD633
"Populate the subdeployment only with JMS servers - not WebLogic servers. Only include the JMS servers that you wish to host destinations. This ensures that when the JMS resources are configured, they are targeted to the correct JMS servers. For modules that support non-distributed destinations, the subdeployment must only reference a single JMS Server. If you have a mix of distributed and non-distributed destinations, use two modules each with its own subdeployment."
Best Regards
Luz -
Invoke Error while inserting consumed JMS Topic msg in table thru DBadapter
Hi All,
To brief abt my requirement, I am integrating Peoplesoft HRMS module with Oracle SOA i.e.,
+
1. PS HRMS module will publish a JMS msg into a JMS Topic
2. I will consume the same msg using JMS adapter consume operation in my SOA project
3. The Payload(msg) is coming into RECEIVE activity and thru ASSIGN activity invoking the DB adapter to insert the msg into a table.
4. INVOKE activity is throwing the below error(along with the error, able to see the payload in INVOKE activity )
<part name="summary"> +
<summary>*Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'insert' failed due to: Mapping Not Found Exception. The mapping [EMPLID] for descriptor [class insert.Employee] could not be found. The input xml record had an element [Employee/EMPLID]. Most likely the wrong xml input variable (not matching the expected xsd) was passed to this invoke. Make sure that the input xml is valid relative to the xsd and that the mapping exists in the Mappings.xml. If an old version of the descriptor without this mapping has been loaded by the database adapter, you may need to bounce the app server. If the same descriptor is described in two separate Mappings.xml files, make sure both versions include this attribute/mapping. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. *</summary>
</part>
Please, provide some suggestions.
Regards,
SatyaHi Satya,
Try replacing the Assign activity with a Transform acitivity.
Also please check the schema that comes of the DB adapter is having the similar sort of definition that you are getting in your input.
What I mean is to check for length of fields, type of the fields etc.
Thanks,
Deepak.
Edited by: DeepakDabbiru on Oct 23, 2012 3:29 AM -
Getting DOM Parsing Exception in translator while Dequeuing the message from JMS topic
Hi All,
Hope you all doing good.
I have an issue.
I am running on 11.1.1.5 SOA suite version on Linux.
In my aplication I have 4 projects which are connected by with topic/queue.
But in one of the communication, the JMS topic throws me the below error in the log, but dequeue happend perfectly fine and the application runs smoothly.
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project1>
JmsConsumer_sendInboundMessage:[des
tination = <TOPIC NAME> subscriber = <Consumer project name>
Error (DOM Parsing Exception in translator.[[
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
) while preparing to send XMLRecord JmsXMLRecord
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project name>
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:603)
at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:403)
at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1161)
at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1048)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
But when I try putting the archived data on this topic, it throws me the same error but even dequeuing doesnt happen.
I have extracted the payload and validated against the xsd, it looks fine and even the validator doesnt throw me any error.
But I guess I am missing something, which I am immediately not getting.
Please let me know, if I am soemthing here which is causing this erro.
Thanks,
ChandruI searched about this error, but no luck.
First time when the message dequeues, the consumer can consume the message but throws the error in the log.
But when I put the message back into queue from archive directory, the consumer doesnt consume message and throws me the same error.
Does anyone faced this sort of issue.
I checked my xsd throughly, and validated it externally. but didnt fine any error.
if anyone knows, suggest me how to resolve this issue.
thanks & regards
Chandru -
Messages in JMS Topic Error destination
Hi,
I have a JMS Topic with an error destination queue configured. Now, In our scenario , there are two subscribers of topic for the same message. Suppose for a message published to topic, subscriber1 is able to processes message successfully but subscriber2 throws errors when processing the same message.
1. Once the redelivery limit is reached and subscriber2 continues to throw exception, Will the message get en queued to Error Destination (in spite of the fact that subscriber 1 has processed the same message successfully) ?
2. For a consumer (e.g MDB) listening to Error destination and consuming error messages, Is it possible to determine which topic subscriber was unable to process the message ?
Please let me know
Regards,
ArifHere it depends on the state of the message, if the message is visible then the message would be available for consumption, else it is not. In case the subscriber 2 failed to consume the message and the message is still visible then a retry would be made, else the message would not be retried.
In case the message is visible then the message would be move to the error queue based on the configured redelivery attempts.
Additionally, an MDB can find the destination using the getJMSDestination() call. But as per my understanding we will only be able to get the name of the last destination which in this case would be error queue:
http://docs.oracle.com/javaee/1.4/api/javax/jms/Message.html#getJMSDestination%28%29 -
Receive asynchronous message from JMS topic over web service
Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
SivaSo you expect clients to be receiving SOAP messages over HTTP? In this
case, the clients are really servers that are capable of servicing SOAP
requests, correct? And how about the senders: are they also using
SOAP/HTTP to send messages that are delivered to the receivers?
It should be possible to write this yourself using JMS not as the
transport, but as a mechanism for distributing the message to a set of
clients. You'll need to implement a Web Service for publishing to a
topic, an operation for registering an end point to recieve messages,
and an MDB (or other form of JMS subscriber) executing on the server to
relay the message to the end point.
Siva wrote:
Hi,
I have a JMS topic and I want to expose it as a web service so that clients can
make durable subcription to the topic and receive messages asynchronously. What
is the best way of doing this ? Is there a portable (to other containers) way
of do this ? If not, is there a web logic specific way of doing this ?
Thanks,
Siva -
JNDI Lookup for JMS Topic issue.......!
Hi,
Our application is deployed on two nodes (MS1 and MS2 in a cluster) and I created JMSServer on MS1, JMS ConnectionFactory and Distributed Topic are targeted on both MS1 and MS2 i.e on entire cluster.
We have the JMS Code in postStart() method of starup class which extends ApplicationLifecycleListener which would create the JMS Subcriber and set the message listener on to it.
code snippet:
System.out.println("createSubscriber called");
subSession = topicConnection.createTopicSession(false, Session.AUTO_ACKNOWLEDGE);
// Lookup for the Topic
Topic cadTopic = (Topic) ctx.lookup("JMSTopicLog4j");
System.out.println("Topic is: " + cadTopic.getTopicName());
// Create JMS Subscriber.
cadSubscriber = subSession.createSubscriber(cadTopic);
// Set the listener to Subscriber.
cadSubscriber.setMessageListener(new CADMessageListener());
topicConnection.start();
When I start the cluster (managed Servers MS1 and MS2) for the first time and deploy the application on them (entire cluster) it works well i.e. message listener is active and able to receive messages published by publisher but when I try to stop and start MS2 it gives the following exception during server startup
javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''
javax.naming.NameNotFoundException: Unable to resolve 'JMSTopicLog4j'. Resolved ''; remaining name 'JMSTopicLog4j'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:362)
Note: I thought my application context is getting started before JNDI tree is loaded but I could see that it is able to lookup the ConnectionFactory and throws the given exception when it comes to lookup code of JMS Topic.
is there any configuration issue or am I missing something? Please help me in this regard.
Thanks in advance.
Kris.Very interesting, I mean in the sense that we have the same setup, but instead of topic we are using the queues.
And our problem is exactly the same,deployment works but after restart same javax.naming.NameNotFoundException happens on server 2. -
JMS Topics translate to Queues behind the scenes?
Hi There:
In discussing JMS implementation with coworkers I found someone mention that even if we created topics and have users subscribed to those topics, those topics get translated into individual queues per topic per user. So the queue in affect gets subscribed to the topic and the user is actually subscribed to the queue. While I can imagine that this kind of implementation makes sense for reliable delivery, I find it hard to believe that this is the way JMS implements topics internally.
Can someone throw some lite on this please?RajMap wrote:
Well the content gets replicated to the queues when it is not necessary to do that. If I am not doing reliable delivery, then the message that is published to the topic is delivered to the users that are subscribed to the topic at the point in time, and to do that I do not see the need to implement it via queues. Like I mentioned before for reliable delivery it makes sense to implement them to queues.
And secondly it might lead to an explosion of queues internally. Consider for e.g. if we have say 5000 topics and about 10-15 subscribers for each topic, it will result in up to 75000 queues. I am not sure if that is a big number for queues, but it feel larger than what I designed for because in my mind I am thinking 4000-5000 topics.you are making a lot of conjectures based on entirely abstract concepts. what is a "queue"? what is a "topic"? these are just abstract ideas used by the jms spec. the words "queue" and "topic" define a bunch of behavior, but say nothing about how you need to implement that behavior. is 75000 queues a lot of queues? who knows, depends how i choose to implement a queue. is the data "replicated" to each queue in a topic? who knows, depends how i choose to store data. you can't make any of these statements outside of a specific implementation of the jms spec. -
JMS Topic - Can there be multiple pubs/subs
I belive JMS Topic supports multiple publishers, subscribers
for the same topic right? I am sure about the multiple subsicriber part because
I have done it before (with one publisher). However, I am changing my
design to have multiple publishers now as well. Is this possible?
Thanks
Ashique wrote:
> I belive JMS Topic supports multiple publishers, subscribers
> for the same topic right?
Yes.
> I am sure about the multiple subsicriber part because
> I have done it before (with one publisher). However, I am changing my
> design to have multiple publishers now as well. Is this possible?
>
Yes.
>
> Thanks
-
JMS Topic - Deliver to only one Durable Subscriber
Hi,
Is it possible to put a message onto a topic but only have it delivered to a single durable subscriber?
I realise this breaks the rules of what a topic is but this is for a scenario where a single subscriber has errored when processing the original message from the topic. I am putting a user interaction process to recover it and if the user selects ‘resubmit’ I want to put the message back on the topic but only deliver it to the one subscriber that failed to process the message.
My ways to achieve this (in order of preference) would be.
1. JMS Adapter
2. Writing Java to use JMS API
If neither of these are possible than:
3. Create a System Resubmit queue and have every composite look for message on the resubmit queue (with their client ID) as well as the normal topic they use
Of course I would like to avoid 3 as it introduces a complication into every process we create that takes messages from a JMS Topic.
Thanks for your help.
RobertI could suggest a (dirty) trick:
all subscribers subscribe to the topic using a filter (message selector, http://docs.oracle.com/javaee/6/tutorial/doc/bnceh.html#bncer)
SUBSCRIBER1 uses:
destination = ALL OR SUBSCRIBER1
SUBSCRIBER2 uses:
destination = ALL OR SUBSCRIBER2
etc
The first message has the property destination set to ALL, so all subscribers will process it.
The resubmitted message will have destination = SUBSCRIBER<N>, where N is the failed subscriber -
Error :- while accessing JMS topic messages in Design Studio
Hi,
Am getting this error while clicking update button in Design Studio to populate a dataobject using JMS Topic messages sent by oracle Bpel manager.
IMessageSourceReceiver->messageReceive: javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory. Root exception is java.lang.ClassNotFoundException: oracle.j2ee.rmi.RMIInitialContextFactory
Can you tell me where to find the class and how to use it to resolve the problem?
P.S:-
If you can provide any document how oracle BPEL process manager use JMS topic to send message to Oracle BAM and display in reports.
Thanks in advance
Cheers,
Praveen G
iSOFT R& D Pvt Ltd.
[email protected]Hi,
We are using BAM 10.1.3 against BPEL 10.1.2 and we cannot get it to work.
We are also getting the error "javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory...." .
Our startup paramters for Enterprise Source “Oracle (AS JMS and OJMS) looks like this:
JMS*".;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jndi.jar;C:\OracleBAM\OC4J\j2ee\home\oc4j.jar;C:\OracleBAM\OC4J\j2ee\home\oc4jclient.jar;C:\OracleBAM\OC4J\j2ee\home\lib\oc4j-internal.jar;C:\OracleBAM\OC4J\j2ee\home\lib\ejb.jar;C:\OracleBAM\OC4J\j2ee\home\lib\servlet.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jta.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax88.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax77.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmxri.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmx_remote_api.jar;C:\OracleBAM\OC4J\j2ee\home\lib\adminclient.jar;C:\OracleBAM\OC4J\j2ee\home\ojspc.jar;C:\OracleBAM\OC4J\j2ee\home\jazn.jar;C:\OracleBAM\OC4J\opmn\lib\optic.jar;C:\OracleBAM\OC4J\rdbms\jlib\aqapi.jar;"".;c:\TIBCO\JMS\clients\java\tibjms.jar;c:\TIBCO\JMS\clients\java\jms.jar;c:\TIBCO\JMS\clients\java\jndi.jar;c:\TIBCO\JMS\clients\java\jta-spec1_0_1.jar;c:\TIBCO\JMS\clients\java\jcert.jar;c:\TIBCO\JMS\clients\java\jnet.jar;c:\TIBCO\JMS\clients\java\jsse.jar;c:\TIBCO\JMS\clients\java\tibcrypt.jar;"".;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;"".;C:\Program Files\SonicSoftware\SonicMQ\lib\sonic_Client.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\gnu-regexp-1.0.6.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jaxp.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\xerces.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\tools.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\providerutil.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\fscontext.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\sslj.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jsafe.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\certj.jar;"".;C:\bea\weblogic700\server\lib\weblogic.jar;"".;C:\eGate\client\classes\stcjms.jar;C:\eGate\client\JRE\1.3\lib\ext\fscontext.jar;C:\eGate\client\JRE\1.3\lib\ext\providerutil.jar;C:\eGate\client\ThirdParty\sun\jms.jar;C:\eGate\client\ThirdParty\sun\jndi.jar;C:\eGate\client\ThirdParty\sun\jta.jar;"".;C:\JNDI-Directory_WebMethods\fscontext.jar;C:\JNDI-Directory_WebMethods\providerutil.jar;C:\JNDI-Directory_WebMethods\javax.jms.jar;C:\Program Files\webMethods6\Broker\lib\BrokerJMS60.jar;C:\Program Files\webMethods6\common\lib\client60.jar;C:\Program Files\webMethods6\Broker\lib\xerces.jar;"
We are trying to get to our oc4j container on our BPEL server. We have the following settings on our created message sourcein BAM architect:
Initial Context Factory: oracle.j2ee.rmi.RMIInitialContextFactory
JNDI Service Provider URL: opmn:ormi://hostname:6003:OC4J_BPEL
TopicConnectionFactory Name: java:comp/resource/ojms_ipl/TopicConnectionFactories/iplerror
Topic Name: java:comp/resource/ojms_ipl/Topics/iplerror
ojms_ipl refers to the datasource on our BPEL server that is defined in application.xml.
Where is the class located?
Best regards -
ORABPEL-12165 error while publishing a 77KB message payload to a JMS topic
Our BPEL process reports the above exception when we tried to publish a 23 line PO to a JMS topic with the default partner link settings (on a dev workstation using the OC4J JMS provider). We do not see the above errror manifest itself on smaller size purchase orders (1-6 line orders). The stack trace from the domain long is shown below:
<2006-04-05 16:28:13,390> <DEBUG> <default.collaxa.cube.ws> <JMSAdapter::Outbound> XMLHelper_setJmsMessageHeadersAndPropertiesFromXML: No headers/properties set because element is null
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound> JmsProducer_execute: A resource exception occured while producing message
<2006-04-05 16:28:13,406> <ERROR> <default.collaxa.cube.ws> <JMSAdapter::Outbound>
ORABPEL-12165
ERRJMS_PROVIDER_ERR.
Could not produce message due to JMS provider error.
Please examine the log file to determine the problem.
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:209)
at oracle.tip.adapter.jms.outbound.JmsProducer.execute(JmsProducer.java:114)
at oracle.tip.adapter.jms.JmsInteraction.executeProduce(JmsInteraction.java:195)
at oracle.tip.adapter.jms.JmsInteraction.execute(JmsInteraction.java:154)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:458)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:647)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:448)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:327)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:189)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:317)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:188)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3408)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1836)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:166)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:252)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5438)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1217)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:511)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:335)
at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:125)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:755)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:928)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.jms.JMSException: storeMessage(ID:Oc4jJMS.Message.OCS1PC.737371:10a6c2453eb:-8000.352,c0:a7:7:1f:24:2c:0:0:29:0:0:0:0:0:0:0:0:2a:1:a:6c:2b:84:11)
at com.evermind.server.jms.JMSUtils.makeJMSException(JMSUtils.java:1844)
at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1860)
at com.evermind.server.jms.ServerStore.storeMessage(ServerStore.java:757)
at com.evermind.server.jms.ServerStore.enq(ServerStore.java:157)
at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:464)
at com.evermind.server.jms.ServerTopic.enq(ServerTopic.java:97)
at com.evermind.server.jms.JMSProvider.enqMessage(JMSProvider.java:574)
at com.evermind.server.jms.EvermindSession.send(EvermindSession.java:1099)
at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:409)
at com.evermind.server.jms.EvermindMessageProducer.send(EvermindMessageProducer.java:201)
at com.evermind.server.jms.EvermindTopicPublisher.publish(EvermindTopicPublisher.java:77)
at oracle.tip.adapter.jms.JMS.JMSMessageProducer.produce(JMSMessageProducer.java:195)
... 30 morelook into the jms.log - can be found @ $BPEL_HOME/integration\orabpel\system\appserver\oc4j\j2ee\home\log
maybe this gives some more information..
hth clemens -
How to configure a error queue for weblogic jms topic
Hi guys.
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration Policy: Redirect
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.
Any suggestions for this topic? Can anyone provide some helps or any useful links.
Thanks in advance.
MingzhuangMingzhuang
I want to configure a error queue for weblogic jms topic. Wanted: The message goes to error destination when messages have expired or reached their redelivery limit.
1. using jms transport configure proxy service:
Retry Count :3
Retry Interval:10
Error Destination: ErrorTopic
Expiration olicy: RedirectUnlike File/SFTP, JMS proxy service definition does not have the concept of Error Destination. To accomplish similar functionality go to JMSQ on (for which proxy is configured) server console (http://localhost:7001/console) and configure the Error Destination. Following URL will help in how to configure JMS Q.
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueues.html
http://edocs.bea.com/wls/docs103/ConsoleHelp/taskhelp/jms_modules/queues/ConfigureQueueDeliveryFailure.html
I tried use the proxy service to consume message from the jms topic . and generation an error in the proxy message flow. But the message didn't goes into the error topic.If every thing is configured as per above step, then the after retries, the weblogic server will put the message into JMS topic configured. Your proxy will receive from this topic.
Let me know if we are not on same page.
Cheers
Manoj -
Jms adapter not polling messages from jms topic
Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
<activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
<!--property name="DurableSubscriber" value="XYZ"/-->
<property name="PayloadType" value="TextMessage"/>
<!--property name="MessageSelector" value="Target in ('XYZ')"/-->
<property name="UseMessageListener" value="true"/>
<property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
</activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
BajiAfter changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji -
Error in Applet reading a JMS topic
I have an applet trying to read a JMS topic. It connects fine, but as
soon as a message is written into the topic (that the applet is
subscribed to), I get the following error on the server:
<Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
response for: '-1'>
The applet shows the following stacktrace:
<Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
oid: '257', implementation:
'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
generate the Skeleton on the server for:
weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
oid: '2', implementation:
'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
generate the Skeleton on the server for:
weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.Kernel.execute(Kernel.java:235)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
<Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,7001,7002,7002,7001,7002,-1]:mydomain:myserver',
oid: '2', implementation:
'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
generate the Skeleton on the server for:
weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDescriptor.java:296)
at weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescriptor.java:309)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.Kernel.execute(Kernel.java:235)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
at weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.java:42)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
>
Thanks in advance for suggestions/help.
Raj
Is it with 7.0 GA or beta?
Do you know whether the classpath servlet is open or not?
Can you run this url from a browser and update this issue please.
http://host:port/bea_wls_internal/classes/weblogic/jms/dispatcher/Dispatcher
Impl_WLSkel.class
You should get a downloaded file to be saved. Otherwise your server need to
open the classpathservlet.
use -Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true to open the
classpath servlet.
Attach the applet code, so that it will help us to nail down the issue.
Cheers,
..maruthi
"theist" <[email protected]> wrote in message
news:[email protected]...
> I have an applet trying to read a JMS topic. It connects fine, but as
> soon as a message is written into the topic (that the applet is
> subscribed to), I get the following error on the server:
>
> <Apr 26, 2002 2:46:39 PM PDT> <Error> <RJVM> <Unsolicited error
> response for: '-1'>
>
>
> The applet shows the following stacktrace:
>
> <Apr 26, 2002 2:40:26 PM PDT> <Warning> <Dispatcher> <Error thrown by
> rmi server: 'weblogic.rmi.internal.BasicServerRef@101 - jvmid:
>
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
7001,7002,7002,7001,7002,-1]:mydomain:myserver',
> oid: '257', implementation:
> 'weblogic.jms.dispatcher.DispatcherImpl@2c3327''
> weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
> generate the Skeleton on the server for:
> weblogic.jms.dispatcher.DispatcherImpl_WLSkel ]
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
scriptor.java:296)
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
tor.java:309)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
> at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
> at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
> <Apr 26, 2002 2:40:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
> rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
>
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
7001,7002,7002,7001,7002,-1]:mydomain:myserver',
> oid: '2', implementation:
> 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
> weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
> generate the Skeleton on the server for:
> weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
scriptor.java:296)
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
tor.java:309)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
> at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
> at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.Kernel.execute(Kernel.java:235)
> at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
> at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
a:42)
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
> at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
> <Apr 26, 2002 2:41:39 PM PDT> <Warning> <Dispatcher> <Error thrown by
> rmi server: 'weblogic.rmi.internal.BasicServerRef@2 - jvmid:
>
'-8904810875822286436C:127.0.0.1R:1187444208533444527S:192.103.129.38:[7001,
7001,7002,7002,7001,7002,-1]:mydomain:myserver',
> oid: '2', implementation:
> 'weblogic.rmi.internal.dgc.DGCServerImpl@4d7745''
> weblogic.utils.AssertionError: ***** ASSERTION FAILED *****[ Could not
> generate the Skeleton on the server for:
> weblogic.rmi.internal.dgc.DGCServerImpl_WLSkel ]
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeletonClass(BasicRuntimeDe
scriptor.java:296)
> at
weblogic.rmi.internal.BasicRuntimeDescriptor.getSkeleton(BasicRuntimeDescrip
tor.java:309)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:288)
> at
weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
> at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:2
2)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.Kernel.execute(Kernel.java:235)
> at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:169)
> at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:195)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:642)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:589)
> at
weblogic.rjvm.ConnectionManagerClient.handleRJVM(ConnectionManagerClient.jav
a:42)
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:637)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at
weblogic.socket.JavaSocketMuxer.processSockets2(JavaSocketMuxer.java:319)
> at
weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:233)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> >
>
>
> Thanks in advance for suggestions/help.
> Raj
Maybe you are looking for
-
Hello people from the forum, I have made a beatifull website, and upload it with filezilla to a server, and also I upload it to a local map. Everthing was going very well, but i don't get my website on the internet, because one page will not be uploa
-
hi Guys, working on below error if anyone has work around. It is on SQL Server 2012 cluster. The SQL Server specified in Integration Services service configuration is not present or is not available. This might occur when there is no default insta
-
Hy. I have HP Pavilion g4 1357-TX, with Windows 7 Ultimate Edition 32 bit, Intel Core i3-2330M and 2GB memory. To the point, how to activate Bluetooth in this notebook ? Maybe it sounds silly or stupid to you, but I reall have no idea about this. Nee
-
Has anyone had the problem of their mouse pad working sporadically after downloading Maverick? I need to "sleep" mine every 2-3 min to get it to work again. Help
-
Please its very important I get his family this Video from my Crackberry phone to a computer disk. I am trying to use Windows DVD Maker with DVD+r disks. Video is of his best friend trying to come to grip with his up coming voyage back to our father'