Weblogic Pool Driver doesn't support XA driver

          I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store uses the Oracle
          XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen the JMS server
          starts it gives me the following exception: Weblogic Pool Driver doesn't support
          XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2. THe full error
          trace is shown below:
          <Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer "jmsTestJmsServer1"
          store failed to open java.io.IOException: JMS JDBC store, connection pool = <jmsTestJdbcConnectionPool>,
          prefix = <JMS1>: cannot determine DBMS type
          <java.sql.SQLException: Pool connect failed : java.lang.Exception: Weblogic Pool
          Driver doesn't support XA driver, Please change your config to use a Non-XA driver
          <     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
          <     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
          <     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
          <     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
          <     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          <     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          <     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          <     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          <     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          <     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
          <     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          <     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          <     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:324)
          <     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          <     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          <     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          <     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          <     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          <     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          <     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          <     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          <     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          <     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          <     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          <     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          <     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
          <     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          <     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
          <     at weblogic.Server.main(Server.java:32)
          

          It appears that WebLogic 8.1 does not have the "user transactions enabled" flag
          for a connection factory. I see references to this flag in earlier versions of
          WebLogic. The closest thing in WL 8.1 seems to be the "XA Connection Factory Enabled"
          flag.
          Tom Barnes <[email protected]> wrote:
          >Actually, all you normally need to check is "user transactions enabled".
          >The XA versions of the javax.jms interfaces (which are generated
          >via XA connection factories) are not required - except
          >that I think that MDBs make a check for this.
          >
          >Naresh Bhatia wrote:
          >> So I assume that the XA capability is enabled by checking the "XA Connection
          >Factory
          >> Enabled" checkbox for the JMS connection factory.
          >>
          >> Thanks.
          >> Naresh
          >>
          >> Tom Barnes <[email protected]> wrote:
          >>
          >>>Just use a non-XA driver and non-XA pool for JMS JDBC stores.
          >>>WL JMS' XA capability does not come from its JDBC driver.
          >>>
          >>>Naresh Bhatia wrote:
          >>>
          >>>
          >>>>I am trying to set up a JDBC Strore for a JMS Server. The JDBC Store
          >>>
          >>>uses the Oracle
          >>>
          >>>>XA driver (oracle.jdbc.xa.client.OracleXADataSource). However whaen
          >>>
          >>>the JMS server
          >>>
          >>>>starts it gives me the following exception: Weblogic Pool Driver doesn't
          >>>
          >>>support
          >>>
          >>>>XA driver. Any idea what I am doing wrong? I am using WL 8.1 SP2.
          >THe
          >>>
          >>>full error
          >>>
          >>>>trace is shown below:
          >>>>
          >>>><Jan 15, 2004 3:05:09 PM EST> <Alert> <JMS> <BEA-040052> <JMSServer
          >>>
          >>>"jmsTestJmsServer1"
          >>>
          >>>>store failed to open java.io.IOException: JMS JDBC store, connection
          >>>
          >>>pool = <jmsTestJdbcConnectionPool>,
          >>>
          >>>>prefix = <JMS1>: cannot determine DBMS type
          >>>><java.sql.SQLException: Pool connect failed : java.lang.Exception:
          >>>
          >>>Weblogic Pool
          >>>
          >>>>Driver doesn't support XA driver, Please change your config to use
          >>>
          >>>a Non-XA driver
          >>>
          >>>><     at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:160)
          >>>><     at weblogic.jdbc.pool.Driver.connect(Driver.java:156)
          >>>><     at weblogic.jms.store.JDBCIOStream.checkDbmsType(JDBCIOStream.java:1490)
          >>>><     at weblogic.jms.store.JDBCIOStream.open(JDBCIOStream.java:420)
          >>>><     at weblogic.jms.store.JMSStore.open(JMSStore.java:224)
          >>>><     at weblogic.jms.backend.BEStore.open(BEStore.java:262)
          >>>><     at weblogic.jms.backend.BEStore.start(BEStore.java:151)
          >>>><     at weblogic.jms.backend.BackEnd.openStores(BackEnd.java:1171)
          >>>><     at weblogic.jms.backend.BackEnd.resume(BackEnd.java:1290)
          >>>><     at weblogic.jms.JMSService.addJMSServer(JMSService.java:2241)
          >>>><     at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:330)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:590)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:568)
          >>>><     at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:240)
          >>>><     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:324)
          >>>><     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:711)
          >>>><     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:690)
          >>>><     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:476)
          >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
          >>>><     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
          >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:947)
          >>>><     at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:908)
          >>>><     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
          >>>><     at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
          >>>><     at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7271)
          >>>><     at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1210)
          >>>><     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:362)
          >>>><     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
          >>>><     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
          >>>><     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
          >>>><     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
          >>>><     at weblogic.Server.main(Server.java:32)
          >>>>
          >>>
          >>
          >
          

Similar Messages

  • The driver doesn't support the version of ODBC

    Hi:
    We have been working with timesten client on a windows, we had not have any problem, the number of clients had not connect more than 80 clients, but today we connected 125 clients and we got this error directly to the client application.
    ERROR [08001] [TimesTen][TimesTen 7.0.1.0.0 CLIENT]Unable to connect to data source (DSN: SentraProdDSN; Network Address: 10.100.134.24; Port Number: 16003). ENOTSOCK: Invalid socket or socket closed.
    ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).
    But on the server error log the messages were:
    14:52:02.75 Err : SRV: 8974: EventID=5| Socket recv() failed. Error (131): Con
    nection reset by peer. File: /olympus/build/release_20070911/VisiChannel/oc/src/
    vostcpip.cpp; Line: 632
    14:52:02.75 Err : SRV: 8974: EventID=68| Failed to read request from client. Cl
    osing connection without reply.
    14:52:06.38 Err : SRV: 9078: EventID=5| Socket recv() failed. Error (131): Con
    nection reset by peer. File: /olympus/build/release_20070911/VisiChannel/oc/src/
    vostcpip.cpp; Line: 632
    14:52:06.38 Err : SRV: 9083: EventID=5| Socket recv() failed. Error (131): Con
    nection reset by peer. File: /olympus/build/release_20070911/VisiChannel/oc/src/
    vostcpip.cpp; Line: 632
    14:52:06.38 Err : SRV: 9078: EventID=68| Failed to read request from client. Cl
    osing connection without reply.
    14:52:06.38 Err : SRV: 9083: EventID=68| Failed to read request from client. Cl
    osing connection without reply.
    14:52:06.81 Err : SRV: 9116: EventID=3| Socket send() failed. Error (32): Brok
    en pipe. File: /olympus/build/release_20070911/VisiChannel/oc/src/vostcpip.cpp;
    Line: 728
    14:52:06.81 Err : SRV: 9116: EventID=5| Socket recv() failed. Error (131): Con
    nection reset by peer. File: /olympus/build/release_20070911/VisiChannel/oc/src/
    vostcpip.cpp; Line: 632
    14:52:06.81 Err : SRV: 9116: EventID=68| Failed to read request from client. Cl
    osing connection without reply.
    14:52:07.13 Err : SRV: 16186: EventID=5| Socket recv() failed. Error (146): Con
    nection refused. File: /olympus/build/release_20070911/VisiChannel/oc/src/vostcp
    ip.cpp; Line: 632
    14:52:07.57 Err : SRV: 16186: EventID=5| Socket recv() failed. Error (146): Con
    nection refused. File: /olympus/build/release_20070911/VisiChannel/oc/src/vostcp
    ip.cpp; Line: 632
    So we don't know if this error could happen because the number of connections were exceeded, but when this has happened the error messages is different.
    Let me tell you that the application client was developed using C#. So could it be that the C# on .NET could have a instruction that the timesten ODBC could not manage?

    Is this problem reproducable? i.e. Does it occur whenever you get close to 125 clients connecting to TimesTen? Next time when it happens again, can you check to see whether you can establish a new client/server connection locally on the TimesTen server machine?
    Each TimesTen Client connection requires one server process, and by default, a server process is spawned when a client requests a connection. It is possible that you may have too many processes running on the server, hence it cannot spawn additional server processes to handle the new connections. The good news is that in 7.0.3, the TimesTen server is now multi-threaded and each process can handle multiple client connections (this number is configurable), so it's possible to have fewer server processes for the same number of client connections compared to previous releases.
    Please check out "Specifying multiple connections to the TimesTen Server" in the 7.0.3 Oracle TimesTen Operations Guide for more information on how to turn on the multithreaded mode.
    Regards
    Simon

  • Hp p1005 driver doesn't support duplex

    The driver for my HP LaserJet P1005 (version 1.4.0) doesn't support the manual duplex option that was available under previous version of the OS.  This behavior exhibits in all applications.  Have tried deleting, adding, resetting print system.  Other printers seem fine.  Installed via USB.

    OXR wrote:
    I found a ppd file for a different printer thatThad duplex support, added 7lines of DuplexUI to the ppd file, which yields a dialog box, but alas still prints single sided. So, I think I'm close, but not there yet.
    I doubt that another PPD file will work.  Your printer does not have a mechanical duplex unit.  Any duplex output must be done in software that is usable for all printers or is specifically part of the manufacturer's software for your printer model.
    Remember also that your printer is a very dumb printer.  It has to have its firmware sent to it each and every time it is turned on.  You will not be able to just use any driver that contains a provision for duplex.
    But you are spot on, for the current driver.  Generic print only.  I've p,ayed around with some of the other HP drivers, but get worse (no print at all) results.  So I'm hoping the CUPS solution will work. Just missing a few things yet.
    Your best bet is if an older version of the HP software is usable in Mavericks.  Failing an older version working, you would seem to be left with only the chance that the PDF workflow that HP provides will work for you.

  • T520 Beta Sound Driver doesn't support multi stream output with docking station

    I always used (and loved) the ability to use the laptop speakers and the headphone jack as independend outputs. For Windows 8 it doesn't work. Neither Win8 beta driver nor the latest Win7 driver brings this feature to Win8.
    The option for Multistream is still selectable in SmartAudio. Selecting this option makes Win8 installing some things but doesn't actually make MultiStream work 
    Hope this is just because of the drivers beta stage...
    Solved!
    Go to Solution.

    The new audio driver for windows8 brings back the multi stream output. It also fixes the crash on selecting VoIP-Settings in SmartAudio application Driver is here.

  • JDBC Thin driver doesn't support writing data into remote database via database link

    Dear Oracle Guru:
    Please confirm: Oracle JDBC thin driver does not support writing data to remote database via database link.
    The following errors occur when trying to write data into a remote database via database link through jdbc thin driver:
    ORA-03106: fatal two-task communication protocol error
    ORA-02063: preceding line from FDBE.PAPDSRAS1
    ORA-02063: preceding 2 lines from PA
    SQL statement is a prepared statement using a SQL like: insert into mytable@pa (col1,col2) values (?,?).
    Thanks.
    null

    Thanks, Dan.
    I still think it is a driver problem, because I can do similar things in a stored procedure or in PL/SQL Developer to copy records from a local database table to a remote database table via database link (insert into mytable@pa select * from mytable). The value for distributed_transactions of our database is 10.

  • Error saving Project 2010 files to network drive - doesn't see network drive

    ANSWERED (11 April 2014):
    So it seems the resolution to this is to simply create a new share with a different name. I used the existing folder (to retain NTFS permissions) and just select to Add a new Share (applying the same Share permissions as the non working Shares).
    Deploying this new Share via Group Policy as a test resulted in staff being able to open files from Windows Search, save files through MS Project and the Share being accessible through browsing SMB.
    All problems resolved by using a new share name for the existing folder. Seems to be a corruption in the namespace.
    Note: I had previously deleted the share and recreated it. I had removed all NTFS permissions and readded (through both the GUI and icacls). This didn't make a difference.
    Only changing the name of the share fixed the problem.
    Original Question
    Already
    posted here... but Microsoft Support has not responded.
    It seems some staff on some computers are having problems saving MS Project files to the network. This is only since an upgrade to SBS2011 (from SBS2003). The only difference now, is that network drives are mapped via group policy rather than a  'net
    use' script.
    This is affecting users on Windows 7 and Windows Server 2008 R2, with either MS Project 2007 or 2010. The users have full change access to the folders and can create new files and modifying existing files, just not a MS Project file. Other file tyes, e.g
    Word .docx, Excel .xlsx, Adobe .pdf files, all work fine. These files can be opened, edited and saved normally without problem.
    To replicate this:
    The user opens an existing file or creates a new file on the network folder (either through Windows Explorer or MS Project). They then click File > Save in MS Project and receive the following error (see pic below):
    An interesting symptom of this is that if you select File > Save As in MS Project, the Sae As dialog box doesn't remeber the path location of the network drive. MS Project instead prompts to save the file in the local users documents folder (see pic below):
    If they browse back to the original folder where the file was saved and choose to save it there, they are of course, prompted to overwrite the existing file and they can save the file. But the same thing happens every time they open the file.
    It seems the problem is that Project isn't seeing the path of the file or that the network drive is attached.
    If a user closes the file without saving it, they are prompted to save the file and the prompt shows the drive path:
       Do you want to save changes to "N:\... Projects\Active Projects\CC...\F4 Project Plan File\004 Programme\test project file.mpp"?   
    But choosing to save the file gives them the same result as Save As, they are prompted for a new location as if the original file location doesn't exist.
    I have disconnected the mapped drive and connected it again using net use but get the same error.
    I have reinstalled MS Project 201, installed Project 2010 SP2 and installed Windows updates and it does the same thing, exactly the same symptoms.
    Further, if the user opens a file from the network drive, the file shows in the Project recent files list. If they try to open the file from the recent files list in project they get the following error:
    "Project cannot open the file.
    -Check that the file name and path are correct.
    -Check that the file format is recognized by Project.
    Project files saved in a version earlier than Microsoft Project 98 can't be opened...."
    This is a test file that I created on the user's computer and network drive, This is being opened with the same version it was created in. If I browse to the folder in Windows Explorer I can open the file. Of course, I then can't save the file (I still get
    the original error). I'm logged on with Domain Admin privileges.
    I've checked these links from other threads (neither apply to my scenario):
    http://support.microsoft.com/kb/983458/en-us|
    http://social.technet.microsoft.com/Forums/en-US/excel/thread/2eeea140-7e6c-4cb9-a89b-06d2102bd9f7/
    I've downloaded my TechNet version of he software and installed it with Sp2 and Windows updates and it does the same thing. This also happens on the Remote Desktop server (Server 2008 R2) using MS Project 2007.

    Case 1
    This error message appears when the document is open on two or more computers that are running different operating platforms. For example,
    if the document is open on a Macintosh computer and you open it on a second computer running Windows or Windows NT, the error occurs when either user tries to save the document.
    This problem stems from a difference between the ways Macintosh OLE and Windows OLE open files. As a result, you cannot save a file on two different operating platforms at the same time.
    Case 2
    This error occurs in Word 97 for Windows if you save to a MAPROOT type network drive connection on a NetWare server where spaces exist in
    the file or folder name.
    Case 3
    This problem may occur if an anti-virus program running on a network has the ability to scan for macro viruses in documents in shared network
    folders.
    For example, if you have the following:
    a shared folder on a network server
    -and-
    an anti-virus program is running on the network server that is set to monitor the shared folder,
    when you attempt to save a document (across the network) to the shared folder, the anti-virus checker may cause the error to occur.
    Case 4
    This problem may occur on Novell networks when the AutoRecover files path is either blank or set to a network drive.
    According each, please try the following workaround:
    WORKAROUND
    To work around this problem, use one of the following methods appropriate to your situation.
    Case 1
    Method 1:
    Move the document to your local hard disk for editing. Move it back to the server after you finish.
    Method 2:
    Save a copy of the
    file with a different
    file name, and work on the copy, either on your hard disk or on the server.
    Case 3
    Method 1:
    Move the document to your local hard disk for editing. Move it back to the server after you finish.
    Method 2:
    Do not use spaces in the directory or document names.
    Method 3:
    Do not use MAPROOT-drive connections. Map your drive connections to the volume-level only.
    Case 4
    Turn off the anti-virus protection on the network server and then try to
    save the document. Contact your anti-virus protection software company for additional details and/or updates to their programs.
    Case 5
    Set the AutoRecover files path to your local drive. To change the AutoRecover path, use the following steps:
    1.
    On the Tools menu, click Options.
    2.
    On the File Locations tab, select AutoRecover files and then click Modify.
    3.
    Change the Modify Location dialog box to a
    folder on your local drive and then click OK.
    4.
    Click OK to close the Options dialog box.
    Hope that helps.
    Smith

  • Weblogic Migration, JDBC doesn't support XA issue

    We are doing Weblogic Migration from WLS10.3.2 to WLS10.3.6 and Java from jdk1.6.0_26 to jdk1.7.0_07
    we are facing the following error for two modules which sends email but few other modules sending email are working fine :
    javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
    *[Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource*
    In Weblogic10.3.6, if we change the Datasource --> Transaction from one-phase commit to Logging Last Resource,
    this issue is getting resolved.
    But all the modules were working fine with one-phase commit in Weblogic10.3.2
    Could you kindly help us to fix this issue and problem in migration.

    Hi Joe,
    We have changed the driver to XA ( Oracle's Driver (Thin XA) for instance connections; Versions:9.0.1 and later )
    and we are getting the below issue in below case
    CASE:
    I will start a transaction and it gets connected to the Database through
    the datasource in weblogic server and then it updates the data into the database which was given from the screen
    Issue:
    Caused by: java.sql.SQLException: Connection closed
    at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:213)
    at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:84)
    at weblogic.jdbc.wrapper.ResultSetMetaData.preInvocationHandler(ResultSetMetaData.java:61)
    at weblogic.jdbc.wrapper.ResultSetMetaData_oracle_jdbc_driver_OracleResultSetMetaData.getColumnCount(Unknown Source)
    Hence i think i cannot go for XA driver....
    It is working for Non XA driver with Logging Last Resource
    As per your note
    Logging Last Resource is an excellent way to engage one non-XA
    resource in a global transaction, with complete safety. The LLR resource is used for logging the
    XA transaction, and is committed as the first part of the second phase of the commit. As such it
    can be managed XA-wise whether that succeeds or fails.
    Can i keep as LLR itself
    Will there be any impact for my applications for below transaction scenarios ?
    One case
    I will start a transaction and it gets connected to the Database through
    the datasource in weblogic server and then it updates the data into the database which was given from the screen
    Another case
    I will start a transaction and it gets connected to the Database(2) through the datasource(2) in weblogic server and it
    reads the data from database(2) and then it updates the data(which was read) into database(1)
    I am also using EJB 3.0 version ( transaction-type - Container and Bean. Session-type - Stateless )
    Note the changes
    Previous Datasources details
    X datasource points to a my db - Non XA driver with one phase commit
    Y datasource points to a other db - Non XA driver with one phase commit
    Issue :
    javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
    [Wed Apr 10 08:40:03.069,<gzd4qc>] DEBUG (WorkRequestServiceImpl:sentEmailNotification) - Remote Exception occurred : javax.transaction.TransactionRolledbackException: BEA1-0020971AAD25AA29B1E3: javax.transaction.xa.XAException: JDBC driver does not support XA, hence cannot be a participant in two-phase commit. To force this participation, set the GlobalTransactionsProtocol attribute to LoggingLastResource (recommended) or EmulateTwoPhaseCommit for the Data Source = ABATDataSource
    Changed Datasources details
    X datasource points to a my db - Non XA driver with LLR
    Y datasource points to a other db - Non XA driver with one phase commit
    Working
    Can you please provide ur advise . thanks
    Thanks and Regards
    K.Vickram

  • Re: Portege M800: WebCam driver doesn't support internal microphone on 64bit OS

    Hi All!
    I have the problem that the internal microphone of the webcam (Chicony) is not working in 64 bit systems (Vista or Windows7).
    Has someone a fix for that?
    Best regards,
    Sven

    I had what sounds like exactly the same problem and seem to have solved it. You may have tried this already but here's how I got my internal mic working for my Portege M800 on a 64bit OS:
    -I went to (http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU)
    -I downloaded the latest audio/sound driver and installed it.
    -Then I went back to (http://eu.computers.toshiba-europe.com/innovation/download_drivers_bios.jsp?service=EU)
    -I then downloaded the latest webcam driver and installed it.
    - I restarted my computer and it worked perfectly. Upon opening Skype, the program automatically noticed a "new" microphone.
    Hopefully this is of some help to you.
    Good luck with it.

  • JDBC driver does not support XA - Exception

    JDBC driver does not support XA
    cannot participate in a two-phase commit
    To Force participation set EnableTwoPhaseCommit property on the corresponding JDBCTxDataSource property to true
    1) What is a JDBCTxDataSource - what does the TX mean?
    2) I have two data sources and according to BEA Weblogic docs, setting the property on both won't solve the problem. I tried.
    3) When I try to change the data pools to use XA drivers, I get the following error on server startup:
    java.sql.SQLException: Pool connect failed: java.lang.Exception: WebLogic Pool Driver doesn't support XA driver, Please change your config file to use a Non-XA driver

    JDBC driver does not support XA
    cannot participate in a two-phase commit
    To Force participation set EnableTwoPhaseCommit
    property on the corresponding JDBCTxDataSource
    property to true
    So use an XA driver.
    TX usually means "transaction".
    1) What is a JDBCTxDataSource - what does the TX mean?
    2) I have two data sources and according to BEA
    Weblogic docs, setting the property on both won't
    solve the problem. I tried.Right - you need XA drivers and JTA for both.
    3) When I try to change the data pools to use XA
    drivers, I get the following error on server
    startup:
    java.sql.SQLException: Pool connect failed:
    java.lang.Exception: WebLogic Pool Driver doesn't
    support XA driver, Please change your config file to
    use a Non-XA driverCreate new pools using the XA drivers. Don't reuse the old ones.
    Which version of WebLogic? I've made XA work for both 8.1 and 9.1.
    %

  • WD external hard drive doesn't appear on my Desktop or in Finder

    Hi, 
    I have a Western Digital hard drive connected to my iMac (Intel).  When I first intstalled it, it worked fine.  Then it began to intermittently exit my desktop, generating the message This Device Was Not Properly Disconnected.  If I restarted my computer it would usually return.  However now I can't get it to appear on my Desktop at all. 
    I ran a WD Smartware check of the hard drive which indicated that it is fine.  It powers on, the small white light is on, and I can hear and see that it is on.  I also tried different data and power cables and ran Disk Utility, which said the WD drive was fine.  The hard drive is connected directly to the computer, and to the wall socket, no buses, etc.  I tried to download some pictures from my camera and got the error message Camera Window Does Not Recognize Hard Drive.  Finally I tried connecting it to my laptop.  The hard drive appears perfectly on the laptop and all my info, photos, backups etc, are there.
    According to the WD website, if these are the results of the various trials, the problem is with a driver within my Mac OS.  The WD drive doesn't have a driver of its own, it uses one that is built into the Mac OS, which WD says must have become corrupted. 
    I have no idea how to correct this!  Does anyone have an idea??  WD says they don't know, only Apple will know.
    I have two other older WD hard drives connected to my Mac as well and they work fine.  They are different models though. 
    Thanks for any help!

    Well now the two other WD hard drives are beginning to act the same way...

  • I have a G4 Quicksilver running 10.5.8. Because the oS is on a small hard drive I coied the folders from that HD to a much larger drive via an external  USB drive enclosure. I then installed the larger drive as an internal in the G4, but it does not show

    I have a G4 Quicksilver running 10.5.8. The OS is on a small HD  with no room for adding any info or applications, so I have copied the OS to a much larger HD in an external USB enclosure. I dragged each folder from the small drive to the larger drive. I can access the applications when the large drive is set as an external drive, but when I installed it internally it would not show up on the Start Up Disc utility and I can not boot from it. Did I do something wrong copying the OS? Can anyone tell me how to boot from the larger drive? Thanks

    If your machine doesn't support large drives natively (Quicksilver 2002 and later) then doing as you are doing may lead to disaster.
    If files are placed on a large drive and those files extend beyond the 128 GB limit of the controller, the first time the drive (internally) accesses data beyond the 128 GB region, the machine will crash and data loss a likely result.

  • Solaris 8 looks doesn't  support APIC for multi-PCI BUS system

    I am Phoenxi BIOS Egnieer
    We are testing with Brkdale System(ICH2)
    This chipset use PCI0/PCI1/PCI2 for PCI device
    With APIC enabled Solaris OS doesn't get the _PRT method on ASL PCI1/2
    So PCI slot Network Card Doesn't work on APIC envinment
    How Solaris supprt ACPI/APIC envernment
    Solaris copy and modify the intel ACPI CA ?
    Doesn any issue internally?
    Thnanks

    As far as i know the wl (proprietary broadcom driver) doesn't support monitor/injection.
    But the Mac80211 alternatives might. If they support the wifi chip in your MacBook.
    From experience with a friends MBP it didn't yet support his broadcom so had to use WL to get basic network connectivity and used an Dual-band(2.4Ghz/5Ghz) 2x2 11n/ac USB dongle for his monitor/injection needs.

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

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

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

  • Wlan doesn't support monitor mode

    Hi everybody, 
    I'm new in the Arch's world and today I installed Arch on my MacBookAir 4.2 and I installed wifite but when I try to change the wl in "monitor mode" the wl crashes and I must restart the wl.
    This is a my pc info with this commands:
    uname -a
    lspci -nnk | grep -iA2 net
    lsusb
    iwconfig
    rfkill list all
    lsmod
    Linux Arch-MacOSX 4.0.4-1-ARCH #1 SMP PREEMPT Mon May 18 06:43:19 CEST 2015 x86_64 GNU/Linux
    02:00.0 Network controller [0280]: Broadcom Corporation BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
    Subsystem: Apple Inc. AirPort Extreme [106b:00e9]
    Kernel driver in use: wl
    Bus 002 Device 003: ID 05ac:8404 Apple, Inc. Internal Memory Card Reader
    Bus 002 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
    Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 003: ID 05ac:850a Apple, Inc. FaceTime Camera
    Bus 001 Device 005: ID 05ac:024d Apple, Inc. Internal Keyboard/Trackpad (MacBook Air) (ISO)
    Bus 001 Device 008: ID 05ac:821f Apple, Inc. Built-in Bluetooth 2.0+EDR HCI
    Bus 001 Device 004: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth)
    Bus 001 Device 002: ID 0424:2513 Standard Microsystems Corp. 2.0 Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    wlp2s0 IEEE 802.11abg ESSID:"cvsg1"
    Mode:Managed Frequency:2.452 GHz Access Point: 64:66:B3:2D:FF:BD
    Bit Rate=52 Mb/s Tx-Power=200 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=33/70 Signal level=-77 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0
    Module Size Used by
    nls_utf8 16384 0
    ntfs 204800 0
    ppp_deflate 16384 0
    bsd_comp 16384 0
    ppp_async 20480 1
    crc_ccitt 16384 1 ppp_async
    l2tp_ppp 24576 0
    l2tp_netlink 20480 1 l2tp_ppp
    l2tp_core 32768 2 l2tp_ppp,l2tp_netlink
    ip6_udp_tunnel 16384 1 l2tp_core
    udp_tunnel 16384 1 l2tp_core
    pppoe 20480 0
    pppox 16384 2 l2tp_ppp,pppoe
    ppp_generic 32768 10 l2tp_ppp,pppoe,pppox,bsd_comp,ppp_async,ppp_deflate
    slhc 20480 1 ppp_generic
    btusb 40960 0
    bluetooth 442368 2 btusb
    hid_generic 16384 0
    wl 6303744 0
    coretemp 16384 0
    intel_rapl 20480 0
    hid_apple 16384 0
    iosf_mbi 16384 1 intel_rapl
    x86_pkg_temp_thermal 16384 0
    intel_powerclamp 20480 0
    joydev 20480 0
    kvm_intel 155648 0
    mousedev 20480 0
    kvm 446464 1 kvm_intel
    crct10dif_pclmul 16384 0
    nls_iso8859_1 16384 1
    crc32_pclmul 16384 0
    nls_cp437 20480 1
    crc32c_intel 24576 0
    i915 1024000 8
    vfat 24576 1
    fat 65536 1 vfat
    ghash_clmulni_intel 16384 0
    uvcvideo 86016 0
    usbhid 49152 0
    snd_hda_codec_hdmi 53248 1
    hid 110592 3 hid_generic,usbhid,hid_apple
    bcm5974 20480 0
    applesmc 20480 0
    mac_hid 16384 0
    iTCO_wdt 16384 0
    evdev 24576 13
    snd_hda_codec_cirrus 20480 1
    iTCO_vendor_support 16384 1 iTCO_wdt
    videobuf2_vmalloc 16384 1 uvcvideo
    led_class 16384 1 applesmc
    aesni_intel 172032 0
    snd_hda_codec_generic 65536 1 snd_hda_codec_cirrus
    drm_kms_helper 102400 1 i915
    input_polldev 16384 1 applesmc
    cfg80211 483328 1 wl
    aes_x86_64 20480 1 aesni_intel
    hwmon 16384 2 applesmc,coretemp
    videobuf2_memops 16384 1 videobuf2_vmalloc
    lrw 16384 1 aesni_intel
    gf128mul 16384 1 lrw
    glue_helper 16384 1 aesni_intel
    ablk_helper 16384 1 aesni_intel
    cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper
    videobuf2_core 40960 1 uvcvideo
    pcspkr 16384 0
    snd_hda_intel 28672 3
    v4l2_common 16384 1 videobuf2_core
    i2c_i801 20480 0
    snd_hda_controller 28672 1 snd_hda_intel
    snd_hda_codec 114688 5 snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel,snd_hda_controller,snd_hda_codec_cirrus
    videodev 135168 3 uvcvideo,v4l2_common,videobuf2_core
    uas 24576 0
    media 20480 2 uvcvideo,videodev
    sbs 16384 0
    snd_hwdep 16384 1 snd_hda_codec
    usb_storage 61440 1 uas
    rfkill 24576 3 cfg80211,bluetooth
    drm 282624 10 i915,drm_kms_helper
    sbshc 16384 1 sbs
    apple_bl 16384 0
    ac 16384 0
    snd_pcm 90112 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_controller
    video 24576 1 i915
    battery 20480 0
    snd_timer 28672 1 snd_pcm
    mei_me 20480 0
    button 16384 1 i915
    shpchp 36864 0
    mei 77824 1 mei_me
    intel_gtt 20480 1 i915
    snd 69632 14 snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_hda_codec_cirrus
    i2c_algo_bit 16384 1 i915
    lpc_ich 24576 0
    i2c_core 53248 7 drm,i915,i2c_i801,drm_kms_helper,i2c_algo_bit,v4l2_common,videodev
    soundcore 16384 2 snd,snd_hda_codec
    processor 28672 0
    sch_fq_codel 20480 3
    ext4 512000 3
    crc16 16384 2 ext4,bluetooth
    mbcache 20480 1 ext4
    jbd2 90112 1 ext4
    sd_mod 36864 5
    ahci 36864 4
    libahci 28672 1 ahci
    libata 184320 2 ahci,libahci
    scsi_mod 147456 4 uas,usb_storage,libata,sd_mod
    uhci_hcd 45056 0
    ehci_pci 16384 0
    ehci_hcd 73728 1 ehci_pci
    usbcore 200704 9 uas,btusb,uhci_hcd,uvcvideo,usb_storage,ehci_hcd,ehci_pci,usbhid,bcm5974
    usb_common 16384 1 usbcore
    0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
    1: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
    How I can use the monitor mode for use wifite?
    Thanks for any answer!!!
    Last edited by skioda86 (2015-05-22 10:00:45)

    As far as i know the wl (proprietary broadcom driver) doesn't support monitor/injection.
    But the Mac80211 alternatives might. If they support the wifi chip in your MacBook.
    From experience with a friends MBP it didn't yet support his broadcom so had to use WL to get basic network connectivity and used an Dual-band(2.4Ghz/5Ghz) 2x2 11n/ac USB dongle for his monitor/injection needs.

  • I have a model 1,1 Mac Book in the black case.  How can I transfer about 30 GB of stuff to a MacBook Pro running Yosemite?  Can't do a Thunderbolt transfer.  The Seagate backup drive I bought doesn't support 10.5.8.  Thank you.

    How do I transfer 30 GB of stuff, mostly text documents, bookmarks and a few hundred photos from a MacBook model 1,1 in the black case, purchased in (2007?) running Leopard 10.5.8 with a 667 bus, 2 GB, 256 GB to a MBP 13" Retina running Yosemite 10.10.1?  Using Migrate is out.  Discovered after I bought it that the Seagate Plus Backup for Mac does not work with 10.5.8.  OnetoOne recommends backing up my data before I do that, which seems like a good idea.  Have a 801.11 n Time Capsule that also isn't working so that is not presently an option.  Thank you.

    The Seagate backup drive I bought doesn't support 10.5.8
    The only reason I can see for that is it's formatted NTFS, which would likely be Read Only in 10.5.x, if you can reformat it MacOS extended, which would erase everything on it now, then that should work for your purposes.

Maybe you are looking for

  • Problem with Crystal reports for Eclipse and Postgres-databases

    Hi, Is there a known problem when using a PostgreSQL-database to create a report with Crystal reports Plugin? When I drag a table, then occurs a error-windows, that the object can't  created. I have found a workaround for solving the problem. After n

  • Unable to download itunes 10.5 for windows 7. multiple errors

    I get multiple errors while downloading itunes 10.5 during set up: 1. apple mobile device failed to start. Verify you have sufficient privileges to start system services. 2. An error occured during installation of assembly "Microsoft.VC80.CRT error w

  • Same batch selected in two different Deliveries

    Dear all I have a problem in Outbound delivery creation.. I have created 2 different outbound deliveries. While creating & Batch determination of first outbound delivery  Batch number X with qty 100 is selected. Then it is saved with out PGI. when i

  • Baffling - Safari Rolling Up My External Drives While Loading Page

    Does anyone have any idea why when I try to open up a web page with Safari, before it will load Safari seems to be rolling up my external hard drives from their sleep mode and won't load the page until they are active and spinning? This is quite baff

  • What are the tarrifs when using a BT Broadband Hub...

    Hi. I'm trying to find out exactly how much calls will cost if I get BT BB and make calls using the hub phone. The info on the website, here, is very basic: http://www.productsandservices.bt.com/consumerProducts/displayTopic.do?topicId=27273&s_cid=co