Receiving Unknown Byte Messages in JMS Queues from MDM 2.0

I am receiving unknown Byte messages in JMS CCB MDM Queue from MDM 2.0.
It keeps on increasing. Please let me know how to avoid this. and what may be the error.

Hi,
Set these flags with in your startup script like setDomainEnv.sh file or startWebLogic.sh file.
set these option near java_properties or options.
once you set please restart and one more point I missed here once you set these debug flags change the logging patter patter to debug mode under
server >> logging
change all the logging severity to debug mode and collect the debug.
Regards,
Kal

Similar Messages

How to view messages in Jms queue from OEM 12c Cloud Control

Hi All,
How can I view messages in a Jms queue from OEM 12c Cloud Control without logging into WebLogic Administration Console?
Thanks in Advance!!

EMCC 12c gets down to the JMS message queue/topic level in regards to the metrics being collected. It doesn't provide a view into the actual messages themselves. Are you trying to capture/track messages with a particular payload?

Posting message to JMS queue from Proxy in OSB 10.3

I am posting a message to a JMS queue using a business service. Is there a way of getting a response from the business service to retrieve the newly generated JMSMessageID?

I am posting a message to a JMS queue using a business service. Is there a way of getting a response from the business service to retrieve the newly generated JMSMessageID?Yes JMS BS can be configured to get Response though from Different Q.
Request-JMSBS----->JMS Request Q------your logic outside of BS----->JMS Response Q----->JMSBS-Response. You can use JMSCorrelationID or JMSMessageID for the response correlation.
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/interopjms/transport.html#wp1097863
Cheers
Manoj

Messages to Weblogic Queue from JCAPS

Hi,
We are facing problems looking up a Weblogic queue from JCAPS to send a JMS message into it. The same code works fine from ICAN and stand alone java class.
Has anyone done this before in JCAPS? Any help would be highly appreciated.
Thanks.

Hi,
Finally getting around to attempting to access a remote Weblogic 8.1 JMS queue from JCAPS 5.1.2. I've created a 9.0 JMS Server under my logical host. I put wlclient.jar and wljmsclient.jar in the directory you specified (the weblogic.jar file is also there from when I used it to create the code shown below to get this to work with low level coding in a jcd). I removed the jndi.properties files from the wlclient.jar (although I'm confused about that and don't know why it needs to be done, etc.). I specified the URL in the env config for the newly created 9.0 JMS server. I set up a simple JCD that takes file input and simply tries to post it to the JMS 'queue'. I set up a connectivity map the file input, the jcd and the 'queue' output. I set up the deployment profile, etc. I'm doing no coding in the jcd as far as setting up any Jms parameters, etc. I'm assuming you can use this just like a regular SeeBeyond JMS queue where there's no coding.
When I run it I get the error before it gets to my simple code. I'm assuming it's failing during it's initial setup to run:
[#|2007-04-30T14:52:25.090-0500|FINE|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|OtdBeanMessageFactory registration error: Connection factory for java:comp/env/BPELConnectionFactory could not be found: javax.naming.NameNotFoundException: DmsInfo_u002F_prjCad_u00_163246830#stcbpelra#javax.resource.cci.ConnectionFactory not found|#]
[#|2007-04-30T14:52:25.093-0500|INFO|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|No object bound to name java:comp/env/stc/SUPPORTED_SERVICES|#]
[#|2007-04-30T14:52:25.093-0500|INFO|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Cached the SupportedTypes, SupportedPortTypes and MapMessageAndClass HashMaps for the OTDService with EJBId : cmJcdTOut_jcdTOut1_PartnerService|#]
[#|2007-04-30T14:52:25.094-0500|FINE|IS5.1.2|com.stc.codegen.OTDImpl.runtime.ejb.OTDService|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Message type for OTD = xsd.otdXmlOrderCreate_1253647779.OrderCreate|#]
[#|2007-04-30T14:52:25.616-0500|FINE|IS5.1.2|Inbound.cmJcdTOut_jcdTOut1.jcdTOut_Runtime_Handler|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Class name for otdXmlOrderCreateOut = xsd.otdXmlOrderCreate_1253647779.OrderCreate|#]
[#|2007-04-30T14:52:25.617-0500|FINE|IS5.1.2|Inbound.cmJcdTOut_jcdTOut1.jcdTOut_Runtime_Handler|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Opening connection for link cmJcdTOut_jcdTOut1_qWeblogic|#]
[#|2007-04-30T14:52:25.693-0500|INFO|IS5.1.2|com.stc.codegen.JMSImpl.runtime.ejb.JMSService|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Cached the connection properties for the JMS Service with EJBId : cmJcdTOut_jcdTOut1_qWeblogic|#]
[#|2007-04-30T14:52:26.093-0500|FINE|IS5.1.2|com.stc.codegen.appconn.jms.JMSApplicationConnection|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Creating a JMS connection without specifying userid or password|#]
[#|2007-04-30T14:52:26.140-0500|FINE|IS5.1.2|com.stc.jmsjca.core.XManagedConnectionFactory|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Creating managed connection for subject Subject:
Principal:
Private Credential: javax.resource.spi.security.PasswordCredential@0
and request info com.stc.jmsjca.core.XConnectionRequestInfo@c640aafc|#]
[#|2007-04-30T14:52:26.142-0500|FINE|IS5.1.2|com.stc.jmsjca.wl.RAWLObjectFactory|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|Looking up JNDI object corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory|#]
[#|2007-04-30T14:52:26.149-0500|WARNING|IS5.1.2|javax.enterprise.resource.resourceadapter|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;|RAR5117 : Failed to obtain/create connection. Reason : Failed to create session: javax.jms.JMSException: Could not find JNDI object by name [corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory]: java.lang.NullPointerException|#]
[#|2007-04-30T14:52:26.150-0500|SEVERE|IS5.1.2|com.stc.codegen.appconn.jms.JMSApplicationConnection|_ThreadID=63; ThreadName=Worker: 13; Context=project=Inbound,deployment=dpJcdOut,collab=cmJcdTOut_jcdTOut1,external=inFile;stacktrace-id=0;|javax.jms.JMSException: Could not create session javax.jms.QueueSession: Error in allocating a connection. Cause: Failed to create session: javax.jms.JMSException: Could not find JNDI object by name [corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory]: java.lang.NullPointerException
javax.jms.JMSException: Could not create session javax.jms.QueueSession: Error in allocating a connection. Cause: Failed to create session: javax.jms.JMSException: Could not find JNDI object by name [corbaname:iiop:1.2@ucadtestapp:22001#weblogic.jms.XAConnectionFactory]: java.lang.NullPointerException
at com.stc.jmsjca.util.Exc.jmsExc(Exc.java:92)
at com.stc.jmsjca.core.JConnection.createSessionByApplication(JConnection.java:139)
at com.stc.jmsjca.core.JConnection.createQueueSession(JConnection.java:270)
at com.stc.jmsjca.core.WQueueConnection.createQueueSession(WQueueConnection.java:58)
at com.stc.codegen.appconn.jms.JMSAdapterFactory$QueueJMSAdapter.createSession(JMSAdapterFactory.java:316)............
I don't want to use a 'XA' type queueconnfactory, so I'm assuming JCAPS is pulling settings from somewhere and failing. I'm not sure how to specify these types of parms in order to get this to work or if I should even have to specify them, etc.
Before I tried the approach above I was able to connect to this remote queue to get/put messages in a jcd with the weblogic.jar file imported. The code to put a message from the jcd to the remote queue, without using a Weblogic 9.x JMS Server created under my logicahost, is:
package DmsInfoprjCadCadApptBookingOutbound;
import javax.naming.*;
import javax.jms.*;
import java.net.*;
import java.util.*;
import java.io.*;
public class jcdApptBookingToAdvantex
public com.stc.codegen.logger.Logger logger;
public com.stc.codegen.alerter.Alerter alerter;
public com.stc.codegen.util.CollaborationContext collabContext;
public com.stc.codegen.util.TypeConverter typeConverter;
private InitialContext jmsContext = null;
private QueueConnectionFactory jmsConnFactory = null;
private QueueConnection jmsConnection = null;
private Queue jmsQueue = null;
private QueueSession jmsSession = null;
private QueueSender jmsSender = null;
public void receive( com.stc.connector.appconn.file.FileTextMessage input, xsd.otdXmlOrderCreate_1253647779.OrderCreate inOutOtdXmlOrderCreate )
throws Throwable
logger.info( "\n^^^^ In jcdApptBookingToAdvantex..." );
try {
String sHostName = "ucadtestapp";
Hashtable htEnv = new Hashtable();
htEnv.put( Context.PROVIDER_URL, "t3://" + sHostName + ":22001" );
htEnv.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
try {
logger.info( "\n^^^^ Create JMS objects, jmsContext..." );
jmsContext = new InitialContext( htEnv );
} catch ( NamingException ne ) {
logger.info( "\n^^^^ Caught InitialContext naming exception, msg is [" + ne.toString() + "]..." );
} catch ( java.security.AccessControlException ae ) {
logger.info( "\n^^^^ Caught InitialContext AccessControlException, msg is [" + ae.toString() + "]..." );
logger.info( "\n^^^^ Throw exception now, hopefully we'll exit gracefully..." );
throw new Exception( "InitialContext Exception" );
try {
logger.info( "\n^^^^ Create JMS object, MSDI QueueConnectionFactory..." );
jmsConnFactory = (QueueConnectionFactory) jmsContext.lookup( "com.mdsi.port.paJms.queueConnectionFactory" );
logger.info( "\n^^^^ Create JMS object, MDSI InboundQueue..." );
jmsQueue = (Queue) jmsContext.lookup( "com.mdsi.port.paJms.DefaultCIS0.InboundQueue" );
} catch ( NamingException ce ) {
logger.info( "\n^^^^ Caught Context naming exception, msg is [" + ce.toString() + "]..." );
try {
logger.info( "\n^^^^ Populate sample data into OrderCreate..." );
String sTestMessage = null;
inOutOtdXmlOrderCreate.getOrderCreate_T0( 0 ).setOrderNumber( "A00001" );
inOutOtdXmlOrderCreate.getOrderCreate_T0( 0 ).setJobCode( "J0001" );
sTestMessage = inOutOtdXmlOrderCreate.marshalToString();
logger.info( "\n^^^^ Sample data to send is [" + sTestMessage + "]..." );
logger.info( "\n^^^^ Create JMS object, createQueueConnection..." );
jmsConnection = jmsConnFactory.createQueueConnection();
logger.info( "\n^^^^ Create JMS object, createQueueSession..." );
jmsSession = jmsConnection.createQueueSession( false, Session.AUTO_ACKNOWLEDGE );
logger.info( "\n^^^^ Create JMS object, jmsSender..." );
jmsSender = jmsSession.createSender( jmsQueue );
logger.info( "\n^^^^ Start jmsConnection..." );
jmsConnection.start();
javax.jms.BytesMessage jmsMsgBytesMessage = null;
jmsMsgBytesMessage = jmsSession.createBytesMessage();
try {
byte[] bytesOut = new byte[0];
int iBufLen = 10000 * 1024;
byte[] bytesBuf = new byte[iBufLen];
byte[] bytesTmp = null;
int iLen = 0;
iLen = sTestMessage.length();
bytesTmp = new byte[bytesOut.length + iLen];
System.arraycopy( bytesOut, 0, bytesTmp, 0, bytesOut.length );
System.arraycopy( bytesBuf, 0, bytesTmp, bytesOut.length, iLen );
bytesOut = bytesTmp;
bytesTmp = null;
jmsMsgBytesMessage.writeBytes( bytesOut );
logger.info( "\n^^^^ Send to Advantex..." );
jmsSender.send( jmsMsgBytesMessage );
// Send final control message indicating end of messages ??
// jmsSender.send( jmsSession.createMessage() );
} catch ( Exception e ) {
logger.info( "\n^^^^ Caught Exception during send setup..." );
e.printStackTrace();
} finally {
if (jmsSender != null) {
try {
logger.info( "\n^^^^ Close jmsSender..." );
jmsSender.close();
} catch ( Exception se ) {
logger.info( "\n^^^^ Caught Exception closing jmsSender..." );
} catch ( JMSException jee ) {
logger.info( "\n^^^^ Jms Exception caught during setup of jmsSender, msg is [" + jee.toString() + "]..." );
} finally {
logger.info( "\n ^^^^In finally for queue send , will try to close connection..." );
if (jmsConnection != null) {
try {
jmsConnection.close();
logger.info( "\n^^^^ Jms Queue Connection closed." );
} catch ( JMSException e ) {
logger.info( "\n^^^^ Jms Exception caught while trying to close Queue Connection, msg is [" + e.toString() + "]..." );
} catch ( Exception ex ) {
logger.info( "\n^^^^ Caught General Exception, will printstacktrace" );
ex.printStackTrace();
logger.info( "\n^^^^ Exit jcdApptBookingToAdvantex..." );
Not sure if I've somehow got to specifiy more detailed info to JCAPS so the 9.x approach will work??
Thanks,
Rich

Integration with JMS queue from BizTalk 2013R2

Hi All,
We are planning to integrate biztalk application with Oracle Siebel CRM (8.1.1.11). they wanted to use JMS queue to receive xml message from BizTalk2013R2 and also send message to BizTalk for more reliability.
IS there any out of box adapter by which we can connect to their JMS queue.
We dont want to go with 3rd party software like jt adapter for JMS queue
Regards,
Manish
Manish

Hi Manish,
As of now there is no out-box-adapter for JMS queue.
If you don’t want JNBridge adapter (I hope you’re referring to same. There is no “jt” adapter as you mentioned), you can create a custom adapter which access the JMS queue.
Use WCF LOB adaper (WCF Lob
Adapter Wizard)and create an adapter.
Following article details about the .NET code for messaging with JMS queue, try the code.
Use JMS Messaging in your C# Applications
And following articles give details about using WCF LOB adapter/Wizard:
What Is the WCF LOB Adapter SDK?
Sample:
https://msdn.microsoft.com/en-us/library/bb798102.aspx
http://geekswithblogs.net/michaelstephenson/archive/2009/02/10/129302.aspx
Use similar code (one from above codeproject article where how to do messaging between JMS queue is shown) to wrapper it around custom WCF LOB adapter.
Give it a try, if you don’t want to spend anything on a 3<sup>rd</sup> party adapter.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Posting a message to JMS queue using B2B

Hi,
Could anyone suggest a solution for this scenario?
I have two trading partners say TP1 & TP2. Suppose TP1 is sending an xml message to TP2 using custom ebMS protocol, then at TP2, the message should be posted to a JMS Queue so that some other application can read it and process it.
The problem which I am facing is..
1) where to create that JMS Queue(I could not find any options for creating a JMS Queue neither in B2B console nor in enterprise manager console..!!)?
2) how to register TP2 to send msg to that JMS Queue(How that queue will be vissible to B2B)?
3) Should the endpoint be given as that JMS Queue while configuring the Delivery Channel for TP2?
Thanx in advance for your suggestions,
Regards,
Satya.

Hi Narayanan,
Thank you for your prompt reply. I understand that we need to create an external delivery channel to post the message to a JMS Queue from TP2. Currently I am using default AQ's (b2b.IP_IN_QUEUE & b2b.IP_OUT_QUEUE) at TP2 end to receive the message.
But, I want to post the message to JMS Queue. For this I need to create an external delivery channel and the corresponding end point should be the name of that JMS Queue. Is my assumption correct?
I have already gone through the thread that you have mentioned and the pdf as well. But, I am not able to find an option on how & where to create that JMS Queue?
Could you clarify on this?
Regards,
Satya.

Error while sending the messages to JMS Queue

Hi ,
I am trying to pick the file from JMS Queue and send the response xml as outbound message to JMS Queue again using XAI Sender
I Created XAI Sender, Outbound Message Type(DM-RCVRESP) and configured these two with External System.
I am able to pick the file from JMS Queue but unable to send the message through XAI Sender (Real-time)
Plz find below the error trace getting.
[Wed Jun 15 16:12:09 IST 2011] Error while processing sender "UPLOADSTG" : Unable to update response in staging table: Row id not given.
com.splwg.mpl.sending.SameThreadSendingManager$ProcessException
     at com.splwg.mpl.sending.SameThreadSendingManager.processDestination(SameThreadSendingManager.java:341)
     at com.splwg.mpl.sending.SameThreadSendingManager.sendResponse(SameThreadSendingManager.java:293)
     at com.splwg.mpl.sending.SameThreadSendingManager.doSend(SameThreadSendingManager.java:249)
     at com.splwg.mpl.server.async.ExecSendRequestProcessor.ProcessRequest(ExecSendRequestProcessor.java:61)
     at com.splwg.mpl.server.async.RequestProcessingThreadAdapter.run(RequestProcessingThreadAdapter.java:46)
     at com.splwg.mpl.server.PooledThread.run(PooledThread.java:91)
     at java.lang.Thread.run(Thread.java:662)
Please guide me in this regard..
Thanks,
sukumar

What have you configured for the response tab for the sender? Are you using the MPL or the MDB?
Take a look at:
MPL Best Practices (Doc Id 1308165.1)
Oracle WebLogic JMS Integration (Doc Id: 1308181.1)

Migration of JMS Queues from Weblogic 10.3 to 12c

Hi - We are currently planning to move our JMS Queues from existing 10.3 server to 12c and for the same we are looking for some feedback :
We need to define a rollback strategy in case our migration to 12c does not work well and we need to revert back to using weblogic 10.3. Are messages sent to weblogic 12c backward compatible with version 10.3? As part of rollback, business would want to drain out any remaining messages from 12c and feed them back to 10.3 queues to allow them for processing. Is this feasible? If yes then, could you please suggest how, If not then could you please suggest a strategy for rollback and process remaining messages in 12c?
We would also want to know if we can keep the same Database for both 10.3 and 12c JMS persistent stores for the same queues or should we define a completely new DB? With weblogic we can define prefixes for the DB stores which would make queue tables to have different names between 10.3 and 12c for same queues. However we are not sure if there are any other internal tables that JMS creates in the persistent stores DB, not using these prefixes, which would then corrupt the data since both 10.3 and 12c tables would be on the same DB.
Thanks
Nitin

Hello,
the final release for WLP is 10.3.6, running on WebLogic Server 10.3.6.
Emmanuel

NoClassDefFoundError while accessing JMS Queue from JDev 10.1.3.3

Hi,
I'm trying to get a handle of a JMS queue, which resides on Oracle App Server 10.1.3.4, from a Java Program which I'm trying to run from JDeveloper 10.1.3.3.
I'm trying to make an RMI connection to the App server from JDeveloper by passing following information to the intialContext:
env.put("java.naming.factory.initial",
"oracle.j2ee.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL,
"ormi://wafedabpelqa10.corp.weyer.pri:12402");
env.put("java.naming.security.principal","oc4jadmin");
env.put("java.naming.security.credentials","welcome1");
Where the above information is related to our App Server.
I'm successfully able to establish an RMI connection from JDev to Oracle App Server and can lookup datasources created on the App server using their
JNDI names. However if I try to look up a JMS Queue from the App server using its JNDI name, I get an error as:
java.lang.NoClassDefFoundError: oracle/tip/adapter/api/OracleConnectionFactory
I have also tried to use the value "com.evermind.server.rmi.RMIInitialContextFactory" for "java.naming.factory.initial",
however I still get the same error.

Hi,
this should work and you need to download the rmi library http://www.oracle.com/technology/software/products/ias/htdocs/utilsoft.html
thanks
# String queueName = "jms/MyJMSQueue";
# String queueConnectionFactoryName = "jms/MyJMSQCF";
# Context ctx;
# try {
# Properties parm = new Properties();
# parm.setProperty("java.naming.factory.initial","com.evermind.server.rmi.RMIInitialContextFactory");
# parm.setProperty("java.naming.provider.url","ormi://localhost:23791/");
# parm.setProperty("java.naming.security.principal","oc4jadmin");
# parm.setProperty("java.naming.security.credentials","welcome");
# ctx = new InitialContext(parm);
# QueueConnectionFactory connectionFactory =
# (QueueConnectionFactory)ctx.lookup(queueConnectionFactoryName);
# connection = connectionFactory.createQueueConnection();
# connection.start();
# session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
# queue = (Queue)ctx.lookup(queueName);
# sender = session.createSender(queue);
# receiver = session.createReceiver(queue);
# } catch (JMSException je) {
# throw new RuntimeException("Fout opgetreden bij het starten ",
# je);
# } catch (Throwable t) {
# throw new RuntimeException("Fout opgetreden bij het starten ",
# t);
# }

Unable to insert messages in JMS QUEUE

Hi All,
I am facing an issue while inserting messages in JMS queue.
The JMS Queue is on another weblogic server and now i created a bpel process which has a jms adapter to insert messages inthe jms queue.I am deploying the Bpel in my server which does not have this particular JMS queue.
I am unable to insert the messages into the JMS queue present on another weblogic server. where as i am able to insert messages if the queue is present on my server.
Can you please let me know if its possible to put messages into a queue on remote server from local server.
Thanks in advance.

Most probably it seems like an issue of security. Please try to establish cross domain trust between these two Weblogic server domains. For more information refer to http://download.oracle.com/docs/cd/E1284001/wls/docs103/secmanage/domain.html#wp1175687_

Need help to connect tibco jms queues from OSB

Hi,
We have a requirement in our project "to connect tibco JMS Queues from OSB".
The Queres are created by some othes in remote system, they provided us the details to connect the Queue. the detail are:
Queue Name :EXT_WEALTHHUB.TO_EXT.SYNC.REQ
Jndi Factory :SSLQueueConnectionFactory
and hostName , PORT
Credentails are provided.
We entered the same details in Business service in transport page by choosing 'jms' as protocol and EndpointURI as.
"jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.REQ"
And we created a service account to maintain the credentials and browsed the same at service account in the business service.
In JMS Transport Page we selected
Response Queue : One for all Request URI's
Response Pattern : JMS CorrelaltionID
Response UI :jms://100.10.XX.YY:1234/SSLQueueConnectionFactory/EXT_WEALTHHUB.TO_EXT.SYNC.RESP
when we are trying to establish a connection with the above queue getting
javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: er.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: in.checkLoginSuccess(Login.java:131)
     at weblogic.rjvm.t3.MuxableSocketT3.connect(MuxableSocketT3.java:403)
     at weblogic.rjvm.t3.ConnectionFactoryT3.createConnection(ConnectionFactoryT3.java:34)
     at weblogic.rjvm.ConnectionManager.createConnection(ConnectionManager.java:1777)
     at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1417)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:437)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:316)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:254)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
     at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     at weblogic.jndi.Environment.getContext(Environment.java:315)
     at weblogic.jndi.Environment.getContext(Environment.java:285)
     at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
     at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
     at javax.naming.InitialContext.init(InitialContext.java:223)
     at javax.naming.InitialContext.<init>(InitialContext.java:198)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl$2.run(MessageDrivenBeanInfoImpl.java:748)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.doPrivilagedAction(MessageDrivenBeanInfoImpl.java:2238)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:733)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.getInitialContext(MessageDrivenBeanInfoImpl.java:689)
     at weblogic.jms.common.CDS$DD2Listener$1.run(CDS.java:1018)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContextFromListener(CDS.java:1012)
     at weblogic.jms.common.CDS$DD2Listener.getInitialContext(CDS.java:984)
     at weblogic.jms.common.CDS$1.run(CDS.java:436)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
     at weblogic.jms.common.CDS.createInitialContext(CDS.java:431)
     at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:270)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
     at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
     at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:532)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:158)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1269)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentM
Any pointers on how to resolve the above issue will be a greate help to us.
Thanks in Advance

Wrong forum, please ask this on dedicated weblogic or soa forums

QueueBrowser not scaning all messages in JMS queue (ie not showing inprogre

Hi all,
I am using JMS in jboss-3.2.3, when scaning for pending messages i am using QueueBrowser.
But QueueBrowser not scaning all messages in JMS queue (ie not showing inprogress message)
But i need to know all messages including ongoing messages..
Antone plz help me
I am using Queuesender and QueueReceiver ..But some Exception or Error causes my JMS server(QueueReceiver listening for onMessage()) hanged up..and not responding to remaining messages...So i need to find pending messags in JMS queue..How can find?
Now i am using QueueBrowser to get list of pending msgs in queue... But doesn't contains Message which passed for processing (called onMessage())
.. But i need to find this also..How can?
Thanks,
Thilsen

You're right in thinking that the behaviour you describe looks wrong.
Take a look at the QueueBrowser interface which can be used to inspect a queue. You get one using QueueSession.createBrowser(Queue). The QueueBrowser allows you to scan a queue without consuming the messages. However note that the state of the queue may change while you're observing it through the QueueBrowser so what you see might not always be a 100% accurate representation of the queue at any given time.
Other things to check:
- message selectors - are you setting a message selector on your queue receiver which is resulting in not all of the messages 'matching'.
- expired messages - are you setting a time-to-live on the messages that you publish.
Hope this helps,
David Ingham
http://www.arjuna.com

Writing to a JMS queue from Tux-service?

Greetings,
is there any way to write to a JMS-queue from a Tuxedo/atmi service without
using WebLogic Server (because of WTC needing it)?
Lara

Lara,
One way to write to a JMS-queue from a Tux service would be by using JNI functions.
Inside your server's tpsvrinit function you can create a JVM (using JVM_CreateJavaVM
function) and instantiate a couple of Java objects. You may then call Java methods
on these objects from your Tux services. At the server's tpsvrdone function you
must then destroy the Java objects and the JVM.
Regards,
Lazaros
"Lara Faiazza" <[email protected]> wrote:
Greetings,
is there any way to write to a JMS-queue from a Tuxedo/atmi service without
using WebLogic Server (because of WTC needing it)?
Lara

Publishing message to JMS Queue on Weblogic from OSB proxy service

Hi,
1. I have created a JMS module: testModule and a JMS queue: testQueue in the weblogic admin console.
2. Created a business service with the above queue as endpoint.
3. Created a proxy service which publishes the message to the queue using the business service. I have used Publish activity to publish the message to the business service.
When i run the proxy service with the request message, then, no error is coming but, in the admin console when i click on JMS module->testModule->testQueue->Monitoring tab, i see nothing. There are no entries in the table so, how can i check if the message is properly published to the queue or not.
The queue is not listened by any service for consuming the messages.
Kindly help me in figuring out this issue.
Thanks in advance.

If the destination was a topic, the behavior would be expected. Messages only stays on a topic and are delivered to consumers if there are consumers or durable subscribers.
Did you check the server logs and see if there are any exceptions or warnings?
You can also turn on jms debugging by adding the following to your server startup script.
-Dweblogic.debug.DebugJMSFrontEnd=true
-Dweblogic.debug.DebugJMSBackEnd=true
The debugging messages wiill show up in the server log.

Posting to JMS queue from WLI BPM 7.0

Hi,
I am trying to invoke a workflow process from a servlet by exchanging two JMS
messages.
I have configured my own JMS event queue com.bea.wli.bpm.EventQueueExt and generated
and installed the MDB for it as described in the docs. The servlet sends a XML
JMS to the normal com.bea.wli.bpm.EventQueue which starts the process. This half
works. The process then tries to send an XML to the newly configured queue - but
this fails.
The server console shows that there are absolutely no messages on my new queue.
The java servlet waits forever to receive on it and the workflow process instance
never completes the sending of the XML JMS.
I have attached the sample servlet code that I am trying this with. Would anyone
be able to spot what I am doing wrong?
1000 Thanks in advance,
Karsten
[BaseServlet.java]

Just wondering , why create a separate JMS server for this queue?
"Jared" <[email protected]> wrote in message
news:3f16dfde$[email protected]..
>
I am not sure if I exactly understand what you did -- but if you generatedanother
queue using the utility that WLI provided, I think you may be using itincorrectly.
That kind of queue is meant to be used in addition to the originalEventQueue
-- as an input queue to WLI. Maybe your messages were immediately sentback to
WLI -- in an attempt to start a workflow?
I would create a separate JMS server (from the WLI jms server) and createyour
queue on that server.
"Karsten " <[email protected]> wrote:
Hi,
I am trying to invoke a workflow process from a servlet by exchanging
two JMS
messages.
I have configured my own JMS event queue com.bea.wli.bpm.EventQueueExt
and generated
and installed the MDB for it as described in the docs. The servlet sends
a XML
JMS to the normal com.bea.wli.bpm.EventQueue which starts the process.
This half
works. The process then tries to send an XML to the newly configured
queue - but
this fails.
The server console shows that there are absolutely no messages on my
new queue.
The java servlet waits forever to receive on it and the workflow process
instance
never completes the sending of the XML JMS.
I have attached the sample servlet code that I am trying this with. Would
anyone
be able to spot what I am doing wrong?
1000 Thanks in advance,
Karsten

Receiving Unknown Byte Messages in JMS Queues from MDM 2.0

Similar Messages

Maybe you are looking for