Messaging bridge with JBoss
Hi
I am trying to configure a messaging bridge between weblogic 8.1 sp4 and jboss-4.0.2 on my local machine.
I have the bridge working for the following configuration:
Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDINoTX
Connection URL: jboss server URL with port
Initial Context Factory: org.jnp.interfaces.NamingContextFactory
Connection Factory JNDI Name: ConnectionFactory
Destination JNDI Name: queue/testQueue
and these jar's are in my weblogic class path:
[jboss_home]/client/jboss-common-client.jar
[jboss_home]/client/jbossmq-client.jar
[jboss_home]/client/jboss-system-client.jar
[jboss_home]/client/jboss-transaction-client.jar
[jboss_home]/client/jnp-client.jar
[jboss_home]/lib/concurrent.jar
[jboss_home]/client/log4j.jar
I have also deployed connector module jms-notran-adp.rar on my weblogic server.
I am using "Duplicate-okay" Quality Of Service and the bridge functions correctly.:^O
Now when I try to configure the bridge so that I can use "Exactly-once" Quality Of Service I use the following configuration:
Adapter JNDI Name: eis.jms.WLSConnectionFactoryJNDIXA
Connection URL: jboss server URL with port
Initial Context Factory: org.jnp.interfaces.NamingContextFactory
Connection Factory JNDI Name: XAConnectionFactory
Destination JNDI Name: queue/testQueue
and add these jar's in my weblogic class path:
[jboss_home]/client/jboss-common-client.jar
[jboss_home]/client/jbossmq-client.jar
[jboss_home]/client/jboss-system-client.jar
[jboss_home]/client/jboss-transaction-client.jar
[jboss_home]/client/jnp-client.jar
[jboss_home]/lib/concurrent.jar
[jboss_home]/client/log4j.jar
I also deployed the connector module jms-xa-adp.rar on my weblogic server.
The connection factory that I use for the weblogic destination is also "XA enabled".
The problem which I have is that no messages are transferred via the bridge and following error is printed out from the server :_|:
<2005/08/15 12:20:22 PM> <Error> <Connector> <BEA-190091> <Call to implementation of ManagedConnection.getXAResource in resource adapter with jndiName = eis/jms/WLSConnectionFactoryJNDIXA failed: java.lang.IllegalStateException: can only be called from server>
Could you please assist.
Thanks in advance
Hi,
I am trying to do configure a bridge between weblogic 7.0 SP4 and JBOSS 4.0.3 SP1.
I have set the classpath as mentioned but I am getting an error
####<Apr 11, 2006 2:02:34 PM CEST> <Debug> <MessagingBridge> <DNI6> <dni6testser
ver> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200006> <M
essaging Bridge Debugging RUNTIME! Bridge WebOSSTEST Getting target connection>
####<Apr 11, 2006 2:02:34 PM CEST> <Warning> <Connector> <DNI6> <dni6testserver>
<ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <190032> << Web
logic Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > Resourc
eAllocationException of javax.resource.ResourceException: Failed to start the co
nnection on createManagedConnection.>
####<Apr 11, 2006 2:02:34 PM CEST> <Info> <MessagingBridge> <DNI6> <dni6testserv
er> <ExecuteThread: '10' for queue: 'default'> <kernel identity> <> <200043> <Br
idge "WebOSSTEST" failed to connect to the target destination and will try again
in 60 seconds. (java.lang.Exception: javax.resource.spi.ResourceAllocationExcep
tion: CreateManagedConnection Error: Failed to start the connection
at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
ctionPool.java:1009)
at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
ctionPool.java:1769)
at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
n(ConnectionPoolManager.java:191)
at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
ection(ConnectionManagerImpl.java:25)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMS
BaseConnectionFactory.java:126)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(Messaging
Bridge.java:764)
at weblogic.jms.bridge.internal.MessagingBridge.execute(MessagingBridge.
java:930)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
-------------- Linked Exception ------------
javax.resource.ResourceException: Failed to start the connection
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBase
Connection.java:1273)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnectio
n.java:357)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:2
29)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnect
ion(JMSManagedConnectionFactory.java:190)
at weblogic.connector.common.internal.ConnectionPool.makeResources(Conne
ctionPool.java:1002)
at weblogic.connector.common.internal.ConnectionPool.getConnection(Conne
ctionPool.java:1769)
at weblogic.connector.common.internal.ConnectionPoolManager.getConnectio
n(ConnectionPoolManager.java:191)
at weblogic.connector.common.internal.ConnectionManagerImpl.allocateConn
ection(ConnectionManagerImpl.java:25)
Does anyone have a solution
Similar Messages
-
Using Messaging Bridge with Distributed Destinations
I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
* WLS Server1:
* JMS Server1:
* inbound queue
* outbound queue
* JMS Server2:
* inbound queue
* outbound queue
* WLS Server 2:
* JMS Server3:
* inbound queue
* outbound queue
A distributed destination is configured for the inbound and outbound queues.
Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
Any suggestions?
Hi Rob,
Consumers on distributed destinations are always pinned
to a single physical destination on creation. Only
producers can round-robin each message. When a
distributed destination is used as a source destination,
you will need to configure a bridge per distributed
destination. Alternatively, you can enable
forwarding between the physical queues, which automatically
forwards messages from physical queues with
no consumers to physical queues that have consumers
(but the extra hop impacts performance). For more information,
consult the JMS documentation.
Tom
Rob McArthur wrote:
> I'm having some problems using Distributed Destinations with the Messaging Bridge in WLS 7.0sp2. Our configuration consists of the following:
> * WLS Server1:
> * JMS Server1:
> * inbound queue
> * outbound queue
> * JMS Server2:
> * inbound queue
> * outbound queue
> * WLS Server 2:
> * JMS Server3:
> * inbound queue
> * outbound queue
>
> A distributed destination is configured for the inbound and outbound queues.
>
> Two messaging queues are configured so that bridge from WLS JMS to Tibco JMS using the distributed destinations.
>
> Everything is working fine for the inbound, but we have found that the outbound messaging bridge is picking up messages from only one of the two JMS servers on the first WLS instance. When monitoring, it can be seen that there is no consumer registered against the second JMS server.
>
> Any suggestions?
>
>
-
Messaging Bridge with MQ using SSL
Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks!Hi everybody,
I'm using JMS messaging bridge to transfer messages from WLS 10.3.6 running on a Solaris machine to remote WebSphere MQ 7 running on an AIX machine. Weblogic reads the configuration of remote MQ from a text file, called .bindings, created using the MQ JMSAdmin tool. The file defines a connection factory with the IP address, port, queue and queue manager name and other important definitions of the remote MQ.
The thing is that the bridge starts pretty well and transfer messages normally, but I need to change the configuration to use SSL. To do it I just added the parameter SSLCIPHERSUITE(SSL_RSA_WITH_RC4_128_MD5) and thought it was enough to achieve the goal.
<May 12, 2014 3:05:45 PM BRT> <Debug> <MessagingBridgeRuntimeVerbose> <BEA-000000> <Exception:
com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009
MQJE016: MQ queue manager closed channel immediately during connect
Closure reason = 2009
Wondering the error could be relatedo to an SSL exception, I enabled the SSL debugging (-Dssl.debug=true) to the managed server, but there were no evidences of an SSL handshake of Weblogic and MQ, so there is no SSL communication between the peers.
Does anybody know if this kind of communication is feasible? What may I be missing here?
Tks! -
Oracle JSF Bridge with JBoss Richfaces
Hello,
I have a JSF webapp using RichFaces libraries and I would like to connect to it from Oracle WCI portal. People advised me to use the Oracle JSF bridge, but I struggled to make it working...
I know that other bridges exist:
- JBossPortletBridge, that works great with Richfaces, but not WCI (more JBossPortal...)
- jsfportletbridge, for OpenPortal...
Does anybody succeed in doing this (Richfaces webapp with WCI...) ? It seems that it's possible but with an ADF webapp (Oracle, of course...).
I don't know how to configure the portlet.xml, and web.xml files because what I read in tutorials seem specific to Oracle ADF...
Do you know if, in my case, I should use an Oracle bridge, or a JBoss (->Richfaces) one, or is there any chance to doing this...
Thanks by advance :)Otherwise, instead of replacing all relative URL with absolute URL in Richfaces, do you know if WCI can be configured to gateway another URL than those which are defined in "Gateway URL Prefixes" in "HTTP Configuration" of the Web Service for Remote Portlet ?
In my case, when I run my portlet, the full URL is http://localhost:8080/portal/server.pt/gateway/PTARGS_0_0_208_0_0_43/RichfacesPortlet/test.jsf?javax.portlet.faces.ViewLink=true&org.jboss.portletbridge.NAMESPACE=PT__208
My Tomcat running the webapp is on port 8091, thus the gateway URL prefix is "http://localhost:8091/." (only the dot can be changed).
And when I click on an AJAX link, it calls /RichfacesPortlet/test.jsf?javax.portlet.faces.ViewLink=true and is not gatewayed thus it calls http://localhost:8080/RichfacesPortlet/test.jsf?javax.portlet.faces.ViewLink=true which does not exist !
How can I do to gateway this URL in WCI ?
Thanks for your future answers.
K.L. -
JMS Message Bridge with MQ, only BytesMessage available ?
I have successfully set up bridging between MQ and JMS, and have an MDB that receives messages via the bridge when a message producer puts messages on the MQ-queue. Ideally, I would like to receive MapMessages and not BytesMessages which seems to be the case. Is this at all possible ? It is not clear to me if this is determined by how messages are delivered to the MQ-queue or if it is a bridge configuration issue. The message producer uses the MQ Java API and not JMS to produce and publish messages.
The bridge uses the standard JMS API to dequeue the messages from MQ and provides no vendor specific tuning, so as long as IBM MQ supplies a map message in the first place things should work. In other words, if there's any special configuration required to get MQ to deliver map messages, you'll need to tune MQ, not WebLogic.
Tom
Bridges aren't often required for receiving from non-WebLogic JMS. See
http://e-docs.bea.com/wls/docs81/faq/interop.html -
JMS Message Bridge - WLS to MQ
Hi,
Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
just have couple of questions on that -
1. For a long time, I was struggling with this error on server startup
<BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
Thanks in advance.
best regards,
MuraliIn your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr. -
Weblogic Messaging Bridge - T3S Enabling Process
Dear All,
I need your help to resolve an issue in Weblogic Messaging Bridge - T3S enabling process.
I'm doing a POC to forward messages between 2 different domains (from wl 10.3.2 to wl 10.0) using Messaging Bridge with T3S Protocol.
I enabled SSL Port, Custom Identity and Custom Trust in those domains.
In my laptop (single JVM), WL Messaging Bridge in 10.3.2 is able to forward messages between domains using T3S.
My Testing Scenario:
A Sample web application use the https/t3s protocol to put message(s) in the source jms queue
Weblogic Messaging Bridge use the t3s protocol to get message(s) from source jms queue & forward the message(s) to the destination jms queue
But, When I tried the same POC in sepearate boxes (WL 10.3.2 in one box, WL 10.0 in another box). I got the below exceptiion.
Any one please throw some lights here to resolve the issue.
####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1318416109085> <BEA-000000> <Exception:
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
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:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
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:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.rmi.ConnectException: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
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.getInitialContext(WLInitialContextFactoryDelegate.java:352)
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:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
####<Oct 12, 2011 4:11:49 PM IST> <Warning> <Connector> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109086> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null) ">
####<Oct 12, 2011 4:11:49 PM IST> <Info> <MessagingBridge> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109089> <BEA-200043> <Bridge "Bridge-0" failed to connect to the target destination and will try again in 45 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null)
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1665)
at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1645)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:460)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
-------------- Linked Exception ------------
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
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:197)
at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
... 28 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
... 31 more
)>
####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115051> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
Thanks in advance.Think this can help you on the way - http://blog.eisele.net/2010/06/weblogic-server-ssl-httpst3s-and-java.html
-
Message Bridge Destination points to old IP, after failover with HA pair
Hi
Weblogic Version in use is 7.0sp7
We have this Messaging Bridge configured, between two instances of Weblogic server (Each weblogic server exists on Different Weblogic domains)
Both the weblogic servers run on the same machine.
So we have configured the message bridge destination with localhost, instead of an IP or DNS name in it.. viz.
t3://localhost:8001
t3://localhost:8020 respectively
where 8001 and 8020 are the listen ports of the respective weblogic servers.
This machine is a HA pair, controlled by vcs cluster server.
Which means when we failover from one node to another of the HA pair, the transition(which also involves the IP change from node A to node B) should be ideally transparent to weblogic.
But when it comes to these messaging bridge destinations
The Messaging bridge resolves the localhost in the Message Bridge destination to the old node IP, after the failover is done using vcs cluster server.
To me it looks like weblogic is caching the IP details somewhere and probably reusing it, unaware of the fact that the IP of the machine has changed after the failover.
I tried configuring the message bridge destination with addresses like t3://<DNSname>:8001 and 8020 respectively. But stiil it tries to connect to the IP of the old node only.
I did come across this patch in Weblogic 7.0 sp5, which is pretty close to the issue that i am encountering..
CR126201 In a multiple-server domain, if a Managed Server was rebooted to use a different address or port
number, the JTA subsystem failed to update the address information. This would cause the
following exception when the changed server was rebooted:
javax.naming.CommunicationException. Root exception is
java.net.ConnectException: t3://ip_address:port_number:
Destination unreachable;
nested exception is: java.net.ConnectException: Connection
refused; No available router to destination
Would really appreciate if someone can help with this issue.
Regards
AzadI'm not quite sure what the correct solution might be, but a possible work-around might be to hard-code the two addresses directly into the bridge URL. For example: t3://host:7010,host:7020. WebLogic will try each address in turn, starting from the first one until one succeeds or all fail.
Another solution might be to configure an "external listen address" on each server. This is the address that "reconnectable" external clients (such as EJBs or a bridge ) will use for reconnect in place of the server's actual listen address.
Tom -
HELP with JMS message bridge to MSMQ
Can anyone offer suggestions on how to obtain/build a JMS messaging bridge to MSMQ.
I see that WL has a Messaging Bridge but only for certain foreign messaging systems.
FioranoMQ have a JMS Implementation with a bridge to MSMQ but a complete JMS implementation
seems overkill and is costly.
We already have Weblogic's JMS implementation & just want messages to appear on
a JMS Queue when they are put in a MSMQ queue. A message driven bean will then
trigger from the JMS queue.
It is rare to hear of MSMQ when it comes to messaging.
(I guess MSMQ users typically stay in MS world?)
I suggest building a minimal subset JMS wrapper. Customers
have had success with this approach with other queuing products.
If you can implement asynchronous (onMessage) then the same
wrapper can be used to plug into MDBs as well as into the bridge.
You might find that there already is open source
for these wrappers, search the web.
Take note that interop is what web-services is supposed
to be all about. You might want to investigate writing
an MSMQ app that in turn invokes a WebLogic web-service
that finally enqueues to a WL queue.
Another possibility is to write an MSMQ app that invokes
WebLogic's JMS C client to put messages into a JMS
queue. The JMS C client is due out
shortly, perhaps this week, perhaps within the next
few weeks. It will be posted to dev2dev and work
with 7.0.
Tom, BEA
Pete wrote:
> Can anyone offer suggestions on how to obtain/build a JMS messaging bridge to MSMQ.
> I see that WL has a Messaging Bridge but only for certain foreign messaging systems.
>
>
> FioranoMQ have a JMS Implementation with a bridge to MSMQ but a complete JMS implementation
> seems overkill and is costly.
>
> We already have Weblogic's JMS implementation & just want messages to appear on
> a JMS Queue when they are put in a MSMQ queue. A message driven bean will then
> trigger from the JMS queue.
-
I get constant freezes in Mac CC bridge with error messages that dynamiclinkmediaserver fails
I get constant freezes in Mac CC bridge with error messages that dynamiclinkmediaserver fails
Usually when clicking on certain drives.
Been for a couple of days
Running Mavericks 10.9.1 on an Early 2009 Macpro
I have uninstalled and reinstalled both PS & Bridge.
Trashed preferences
Deleted preview icons
reset Bridge
Run ONYX
repaired permissions several times
All to no avail
Help!Here is the full error report from console:
Date/Time: 2014-01-29 09:48:21 -0500
OS Version: 10.9.1 (Build 13B42)
Architecture: x86_64
Report Version: 18
Command: Adobe Bridge CC
Path: /Volumes/VOLUME/Applications/Adobe Bridge CC/Adobe Bridge CC.app/Contents/MacOS/Adobe Bridge CC
Version: 6.0.1.6 (6.0.1.6)
Parent: launchd [220]
PID: 6136
Event: hang
Duration: 1.40s
Steps: 14 (100ms sampling interval)
Hardware model: MacPro4,1
Active cpus: 16
Fan speed: 916 rpm
Free pages: 1002425 pages (+702)
Pageins: 0 pages
Pageouts: 0 pages
Swapins: 0 pages
Swapouts: 0 pages
Process: Adobe Bridge CC [6136]
Path: /Volumes/VOLUME/Applications/Adobe Bridge CC/Adobe Bridge CC.app/Contents/MacOS/Adobe Bridge CC
Architecture: x86_64
Parent: launchd [220]
UID: 501
Task size: 30825 pages (+2)
CPU Time: 0.007s
Thread 0x19758a DispatchQueue 1 priority 47
14 start + 52 (Adobe Bridge CC) [0x1065e3a54]
14 ??? (Adobe Bridge CC + 7747172) [0x106d44664]
14 ??? (Adobe Bridge CC + 7745591) [0x106d44037]
14 ??? (Adobe Bridge CC + 6865420) [0x106c6d20c]
14 ??? (Adobe Bridge CC + 6865209) [0x106c6d139]
14 ??? (Adobe Bridge CC + 6893783) [0x106c740d7]
14 -[NSApplication run] + 553 (AppKit) [0x7fff8fceb9cc]
14 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 (AppKit) [0x7fff8fcf78db]
14 _DPSNextEvent + 1434 (AppKit) [0x7fff8fcf828e]
14 _BlockUntilNextEventMatchingListInModeWithFilter + 65 (HIToolbox) [0x7fff937d8abc]
14 ReceiveNextEventCommon + 479 (HIToolbox) [0x7fff937d8cb7]
14 RunCurrentEventLoopInMode + 226 (HIToolbox) [0x7fff937d8f0d]
14 CFRunLoopRunSpecific + 309 (CoreFoundation) [0x7fff958df275]
14 __CFRunLoopRun + 995 (CoreFoundation) [0x7fff958df893]
14 __CFRunLoopDoObservers + 391 (CoreFoundation) [0x7fff958ee017]
14 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 (CoreFoundation) [0x7fff958ee0a7]
14 ??? (Adobe Bridge CC + 6890206) [0x106c732de]
14 ??? (Adobe Bridge CC + 6890530) [0x106c73422]
14 ??? (Adobe Bridge CC + 6895943) [0x106c74947]
14 ??? (Adobe Bridge CC + 6911673) [0x106c786b9]
14 ??? (Adobe Bridge CC + 6885978) [0x106c7225a]
14 ??? (Adobe Bridge CC + 6887292) [0x106c7277c]
14 ??? (Adobe Bridge CC + 130163) [0x106600c73]
14 ??? (Adobe Bridge CC + 116160) [0x1065fd5c0]
14 ??? (Adobe Bridge CC + 2946221) [0x1068b04ad]
14 ThumbMetaLib::MediaCoreInitialize() + 519 (Adobe Bridge CC) [0x106c12557]
14 sleep + 42 (libsystem_c.dylib) [0x7fff96137cbf]
14 __semwait_signal + 10 (libsystem_kernel.dylib) [0x7fff8f153a3a]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x1975ae DispatchQueue 2 priority 49 cpu time 0.001s
14 _dispatch_mgr_thread + 52 (libdispatch.dylib) [0x7fff8d515152]
14 kevent64 + 10 (libsystem_kernel.dylib) [0x7fff8f154662]
*14 ??? (mach_kernel + 3948480) [0xffffff80005c3fc0]
Thread 0x19762c priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 8674325) [0x106e26c15]
14 ??? (Adobe Bridge CC + 8566302) [0x106e0c61e]
14 ??? (Adobe Bridge CC + 8675416) [0x106e27058]
14 __semwait_signal + 10 (libsystem_kernel.dylib) [0x7fff8f153a3a]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x1976ba priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976bb priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976bc priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976bd priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976be priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976bf priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976c0 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976c1 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Camera Raw + 2807091) [0x110272533]
14 ??? (Camera Raw + 2807974) [0x1102728a6]
14 MPWaitOnQueue + 192 (CarbonCore) [0x7fff8bc1a38d]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976c2 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Camera Raw + 3887969) [0x11037a361]
14 ??? (Camera Raw + 5581346) [0x110517a22]
14 ??? (Camera Raw + 5967121) [0x110575d11]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976cb priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Adobe Bridge CC + 7803081) [0x106d520c9]
14 ??? (Adobe Bridge CC + 4537529) [0x106a34cb9]
14 ??? (Adobe Bridge CC + 4537870) [0x106a34e0e]
14 ??? (Adobe Bridge CC + 4535576) [0x106a34518]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976cc priority 45
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Adobe Bridge CC + 7803081) [0x106d520c9]
14 ??? (Adobe Bridge CC + 4537529) [0x106a34cb9]
14 ??? (Adobe Bridge CC + 4537870) [0x106a34e0e]
14 ??? (Adobe Bridge CC + 4535576) [0x106a34518]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976cd priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Adobe Bridge CC + 7803081) [0x106d520c9]
14 ??? (Adobe Bridge CC + 4786809) [0x106a71a79]
14 ??? (Adobe Bridge CC + 4535576) [0x106a34518]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x1976f8 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff8bc1a90b]
14 ??? (Adobe Bridge CC + 7803081) [0x106d520c9]
14 ??? (Adobe Bridge CC + 4506413) [0x106a2d32d]
14 ??? (Adobe Bridge CC + 4507088) [0x106a2d5d0]
14 ??? (Adobe Bridge CC + 4506348) [0x106a2d2ec]
14 ??? (Adobe Bridge CC + 4505579) [0x106a2cfeb]
14 ??? (Adobe Bridge CC + 4502720) [0x106a2c4c0]
14 ??? (Adobe Bridge CC + 5435486) [0x106b1005e]
14 ??? (Adobe Bridge CC + 5091473) [0x106abc091]
14 ??? (Adobe Bridge CC + 5111169) [0x106ac0d81]
14 ??? (Adobe Bridge CC + 5115847) [0x106ac1fc7]
14 ??? (Adobe Bridge CC + 5113092) [0x106ac1504]
14 ??? (Adobe Bridge CC + 5179210) [0x106ad174a]
14 ??? (Adobe Bridge CC + 4520385) [0x106a309c1]
14 ThumbMetaLib::HasMediaCoreInitBeenAttempted() + 22 (Adobe Bridge CC) [0x106c12726]
14 MPEnterCriticalRegion + 185 (CarbonCore) [0x7fff8bc195d2]
14 TSWaitOnConditionTimedRelative + 172 (CarbonCore) [0x7fff8bc49c4f]
14 TSWaitOnCondition + 108 (CarbonCore) [0x7fff8bc49a50]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197748 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 175 (SwitchBoardClient) [0x113faae7f]
14 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::ConnectionQueue>, boost::_bi::list1<boost::_bi::value<adobe::switchboard::ConnectionQueue*> > > >::run() + 37 (SwitchBoardClient) [0x1140524e1]
14 boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::ConnectionQueue>, boost::_bi::list1<boost::_bi::value<adobe::switchboard::ConnectionQueue*> > >::operator()() + 92 (SwitchBoardClient) [0x1140524b6]
14 void boost::_bi::list1<boost::_bi::value<adobe::switchboard::ConnectionQueue*> >::operator()<boost::_mfi::mf0<void, adobe::switchboard::ConnectionQueue>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, adobe::switchboard::ConnectionQueue>&, boost::_bi::list0&, int) + 78 (SwitchBoardClient) [0x114052454]
14 boost::_mfi::mf0<void, adobe::switchboard::ConnectionQueue>::operator()(adobe::switchboard::ConnectionQueue*) const + 125 (SwitchBoardClient) [0x1140523af]
14 adobe::switchboard::ConnectionQueue::run() + 481 (SwitchBoardClient) [0x1140486db]
14 void boost::condition_variable_any::wait<boost::unique_lock<boost::mutex> >(boost::unique_lock<boost::mutex>&) + 122 (SwitchBoardClient) [0x11405d4e6]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197749 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 175 (SwitchBoardClient) [0x113faae7f]
14 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Client>, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Client*> > > >::run() + 37 (SwitchBoardClient) [0x113ffb883]
14 boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Client>, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Client*> > >::operator()() + 92 (SwitchBoardClient) [0x113ffb858]
14 void boost::_bi::list1<boost::_bi::value<adobe::switchboard::Client*> >::operator()<boost::_mfi::mf0<void, adobe::switchboard::Client>, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, adobe::switchboard::Client>&, boost::_bi::list0&, int) + 78 (SwitchBoardClient) [0x113ffb7f6]
14 boost::_mfi::mf0<void, adobe::switchboard::Client>::operator()(adobe::switchboard::Client*) const + 125 (SwitchBoardClient) [0x113ffb7a1]
14 adobe::switchboard::Client::run() + 123 (SwitchBoardClient) [0x113fecb6d]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 70 (SwitchBoardClient) [0x11401785e]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19776a priority 47 cpu time 0.005s
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 _NSEventThread + 144 (AppKit) [0x7fff8fe981ce]
14 CFRunLoopRunSpecific + 309 (CoreFoundation) [0x7fff958df275]
14 __CFRunLoopRun + 1161 (CoreFoundation) [0x7fff958df939]
14 __CFRunLoopServiceMachPort + 181 (CoreFoundation) [0x7fff958e0315]
14 mach_msg_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa1a]
*14 ipc_mqueue_receive_continue + 0 (mach_kernel) [0xffffff80002167c0]
Thread 0x197773 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197774 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197775 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197776 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197777 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197778 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197779 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777a priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777b priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777c priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777d priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777e priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19777f priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197780 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x197781 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 164 (MultiProcessor Support) [0x10fe75394]
14 ThreadFunctor::operator()() + 275 (MultiProcessor Support) [0x10fe55303]
14 boost::condition_variable::wait(boost::unique_lock<boost::mutex>&) + 155 (MultiProcessor Support) [0x10fe5544b]
14 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff8f153716]
*14 psynch_cvcontinue + 0 (pthread) [0xffffff7f80b4a940]
Thread 0x19779c priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 175 (SwitchBoardClient) [0x113faae7f]
14 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> > > >::run() + 37 (SwitchBoardClient) [0x113ffb6c5]
14 boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> > >::operator()() + 92 (SwitchBoardClient) [0x113ffb69a]
14 void boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> >::operator()<boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >&, boost::_bi::list0&, int) + 78 (SwitchBoardClient) [0x113ffb638]
14 boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >::operator()(adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio ::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*) const + 125 (SwitchBoardClient) [0x113ffb5e3]
14 adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >::run() + 87 (SwitchBoardClient) [0x114016a73]
14 adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >::runOne(boost::shared_ptr<adobe::switchboard::Connection<boost::asio::basic_stream_sock et<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >&) + 106 (SwitchBoardClient) [0x114016746]
14 unsigned long boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >::read_some<boost::asio::mutable_buffers_1>(boost::asio::mutable_buffers_1 const&, boost::system::error_code&) + 86 (SwitchBoardClient) [0x1140151e0]
14 unsigned long boost::asio::stream_socket_service<boost::asio::ip::tcp>::receive<boost::asio::mutable_bu ffers_1>(boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::implementation_type&, boost::asio::mutable_buffers_1 const&, int, boost::system::error_code&) + 75 (SwitchBoardClient) [0x114015173]
14 unsigned long boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::receive<boost::asio::mutable_buffers_1>(boost::asio::detail::reactive_socket_service<b oost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::implementation_type&, boost::asio::mutable_buffers_1 const&, int, boost::system::error_code&) + 738 (SwitchBoardClient) [0x114014f94]
14 __recvmsg + 10 (libsystem_kernel.dylib) [0x7fff8f15394a]
*14 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*14 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*14 recvmsg_nocancel + 484 (mach_kernel) [0xffffff8000620384]
*14 ??? (mach_kernel + 4324878) [0xffffff800061fe0e]
*14 soreceive + 2306 (mach_kernel) [0xffffff8000614a32]
*14 sbwait + 297 (mach_kernel) [0xffffff800061a939]
*14 msleep + 114 (mach_kernel) [0xffffff80005e1302]
*14 ??? (mach_kernel + 4067541) [0xffffff80005e10d5]
*14 lck_mtx_sleep + 78 (mach_kernel) [0xffffff800022d17e]
*14 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*14 ??? (mach_kernel + 223563) [0xffffff800023694b]
*14 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
Thread 0x1977a0 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 thread_proxy + 175 (SwitchBoardClient) [0x113faae7f]
14 boost::detail::thread_data<boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> > > >::run() + 37 (SwitchBoardClient) [0x113ffb6c5]
14 boost::_bi::bind_t<void, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> > >::operator()() + 92 (SwitchBoardClient) [0x113ffb69a]
14 void boost::_bi::list1<boost::_bi::value<adobe::switchboard::Connection<boost::asio::basic_str eam_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*> >::operator()<boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >, boost::_bi::list0>(boost::_bi::type<void>, boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >&, boost::_bi::list0&, int) + 78 (SwitchBoardClient) [0x113ffb638]
14 boost::_mfi::mf0<void, adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >::operator()(adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio ::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >*) const + 125 (SwitchBoardClient) [0x113ffb5e3]
14 adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >::run() + 87 (SwitchBoardClient) [0x114016a73]
14 adobe::switchboard::Connection<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > >::runOne(boost::shared_ptr<adobe::switchboard::Connection<boost::asio::basic_stream_sock et<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> > > >&) + 106 (SwitchBoardClient) [0x114016746]
14 unsigned long boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >::read_some<boost::asio::mutable_buffers_1>(boost::asio::mutable_buffers_1 const&, boost::system::error_code&) + 86 (SwitchBoardClient) [0x1140151e0]
14 unsigned long boost::asio::stream_socket_service<boost::asio::ip::tcp>::receive<boost::asio::mutable_bu ffers_1>(boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::implementation_type&, boost::asio::mutable_buffers_1 const&, int, boost::system::error_code&) + 75 (SwitchBoardClient) [0x114015173]
14 unsigned long boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::receive<boost::asio::mutable_buffers_1>(boost::asio::detail::reactive_socket_service<b oost::asio::ip::tcp, boost::asio::detail::kqueue_reactor<false> >::implementation_type&, boost::asio::mutable_buffers_1 const&, int, boost::system::error_code&) + 738 (SwitchBoardClient) [0x114014f94]
14 __recvmsg + 10 (libsystem_kernel.dylib) [0x7fff8f15394a]
*14 hndl_unix_scall64 + 22 (mach_kernel) [0xffffff80002f3e06]
*14 unix_syscall64 + 499 (mach_kernel) [0xffffff800063de23]
*14 recvmsg_nocancel + 484 (mach_kernel) [0xffffff8000620384]
*14 ??? (mach_kernel + 4324878) [0xffffff800061fe0e]
*14 soreceive + 2306 (mach_kernel) [0xffffff8000614a32]
*14 sbwait + 297 (mach_kernel) [0xffffff800061a939]
*14 msleep + 114 (mach_kernel) [0xffffff80005e1302]
*14 ??? (mach_kernel + 4067541) [0xffffff80005e10d5]
*14 lck_mtx_sleep + 78 (mach_kernel) [0xffffff800022d17e]
*14 thread_block_reason + 204 (mach_kernel) [0xffffff8000235d4c]
*14 ??? (mach_kernel + 223563) [0xffffff800023694b]
*14 machine_switch_context + 354 (mach_kernel) [0xffffff80002d81d2]
Thread 0x197b8d priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b8e priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b8f priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b90 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b91 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b92 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b93 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b94 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b95 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b96 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b97 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b98 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b99 priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b9a priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b9b priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib) [0x7fff8f14fa56]
*14 semaphore_wait_continue + 0 (mach_kernel) [0xffffff800023b550]
Thread 0x197b9c priority 47
14 thread_start + 13 (libsystem_pthread.dylib) [0x7fff8dea7fc9]
14 _pthread_start + 137 (libsystem_pthread.dylib) [0x7fff8dea372a]
14 _pthread_body + 138 (libsystem_pthread.dylib) [0x7fff8dea3899]
14 ??? (Adobe Bridge CC + 3999326) [0x1069b165e]
14 semaphore_wait_trap + 10 (libsystem_kernel.dylib -
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?
-
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 ? -
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 -
Message Bridge error "Received message with no URI property"
I have created a message bridge between two weblogic JMS servers on different domains.
Message bridge has source and destinations.
I have tested each ques seperately with MDB deployed on each server.
When i am putting message on source que then i am getting this error "Received message with no URI property"
It would be grat help if some could tell me what might be going wrong.
Thanks
AkashHi,
This exception indicates a failure to establish a JNDI context for either the source or target destination host. Check if the the bridge's configured URLs for both are correct. I'm not 100% sure, but it is likely that no URL need be configured for destination's that are in the same cluster as the bridge.
For more information, I suggest looking at the Messaging Bridge FAQ, which contains some troubleshooting tips. You can find a link to it here:
http://dev2dev.bea.com/technologies/jms/index.jsp
Tom Barnes, BEA
Maybe you are looking for
-
Problems when copying item from a page to another one
I am copying a value of an item, from a page to another one in branch, and it cuts the value to me in ' : ' ej: item a = 08:00 Hs item b = 08 thanks Juan Pablo
-
Shopping For A RAID Controller
I have seen the Areca brand name on here many times, so I assume they are the best for what we do. But, there are so many models that I have no idea what to look for. I probably won't ever have more than 4 or 6 storage drives plus an SSD system drive
-
Computer authorization stuck in loop
I am trying to authorzie a computer with Adobe Digital Edition 2.0. I am using a windows 7 machine. I try and download a book from the library it asks me to authorize my machine. I do by entering the email address and password and entering. Then
-
How do I create a slide show that repeats (continuously loops)
I am new to iMovie and iDVD. I am creating a photo album in iMove and want to burn for iDVD to show at a party. I can't find out how to set this up to loop - repeat. Novice Bruce
-
Read web service with JDeveloper
I have web service from AJPES, but i have problem how to read it. I search for good how to but i can not find it. Does anyone know any good how to for reading web service and manipulate with it? regards Mitja