Messages posted to JMS Topic from OSB disappear even when not subscribed

Hi,
We are using an OSB service to publish xml messages to a weblogic JMS Topic. Message is persistent. There are no consumers for the Topic. There is no expiration limit set.
We are able to see the message from OSB reach the Topic. It stays in the Topic for a few seconds and then disappears.
The State of the message shows up as "send transaction" on the Topic in the weblogic console. And it shows up as Message Pending instead of Message Current.
Is there a way to ensure that the message stays in the Topic till it is consumed by a subscriber?
Thanks,
Senthil

Hi Senthil,
The topic persists messages only for subscribers, if there is no subscribers, then it is not necessary to persist the message.
This is the same case for you as well, as there are no subscribers the message gets deleted.
So first you need to have atleast one subscriber first (A dummy proxy that is reading from the topic) and then post to the topic (through your OSB service or hermes jms tool, etc .. ) . Then if you try to go and check the topic you will be able to see the message.
Hope this information helps.
Thanks,
Patrick
Edited by: Patrick Taylor on May 13, 2011 2:40 PM

Similar Messages

Mail "New Message" window retreats to background after drag and drop attachment from Finder to Mail "New Message", click, and Finder window stays in foreground even when not in focus

Hi, I'm surprised I can't quickly find if anyone else is having this issue. For me it has been going on since Lion on my 13" MacBook Pro 2011 and it's still persisting in Mavericks, and even still now that I've "downgraded" to a 15" MacBook Pro 2010 with Mavericks. The behavior is odd and difficult to explain concisely. Basically, when I want to add an attachment to Mail, I'll Cmd+Tab over to Finder click and drag and Cmd+Tab back to Mail, and drop the attachment. At first it looks fine, but when I click in the New Message window where I just dropped the attachment, to move the cursor, it retreats to the background and the Mail Main Window comes to the foreground. Then, if I click on that, the Finder window that I just used comes to the foreground. Sometimes if I switched to another app before going to Finder to select the drag and drop, that other app window will appear in the foreground instead. If I click on the other app window that is now in the foreground, then the Finder window that was last used will come to the foreground. The only thing that seems to fix this switch-a-roo effect is Cmd+Tab-ing back and forth a few times, or click on the window "frame" at the top to move the window around.
The way to prevent this is to have my Mail Message window visible in the foreground side by side with the Finder window when the drag and drop occurs (this is a tedious extra step if mulitple windows are open, or to use the add attachment command in the menu within Mail. But it sure is annoying buggy behavior.
Thanks
Daniel

Yep, I get exactly the same thing when using Thunderbird mail client on my 2011 iMac running Lion. I've been putting up with it for at least a year, maybe longer.
For me it appeared to start after a Thunderbird update, so I figured that was the cause and couldn't find a solution at the time. However I've now noticed it starting to happen in Apple Motion 4 when dragging files from Finder into a DropZone in my animations. Motion remains the active program but the Finder window sits on top until I Cmd-tab out to a third open program (ie not Finder) and back to Motion again.
This is the first indicator I've had that it's an OS X issue.
Be great to find a solution as D&D is by far my preferred way of adding attachments to emails and similar tasks.

Garbage added to log while sending message to Weblogic JMS topic

Hi All,
Was able to sucessfully send messages to Weblogic JMS topic and also able recieve them.
But while sending the messages to topic loy of debug statements are printed to the standard output
This is seen only in production and not in developement, and expecting it due config issue...
Any ideas on this is greatly appriciatied.
Thanks in advance !
Cheers,
Ambha

Thanks for the replies,
The problem is certainly not with logger settings...
The statements which are getting printed are SSL debugging
The following settings are used by the application which sends messages to the topic :
Dssl.debug=true
Dweblogic.StdoutDebugEnabled=true
These settings are same in Dev, UAT, and Production. But why the debug statements are seen only
in UAT and Production I am not sure...
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
any Ideas... ?
Thanks
Ambha

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

I have just updated to LR5. I also have a new Camera. Nikon D800. Trying to import directly (from camera) into LR. But unsuccessful. Getting the following message. "The files are from a camera which is not recognised by the raw format support in Ligh

I have just updated to LR5. I also have a new Camera. Nikon D800. Trying to import directly (from camera) into LR. But unsuccessful. Getting the following message. "The files are from a camera which is not recognised by the raw format support in Lightroom." How can I import please?

Hi,
I assume you mean the Nikon D810 because D800/800E support has been there since Lightroom 4.1
Currently, because it is a new camera (D810) the only support is in a RC of ACR 8.6 for Photoshop CS6 and CC, as the RC runs out on 31 August it is expected support will be there in the next dot release of Lightroom.
Current limitations are that only full sized NEF is supported.
If you wish to import to Lightroom 5.5. you will need to download the DNG Converter v8.6RC and convert the NEF files (full size RAW ony) to DNG then import into Lightroom 5.5

Using OS X 10.6.8 on my IMac, I find that items on my message list no longer "fade" from dark to light when I click on them. I recently switched the font from Arial to Helvetica to permit me to select italics for any word. I am composing in rich text.

Using OS X 10.6.8 on my IMac, I find that items on my message list no longer "fade" from dark to light when I click on them. I recently switched the font from Arial to Helvetica to permit me to select italics for any word. I am composing in rich text.

Not sure why it would default to IMAP? But any how, start the account anew, fill in the first page of info, but before clicking on the Create button, hold down the Option key until the Create button changes to read Continue. Click continue, and proceed in a more manual process during which you can set the account type as POP.
Ernie

Forefox won't start in windows XP: I get the message that windows "cant' find the exe file" even when I click from the program file, rather than the shortcut.

Forefox won't start in windows XP: I get the message that windows "cant' find the exe file" even when I click from the program file, rather than the shortcut.

Delete the current Firefox shortcut on the desktop and create a new desktop shortcut via the right-click context menu on the Firefox.exe program (Send to > Desktop)

My wifes iphone will not allow her to download from the app store when not connected to the computer. Does anyone know what is wrong?

My wifes iphone will not allow her to download from the app store when not connected to the computer. Does anyone know what is wrong?

Resetting your Mac's PRAM and NVRAM
If you have Apple Care you should give them a call.

I am trying to install a new theme but FF is preventing me from doing so even when I click 'Allow'

I am trying to install a new theme but FF is preventing me from doing so even when I click 'Allow'. Might someone help?
Thank you,
Leeflea

Do you mean this?
*Firefox/Tools > Options > Advanced > General : Accessibility : [ ] "Warn me when web sites try to redirect or reload the page"
The setting in "Tools > Options > Advanced > General" is meant as an accessibility feature, as you can see by the label of that section, so that people with disabilities or people who use screen readers do not get confused and is not meant as a safety protection to stop redirecting.
See also:
*https://support.mozilla.org/kb/settings-network-updates-and-encryption#w_general-tab
*http://kb.mozillazine.org/accessibility.blockautorefresh
*http://kb.mozillazine.org/Accessibility_features_of_Firefox

Newbie question about JMS topic and OSB

So here is what I want to achieve:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. The way I picture this is that a producer will invoke a proxy to publish a message. The subscriber will (asynchronously) invoke another proxy to pickup the message.
Is this possible and how do I go about doing this?
thanks
Edited by: user10341230 on Apr 28, 2010 8:49 AM

Hi there,
user10341230 wrote:
I want to "front" a JMS topic on WLS using OSB 10g. I want the users (producers and subscribers) to be access the topic via proxy services. > it's not really clear what you want to achieve here.
you say
user10341230 wrote:
The way I picture this is that a producer will invoke a proxy to publish a message.you need a proxy with whatever inbound protocol you like (http, file, mail...), which through a jms business service push the message to the Topic.
you say
user10341230 wrote:
The subscriber will (asynchronously) invoke another proxy to pickup the messagethe subscriber can be either asyncrhnous, in which case you need a proxy service with inbound protocol jms. or as you probably need a synchronous one
in which case you need another proxy with whatever inbound protocol you like whch once called in its pipeline calls some pojo class to read from this topic synchrnously (you need a durable subsciber).
Regards,
Tony
ps: have a look http://download-llnw.oracle.com/docs/cd/E11035_01/wls100/jms/design_best_practices.html#wp1058694

How to make message transfer to a topic from a business service synchrouns?

hi,
I am posting a message to a JMS queue using a business service (say A) and then I am fetching that message from that queue and using a proxy service (B) and a business service (C) for transferring that message to a topic, now I want that my business service A gets the same message that it initially posted as a response back from the topic to make the whole message transfer synchronous, but the problem is that as I select topic on my JMS transport configuration page of business service the text box where I need to specify the URI for the topic gets blocked,hence I am unable to get a response from the topic, can anybody help me out with this as I really want to make this synchronous.
Edited by: user12826319 on Jul 21, 2010 4:36 AM

yes u got it correct...v require a synchronous message transfer to happen i believe d alternative can be that i send the message to topic directly using a business service and expect a response from the topic itself in the form of the message i initially posted, that thing I would manage but the real problem is to get a response to the business service when i use topic, because as i select topic on JMS transport configuration page of business service the end point URI textbox gets blocked...

Garbage added to log file while sending messags to weblogic JMS topic

Hi All,
While I am sending messages to JMS Topic some debug statements are printed to stdout...
which is only happening in production rather than in dev environment, hence I feel this is a configuration issue..
sheding light on this issue is greatly appreciated,
thanks in advance !
regards,
Ambha

Thanks for the replies,
The problem is certainly not with logger settings...
The statements which are getting printed are SSL debugging
The following settings are used by the application which sends messages to the topic :
Dssl.debug=true
Dweblogic.StdoutDebugEnabled=true
These settings are same in Dev, UAT, and Production. But why the debug statements are seen only
in UAT and Production I am not sure...
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
*<Some TIME IST> <Debug> <TLS> <000000> <......>*
any Ideas... ?
Thanks
Ambha

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

Convert JMS Headers from EBCDIC to ASCII when using JMS Bridge (WLS - WMQ)

I have a Java app on Weblogic 11g using a Message Bridge to talk JMS with IBM Websphere MQ. The MQ server is running on IBM z/OS platform which uses EBCDIC encoding. I need to use the Weblogic message selector feature to filter messages on the bridge coming from Websphere MQ. But the JMS Headers of MSGs posted by WMQ are in EBCDIC format. How can I instruct MQ to convert the msg headers to ASCII before put on the bridge? Is there any flag on bindings config file? Or can I set some WMQ specific header before sending the msg on WLS side?
Thanks in advance.

Hi,
Such option is not possible in weblogic but I think this property will help you with in MQ.
Property - Convert EBCDIC newline
Description - EBCDIC code pages contain a new line (NL) character that is not supported by the ASCII code pages (although some ISO variants of ASCII contain an equivalent). If messages are sent from a system that uses EBCDIC code pages (for example, a z/OS system) to a system that uses ASCII, you can control how the EBCDIC newline character is converted into ASCII format.
The default value is NL_TO_LF, which means that the EBCDIC NL character (X'15') is converted to the ASCII line feed character LF (X'0A') for all EBCDIC to ASCII conversions. To convert the EBCDIC NL character according to the conversion tables on your operating system, click TABLE. Note that the results of a TABLE conversion can vary from platform to platform and from language to language; even on the same platform the results might vary if you use different coded character set identifiers (CCSIDs). To convert ISO CCSIDs using the TABLE method and use the NL_TO_LF method for all other CCSIDs, click ISO.
Registry Stanza Key - ConvEBCDICNewline
Also, the MQSeries (not MQSC) adapter provides the data conversion property may handle this conversion as well.
Regards,
Kal

Safari bookmarks bar disappears - even when settings set to display

Not sure if anyone else has this bug, but the bookmarks bar in Safari disappears even after the option is turned on in Settings/Safari.
Ideas?

Another detail is that I am set to sync bookmarks via MobileMe. That is working fine.

Messages posted to JMS Topic from OSB disappear even when not subscribed

Similar Messages

Maybe you are looking for