Connect from Weblogic JMS queue to SAP WAS JMS queue

Hi,
I am trying to setup a WLS 8.1 messaging bridge between a weblogic JMS queue and a SAP WAS JMS queue. I have configured a queue on both Weblogic and SAP WAS and I have set up the messaging bridge and bridge destintations in weblogic. However when weblogic tries to get the SAP initial context factory it fails with the error below.
I have added the SAP Client jars to the weblogic system classpath, and in the weblogic startup script but it still fails. Has anyone connected from an external JMS queue to a SAP WAS JMS queue that could provide me with some guidence?
<10/08/2006 08:23:45 AM WST> <Warning> <Connector> <BEA-190032> << Weblogic Mess
aging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocatio
nException of javax.resource.ResourceException: ConnectionFactory: failed to get
initial context (InitialContextFactory =com.sap.engine.services.jndi.InitialCon
textFactoryImpl, url = ux0800:55304, user name = username) on createManagedConnectio
n.>
Thanks
Warren

Stoyan,
Thanks for that.
My problem ended up being a classpath problem. I referenced the directory of the SAP jars in the weblogic start up script. When I changed this to reference each jar individually it worked.
I have a new issue now which may have something to do with security. The trace suggests it is logging on as the guest user, even though I entered my username and password in the Messaging bridge.
#1.5#000E7FED310600A30000008A0000302D00041AA399E338B4#1155189870559#com.sap.jms##com.sap.jms.server.sessioncontainer.InboundBus instance=BWIP#J2EE_GUEST#0####165536f0283611db8903000e7fed3106#SAPEngine_Application_Thread[impl:3]_126##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerInvalidDestinationException: No destination with ID=0 found.
        at com.sap.jms.server.service.impl.RegistryServiceImpl.getDestinationContext(RegistryServiceImpl.java:404)
        at com.sap.jms.server.sessioncontainer.InboundBus.getDestinationContext(InboundBus.java:98)
        at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:153)
        at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
        at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
        at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:447)
        at com.sap.jms.server.JMSServerContainer.dispatchRequest(JMSServerContainer.java:635)
        at com.sap.jms.server.JMSServerFrame.request(JMSServerFrame.java:536)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Warren

Similar Messages

SAP WAS JMS Provider

Hi,
Has anyone ever tried to use SAP WAS JMS Provider to connect with another JMS Provider like WMQ? I am looking for information from reliability perspective.
I have seen a blog on SDN on this subject but there aren't any productive uses of JMS provider by SAP. [JMS Provider|http://wiki.sdn.sap.com/wiki/display/JSTSG/%28JSTSG%29%28JMS%29FAQ-JMSProvider] has further information on what is offered.
Regards

No answer so closing the thread

SAP WAS JMS ID and MQ JMS ID is incompatiable

Our scenario is to connect SAP WAS JMS Provider to MQ Series.
But the problem we are facing is the JMS Message ID is incomapatiable with the MQ JMS ID.
I am getting the error
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: Unable to set message properties for message JMSMessage class: jms_text JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: 0 JMSCorrelationID: null JMSDestination: null JMSReplyTo: null JMSRedelivered: false com.ibm.msg.client.jms.DetailedJMSException: JMSCMQ1044: String is not a valid hexadecimal number - '122B3E1E683C8DE8-00000000001B'.
Please let me know if you have faced similar issues

Hello
See http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.javadoc.doc/WMQJMSClasses/errorcodes.html for more details on this JMSCMQ1044 error.
Have you configured the correlation? See [Configuring the Receiver JMS Adapter|http://help.sap.com/saphelp_nwpi71/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/content.htm].
Regards
Mark

Memory leak after connect from Weblogic 8.1 to oracle 9.1.2

Hi,
I have a application migrated from Weblogic 6.1 to Weblogic 8.1. It is working
fine in weblogic 6.1. But it has memmory leak in weblogic 8.1. My current system
is
Solaris 9 with weblogic 8.1(SP2)
Solaris 9 with oralce 9i
The problem happen when the application is running for some time. All memory
is ate out in oracle instance. But the weblogic is alive. And in fact oracle
is alive too but it is not allowed for any future connection. Then after that,
all hang. We need to restart both webligc and oracle instances.
Does anyone can help on this? Is any specicial things in weblogic 8.1 for JDBC
connection? Thank you very much.
Yang Lin

"YangL" <[email protected]> wrote in message news:[email protected]..
I have a application migrated from Weblogic 6.1 to Weblogic 8.1. It is working
fine in weblogic 6.1. But it has memmory leak in weblogic 8.1. My current system
is
Solaris 9 with weblogic 8.1(SP2)
Solaris 9 with oralce 9i
The problem happen when the application is running for some time. All memory
is ate out in oracle instance. But the weblogic is alive. And in fact oracle
is alive too but it is not allowed for any future connection. Then after that,
all hang. We need to restart both webligc and oracle instances.
Does anyone can help on this? Is any specicial things in weblogic 8.1 for JDBC
connection? Thank you very much.Check with your DBA - he/she should have enough tools to tell
what has happened on the Oracle side.
Regards,
Slava Imeshev

ResourceException: Access not allowed (when trying to grab a connection from weblogic pool)

I am using WLS7 with SP1.
I just recently migrated from WLS6.0. When my code tries to grab a
connection from the pool, it throws an exception
java.sql.SQLException: Pool connect failed:
weblogic.common.ResourceException: Access not allowed
at weblogic.jdbc.pool.Driver.connect(Driver.java:202)
Does anyone know if anything changed from 6.0 to 7?
Here is a piece of the code that throws exception.
Driver driver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver")
.newInstance();
conn = driver.connect("jdbc:weblogic:pool:" +
dbName, null);
Thanks in advance.

Hi Jung,
"Jung Yang" <[email protected]> wrote in message
news:[email protected]...
Do you know how to change security setting on the connection pool?
Thanks.WebConsole:
1.Compatibility Security => ACLs
Create a new ACL,
name : weblogic.jdbc.connectionPool.yourPoolname
permission : reserve, reset
group : everynone
2.Services => JDBC => Connection Pool
Create a new Connection Pool
ACL Name : weblogic.jdbc.connectionPool.yourPoolname
In 'Target' tab, choose server and click the Apply button
Slava
>
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]...
Hi Jung,
Could you try providing weblogic user name and password
in the properties?
Could you also check security setting of the connection pool?
Regards,
Slava Imeshev
"Jung Yang" <[email protected]> wrote in message
news:[email protected]...
Well that is exactly what I am doing. The variable dbName is database
connection pool name that I created in weblogic console. Again, it
worked
in WLS6 but after migration, it stopped working.
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
In my code I am supplying name of the connection pool already
created
in
weblogic server. I am asking you to get connection from the pool
using
pool
driver.
In your case you are trying to create connection straight to
database
using pool
driver.
What I am asking is pass name of the connection pool instead of
database
name.
Thanks,
Mitesh
Jung Yang wrote:
What would be the difference between your code and mine? Mine
simple
appends dbName string value for connection pool name at the end of
"jdbc:weblogic:pool:"? And why same exact code would work in WLS6and
not
work in WLS7?
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
conn = driver.connect("jdbc:weblogic:pool:" +
dbName, null);Instead of doing this what if you use
Connection conn =
myDriver.connect("jdbc:weblogic:pool:myConnectionPool", null);
Will you please try this and see if that helps?
Mitesh
Jung Yang wrote:
Isn't that exactly what I posted for my code piece?
Thanks.
"Mitesh Patel" <[email protected]> wrote in message
news:[email protected]...
Try As described below:
The following example demonstrates how to use a database
connection
pool
from a servlet.
Load the pool driver and cast it to java.sql.Driver. The
full
pathname
of
the driver is weblogic.jdbc.pool.Driver. For example:
Driver myDriver = (Driver)
Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Create a connection using the URL for the driver, plus
(optionally)
the
name of the registered connection pool. The URL of the pool
driver
is
jdbc:weblogic:pool.
You can identify the pool in either of two ways:
Specify the name of the connection pool in a
java.util.Properties
object
using the key connectionPoolID. For example:
Properties props = new
Properties();props.put("connectionPoolID",
"myConnectionPool");Connection conn =
myDriver.connect("jdbc:weblogic:pool", props);
Add the name of the pool to the end of the URL. In this case
you
do
not
need a Properties object unless you are setting a username
and
password
for using a connection from the pool. For example:
Connection conn =
myDriver.connect("jdbc:weblogic:pool:myConnectionPool",
null);
Note that the Driver.connect() method is used in theseexamples
instead of
the DriverManger.getConnection() method. Although you may
use
DriverManger.getConnection() to obtain a databaseconnection,
we
recommend
that you use Driver.connect() because this method is not
synchronized
and
provides better performance.
Note that the Connection returned by connect() is an
instance
of
weblogic.jdbc.pool.Connection.
Call the close() method on the Connection object when youfinish
with
your
JDBC calls, so that the connection is properly returned to
the
pool. A
good coding practice is to create the connection in a try
block
and
then
close the connection in a finally block, to make sure the
connection
is
closed in all cases.
conn.close();
Mitesh
Jung Yang wrote:
I am using WLS7 with SP1.
I just recently migrated from WLS6.0. When my code tries
to
grab a
connection from the pool, it throws an exception
java.sql.SQLException: Pool connect failed:
weblogic.common.ResourceException: Access not allowed
at
weblogic.jdbc.pool.Driver.connect(Driver.java:202)
Does anyone know if anything changed from 6.0 to 7?
Here is a piece of the code that throws exception.
Driver driver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver")
.newInstance();
conn =
driver.connect("jdbc:weblogic:pool:"
+
dbName,
null);
>>>>>>>>>
Thanks in advance.

Problem with connecting from Netweaver Session Bean to SAP R/3

Hi,
i just want a connection to RFC in SAP R/3 and with help of sap ("Proxy generation" etc) and wizard in NWDS i get the rfc. Now i want to connect and use it (like in handbook) but: Every time i create and use jcoclient.connect() system gets an error like:
"Class File Editor
Source not found
The jar file jrfc.jar has no source attachment."
I have add all files that are used to "Used DCs" or bind library into projekt as "Third party library", but the error is still there.
Any idea? Do i have to make something else? Some failure made?
thx
Here is text for connection:
Created on 26.06.2008
To change the template for this generated file go to
Window>Preferences>Java>Code Generation>Code and Comments
package com.XXXXXXXXXXXXXXXXX;
import com.XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX;
import com.sap.aii.proxy.framework.core.ApplicationFaultException;
import com.sap.aii.proxy.framework.core.SystemFaultException;
import com.sap.mw.jco.JCO;
@author XXXXX
To change the template for this generated type comment go to
Window>Preferences>Java>Code Generation>Code and Comments
public class MyMainClass extends Object
     public static void main(String[] args)
          throws ApplicationFaultException, SystemFaultException
          JCO.Client jcoclient =
               JCO.createClient(
                    "XXX", //Client
                    "XXX", //User
                    "XXX", //Password
                    "XXX", //Language
                    "XXX", //Server
                    "XXX", //System
                    "XXX"); //Group
          jcoclient.connect();
          jcoclient.disconnect();
Edited by: Torsten on Aug 27, 2008 10:43 AM
Where can we download SAP NW7.0 (2004s) as Java Trial for testing? We only find ABAP Trial... Link? thx

So we tested some things that are described in the SDN or by SAP with Connectors.
We tested JCO version 2.0.12, 2.1.18 and 3.0 in J2EE Projects in netweaver and in Eclipse (Standalone).
For version 2.0.12 there is a failure that this version is not compatible with the other things in netweaver.
This version is for standalone and integrated sytems.
For version 2.1.18 is only described as standalone and so failure happened in netweaver that other classes are coruppted or missed. The internal test in "content administrator" (Ping and Test) do not work and had the same error.
For version 3.0 (that displace the other two versions) there is many to do in settings and coding that we do not have tested yet because project is not that small to write it for JCO 3.0 only for testing. When we only displaced files in netweaver the server do not start any more.
So:
Is there a way to call R/3 from session bean and 1. create an JCO client or 2. add a client to the "standard" pool of netweaver to use it?
Any ideas? help? links?
Project have to be complete in september...
Our combi is SAP Netweaver 2004 SP21 on Windows XP SP2 / Server 2003 Standard SP1 with JVM 1.4.2_16... need of any more info?
thx

Error connecting to websphere MQ from weblogic 10.3.0 :EndPointFinder

1)     We are in process of connection from weblogic 10.3.0 to websphere MQ series . We are trying connecting to the response queues using MQclient binding . I created .binding file using following configuration
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69874.bst.bls.com) PORT(1415) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE Q(BBNMSSERESPONSEQUEUE1) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU1) TARGCLIENT(MQ)
DEFINE Q(BBNMSSERESPONSEQUEUE2) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU2) TARGCLIENT(MQ)
DEFINE QCF(BBNMSRMSCF1) QMGR(ESBMBJU1) CHAN(ESBMBJU1_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
ALTER QCF(BBNMSRMSConnectionFactory1) CHAN(ESBMBJU1_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
ALTER QCF(BBNMSRMSConnectionFactory2) CHAN(ESBMBJU2_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
2)     The I created the foreign JMS-server as such :
<foreign-server name="ForeignRmsServer-1">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="RmsFusionBusRequestQueue1">
<local-jndi-name>RmsResponseQueue1</local-jndi-name>
<remote-jndi-name>BBNMSSERESPONSEQUEUE1</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="RmsFusionBusFactory1">
<local-jndi-name>RmsFusionBusfactory1</local-jndi-name>
<remote-jndi-name>BBNMSRMSConnectionFactory1</remote-jndi-name>
<username>m66300d</username>
<password-encrypted xsi:nil="true"/>
</foreign-connection-factory>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:/opt/mqm/java/bin/mqjndi</connection-url>
</foreign-server>
3)     Subsequently I use the JNDI names configured in foreign server(above) in weblogic-ejb-jar.xml .
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<weblogic-enterprise-bean>
<ejb-name>RMSRespMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>BBNMSSERESPONSEQUEUE1</destination-jndi-name>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<provider-url>file:/opt/mqm/java/bin/mqjndi</provider-url>
<connection-factory-jndi-name>BBNMSRMSConnectionFactory1</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>jms.RMSRespMDB</jndi-name>
<dispatch-policy>JbbosServicesServerXQ</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-compatibility>
<entity-always-uses-transaction>true</entity-always-uses-transaction>
</weblogic-compatibility>
</weblogic-ejb-jar>
4)     Now when my MDB comes up its giving following error
Mar 8, 2011 10:13:16 AM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application
'RMSRespMDB'.
weblogic.application.ModuleException: Exception activating module: EJBModule(RMSRespMDB)
Unable to deploy EJB: RMSRespMDB from RMSRespMDB.jar:
unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
Truncated. see log file for complete stacktrace
java.lang.AssertionError: unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.rmi.spi.RMIRuntime.getEndPointFinder(RMIRuntime.java:61)
at weblogic.rmi.spi.RMIRuntime.findOrCreateEndPoint(RMIRuntime.java:42)
at weblogic.rmi.extensions.server.RemoteDomainSecurityHelper.isRemoteDomain(RemoteDomainSecurityHelper.java:379)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.isRemoteDomain(ServerCrossDomainSecurityUtil.java:319)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.getRemoteSubject(ServerCrossDomainSecurityUtil.java:116)
Truncated. see log file for complete stacktrace
>
My binding file is correctly placed on the following location file:/opt/mqm/java/bin/mqjndi with appropriate permissions
Some info :
Our weblogic version is 10.3.0
I tracked this exception (unable to find EndPointFinder) to bug id 8168598
Can anyone please suggest what can be issue potentially
Thanks in advance

hi,
Even i want to connect webspere MQ 7 with weblogic 10.3, can u suggest me some document where i can follow step by step?
I have too tried using some binding file,but it is not reading the same.

Issue while connecting from Biztalk adapter to SAP ECC 6.0

Hi Friends
Issue while connecting from Visulal Studio 2005 to SAP ECC 6.0 throgh Biztalk adapter2.0, even if we pass the correct login details, system is throwing an error like incorrect user/password.
Can you please tell anybody the solution for this.
Regards
Praveen

HI,
is there a special "formation" to put in the user / pass ?
maybe a missing domain ? or missing values like "/" or "\" ?
Do you getting this error in the Biztalk Monitor (Visual 2005) ?

Clustering (Queues) on SAP J2EE

Does the J2EE JMS engine support clustering ?
Thanks, John

Hi John,
        JMS is in SAP WAS J2EE server.WAS server supports clustering,load balancing as other standard J2EE servers in the market.
         Refer this link which has some useful info.
         http://help.sap.com/saphelp_nw04/helpdata/en/e9/8eca943e04c047a04692c62fd2fa3d/frameset.htm
Rdgs,
guru

JMS connection from SAP PI to Oracle AQ via JNDI...

Hi,
I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
Has anyone had similar solutions in production ? How repliable it is ?
Your help is very much appreciated
Tim

Hi Tim,
We implemented a similar scenario and now itu2019s still working.
You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
Best Regards,
Roberto

Migration of JMS Queues from Weblogic 10.3 to 12c

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

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

Proxy authentication required when connecting to internet from SAP WAS

Hi,
I have deployed a J2EE application in SAP WAS 7.0 and this aplication wants to access an application from internet.
I have set the proxy server details in Visual Admin -> Web Service Container -> setting.
The server is installed locally in my PC.
I am able to run the same java application in my command prompt wit the same proxy details and it is able to access the 3rd party application , but when I am trying to access through web application through SAP WAS I am getting 407 Proxy authentication required.
Thanks in advance.
Regards,
Hari

Hi,
it seems like your Proxy requires authentication (e.g. Basic authentication)
I am able to run the same java application in my command prompt wit the same proxy details and it is able to access the 3rd party application
Are you providing any credentials here in order to access the internet via Proxy?
What kind of Proxy are you using
Cheers

Setting up JMS in a clustered SAP WAS 6.40

Hello all,
We are trying to start our app in the clustered SAP WAS 6.30 Patch Level 77737.313 and application start fails with a JMS Error:
Error#1#/System/Audit#Java###Exception #1#com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: JMS error.
     at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadDestination(ContainerImpl.java:1874)
     at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.prepareStart(ContainerImpl.java:717)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:347)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:309)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:308)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.run(ParallelAdapter.java:73)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:60)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:72)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:126)
Caused by: javax.jms.JMSException: ConnectionFactory with name com.ttt.jms.TTTTopicFactory does not exist.
Same app starts up fine in a non-clustered environment.
The JMS error says that application can't find the specified JMS Factory name. So it can be an issue with JNDI replication.
The jms deployment descriptors we are using are:
<jms-factories>
     <connection-factory>
          <connection-factory-type>QueueConnectionFactory</connection-factory-type>
          <factory-name>com.ttt.jms.TTTQueueFactory</factory-name>
          <context-factory-type>
               <link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTQueueFactory</link-factory-name>
                   <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
          </context-factory-type>
     </connection-factory>
     <connection-factory>
          <connection-factory-type>QueueConnectionFactory</connection-factory-type>
          <factory-name>com.ttt.jms.enterprise.TTTQueueFactory</factory-name>
          <context-factory-type>
               <link-factory-name>jmsfactory/TTT/com.ttt.jms.enterprise.TTTQueueFactory</link-factory-name>
                   <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
          </context-factory-type>
     </connection-factory>
     <connection-factory>
          <connection-factory-type>TopicConnectionFactory</connection-factory-type>
          <factory-name>com.ttt.jms.TTTTopicFactory</factory-name>
          <context-factory-type>
               <link-factory-name>jmsfactory/TTT/com.ttt.jms.TTTTopicFactory</link-factory-name>
                   <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>
          </context-factory-type>
     </connection-factory>
</jms-factories>
<jms-destinations>
     <destination>
          <connection-factory>com.ttt.jms.TTTTopicFactory</connection-factory>
          <destination-name>com.ttt.jms.Topic1</destination-name>
     </destination>
     <destination>
          <connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>
          <destination-name>com.ttt.jms.Queue1</destination-name>
     </destination>
     <destination>
          <connection-factory>com.ttt.jms.TTTQueueFactory</connection-factory>
          <destination-name>com.ttt.jms.Queue2</destination-name>
     </destination>
     <destination>
          <connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>
          <destination-name>com.ttt.jms.enterprise.Queue1</destination-name>
     </destination>
     <destination>
          <connection-factory>com.ttt.jms.enterprise.TTTQueueFactory</connection-factory>
          <destination-name>com.ttt.jms.enterprise.Queue2</destination-name>
     </destination>
</jms-destinations>
JMS Provider is configured with JMS server TTT and corresponding 4 queue factories and 1 topic factory.
If you can see anything wrong with this configuration, I would really appreciate your comments.
Maybe there is something specific that must be configured for JMS in a clustered environment?
Thanks.

Yuri:
there may be cluster Q , check once or you should change the values in all cluster servers locally .

Issue listeneing queue from Weblogic Cluster server with multiple managed server

Haveing issue listeneing queue from Weblogic Cluster server with multiple managed server.
Weblogic Cluster structure is like
Weblogic Cluster01
--ManagedServer01(http://server01.myhost.com:7001)
--ManagedServer02(http://server02.myhost.com:7001)
JMS Servers
JMSserver01 targeting: ManagedServer01
JMSserver02 targeting: ManagedServer02
JMSmodule
ConnectionFactory01 targeting:JMSserver01,JMSserver02
UDQueue01 targeting:JMSserver01,JMSserver02
Uniform Distributed Queue in Monitoring tab showing like this
mysystemmodule!JMSserver01@UDQueue01
mysystemmodule!JMSserver02@UDQueue01
So when I am sending message to any Host(by specifying the provider URL) its distributing equally on both server like
mysystemmodule!JMSserver01@UDQueue01 10
mysystemmodule!JMSserver02@UDQueue01 10
But when try to listen message from these queue, it is listening from one server, for which URL given to connect.
mysystemmodule!JMSserver01@UDQueue01 0
mysystemmodule!JMSserver02@UDQueue01 10
untill I connect to other server by giveing its URL, will not able to access other message left on the queue.
Solutions that tried
1) we have tried give both server URL coma sparated in provider URL
we need to configur same scenario for 5 managed server with 3 listener on other servers.
Do any one have solution for this.

You need to have:
1. Consumers connected to each UDQ member
OR
2. If no consumers in some of the members is expected, you can configure Forward Delay (specify the amount of time, in seconds, that a queue member with messages, but with no consumers, will wait before forwarding its messages to other queue members that do have consumers):
http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13952/taskhelp/jms_modules/distributed_queues/ConfigureUDQGeneral.html
For example you can set it to 10 (10s)
Additional Information here:
http://docs.oracle.com/cd/E23943_01/web.1111/e13727/dds.htm#i1314228
http://docs.oracle.com/cd/E23943_01/apirefs.1111/e13951/mbeans/DistributedQueueBean.html?skipReload=true#ForwardDelay
How Does JMS Load Balancing Work with Distributed Queues and Uniform Distributed Queues? (Doc ID 827294.1)
I hope this helps
Best Regards
Luz

Unable to Connect to SUN MQ using Messaging Bridge from Weblogic

Hello
          I am trying to connect to Sun MQ Queueu from weblogic using a messaging bridge. I get the following error message
          <Warning> <Connector> <BEA-190032> << Weblogic Mes
          saging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllocati
          onException of javax.resource.ResourceException: Failed to start the connection
          on createManagedConnection.>
          Please looks at my configuration and see if I am missing something.
          I had configured the following:
          1. Source JMS Bridge Destination with
          the following (
          Adapter JNDIname = eis/jms/WLSConnectionFactoryJNDIXA ,
          connection url = file:///c:/temp (Sun MQ File based Store ,
          Initial Conext Fac = com.sun.jndi.fscontext.RefFSContextFactory,
          sun mq Connection fac Jndi name,
          sun mq destination jndi name
          2. Target JMS Bridge Destination
          ( Corresponding weblogic configuration)
          3. Messaging Bridge which uses the above two JMS Bridges.
          4. Also included fscontext.jar from Sun MQ Library into weblogic server classpath.
          Looks like the weblogic is able to get the intial context, but is unable to make connection to the SUN MQ Queue.
          Any help would be appreciated.
          skaturu

Sister f*cking brother bbw picpost teen titans hentai, brother sister f*ck teen ... Dad fucking daughter pics gallery brother fu*king. Pics of teens fuckin

Connect from Weblogic JMS queue to SAP WAS JMS queue

Similar Messages

Maybe you are looking for