No suitabel driver SQLException with Managed Server

Hi,
I have created a managed server and configured it to listen to a particular IP
address. When I try to access a jsp file which uses mssqlserver4 driver, with
this managed server; i get following exception...
java.sql.SQLException: No suitable driver
whereas if I access same page through administrator server (I've used myserver
as administrator server), I get the expected output.
I've checked the classpaths for both the managed servers as well as the administrator
server, and they are identical.
Could any one give me some suggestions?
Thans in advance,
Anand

This error usually is caused by the fact no driver was found that understand the URL
provided to connect to the database. Look closely at the URL for the database
connection.
Anand wrote:
Hi,
I have created a managed server and configured it to listen to a particular IP
address. When I try to access a jsp file which uses mssqlserver4 driver, with
this managed server; i get following exception...
java.sql.SQLException: No suitable driver
whereas if I access same page through administrator server (I've used myserver
as administrator server), I get the expected output.
I've checked the classpaths for both the managed servers as well as the administrator
server, and they are identical.
Could any one give me some suggestions?
Thans in advance,
Anand

Similar Messages

Problem with Managed Server pointing to a different JDK

Hi,
My Adminserver is pointing to JDK 1.7 which is shown in the startup, but my managed servers are pointing to a different 1.6_43 . We are running into Java version mismatch problem while deploying our application built with jdk 1.7 onto these managed servers . How do i change the version of my managed server ?
Thanks
Sam

Hi Sam,
You generally only have to change it in two places.
DOMAIN_HOME/bin/setDomainEnv.sh and MW_HOME/wlserver_12.1/common/bin/commEnv.sh
See examples below.
If you are on Linux you can quickly fix it. For example:
cd /u01/app/oracle/product/fmw
find . -type f -exec sed -i "s/\/u01\/app\/oracle\/product\/jdk1.6.0_39/\/u01\/app\/oracle\/product\/java_current/g" {} \;
It is a good idea to make a softlink to your Java installation, then you will not have this problem in the future. If you are on Windows you can use a symlink.
Linux example:
ln -s /u01/app/oracle/product/jdk1.7.0_25 /u01/app/oracle/product/java_current
Windows example:
mklink /d D:\oracle\product\java_current D:\oracle\product\jrockit-jdk1.6.0_26-R28.1.4-4.0.1
setDomainEnv.sh
/u01/app/oracle/domains/eksudv/bin/setDomainEnv.sh
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
        JAVA_HOME="${BEA_JAVA_HOME}"
        export JAVA_HOME
else
        if [ "${JAVA_VENDOR}" = "Sun" ] ; then
                JAVA_HOME="${SUN_JAVA_HOME}"
                export JAVA_HOME
        else
                JAVA_VENDOR="Sun"
                export JAVA_VENDOR
                JAVA_HOME="/u01/app/oracle/product/java_current"
                export JAVA_HOME
        fi
fi
commEnv.sh
/u01/app/oracle/product/fmw/wlserver_12.1/common/bin/commEnv.sh
# Reset JAVA_HOME, JAVA_VENDOR and PRODUCTION_MODE unless JAVA_HOME
# and JAVA_VENDOR are pre-defined.
if [ -z "${JAVA_HOME}" -o -z "${JAVA_VENDOR}" ]; then
# Set up JAVA HOME
JAVA_HOME="/u01/app/oracle/product/java_current"
# Set up JAVA VENDOR, possible values are
#Oracle, HP, IBM, Sun ...
JAVA_VENDOR=Sun
# PRODUCTION_MODE, default to the development mode
PRODUCTION_MODE=""
fi
Regards Peter
http://theheat.dk

Not able to connect with managed server using ssl connection

Hi Guys,
My weblogic server is running on linux. I have setup ssl connction bu using Demo Identity and Demo Trust.In server logs i can find the following infomation that server is running on secure port.
But once i try connect to managed server using client i m facing below error:
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<May 27, 2013 2:55:00 PM IST> <Info> <Security> <BEA-090908> <Using default WebLogic SSL Hostname Verifier implementation.>
javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://host:port: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination]
     at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
     at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:767)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:366)
     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:684)
     at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
     at javax.naming.InitialContext.init(InitialContext.java:242)
     at javax.naming.InitialContext.<init>(InitialContext.java:216)
     at com.akt.client.WLCLIENT.makeConnection(WLCLIENT.java:40)
     at com.akt.client.WLCLIENT.main(WLCLIENT.java:60)
Caused by: java.net.ConnectException: t3s://host:port: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; 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:165)
     at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:345)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
     at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:340)
     ... 9 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
     javax.net.ssl.SSLHandshakeException: General SSLEngine problem; No available router to destination
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:470)
     at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:321)
     at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:260)
     at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:197)
     at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
     at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
     ... 15 more
But in server logs i can see below message
opt/Oracle/Middleware/wlserver_12.1/server/lib/DemoIdentity.jks.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/Oracle/Middleware/wlserver_12.1/server/lib/DemoTrust.jks.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/jdk1.7.0_21/jre/lib/security/cacerts.>
<May 27, 2013 2:47:06 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on hostname:port for protocols iiops, t3s, ldaps, https.>
<May 27, 2013 2:47:06 PM IST> <Notice> <WebLogicServer> <BEA-000332> <Started the WebLogic Server Managed Server "Server-Test" for domain "base_domain" running in development mode.>
Please suggest
Edited by: 1008140 on May 27, 2013 2:37 AM

Welcome to OTN
This section related to Database question not fusion middle ware Post your question
Oracle Discussion Forums » Fusion Middleware

WebService with managed server as target is also available on 7001

I deployed a EAR file which has a webservice module (WAR file) on to a managed server using wldeploy ANT task. ANT task is run from my machine and Weblogic Server is on a different machine. The managed server is listening on 8005 port.
<wldeploy action="deploy" name="MyWebService" source="build/MyWebService.ear" user="wluser" password="wlpwd" upload="true" verbose="true" adminurl="t3://mywlhost:7001" targets="mymgdserver1"/>
In Weblogic console I can see that the target for this app is mymgdserver1 and the WebService is accessible on port 8005. But for some reason the WebService is also accessible on port 7001. For security reasons we don't want the webservice to be available on port 7001. Can any one throw some light on why this is happening and how to achieve what I need. Thanks in advance.

Hi,
Upload option we use to upload any Application in AdminServer so that later we can deploy it through the Admin Server to Clusters or to other Managed Servers….When you upload files to the Administration Server machine, the archive file is automatically placed in the server’s upload directory.
java weblogic.Deployer -adminurl t3://localhost:7001 -user weblogic -password weblogic -verbose -noexit -deploy -upload C:\DELETE\WLST_Deploy_Test\uploadant\xyz.ear
For more information on upload via weblogic.Deployer please refer to link below
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/deployment/deploy.html#wp1026337
Regards,
Kal

500 Go Drive modules with MacOS server 10.3.9

Hello,
I need to expand an Xserve/Xraid system with new disks. because 400 GB disks are no longer available i got the 500 GB instead. I read on the box "requires Xserve G5 and Mac OSX server v10.4.3 or later). Is it absolutely necessary to install v10.4.3 ? Couldn't these 500 Go disks work with the current 10.3.9 system version ?
Thank You
Pierre

Pierre
500gb drives work just fine with 10.3.9
Ed

Problem using odbc driver 10g with SQL Server 2005

We are getting following error. Any solution?
cannot retrieve the column codepage info from the OLE DB provider

there is an additional error message
The output column SR_CONTACT_POINT_ID (58) has a precision which is not valid. Precision must be between 1 and 38.

Problem with Reports Server and invalid DB packages when release code

Hello,
I'm not certain that this is a Reports issue or not, but wondered if anyone had encountered similar. We've recently upgraded from Forms and Reports 6i to 10.1.2.0.2. A couple of times now, after doing a release of code to our environment, we find that the next request to the Reports Server generates a 'existing state of packages has been discarded' error. Submitting exactly the same report request a second and subsequent times works fine.
However, we always make sure we recompile all invalid packages after a code release; and our Forms front-end doesn't encounter any errors like this. Is there some possible issue with using existing Reports engines to run reports after a code release - should we be bouncing the Reports server..?
Thanks,
James

Hi. Thanks for your quick response. The contain of StrSql is:
"SELECT IdTipo FROM TIPOSTELEFONO", where IdTipo id a column of TIPOSTELEFONO Table.
I tryied the same sql setence with SQL Server Management Studio Express and it works fine. Already I have tryied with others sql sentences. All they worked fine in SQL Server Management Studio, but not with my java example using sqljdbc4.jar.
sqljdbc4.jar documentation comment that these driver work with sql server 2000 to sql server 2008. I'll ask this cuestion in Microsoft forums.
Thanks.

Problem upgrading from SCOM 2012 SP1 to R2 (near impossible to uninstall SCOM agent from Management Server)

I'm trying to upgrade our SCOM 2012 SP1 environment to R2, but I have a heck of a problem getting there.
We currently have an test installation with SCOM 2012 SP1 with Management Server and Console on a single 2012 Standard server. The database are located on a remote server. The R2 setup stopped mid way through the setup, because the SCOM 2012 SP1 agent is
installed. And I could NOT remove it my any normal means. I've tried "misexec.exe /x productcode", the setup, powershell uninstall and so on. Nothing works, because the management server installation is blocking the uninstall. The uninstall says
I have to remove the management installation first. And that's not gonna happen.
I had to follow this guide to finally getting through the setup: http://www.opsman.co.za/forcibly-removing-a-scom-agent-that-cannot-be-uninstalled-by-normal-means/
In addition to searching for the agent msi install key in registry, and deleting everything. After I did this, the setup is working, and the SCOM management server, console and DB are up to date. However, the Microsoft Monitoring Agent are STILL there in
Control Panel. And this can NOT be the most healthy way of getting through the setup.
I'm about to upgrade to R2 in our production environment with 3 management servers, and I would hate to go through this sketchy process there as well. Just for the record, I have no idea why the agents are installed on our management servers.
Any of you have tips as to how I can get rid of the agents more gracefully?

Hi
Thanks for the replay guys!
None of those links touch my problem I'm afraid. I have followed the Upgrade guides you pointed to, step by step. But the setup does not Complete. There's problems during the actual software Upgrade of the management servers (3'rd step in the Upgrade page).
I've dived into the Application logs and installation logs, and as far as I can tell, it stops because it has trouble upgrading while the server has the 2012 SP1 Agent installed. I do not remember the actual error text right now, but I can get it in a few
days.
Anyhow, the setup DID move on once I removed most of the registry information of the agent installation. So. that leaves me to the conclusion that the agent IS in fact stopping the setup. Either the agent are malfunctioning, or the setup do not expect the
agent to be present on the management servers. I suspect the latter to be the the most plausible. At least until Yan Li told me this was normal.
So, I'm not sure what to think. I'm pretty much forced to remove this agents, as this is the only thing allowing me to continue the setup. At least untill I'm told otherwise. But I hate to do it this way. It's so dirty. The registry is pretty much cleaned,
but there's still Application files present, and the agent is still in the Control panel and can be started. It's not something I would like to do in our prodution environment.

Admin server and Managed Server not Running

Hi,
Admin server doesnot change its state to RUNNING from STARTING. Even after hrs of starting the server.. the satus is as shown.
<Jun 1, 2011 10:22:59 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Jun 1, 2011 10:23:01 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Jun 1, 2011 10:23:01 AM IST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <LoggingService> <BEA-320400> <The log file D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\AdminServ
er.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminS
erver\logs\AdminServer.log00056. Log messages will continue to be logged in D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\AdminServer.log.
>
<Jun 1, 2011 10:23:02 AM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\OSB11g_Home\user_projects\domains\osb11g_domain\servers\AdminServer\logs\Ad
minServer.log is opened. All server side log events will be written to this file.>
<Jun 1, 2011 10:23:07 AM IST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Jun 1, 2011 10:23:17 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Jun 1, 2011 10:23:17 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
It just stops at this stage. Facing the same prob with Managed Server as well.
I tried Killing all the java process, as well as updated boot.properties file and restarted which dint help.
can anyone Help me on this.
Thanks & Regards,
Indu

Yes, i do have applications deployed.
Here is my config.xml
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>osb11g_domain</name>
<domain-version>10.3.4.0</domain-version>
<security-configuration>
<name>osb11g_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType">
<wls:use-retrieved-user-name-as-principal>true</wls:use-retrieved-user-name-as-principal>
</sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<credential-encrypted>{AES}sLWSLcQMQZchzo4SR4mjU9t+aXrRFlW76I0/Ie1V/yHuMxEZuy5UXjjl3D0Nzrx43Y4+uYwH+l4fz2RHNJdUBNyjN06wyjujzfOf1o61GuXTvWeBrT5LAIlAhstSWvMZ</credential-encrypted>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>{AES}vIICdR6YTBvPsRxkaKtwek5yf6wEPemMg5NLqoMoSSY=</node-manager-password-encrypted>
</security-configuration>
<server>
<name>AdminServer</name>
<listen-address>localhost</listen-address>
<server-diagnostic-config>
<name>AdminServer</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<server>
<name>osb_server1</name>
<listen-port>8011</listen-port>
<listen-address></listen-address>
<server-diagnostic-config>
<name>osb_server1</name>
<diagnostic-context-enabled>true</diagnostic-context-enabled>
</server-diagnostic-config>
</server>
<embedded-ldap>
<name>osb11g_domain</name>
<credential-encrypted>{AES}y3pEDYlwHWeJTJDCHip1ctAwdCh6Q+4nW09EsH6rlDtzqCsaxpc5fx4SoASAKkIo</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.4.0</configuration-version>
<app-deployment>
<name>FMW Welcome Page Application#11.1.0.0.0</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jrf_11.1.1/fmw-welcome.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>wsil-wls</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.webservices_11.1.1/wsil-wls.ear</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DMS Application#11.1.1.1.0</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.dms_11.1.1/dms.war</source-path>
<deployment-order>5</deployment-order>
<security-dd-model>CustomRoles</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FileAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/FileAdapter.rar</source-path>
<deployment-order>321</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>DbAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/DbAdapter.rar</source-path>
<deployment-order>322</deployment-order>
<plan-dir xsi:nil="true"></plan-dir>
<plan-path>D:\OSB11g_Home\Oracle_OSB1\soa\connectors\Plan.xml</plan-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JmsAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/JmsAdapter.rar</source-path>
<deployment-order>323</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>AqAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/AqAdapter.rar</source-path>
<deployment-order>324</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FtpAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/FtpAdapter.rar</source-path>
<deployment-order>325</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SocketAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/SocketAdapter.rar</source-path>
<deployment-order>326</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>MQSeriesAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/MQSeriesAdapter.rar</source-path>
<deployment-order>327</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleAppsAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/AppsAdapter.rar</source-path>
<deployment-order>328</deployment-order>
<plan-dir xsi:nil="true"></plan-dir>
<plan-path>D:\OSB11g_Home\Oracle_OSB1\soa\connectors\Plan_Apps.xml</plan-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>OracleBamAdapter</name>
<target>AdminServer,osb_server1</target>
<module-type>rar</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/soa/connectors/OracleBamAdapter.rar</source-path>
<deployment-order>329</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Cluster Singleton Marker Application</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/clustersingletonmarker.ear</source-path>
<deployment-order>80</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Domain Singleton Marker Application</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/domainsingletonmarker.ear</source-path>
<deployment-order>85</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Framework Starter Application</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/frameworkstarter.ear</source-path>
<deployment-order>90</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Coherence Cache Provider</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/coherence.ear</source-path>
<deployment-order>93</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>XBus Kernel</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/kernelEar</source-path>
<sub-deployment>
<name>/httpTransport</name>
<module-type>war</module-type>
<compatibility-name>XBus HTTP Transport Webapp</compatibility-name>
</sub-deployment>
<deployment-order>95</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB UDDI Manager</name>
<target>AdminServer</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/uddiEar</source-path>
<deployment-order>122</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Subscription Listener</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/uddi_subscription</source-path>
<deployment-order>123</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JMS Reporting Provider</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/jmsreportprovider.ear</source-path>
<deployment-order>125</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Message Reporting Purger</name>
<target>osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/common/msgpurger.ear</source-path>
<deployment-order>126</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Ftp Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>FTP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ftp_transport.ear</source-path>
<sub-deployment>
<name>ftp_transport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>ftp_transport.jar</compatibility-name>
</sub-deployment>
<deployment-order>151</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SFTP Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SFTP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/sftp_transport.ear</source-path>
<sub-deployment>
<name>sftp_transport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>sftp_transport.jar</compatibility-name>
</sub-deployment>
<deployment-order>165</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Email Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>EMail Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/emailtransport.ear</source-path>
<sub-deployment>
<name>emailtransport.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>emailtransport.jar</compatibility-name>
</sub-deployment>
<deployment-order>153</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>File Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>File Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/file_transport.ear</source-path>
<sub-deployment>
<name>filepoll.jar</name>
<target>osb_server1</target>
<module-type>jar</module-type>
<compatibility-name>filepoll.jar</compatibility-name>
</sub-deployment>
<deployment-order>155</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>MQ Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>MQ Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/mq_transport.ear</source-path>
<deployment-order>172</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>EJB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ejbtransport.ear</source-path>
<deployment-order>157</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>Tuxedo Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/tuxedo_transport.ear</source-path>
<deployment-order>159</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALDSP Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<compatibility-name>ALDSP Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/aldsp_transport.ear</source-path>
<deployment-order>161</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SB Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/sb_transport.ear</source-path>
<deployment-order>163</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>WS Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>WS Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/ws_transport.ear</source-path>
<deployment-order>166</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>WS Transport Async Applcation</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/bea_alsb_ws_async_response.war</source-path>
<deployment-order>167</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>FLOW Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>FLOW Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/flow_transport.ear</source-path>
<deployment-order>175</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>BPEL 10g Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>BPEL 10g Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/bpel10gtransport.ear</source-path>
<deployment-order>177</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JCA Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>JCA Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/jcatransport.ear</source-path>
<deployment-order>181</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>JEJB Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>JEJB Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/jejb_transport.ear</source-path>
<deployment-order>184</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>SOA-DIRECT Transport Provider</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<compatibility-name>SOA-DIRECT Transport</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/transports/soa_transport.ear</source-path>
<deployment-order>185</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Routing</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbusrouting.ear</source-path>
<deployment-order>410</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Transform</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbustransform.ear</source-path>
<deployment-order>420</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Publish</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbuspublish.ear</source-path>
<deployment-order>430</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Logging</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/stages/xbuslogging.ear</source-path>
<deployment-order>440</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Resource</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbresourceWar/sbresource.war</source-path>
<deployment-order>500</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB WSIL</name>
<target>osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/wsilWar/wsil.war</source-path>
<deployment-order>510</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ServiceBus_Console</name>
<target>AdminServer</target>
<module-type>war</module-type>
<compatibility-name>sbconsole</compatibility-name>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbconsoleEar</source-path>
<deployment-order>810</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<app-deployment>
<name>ALSB Test Framework</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/Oracle_OSB1/lib/sbTestFwk.ear</source-path>
<deployment-order>910</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</app-deployment>
<library>
<name>oracle.bi.jbips#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-jbips-slib-stub.ear</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.composer#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-composer-slib-stub.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.model.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-model-slib.ear</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.view.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-view-slib.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.bi.adf.webcenter.slib#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.bi.presentation_11.1.1/bi-adf-webcenter-slib.war</source-path>
<deployment-order>100</deployment-order>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.wsm.seedpolicies#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.wsm.policies_11.1.1/wsm-seed-policies.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.jsp.next#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jsp_11.1.1/ojsp.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.dconfig-infra#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.dconfig-infra_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>orai18n-adf#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.nlsgdk_11.1.0/orai18n-adf.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.dconfigbeans#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.dconfigbeans_11.1.1.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.pwdgen#[email protected]</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.pwdgen_11.1.1/pwdgen.jar</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.jrf.system.filter</name>
<target>AdminServer,osb_server1</target>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.jrf_11.1.1/system-filters.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>ear</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.model_11.1.1/adf.oracle.domain.ear</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.businesseditor#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.businesseditor_11.1.1/adf.businesseditor.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>oracle.adf.management#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.management_11.1.1/adf-management.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>adf.oracle.domain.webapp#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.adf.view_11.1.1/adf.oracle.domain.webapp.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>jsf#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:\OSB11g_Home\wlserver_10.3/common/deployable-libraries/jsf-1.2.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>UIX#[email protected]</name>
<target>AdminServer,osb_server1</target>
<module-type>war</module-type>
<source-path>D:/OSB11g_Home/oracle_common/modules/oracle.uix_11.1.1/uix11.war</source-path>
<security-dd-model>DDOnly</security-dd-model>
<staging-mode>nostage</staging-mode>
</library>
<library>
<name>ohw-

Sql Exception on Testing Configuration with SQL Server JDBC driver for XA

I have a requirement of analyzing the behavior of SQL Server JDBC data sources for XA transactions in our application.We have been using Non-XA drivers for both Oracle and SQL Server as we had no requirement for transactions spanning across multiple databases in past.I have setup and tested the XA driver for Oracle (Oracle Driver (Thin XA) for Instance Connections 9.0.1,9.2.0,10,11) in Weblogic 11g and its working perfectly for transactions spanning across two databases.No when I am trying to configure weblogic 11g R1 for Sql server JDBC driver to support XA transactions with driver details as follows,
Server:Weblogic 11g R1
Driver Type: MS Sql Server
Database Driver :Oracle's MS SQL Server Driver(Type 4 XA) Version:7.0,2000,2005)
Database:SQL Server 2005(Single Instance)
and try to create a new data source and select "Test Configuration" and following error is thrown ,
<Mar 17, 2011 4:49:49 PM GMT+05:30> <Error> <Console> <BEA-240003> <Console encountered the following error java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]xa_open (0) returns -3
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRPCRequest.processReplyToken(Unknown Source)
at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at weblogic.jdbc.sqlserver.SQLServerImplStatement.getNextResultType(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonTransitionToState(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.postImplExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.commonExecute(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseStatement.executeUpdateInternal(Unknown Source)
at weblogic.jdbc.sqlserverbase.BasePreparedStatement.executeUpdate(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.executeXaRpc(Unknown Source)
at weblogic.jdbcx.sqlserver.SQLServerImplXAResource.open(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection.init(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXAConnection40.init(Unknown Source)
at weblogic.jdbc.sqlserverbase.BaseClassCreatorForJDBC40.createXaConnection(Unknown Source)
at weblogic.jdbcx.sqlserverbase.BaseXADataSource.getXAConnection(Unknown Source)
at com.bea.console.utils.jdbc.JDBCUtils.testConnection(JDBCUtils.java:550)
at com.bea.console.actions.jdbc.datasources.createjdbcdatasource.CreateJDBCDataSource.testConnectionConfiguration(CreateJDBCDataSource.java:450)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:870)
at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:809)
at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:478)
at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:306)
at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:336)
at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:52)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.access$201(PageFlowRequestProcessor.java:97)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor$ActionRunner.execute(PageFlowRequestProcessor.java:2044)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:64)
at org.apache.beehive.netui.pageflow.interceptor.action.ActionInterceptor.wrapAction(ActionInterceptor.java:184)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.invoke(ActionInterceptors.java:50)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors$WrapActionInterceptorChain.continueChain(ActionInterceptors.java:58)
at org.apache.beehive.netui.pageflow.interceptor.action.internal.ActionInterceptors.wrapAction(ActionInterceptors.java:87)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:2116)
at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:261)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:556)
at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:853)
at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:631)
at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:158)
at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:256)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:133)
at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:1199)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:686)
at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:142)
at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:106)
at com.bea.portlet.adapter.NetuiActionHandler.raiseScopedAction(NetuiActionHandler.java:111)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:181)
at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:167)
at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:225)
at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:180)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:324)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:334)
at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:130)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:352)
at com.bea.netuix.nf.Lifecycle.runInbound(Lifecycle.java:184)
at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:159)
at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:199)
at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
I followed the instruction in weblogic jdbc drivers guide to configure the JTA Transactions to support XA on SQL Server machine and weblogic server which included,
1.Copying sqljdbc.dll copied to SQL_Server_Root/bin directory from WL_HOME\server\lib.
2.Copied instjdbc.sql to sql server machine and executed the script with following output,
Changed database context to 'master'.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_open2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_close2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_start2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_end2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_prepare2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_commit2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_rollback2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_forget2', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover', because it does not exist or you do not have permission.
Msg 3701, Level 11, State 5, Server SQLDB, Procedure sp_dropextendedproc, Line 16
Cannot drop the procedure 'xp_jdbc_recover2', because it does not exist or you do not have permission.
creating JDBC XA procedures
instxa.sql completed successfully.
3.Verified that MSDTC service is running on both SQL Server and weblogic machines with XA Transaction enabled and DTC option enabled for both inbound and outbound connections.
4.Copied sqljdbc.jar (version 3.0 downloaded from msdn portal) to "C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver" directory and updated weblogic_classpth variable in commEnv.cmd file.
set WEBLOGIC_CLASSPATH=%JAVA_HOME%\lib\tools.jar;%BEA_HOME%\utils\config\10.3\config-launch.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%FEATURES_DIR%\weblogic.server.modules_10.3.2.0.jar;%WL_HOME%\server\lib\webservices.jar;%ANT_HOME%/lib/ant-all.jar;%ANT_CONTRIB%/lib/ant-contrib.jar;C:\Oracle\Middleware\wlserver_10.3\server\ext\jdbc\sqlserver\server\ext\jdbc\sqlserver\sqljdbc.jar
Can some one please provide some input on whats causing this and any other steps needs to be followed to implement XA support using SQL Server JDBC driver.

You seem to have done everything correctly and diligently. I would ask that you open
an official support case.

MQSeries as a Transactional Resource Manager with Weblogic Server

          I am trying to setup the example given in the BEA white paper:
          Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          Version 1.
          October 25, 2001.
          I followed the instructions given in the documents, but when i run client program
          >java MQClient t3://localhost:7001 "MQSeries test"
          I received the following exception below. Does anyone how what is the reason for
          this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
          6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
          for java and the MQSeries classes for Java Message Service on the weblogic
          server machine.
          sending: "MQSEries test"
          Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
          sted exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          at $Proxy1.bridgeWLS2MQS(Unknown Source)
          at MQClient.main(MQClient.java:54)


The point is that over TCPIP the MQ XA connection factory is not available.
          The MQ shared memory/JNI driver is required to access it, which limits
          access to those processes that are on the same box as the MQ q manager.
          This is an MQ series limitation.
          Douglas WF Acheson wrote:
          > Hello,
          >
          > If memory server me correct, default connection to MQ Series is through
          > JNI calls and shared memory. You have to change the protocol to TCPIP when
          > connection to the queue manager on another box (do not know much about XA
          > with MQ Series); that is when you connect to MQ Series vi JMS on another
          > box you must do something like the following:
          >
          > qcf = new MQQueueConnectionFactory() ;
          > qcf.setHostName(hostName) ;
          > qcf.setPort(port) ;
          > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
          > qcf.setQueueManager(qManagerName) ;
          >
          > Then when you create you queues, sesions etc. you are point at the correct Q
          > manager.
          >
          > Hope this helps ...
          >
          > Douglas WF Acheson
          >
          > "Raja Mukherjee" <[email protected]> wrote in message
          > news:[email protected]...
          > > On a closer look at the original post (sorry for missing that, it was
          > early
          > > in the morning), you would not be able to use XA if your QM and WLS are in
          > > different boxes. Check on this newsgroup, there are several posts on this
          > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
          > on
          > > the sames box. This is a MQSeries limitation not WLS.
          > >
          > > .raja
          > >
          > >
          > > "ibrahim Nehme" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > I am trying to setup the example given in the BEA white paper:
          > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          > > > Version 1.
          > > > October 25, 2001.
          > > > I followed the instructions given in the documents, but when i run
          > client
          > > program
          > > >
          > > > >java MQClient t3://localhost:7001 "MQSeries test"
          > > > I received the following exception below. Does anyone how what is the
          > > reason for
          > > >
          > > > this exception(s) and how i can solve the problem? My MQSeries Server
          > and
          > > Weblogic
          > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
          > > classes
          > > > for java and the MQSeries classes for Java Message Service on the
          > weblogic
          > > > server machine.
          > > > ---------------------------------------
          > > > sending: "MQSEries test"
          > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
          > > server; ne
          > > > sted exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > <<no stack trace available>>
          > > > --------------- nested within: ------------------
          > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ]
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
          > > > at MQClient.main(MQClient.java:54)
          > >
          > >

How to prevent SQLException with MS SQL Server?

Hi,
I have the following problem (just an example): I have a stored procedure in my MS SQL database that does an INSERT into a table. If the record is already in the table, a unique key violation is detected and my procedure does some other things, generates an error code and returns it to the calling Java method.
Problem is now, that even if I catch the error in the procedure and do some processing, after returning to the calling Java method, I receive an SQLExcetion with the original error (duplicate key...).
How can I prevent this? I want the stored procedure to do the complete error processing and return a self-made error code to Java. So, there must be some way to "reset" the error either in the stored procedure or in the JDBC connection.
Any ideas? With Oracle everything works like expected.
Regards,
Juergen

Juergen,
The SQL Server stored procedure implementation is somewhat different from the Oracle one. As you might have noted in Oracle all results (including ResultSets) can only be returned as output parameters from the stored procedure. With SQL Server you can just do a SELECT inside the procedure and you will see a ResultSet in Java (somewhat of an asynchronous call). There are advantages and disadvantages to both approaches.
One of the SQL Server "disadvantages" is the problem you are experiencing: error messages are also generated as they occur and sent to the client (JDBC driver), which transforms them into SQLExceptions. Another SQL Server disadvantage is the fact that output parameters are only available after the driver has parsed and cached or discarded all results.
With Oracle, on the other hand, you can only obtain ResultSets from stored procedures through cursors. This has two disadvantages: first there's an overhead on the server side to maintain the cursor snd seconf you need non-standard JDBC code to obtain the ResultSet.
So the short answer to your question would be that there isn't (as far as I know) any way to avoid the SQLException. However, you can skip it and either get the linked SQLExceptions or call getMoreResults() until you get your custom error message.
Alin.

No suitable driver with SQL Server Driver

Hi,
i'm making a jsp page that it use a JDBC Connection to a SQL Server with SQL Server 2000 Driver for JDBC.
I put in JDeveloper Project Settings, Configurations\Development\Libraries, the reference to msbase.jar, msutil.jar and mssqlserver.jar. Alse i put the reference to Oracle JDBC libraries.
The code in jsp page to reference the driver, obtain the DataSource and get the connection is the following:
java.sql.DriverManager.registerDriver(new com.microsoft.jdbc.sqlserver.SQLServerDriver());
javax.naming.Context ic = new javax.naming.InitialContext();
javax.sql.DataSource ds = (javax.sql.DataSource) ic.lookup("jdbc/SQLServerDS");
java.sql.Connection con = ds.getConnection();
I defined the DataSource in data-sources.xml, wich look like:
<data-source class="com.evermind.sql.DriverManagerDataSource" location="jdbc/SQLServerCoreDS" password="<pass>" username="<user>" url="jdbc:microsoft:sqlserver://<server>:1433" xa-location="jdbc/xa/SQLServerXADS" inactivity-timeout="30" connection-driver="com.microsoft.jdbc.sqlserver.SQLServerDriver" name="SQLServerDS" ejb-location="jdbc/SQLServerDS">
<property name="DatabaseName" value="Northwind"/>
<property name="SelectMethod" value="direct"/>
</data-source>
This compile ok, but when i run the page appears the following error (SQLException):
No suitable driver
After looking so much, i don't find the cause of the problem.
Can anyone helpme?
Thanks
Javier S.

Hi Javier,
Although I don't work with JDeveloper, as far as I know, for OC4J, I believe you need to put the relevant JAR files in the "j2ee/home/lib" subdirectory of the OC4J installation. Unfortunately, since I don't work with JDeveloper, I can't tell you where that would be -- sorry :-(
I suggest that you try asking also in the JDeveloper forum (in case you haven't already :-)
Hope this helps you.
Good Luck,
Avi.

Add management server: Setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0

I want to add another management server to our existing SCOM environment. But whenever I run this setup on a new server I get stuck in the window for selecting the OperationsManager database. The database field stays blank and in the OpsMgrSetupWizard log
there are lines that the setup version is not compatible with the database version. But I use the same installer as when I installed the other management servers a year ago.
Maybe there is a newer setup installer? But I can't find it.
[10:42:54]: Error:
:Error:setup version: 7.0.9538.0 is not compatible with database version: 7.1.10226.0
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read returned true. so far, this is OM DB, not an empty DB
[10:42:54]: Debug:
:Connection was not open. We will try to open it.
[10:42:54]: Debug:
:SqlConnectionReady returned True.
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Info:
:Info:isOMDatabase: Read did not return true. The MG is missing. This is not OM DB
[10:42:54]: Info:
:Info:Using DB command timeout = 1800 seconds.
[10:42:54]: Always:
:Azman store table not found in OperationsManagerDW table, assuming this is an not a valid OMDB for empty DB scenario.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.
[10:42:54]: Info:
:Info:DatabaseConfigurationPage: DB connection attempt completed.

Never mind, found it!
Apparently there was a newer version of SCOM setup in msdn and someone upgraded our existing SCOM environment. Downloaded the new setup, new report viewer controls and a System
CLR Types for Microsoft® SQL Server® 2012 and now it works!!

VPP Distribution issues with OSX Server Profile Manager

Hi, I have a new issue with my OSX 10.9.5 Server. I use VPP to distribute apps to users devices, when I would add a new user I would send them an invitation message through /profilemanager . All was working well until recenetly , the message still arrives in the users mailbox however when you click the "sign in" link on the "receive apps and books from xxxxx" email instead of opening through the Mac App store app it now opens Safari and connects to the profile manager server , any ideas ? it never has done this before and although I thought it was a new feature or method I can not seem to resolve the issue.

Hi if when you are redirected back to your Mac Server you enter the user name and password of the user you are trying to receive VPP apps for i.e the Open Directory credentials it will then open the App Store providing the credentials are correctly entered so it looks like an additional layer of security. The process is click on the link in the VPP invite email, this takes you to your Mac Server profile manager, log on with your OD account, App store then opens on your Mac like it used to.

No suitabel driver SQLException with Managed Server

Similar Messages

Maybe you are looking for