Message Bridge problems
Hi Tom,
Message Bridge is configured to transfer messages from AQ to DQ.
When the Message Bridge is deployed on Admin Server & Cluster, it works successfully. But, a closer look reveals that it’s the instance deployed on the Admin Server (and not the ones on the cluster) which is doing the job of looking up AQ & DQ and transferring messages from AQ to DQ. Monitoring Message Bridge instances on the cluster shows "WARN: failed to look up the source adapter." The corrective action for this is "Check if the adapter is deployed or the JNDI name in the source JMSBridgeDestination instance is correct.". But the adapter is correctly deployed and the JNDI name of the AQ is correctly bound, else the Message Bridge wouldn't have shown "Forwarding messages." for Admin Server's Message Bridge instances. The same set of configuration (MB destinations and MB) is shared by the Message Bridge instances on Admin Server & Cluster. So, the question of incorrect configuration of the JMS destinations i.e. AQ & DQ doesn't arise.
Can you point out where the problem could be ? ?:|
Cheers
Dips
Patch for this problem should be added to the front of your WLS instance's CLASSPATH prior to any weblogic classes. This issue is resolved in WLS 8.1 SP3 and this is the recommended path to resolution, the patch should be used only if one can't upgrade to SP3.
CR126671
Setup a cluster configuration on 8.1SP1 with at least on managed server in the cluster. Deploy the bridge adapter jms-xa-adp.rar to the cluster. Configure a bridge and target it to the cluster.Bridge never receives Add
Notification for the adapter. However, if you retarget the adapter to the individual servers in the cluster it works fine.
Dips
Similar Messages
-
JMS Messaging Bridge Problems with WLS 8.1 sp2
Thank you in advance for your help.
I am trying to configure a JSM Messaging Bridge to connect an MQ Q to a Weblogic
Q. I have this working wonderfully in an environment without clustering but once
I try to deploy to a cluster, I am having two major problems.
1) When the managed servers are restarted, the messaging bridges immediately complain
about not being able to find the resource adaptor. After I manually un-target
the messaging bridge from the cluster and re-target them, they find the resource
adaptor but cannot connect to the source... which leads to my next problem.
2) The messaging bridges cannot connect to the source destination whether it is
an MQ Q or a Weblogic JMS Q does not matter. Here are the log entries that I
see relative:
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Got Notification:weblogic.management.AttributeAddNotification:
Deployments from <null> to [Caching Stub]Proxy for eBusDev02:Location=secaServer01,Name=seca_OES_ADV_REPLY
Messaging Bridge,Type=MessagingBridgeConfig - weblogic.management.AttributeAddNotification[source=eBusDev02:Location=secaServer01,Name=secaServer01,Type=ServerConfig].>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! creating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is deployed as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Initializging bridge seca_OES_ADV_REPLY Messaging
Bridge as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
source configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = file:/e:/private/JNDI/eBusDev02
DestinationType = Queue
DestinationJNDIName = jms.oes.MQ-ADV-REPLYQ
InitialContextFactory = com.sun.jndi.fscontext.RefFSContextFactory
ConnectionFactoryJNDIName = jms.oes.MQ-QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge's
target configurations are:
AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
Classpath=null
ConnectionURL = t3://30.135.10.63:8103,30.135.10.63:8104
DestinationType = Queue
DestinationJNDIName = jms/oes/ADV-REPLYQ
InitialContextFactory = weblogic.jndi.WLInitialContextFactory
ConnectionFactoryJNDIName = jms/oes/QCF
.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging STARTUP! Bridge seca_OES_ADV_REPLY Messaging Bridge
is successfully initialized.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully initialized as a migratable.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Activating bridge seca_OES_ADV_REPLY Messaging
Bridge.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
has been successfully activated..>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200033>
<Bridge "seca_OES_ADV_REPLY Messaging Bridge" is obtaining connections to the
two adapters.>
####<Apr 1, 2004 4:38:44 PM EST> <Debug> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200006>
<Messaging bridge debugging RUNTIME! Bridge seca_OES_ADV_REPLY Messaging Bridge
Getting source connection.>
####<Apr 1, 2004 4:38:44 PM EST> <Info> <MessagingBridge> <dv2kwls03> <secaServer01>
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <> <BEA-200042>
<Bridge seca_OES_ADV_REPLY Messaging Bridge failed to connect to the source destination
and will try again in 15 seconds. (java.lang.NullPointerException)>
I know the queues are up and I am pretty sure my MQ client configuration is correct.
Is there anyway to get more information about the NullPointerException or the
error being encountered?
Given that you have ruled out message backlogs, my first suspicion is that the leak has something to do with connection allocation. Does JMS stats reveal an application generated connection leak? Check to see if the current number of connections/sessions stays steady.
If this doesn't help, you can use a third party tool like OptimizeIt to get periodic snap-shots of memory usage and identify the leaked object (or create a reproducer and have customer support do it). A possible work-around is to modify your app to pool JMS connections/sessions for re-use - greatly reducing the number of connections created per day.
Tom -
Hi,
I've set up a messaging bridge between 2 Weblogic 8.1 SP5 boxes, and am getting the following generic error when it's trying to connect to the target. I've got bridge debugging on.
I've tried all the usual suspects: XA enabled connection factories, disabled certificate generation and set certificate to the same thing for both servers, disable guest is unchecked, connectors are deployed, etc.
This error message is useless...anyone have any ideas?
<Aug 16, 2006 2:56:24 PM IDT> <Debug> <MessagingBridge> <BEA-200006> <Messaging bridge debugging RUNTIME! Bridge bridge.test Getting target connection.>
<Aug 16, 2006 2:56:24 PM IDT> <Warning> <Connector> <BEA-190032> << Weblogic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocationException of javax.resource.ResourceException: Failed to start the connection on createManagedConnection.>The bridge just does a basic JNDI lookup, and there's nowhere to put additional parameters. However, you can do this using a "Foreign JMS Server".
Create a "Foreign JMS Server" either using the console, or by putting a ForeignJMSServer entry in config.xml. There is a "JNDI Properties" field, where you can specify your security credentials in name/value form (you'll need the values of those JNDI constants, which are "javax.jndi.something.something", not SECURITY_PRINCIPAL and SECURITY_CREDENTIALS.)
Then, have the bridge look up the "Local JNDI Name" from the Foreign JMS bean rather than the remote TIBCO JNDI object. (You do this by removing all the JNDI parameters from the bridge destination so that it uses the local JNDI provider, not the TIBCO JNDI provider.)
Essentially, by doing this, the Foreign JMS code in WLS is going to delegate the JNDI lookup to the TIBCO provider using all the JNDI parameters you specify, including security. -
When opening Bridge (CS6) I get the following message: "Bridge encountered a problem and is unable to read the cache. Please try purging the central cache in Cache Preferences to correct the situation" I tried and after selecting purge cache it does not allow me to select OK. Also Bridge keeps saying "Building Criteria" with the spinning wheel and nothing happens. I tried uninstalling and reinstalling to no avail. Please help:)
Maybe a Preferences reset can help:
Numerous program settings are stored in the Adobe Bridge preferences file, including display, Adobe Photo Downloader, performance, and file-handling options.
Restoring preferences returns settings to their defaults and can often correct unusual application behavior.
Press and hold the Ctrl key (Windows) or the Option key (Mac OS) while starting Adobe Bridge.
In the Reset Settings dialog box, select one or more of the following options:
Reset Preferences
Returns preferences to their factory defaults. Some labels and ratings may be lost. Adobe Bridge creates a new preferences file when it starts.
Purge Entire Thumbnail Cache
Purging the thumbnail cache can help if Adobe Bridge is not displaying thumbnails properly. Adobe Bridge re-creates the thumbnail cache when it starts.
Reset Standard Workspaces
Returns Adobe predefined workspaces to their factory default configurations.
Click OK, or click Cancel to open Adobe Bridge without resetting preferences. -
My bridge is not working normally and keep given me this message : bridge encountered a problem and is unable to read the cache . Please try purging the central cache in cache preferences to correct the situation
And did you then actually purge the cache?
Please realize that you have given ZERO details.
BOILERPLATE TEXT:
Note that this is boilerplate text.
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CS6", but something like CS6v.13.0.6) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
a screen shot of your settings or of the image could be very helpful too.
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks! -
When opening Bridge I get this message: Bridge encountered a problem and is unable to read the cash. Please try purging the central cache in the cache preferences to correct this problem. I did this and still get this same message.Also now when deleting images they don't delete till I close and reopen Bridge. What can i do to fix this problem?
Maybe a Preferences reset can help:
Numerous program settings are stored in the Adobe Bridge preferences file, including display, Adobe Photo Downloader, performance, and file-handling options.
Restoring preferences returns settings to their defaults and can often correct unusual application behavior.
Press and hold the Ctrl key (Windows) or the Option key (Mac OS) while starting Adobe Bridge.
In the Reset Settings dialog box, select one or more of the following options:
Reset Preferences
Returns preferences to their factory defaults. Some labels and ratings may be lost. Adobe Bridge creates a new preferences file when it starts.
Purge Entire Thumbnail Cache
Purging the thumbnail cache can help if Adobe Bridge is not displaying thumbnails properly. Adobe Bridge re-creates the thumbnail cache when it starts.
Reset Standard Workspaces
Returns Adobe predefined workspaces to their factory default configurations.
Click OK, or click Cancel to open Adobe Bridge without resetting preferences. -
Problems starting a Message Bridge on 8.1sp3
Hi,
We've been ruuning weblogic server 8.1 sp2 for sometime using a message bridge it has always startted transferring message automatically after a ser ver restart, you see messages such as :
Oct 12, 2004 10:27:10 AM BST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 16
1.2.231.193>
<Oct 12, 2004 10:27:10 AM BST> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
<Oct 12, 2004 10:27:10 AM BST> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has been backed up at
/qv/dev/capg002b/weblogic/./config.xml.booted.>
<Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200020> <Bridge "BLS-BLP Messaging Bridge" is stopped.>
<Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200033> <Bridge "BLS-BLP Messaging Bridge" is obtaining connections to the two adapters.>
<Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200032> <Bridge "BLS-BLP Messaging Bridge" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
<Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200030> <Bridge "BLS-BLP Messaging Bridge" is configured to work in "Exactly-
once" mode, and it is actually working in "Exactly-once" mode.>
<Oct 12, 2004 10:27:44 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
<Oct 12, 2004 10:28:09 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
<Oct 12, 2004 10:28:34 AM BST> <Info> <MessagingBridge> <BEA-200028> <The bridge "BLS-BLP Messaging Bridge" has started transferring messages.>
but with 8.1sp3 the Message Bridge does NOT automatically start transferring messges after a restart and you get messgaes like this :
<Oct 12, 2004 10:42:24 AM BST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 8001, ip address 161.2.231.193>
<Oct 12, 2004 10:42:24 AM BST> <Info> <Management> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
<Oct 12, 2004 10:42:24 AM BST> <Info> <Configuration Management> <BEA-150007> <The booted configuration ./config.xml has been backed up at /qv/dev/capg002b/weblogic/./config.xml.booted.>
<Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200020> <Bridge "BLS-BLP Messaging Bridge" is stopped.>
<Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200033> <Bridge "BLS-BLP Messaging Bridge" is obtaining connections to the two adapters.>
<Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200032> <Bridge "BLS-BLP Messaging Bridge" is configured to disallow degradation of its quality of service in cases where the configured quality of service is unreachable.>
<Oct 12, 2004 10:43:07 AM BST> <Info> <MessagingBridge> <BEA-200030> <Bridge "BLS-BLP Messaging Bridge" is configured to work in "Exactly-once" mode, and it is actually working in "Exactly-once" mode.>
with sp3 the message transfer needs to be started manually from the browser console.
So my questing : why is bridge start up not automatic in sp3, bug ? or feature ?
thanks
justinI've got some more info on this, and it gets stranger !!
Basically I upgraded another system that uses Message Briging to sp3, and miraculuously, the transfer DID start automatically as desired. Very confusing ! so I compared the MessagingBridge stanzas in the config.xml for each system:
this from the "broken" system where the bridge does not automatically start :
<MessagingBridge Name="DStoMHMessagingBridge"
QualityOfService="Exactly-once"
SourceDestination="DStoMHSourceDestination" Started="true"
TargetDestination="DStoMHTargetDestination" Targets="datasourceCluster"/>
and this from the system where the bridge DOES automatically start :
<MessagingBridge BatchSize="1" Name="BLS-BLP Messaging Bridge"
SourceDestination="BLS-BLP Bridge Source Destination"
Started="true"
TargetDestination="BLS-BLP Bridge Target Destination" Targets="smpd289-bls1"/>
I noticed that
QualityOfService="Exactly-once"
was missing from the working system, so removed it from the broken system. And sure enough the bridge transfer DID start automically, when it had'nt done before. Problem fixed.
So there are several questions :
1. Why does the QualityOfService setting have an impact on whether the Bridge starts automatically ?
2. When you look at the web console on both the working and broken original systems and on the "broken" system with the QualityOfService="Exactly-once" line removered, It still says Exectly-once on the webpage. So Why this miss-match between whats contained in config.xml and whats shown on the webconsole ? -
Problems with Messaging Bridge and MQ.
Hi,
I'm trying to use the Weblogic messaging bridge to provide a set of local queues
to my application server from a set of MQ queues, using XA.
My problem is that when the bridge starts up, it gives the following error:
<Aug 5, 2002 4:35:14 PM BST> <Info> <MessagingBridge> <Bridge "BRIDGE.STATUS1"
failed to connect to the source destination and will try again in 20 seconds.
(javax.resource.spi.ResourceAllocationException: CreateManagedConnection Error:
ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory,
url = file:////blah/adminobjects, user name = null, password = null)>
<Aug 5, 2002 4:35:14 PM BST> <Notice> <WebLogicServer> <ListenThread listening
on port 8051>
I think the problem is as follows...
This bridge should be connecting to a file-server JNDI implementation, and should
therefore being trying to obtain a com.sun.jndi.fscontext.RefFSContextFactory
initial context, not a weblogic.jndi.WLInitialContextFactory one. I have set up
the destination in the weblogic console with a file server context, but this doesn't
have any effect.
The file server JNDI implementation definitely works, as I can access the queues
directly and use them to call MDBs.
Can anyone help?
You mentioned that the patch initially worked. What did you do after
that?
You can turn on the messaging bridge debug by adding those to
you script for starting the server:
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
See what you get in the server log.
You need to post your config.xml and the script as well for further
help.
Dongbo
Christopher Sceats wrote:
>
> I'm afraid this is not the problem - I have all of the required things in my PATH
> and CLASSPATH:
>
> CLASSPATH:
> com.ibm.mq.jar
> com.ibm.mqbind.jar
> com.ibm.mqjms.jar
>
> PATH:
> /opt/mqi/bin
> /opt/mqi/java/lib
>
> Dongbo Xiao <[email protected]> wrote:
> >The possible problem is your PATH and CLASSPATH. You have to have the
> >
> >MQSeries stuff in your PATH and CLASSPATH (NOT the AdapterClasspath
> >attribute of your BridgeDestination) for starting the WebLogic server.
> >
> >Those are all documented. Please take a look
> >at the WebLogic Server online doc
> >http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html
> >and
> >the latest integrating foreign providers white-paper. It is
> >available on dev2dev, or you can find it here:
> >http://newsgroups.bea.com/cgi-bin/dnewsweb?cmd=article&group=weblogic.developer.interest.jms&item=9364&utag=
> >
> >Dongbo
> >
> >
> >Christopher Sceats wrote:
> >>
> >> Thanks Dongbo.
> >>
> >> This initally worked and I was able to connect the bridge to the source
> >destination.
> >> However, today this no longer works, and I get the following error...
> >>
> >> <Aug 6, 2002 12:00:02 PM BST> <Warning> <Connector> << Weblogic Messaging
> >Bridge
> >> Adapter (XA) > ResourceAllocationException of javax.resource.ResourceException:
> >> Failed to start the connection on createManagedConnection.>
> >>
> >> Having seen a previous post on this subject, I tried sending a message
> >to this
> >> queue with a standalone client, and this works fine. However, when
> >I use the application
> >> server it fails to start the connection. Is there any way I can get
> >further diagnostics?
> >>
> >> Dongbo Xiao <[email protected]> wrote:
> >> >Are you using 6.1SP3? There is a known problem in 6.1SP3 that may
> >have
> >> >caused
> >> >your problem. Contact BEA support to get the Temporary Patch for the
> >> >problem.
> >> >The internal Change Request is CR081511 and the patch is
> >> >CR081511_61sp3.jar.
> >> >
> >> >Dongbo
> >> >
> >> >
> >> >Christopher Sceats wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I'm trying to use the Weblogic messaging bridge to provide a set
> >of
> >> >local queues
> >> >> to my application server from a set of MQ queues, using XA.
> >> >>
> >> >> My problem is that when the bridge starts up, it gives the following
> >> >error:
> >> >>
> >> >> <Aug 5, 2002 4:35:14 PM BST> <Info> <MessagingBridge> <Bridge "BRIDGE.STATUS1"
> >> >> failed to connect to the source destination and will try again in
> >20
> >> >seconds.
> >> >> (javax.resource.spi.ResourceAllocationException: CreateManagedConnection
> >> >Error:
> >> >> ConnectionFactory: failed to get initial context (InitialContextFactory
> >> >=weblogic.jndi.WLInitialContextFactory,
> >> >> url = file:////blah/adminobjects, user name = null, password = null)>
> >> >> <Aug 5, 2002 4:35:14 PM BST> <Notice> <WebLogicServer> <ListenThread
> >> >listening
> >> >> on port 8051>
> >> >>
> >> >> I think the problem is as follows...
> >> >>
> >> >> This bridge should be connecting to a file-server JNDI implementation,
> >> >and should
> >> >> therefore being trying to obtain a com.sun.jndi.fscontext.RefFSContextFactory
> >> >> initial context, not a weblogic.jndi.WLInitialContextFactory one.
> >I
> >> >have set up
> >> >> the destination in the weblogic console with a file server context,
> >> >but this doesn't
> >> >> have any effect.
> >> >>
> >> >> The file server JNDI implementation definitely works, as I can access
> >> >the queues
> >> >> directly and use them to call MDBs.
> >> >>
> >> >> Can anyone help?
-
Messaging Bridge/Resource adapter problem on Solaris?
Has anyone successfully used the supplied resource adapter and messaging bridge
on Solaris? We seem to have problems getting the resource adapter to be bound
properly. After creating a connector through the admin console (using any of the
weblogic supplied jms-*-adp.rar files) the element shows up in the JNDI tree but
has no object information associated with it - which I assume means it is not
bound. The following error shows up in the weblogic log file:
####<Jan 24, 2003 6:28:03 PM CST> <Error> <Connector> <fssun02> <AdminServer>
<ExecuteThread: '0' for queue: '__weblogic_admin_html_queue'> <kernel identity>
<> <190004> <ManagedConnectionFactory not found for jndiName eis/jms/WLSConnectionFactoryJNDINoTX.>
We are using WL 7.0.1.0 and Solaris 2.8 (8). With the same configuration on Win
2K everything works properly. Classpath's etc all seem to be correct. Any ideas?
thanks,
I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
So here goes with my suggestion based on what I have done.
1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
2. In the Local Bridge Destination, put :
Connection URL - nothing
Initial Context Factory - weblogic.jndi.WLInitialContextFactory
Connection Factory JNDI Name - <your JMS conection factory name>
Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
I hope that works.
Andy -
Hi
I'm having some difficulties with the jms-notran-adp messaging brigdge.
The messaging bridge won't work. I'm trying to bridge a MQS 5.2 queue to a weblogic
7.0 queue. The MQS queue and connectionFactory can be found properly from the
filesystem JNDI Provider (meaning I can send a message to this queue from a MDB)
there is no error message during startup but when I try to redeplay there's a
message saying:<error> <connector> >> Weblogic Messaging Bridge Adater (No TX)
Error making initial connections for pool. Reason: Create ManagedConnection Error:
Failed to start the connection>
Thanks
Flo
Here are the most seen problems when using bridge between WLS and
MQSeries:
1. You have to have some MQSeries stuff in your CLASSPAHT and PATH for
starting
the WebLogic Server that hosts the bridge. For details in the
following docs:
http://dev2dev.bea.com/resourcelibrary/whitepapers.jsp?highlight=whitepapers
and
http://edocs.bea.com/wls/docs70/adminguide/msgbridge.html
2. if you have UserName configured for any BridgeDestination (or
JMSBridgeDestination), you have to provide a UserPassword as well.
3. The MQSeries server has to be on the same machine for exactly-once
QOS to work.
4. It is recommended that you put your adapter rar files in a directory
other than
the applications directory and point to that directory in the
config.xml.
In addition, you can always turn on debug to see more detailed error
messages using
-Dweblogic.Debug.DebugMessagingBridgeStartup=true
-Dweblogic.Debug.DebugMessagingBridgeRuntime=true
Hope this helps.
Dongbo
Florian wrote:
>
> Hi
>
> I'm having some difficulties with the jms-notran-adp messaging brigdge.
>
> The messaging bridge won't work. I'm trying to bridge a MQS 5.2 queue to a weblogic
> 7.0 queue. The MQS queue and connectionFactory can be found properly from the
> filesystem JNDI Provider (meaning I can send a message to this queue from a MDB)
>
> there is no error message during startup but when I try to redeplay there's a
> message saying:<error> <connector> >> Weblogic Messaging Bridge Adater (No TX)
> Error making initial connections for pool. Reason: Create ManagedConnection Error:
> Failed to start the connection>
>
> Thanks
> Flo
>
-
Hi friends,
I've a strange problem. I've posted a problem on another newsgroup concerning remote lookup as you can see below.
I'm working on WLS8.1sp2. 2 clusters (front-end with webapps and back-end with ejbs with a firewall without nat between they). Message bridges deployed on back end.
When that problem during loockup(see below) occurs I noticed also this exception regarding message bridge:
####<Jun 6, 2005 6:26:38 PM CEST> <Warning> <MessagingBridge> for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-200026> <Bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" encountered some problems in one of its adapters or underlying systems. It stopped transferring messages and will try to reconnect to the adapters shortly. (The exception caught was weblogic.jms.common.LostServerException: weblogic.rjvm.PeerGoneException: ; nested exception is:
java.io.EOFException.)>
####<Jun 6, 2005 6:26:38 PM CEST> <Error> <MessagingBridge> <ExecuteThread: '120' for queue: 'weblogic.kernel.Default'> <<WLS Kernel>> <BEA1-009BCF7999A0A21B1158> <BEA-200015> <An error occurred in bridge "Bridge1-SourceWLXQueueSend > TargetWLSQueueSend" during the transfer of messages (javax.resource.ResourceException: Error receiving message).>
I'm working on weblogic server 81.sp2.
I've 2 clusters (front-end cluster with web apps and back-end cluster with ejbs) with 2 active server per cluster.
Randomically when I try to make a lookup on the back-end cluster with a servlet deployed in the front-end cluster I received the following error:
javax.naming.CommunicationException. Root exception is java.rmi.ConnectExceptio
n: Unable to get direct or routed connection to: '7425491688784079753S:cihpas04:
[7200,7200,-1,-1,7200,-1,-1,0,0]:cihpas03:7100,cihpas03:7300,cihpas03:7500,cihpa
s04:7200,cihpas04:7400,cihpas04:7600:cie:CIEServer2'
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.j
ava:108)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:284)
at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteR
ef.java:244)
at weblogic.jndi.internal.ServerNamingNode_812_WLStub.lookup(Unknown Sou
rce)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:343)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:336)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
at Cie.servlet.SSCE.CIE045_Ping_Servlet.service(CIE045_Ping_Servlet.java
:157)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:971)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:402)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:305)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6350)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:
118)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3635)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2585)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
Can you help me for both problems?tnx in advancegabriele.folchi,
did you ever resolved this issue ? -
Problem receiving message through Messaging Bridge
Hi!
I am using WLS7.0, and trying to correctly setup two messaging
bridges: one from a WLJMS_SEND_QUEUE to a MQJMS_SEND_QUEUE and
one from a MQJMS_RECEIVE_QUEUE to a WLJMS_RECEIVE_QUEUE.
When sending on the local send queue WLJMS_SEND_QUEUE, the
messages are being forwarded to the remote send queue
MQJMS_SEND_QUEUE as expected, but when setting the JMSReplyTo
field to the local receive queue WLJMS_RECEIVE_QUEUE, no
message is received.
Do I really need to set the JMSReplyTo field to the remote
receive queue? I would like to work only with the local
queue definitions... if possible.
Any hint would be greatly appreciated,
Guillaume Bedard
This is a dark section of the JMS specification. From section 3.12,
"Note the following exception case when a provider is handling a foreign
message implementation. If the foreign message implementation contains a
JMSReplyTo header field that is set to a foreign destination implementation,
the provider is not required to handle or preserve the value of this header
field."
This is to allow wiggle room with respect to serialization and validation of
foreign destinations. In your scenario you have a WebLogic sender that
wants a reply on a WebLogic queue. You put a replyTo of the WebLogic queue
in the message. When that message makes it to MQSeries land and it tries
to respond using an MQSeries producer to a WebLogic queue, bad things
happen. There is no way it can work because MQSeries has no way to handle
WebLogic destinations. In reality the MQSeries application receiving the
message does not want to send it to the WebLogic queue, but to the MQSeries
queue that forwards to the WebLogic queue. That means the WebLogic producer
sends to a WebLogic queue, but puts a replyTo of an MQSeries queue (of
which it knows nothing about in this scenario), and then receives on the
WebLogic queue (even though it said to reply to the MQSeries queue).
Then of course there is the serialization of the foreign destination. You
could just serialize to bytes, and leave it that way. WebLogic does
validation of replyTo queues and the like, so it would try to unserialize
the replyTo destination specified in the message. If this is an MQSeries
destination, then WebLogic may not have the necessary classes on the server
to unserialize the replyTo destination.
_sjz.
-
Messaging Bridge and cluster problem
I am trying to setup the Messaging Bridge between MQ and WLS. Originally, we were going to use the Foreign JMS setup but the loss of transactionality was an issue (QManager cannot be assumed to be on the same box as our cluster). So we moved to the Messaging Bridge in the hopes that it will provide greater stability.
I am following the example provided here https://messaging-bridge.projects.dev2dev.bea.com/ and setting up 2 JMS Destinations. Setting up the MQ Destination was trivial given that I had done it already with the Foreign JMS setup.
But the destination that points to the internal WLS JMS Queue is a little trickier given that we are using clusters. I am stuck trying to figure out what Connection URL I should be using. According the the example above, I should use t3://localhost:7001 but in a clustered setup, what do I point to?I finally got my Messaging Bridge (Tibco to a WLS Cluster) to work. See my post 3 messages before yours - to which no-one responded... :-(
So here goes with my suggestion based on what I have done.
1. Create a Distributed Destination for the WLS queue and "auto deploy" it your cluster. (Read the manual on how to do that, it is quite straightforward).
2. In the Local Bridge Destination, put :
Connection URL - nothing
Initial Context Factory - weblogic.jndi.WLInitialContextFactory
Connection Factory JNDI Name - <your JMS conection factory name>
Destination JNDI Name - <the JNDI name given to the Distributed Destination>.
I hope that works.
Andy -
When i open pc an adobe bridge problem denotes purging
when i open computer an adobe bridge problem denotes purging
Are you trying to say that pointing to your computer in Bridge you get an error message telling you that you need to purge the central Cache?
If so, go ahead and purge it.
Your post is not clear at all. Try rephrasing it, please.
Also:
A lot more information about your hardware and software is needed.
BOILERPLATE TEXT:
If you give complete and detailed information about your setup and the issue at hand,
such as your platform (Mac or Win),
exact versions of your OS, of Photoshop (not just "CC", but something like CC2014.v.2.2) and of Bridge,
your settings in Photoshop > Preference > Performance
the type of file you were working on,
machine specs, such as total installed RAM, scratch file HDs, total available HD space, video card specs, including total VRAM installed,
what troubleshooting steps you have taken so far,
what error message(s) you receive,
if having issues opening raw files also the exact camera make and model that generated them,
if you're having printing issues, indicate the exact make and model of your printer, paper size, image dimensions in pixels (so many pixels wide by so many pixels high). if going through a RIP, specify that too.
a screen shot of your settings or of the image could be very helpful too,
etc.,
someone may be able to help you (not necessarily this poster, who is not a Windows user).
Please read this FAQ for advice on how to ask your questions correctly for quicker and better answers:
http://forums.adobe.com/thread/419981?tstart=0
Thanks! -
CS6 Bridge and Mini Bridge problems
Installed CS6 and clicked on Brose in Bridge. I get the rror messare could not complete the Brose in Bridge commmand because Photoshop was unable to find the Java Script plugin. Also when clicking on Brose in Mini Bridge I get the message cannot complete the command because the extension could not be loaded I have uninstalled CS6 and reinstalled it and get the samew message Help please
Thank you very much I will try that
In a message dated 11/24/2014 12:41:45 P.M. Central Standard Time,
[email protected] writes:
CS6 Bridge and Mini Bridge problems
created by Flashy1995_ (https://forums.adobe.com/people/Flashy_1995) in
Photoshop General Discussion - View the full discussion
(https://forums.adobe.com/message/6958475#6958475)
Maybe you are looking for
-
Getting Error message couldn't open XPCOM and can't open ANY pages
After load of updates were completed, I keep getting this Error 'COULDN'T OPEN XCOM' I can't open any programs or emails, Firefox won't open or IE. Have tried System Restore a number of times without any luck, even that doesn't complete successfully,
-
Apple iphone 4 no ringer, mute switch is off, no volume indicator on screen. tried hard restart and reconfigured via itunes, have IOs 6.1.2, no jailbreak. Can hear ringer with earphone- Have tried almost everything, buit nothing happens. Any suggest
-
Table for PO Followoing Documents
Hi Gurus, Please tell me the table for Purchase Order Following documents table. Suppose i had a PO which had Inbound Delivery and GR or Handling Unit Documents. I want the table which contains all these document numbers for PO.
-
Clean of wiki page of Xorg [Wiki]
Just to be clear, I have almost zero knowledge of Xorg and etc. With the upcoming release of Xorg 1.8, I think a clean and clearer page on the Wiki would be a must for the future. Now the page contain stuff from several years and several versions of
-
HT1688 the activation server is temporarily unavailable
My imei number is 012575006020744 I unlocked my phone but I have this Your iPhone could not be activated because the activation server is temporarily unavailable. Try connecting your iPhone to iTunes to activate it, or try again i a couple of minutes