BC4J with non-SQL datasource

Hi
Is it possible to use BC4J with non-SQL, non-relational datasources? For example, we are exploring the possibility of using a file-based XML datastore (NOT the XDB) as the back-end for some ADF screens.
Thanks,
Sean

BC4J is designed for SQL databases.
http://www.oracle.com/technology/products/jdev/collateral/tutorials/903/j2ee_bc4j/prnt/j2ee_bc4j.html#bc4j-faq

Similar Messages

I met an error when connect to oracle db with tag sql:DataSource

When I use the jstl tag <sql:DataSource> connect to oracle db ,I met an error as :
javax.servlet.jsp.JspException: Unable to get connection, DataSource invalid: "java.sql.SQLException: No suitable driver"
My Source code as follow:
<sql:setDataSource var="dataSource" driver="oracle.jdbc.driver.OracleDriver" url="jdbc:oracle:thin:@192.168.1.220:1521:gzserver" scope="request" user="lnmisscall" password="lnmcadmin"/>
<sql:query dataSource="{$dataSource}" var="data">
I am sure the connection information are right (I can connecte to the db with them in jsp & java bean) , and I have put the oracle's jdbc driver under the tomcat/common/lib folder,
Please help me to fit it ,thanks.

Sabrina,
Its all dependent on the application and whether its 32-bit or 64-bit. For example, SSRS reporting services 2008 R2 is a 64-bit application, so load the 64-bit oracle client there for report execution. Report builder is a 32-bit client application,
assuming its running on a different machine, so load the 32-bit oracle client on any user computers using RB 3.0 and working with Oracle. If the computers are one in the same, then do as the post above says, load both...

Create XA MultiDataSource with Non-XA DataSource(support global txn)

I have two datasources DataSource1 and DataSource2. Since my driver doesnt support XA, I am Emulating XA for these two data sources.
Now, I want to create a Multi Data Source and add these two data sources. Is there anyway I can Emulate XA for this Multi Data Source?

Thanks for your quick reply Joe.
The target for this multipool is single managed server(not a cluster). wee have a lot of resources like MQ, AQ,ORacle etc in the transaction. This datasource is for Tandem jdbc. We dont have XA jdbc driver for this and thats the reason we are emulating the XA.
We were using weblogic 9.2 and there we were able to setup XA Multipool with non xa pools (with XA emulated) without any issues. and now we are migrating to weblogic 9.2
This is what i did in weblogic 9.2 console.
1. Created DataSource1 and DataSource2. Both have GloablTrasactionSupport enabled with Emulate XA
2. Created a MultiDataSource. During creation, I selected non-XA driver and from the data source page, I added DataSource1 and DataSource2. (If I select XA driver, then the datasource selection page wont show DataSource1 and DataSource2 since it is non-XA)
The MultiDataSource is deployed without any issues. but when my application try to get a connection from MultiDataSource, it is throwing below exception.
Sep 8, 2008 1:09:03 AM CDT> <Error> <EJB> <BEA-010080> <An error occurred while attempting to process a message inside a message-driven bean: weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl
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 = Multi_DataSource_XA
Exception is : weblogic.transaction.RollbackException: Could not prepare resource 'weblogic.jdbc.wrapper.JTSXAResourceImpl
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 = Multi_DataSource_XA
     at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1782)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:331)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:227)
     at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:463)
     at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:335)
     at weblogic.ejb.container.internal.JMSMessagePoller.processOneMessage(JMSMessagePoller.java:320)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollContinuously(JMSMessagePoller.java:394)
     at weblogic.ejb.container.internal.JMSMessagePoller.pollForParent(JMSMessagePoller.java:517)
     at weblogic.ejb.container.internal.JMSMessagePoller.run(JMSMessagePoller.java:533)
     at java.lang.Thread.run()V(Unknown Source)
>
Jiji

JSP using BC4J with MS SQL Server

I use JDevelop to develop my JSP apps with BC4J. When I Run a JSP app, the error happened.
The error message is [Microsoft][SQLServer 2000 Driver for JDBC]Can't start a cloned connection while in manual transaction mode.
Who can tell me what the error message means? Or What error might happened to my code?
What parameter I should setup? Or What code I should change?

There is a "how to" that addresses this issue
with SQL*Server:
http://otn.oracle.com/products/jdev/howtos/bc4j/bc_psqlserverwalkthrough.html
You need to qualify your jdbc URL: (this is from the howto)
On the Connection page, enter the Java class name and the URL.
Java class name: com.microsoft.jdbc.sqlserver.SQLServerDriver
URL: jdbc:microsoft:sqlserver://<db-host>:1433;SelectMethod=cursor
Note: There's a semicolon before SelectMethod=cursor.
Note on Select Method: From the MS SQL Server documentation: SelectMethod={cursor | direct} determines whether or not Microsoft SQL Server "server cursors" are used for SQL queries. Setting SelectMethod to direct allows SQL statements to be executed without incurring server-side overhead for managing a database cursor over the SQL statement. Direct mode is the most efficient for executing Select statements; however, applications are limited to a single active statement while executing inside a transaction. If multiple result sets are required from a single query execution, then the application must set SelectMethod to direct.
regards, Karl

EJB calling Spring Bean with non XA Datasources causing Rollback Exception

We have an EJB CMT with Required calling a spring bean (@Transactional Propagation.NOT_SUPPORTED). This is causing an Rollback Exception saying 2 phase commit must be enabled. The EJB has to write to datasource 1, but the Spring Bean is ready only on Data Source 2. The Data Sources are set to use Non XA Driver with Support Global Transaction enabled for One phase commit. Any help is appreciated.

We have an EJB CMT with Required calling a spring bean (@Transactional Propagation.NOT_SUPPORTED). This is causing an Rollback Exception saying 2 phase commit must be enabled. The EJB has to write to datasource 1, but the Spring Bean is ready only on Data Source 2. The Data Sources are set to use Non XA Driver with Support Global Transaction enabled for One phase commit. Any help is appreciated.

Setting v$session.program with javax.sql.DataSource unsing JNDI

I am trying to set v$session's program column while connecting to database.
It works like charm when i use :
java.util.Properties params = new java.util.Properties();
params.put("v$session.program", "MyApp");
DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
conn = DriverManager.getConnection("jdbc:oracle:thin:user/[email protected]:1521:myDB",params);
It just doesn't SET anything when i use, JNDI :
java.util.Properties params = new java.util.Properties();
params.put("v$session.program", "MyApp");
Context ctx = new InitialContext(params);
DataSource ds = (DataSource)ctx.lookup(datasourceName);
conn = ds.getConnection(userName,password);
Just couldn't figure out why its not setting in the 2nd Case. Any ideas ??

Valid..
But then, even if i set v$session.program in my JDev environment or even on app server's connection pool Its NOt getting set.
Am i doing something worng.
Btw, i am using jdbc thin 10.1.0.3 driver. I read somewhere that this was a bug and its fixed with jdbc thin driver 10.2.x versions.
Has anyone tried on 10.2.x versions ?

Concept: How can I handle a hole in a non-sap datasource?

Hello,
I want to discuss here a problem with non-sap datasource:
We load data from oracle db with db-connect technique. Each record we load has an idate(record is created) and a udate(record is changed). Based on the udate we create a kind of delta load:
The udate is selection criteria of the Infopackage(full upload)
In the start routine of the transferrule we detect the oldest udate and store it to the tvarc table. This UDATE is the low selection criteria for udate of the next load. So we reload only the records, which are change after the last load.
The data are transferred to ODS (overwrite) and so on..
That works perfect!
But now we find out, that in this non-sap datasource its possible to delete records directly. In SAP we have usually the procedure that a reversal document is created to delete a record(for example FI documents). In fact this non-sap datasource creates a hole in the database. A record is deleted > no udate change -> no change in BW. That means the record is still in BW!
Do you had a similar problem? Or do you have an idea how we could fix this problem.
I can not load all data every day by full upload that needs to much time more than 2 million data from five different datasources.
Thank you for your attention
Ralf

Hello,
To close my post, here is my solution:
- ODS A is filled by delta using the UDATE field.
- ODS B is filled by full upload. It contents only the key fields of ODS A (load needs
only 20 minutes)
- ODS C is filled by ODS A(only key fields) per full upload. In the startroutine of the
update rule is a check: Delete all data, which are in ODS B.
Result is: ODS C contents only the data, which have to be deleted in ODS A.
- Full upload ODS C to ODS A. Set in the start routine recordmode to 'R'.
Result is: these records are delete from the ODS A and change log of ODS A is
updated.
Before the next load the content of ODS B and C is deleted.
(cool picture:)
..........CUBE X
..............|
.(delta)....|
..............|........ODS C(diff. A - B)
..............|........|....|
..............|..(R).|....|.\ (check)
..............|........|....|..\
............ODS A....ODS B(keys)
.(delta)...|................| (full)
..........non sap systems
It's followed the principle of Sudhi's idea. But I did it not with PSA, because I have five different DataSources, so I need five calls to identify the records, which have to be deleted and five calls to edit the PSA ....
In this way I load everything in ODS and do the procedure only once time.
All the best Ralf

Can BC4J be used with Hypersonic SQL?

Has anyone been sucessful using BC4J applications with Hypersonic SQL? If so, which versions of each.
Thanks in anticition,
Paul Bandler

No. Use SQLXML instead on a SQL Server.

Problem with Oracle XA Datasource

Hi All,
I have created a JDBC XA Resource pool for Oracle DB and when i try to run my application, i am getting the below exception. But the same appln runs in NON-XA Datasource.
<jdbc-connection-pool connection-validation-method="auto-commit" datasource-classname="oracle.jdbc.xa.client.OracleXADataSource" fail-all-connections="false" idle-timeout-in-seconds="300" is-connection-validation-required="false" is-isolation-level-guaranteed="false" max-pool-size="32" max-wait-time-in-millis="60000" name="ORA_XAPool" pool-resize-quantity="2" res-type="javax.sql.XADataSource" steady-pool-size="8">
<property name="URL" value="jdbc:oracle:thin:@192.54.45.245:1521:orcl"/>
<property name="Password" value="TestDB"/>
<property name="User" value="TestDB"/>
<property name="DataSourceName" value="OracleXADataSource"/>
</jdbc-connection-pool>
Any idea.... Please help.
Version: Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs)
Exception Trace:
[#|2004-12-08T01:39:12.140-0800|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=12;|RAR5027:Unexpected exception in resource pooling
java.lang.NullPointerException
     at com.sun.gjc.spi.XAResourceImpl.start(XAResourceImpl.java:162)
     at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:238)
     at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:173)
     at com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:360)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:303)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:115)
     at com.sun.enterprise.resource.SystemResourceManagerImpl.enlistResource(SystemResourceManagerImpl.java:69)
     at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:140)
     at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:205)
     at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:94)
     at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:68)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at
#|2004-12-08T01:39:12.296-0800|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb.entity.finder|_ThreadID=12;|JDO74010: Bean 'ItemEnt' method ejbFindAll: problems running JDOQL query.
com.sun.jdo.api.persistence.support.JDOFatalInternalException: JDO76519: Failed to identify vendor type for the data store.
NestedException: java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:864)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at
thanks,
Bobby

Hi Aditya,
Thanks for looking at my issue.
1. Do you always get this NPE or is it an intermittent issue?
Always i am getting this error, while accesing my sample CMP application.
2. Did you run the code snippet that I posted yesterday with the jdk bundled with the appserver or some other jdk?
I ran the code snippet with the jdk bundled with appserver.
3. Have you run into any more of these NPE issues with other applications and other XA pools?
When i executed another sample demo CMP application with oracle XA Pool, it works fine.
4. Are there any other related expceptions in the log before the NPE? Would you please start with an empty server.log, run this application and post the whole log?
StackTrace:
Starting Sun Java System Application Server Platform Edition 8.0.0_01 (build b08-fcs) ...
[#|2004-12-20T16:46:48.921+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.4.2_04] from [Sun Microsystems Inc.]|#]
[#|2004-12-20T16:46:50.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0020:Following is the information about the JMX MBeanServer used:|#]
[#|2004-12-20T16:46:50.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
[#|2004-12-20T16:46:54.062+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|Creating virtual server server|#]
[#|2004-12-20T16:46:54.062+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|S1AS AVK Instrumentation disabled|#]
[#|2004-12-20T16:46:54.078+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
[#|2004-12-20T16:46:56.890+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [100]|#]
[#|2004-12-20T16:46:58.437+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Satisfying Optional Packages dependencies...|#]
[#|2004-12-20T16:47:00.593+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7008 : Initialized monitoring registry and listeners|#]
[#|2004-12-20T16:47:01.390+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5100:Loading system apps|#]
[#|2004-12-20T16:47:02.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
[#|2004-12-20T16:47:03.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
[#|2004-12-20T16:47:03.234+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
[#|2004-12-20T16:47:03.500+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [Tester:Tester.war] in virtual server [server] at [Tester]|#]
[#|2004-12-20T16:47:04.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [cmpcustomer] loaded successfully!|#]
[#|2004-12-20T16:47:04.343+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [cmpcustomer:cmpcustomer.war] in virtual server [server] at [customer]|#]
[#|2004-12-20T16:47:04.375+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Tomcat.|#]
[#|2004-12-20T16:47:04.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [server] at [web1]|#]
[#|2004-12-20T16:47:04.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [server] at [asadmin]|#]
[#|2004-12-20T16:47:04.562+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
[#|2004-12-20T16:47:04.562+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [server] at [com_sun_web_ui]|#]
[#|2004-12-20T16:47:04.578+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Starting tomcat server|#]
[#|2004-12-20T16:47:04.578+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.Embedded|_ThreadID=10;|Catalina naming disabled|#]
[#|2004-12-20T16:47:04.718+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server-PE-8.0|#]
[#|2004-12-20T16:47:10.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.catalina.startup.ContextConfig|_ThreadID=10;|Missing application web.xml, using defaults only StandardEngine[server].StandardHost[server].StandardContext[]|#]
[#|2004-12-20T16:47:12.203+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 8080|#]
[#|2004-12-20T16:47:12.234+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 8080|#]
[#|2004-12-20T16:47:12.375+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 1043|#]
[#|2004-12-20T16:47:12.375+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 1043|#]
[#|2004-12-20T16:47:12.421+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Initializing Coyote HTTP/1.1 on port 4848|#]
[#|2004-12-20T16:47:12.421+0530|INFO|sun-appserver-pe8.0.0_01|org.apache.coyote.http11.Http11Protocol|_ThreadID=10;|Starting Coyote HTTP/1.1 on port 4848|#]
[#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [d:\servers\Sun\AppServer\imq\bin].|#]
[#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|[AutoDeploy] Enabling AutoDeployment service at :1103541432609|#]
[#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5053: Application onReady complete.|#]
[#|2004-12-20T16:47:12.609+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]
[#|2004-12-20T16:47:33.734+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=11;|WebModule[/asadmin]WARNING: No 'dtdURLBase' init parameter defined in Servlet config!|#]
[#|2004-12-20T16:48:11.453+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5109: EJBC - START of EJBC for [Sample_CMP]|#]
[#|2004-12-20T16:48:27.953+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Processing beans ...|#]
[#|2004-12-20T16:48:28.281+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Compiling RMI-IIOP code ...|#]
[#|2004-12-20T16:48:46.671+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|DPL5110: EJBC - END of EJBC for [Sample_CMP]|#]
[#|2004-12-20T16:48:48.109+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|Total Deployment Time: 41359 msec, Total EJB Compiler Module Time: 35218 msec, Portion spent EJB Compiling: 85%
Breakdown of EJBC Module Time: Total Time for EJBC: 35218 msec, CMP Generation: 5047 msec (14%), Java Compilation: 11344 msec (32%), RMI Compilation: 18375 msec (52%), JAX-RPC Generation: 47 msec (0%),
|#]
[#|2004-12-20T16:48:48.125+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.deployment|_ThreadID=12;|deployed with moduleid = Sample_CMP|#]
[#|2004-12-20T16:48:48.531+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy Sample_CMP]|#]
[#|2004-12-20T16:48:54.515+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.core.classloading|_ThreadID=12;|LDR5010: All ejb(s) of [Sample_CMP] loaded successfully!|#]
[#|2004-12-20T16:48:54.546+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=12;|WEB0100: Loading web module [Sample_CMP:employee.war] in virtual server [server] at [Module]|#]
[#|2004-12-20T16:48:56.000+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.web|_ThreadID=12;|WEB0100: Loading web module [Sample_CMP:web.war] in virtual server [server] at [TestServer]|#]
[#|2004-12-20T16:48:57.187+0530|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=12;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
[#|2004-12-20T16:49:43.890+0530|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5027:Unexpected exception in resource pooling
java.lang.NullPointerException
     at com.sun.gjc.spi.XAResourceImpl.start(XAResourceImpl.java:162)
     at com.sun.jts.jta.TransactionState.startAssociation(TransactionState.java:238)
     at com.sun.jts.jta.TransactionImpl.enlistResource(TransactionImpl.java:173)
     at com.sun.enterprise.distributedtx.J2EETransaction.enlistResource(J2EETransaction.java:360)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.enlistResource(J2EETransactionManagerImpl.java:303)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.enlistResource(J2EETransactionManagerOpt.java:115)
     at com.sun.enterprise.resource.SystemResourceManagerImpl.enlistResource(SystemResourceManagerImpl.java:69)
     at com.sun.enterprise.resource.PoolManagerImpl.getResource(PoolManagerImpl.java:140)
     at com.sun.enterprise.connectors.ConnectionManagerImpl.internalGetConnection(ConnectionManagerImpl.java:205)
     at com.sun.enterprise.connectors.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:94)
     at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:68)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
     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 com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
     at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
     at $Proxy108.findAll(Unknown Source)
     at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
     at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
     at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     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 org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
|#]
[#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5117 : Failed to obtain/create connection. Reason : java.lang.NullPointerException|#]
[#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.resourceadapter|_ThreadID=13;|RAR5114 : Error allocating connection : [Error in allocating a connection. Cause: java.lang.NullPointerException]|#]
[#|2004-12-20T16:49:44.000+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jdo.persistencemanager|_ThreadID=13;|JDO76520: Errors while obtaining information about the database. Got the following exception:
java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
     at com.sun.gjc.spi.DataSource.getConnection(DataSource.java:72)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.TransactionHelperImpl.getConnection(TransactionHelperImpl.java:181)
     at com.sun.jdo.spi.persistence.support.sqlstore.ejb.EJBHelper.getConnection(EJBHelper.java:166)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getConnection(SQLPersistenceManagerFactory.java:886)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:851)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
     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 com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
     at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
     at $Proxy108.findAll(Unknown Source)
     at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
     at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
     at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     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 org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.web.VirtualServerValve.invoke(VirtualServerValve.java:209)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:114)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at com.sun.enterprise.web.VirtualServerMappingValve.invoke(VirtualServerMappingValve.java:166)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:936)
     at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:165)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:683)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:604)
     at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:542)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:647)
     at java.lang.Thread.run(Thread.java:534)
|#]
[#|2004-12-20T16:49:44.093+0530|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.container.ejb.entity.finder|_ThreadID=13;|JDO74010: Bean 'ItemEnt' method ejbFindAll: problems running JDOQL query.
com.sun.jdo.api.persistence.support.JDOFatalInternalException: JDO76519: Failed to identify vendor type for the data store.
NestedException: java.sql.SQLException: Error in allocating a connection. Cause: java.lang.NullPointerException
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.initializeSQLStoreManager(SQLPersistenceManagerFactory.java:864)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getFromPool(SQLPersistenceManagerFactory.java:780)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.SQLPersistenceManagerFactory.getPersistenceManager(SQLPersistenceManagerFactory.java:667)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:849)
     at com.sun.jdo.spi.persistence.support.sqlstore.impl.PersistenceManagerFactoryImpl.getPersistenceManager(PersistenceManagerFactoryImpl.java:681)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.jdoGetPersistenceManager(ItemEJB1437418622_ConcreteImpl.java:594)
     at com.test.orders.itement.ejb.ItemEJB1437418622_ConcreteImpl.ejbFindAll(ItemEJB1437418622_ConcreteImpl.java:308)
     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 com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:146)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:930)
     at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:151)
     at com.sun.ejb.containers.EJBHomeInvocationHandler.invoke(EJBHomeInvocationHandler.java:179)
     at $Proxy108.findAll(Unknown Source)
     at com.test.orders.itement.ejb._ItemEntHome_Stub.findAll(Unknown Source)
     at com.test.webbeans.ProcessListBean.getItemsList(ProcessListBean.java:166)
     at org.apache.jsp.new_005forder_jsp._jspService(new_005forder_jsp.java:222)
     at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:102)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:282)
     at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:263)
     at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:210)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:861)
     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 org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:246)
     at java.security.AccessController.doPrivileged(Native Method)
     at javax.security.auth.Subject.doAsPrivileged(Subject.java:500)
     at org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:268)
     at org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:162)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:236)
     at org.apache.catalina.core.ApplicationFilterChain.access$000(ApplicationFilterChain.java:55)
     at org.apache.catalina.core.ApplicationFilterChain$1.run(ApplicationFilterChain.java:145)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:141)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:214)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:168)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:522)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:109)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:133)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:539)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.webservice.EjbWebServiceValve.invoke(EjbWebServiceValve.java:134)
     at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:107)
     at com.sun.enterprise.security.web.SingleSignOn.invoke(SingleSignOn.java:254)
     at org.apache.catalina.core.StandardValveContext.invokeNext(

Non-JTS datasource

Dumb questions. What is the exact definition of 'non-JTS datasource'? And what are the recommended usages of the datasource? The TopLink's doc has little information on it. It says "Use Non-JTS for Specify if the session requires a non-JTS connection. Note: Normally, use this option for an application server when using cache synchronization".
We use WAS connection pooling with Oracle databases. Some projects use 'XA datasource' while others use 'non-XA datasource'. In the sessions xml files, we all use <datasource> tag.
What are the differences b/w the 'non-JTS datasource' referenced in TopLink and the 'non-XA datasource' concept?
Also, I was told that all datasources in WAS 5.x are JTS datasources. I haven't found any information on it in the WAS documentations. Anyone has any more info on it?
Thanks a lot for your assistance.
Haiwei

Andrei,
I tried what you suggested, with WAS XA and non-XA datasource. Here is the code:             UserTransaction transaction = (UserTransaction) new InitialContext().lookup(USER_TRANSACTION);
            transaction.begin();
            connection = ((DataSource) new InitialContext().lookup(NON_XA_DATASOURCE)).getConnection("user04", "user04");
            statement = connection.createStatement();
            numberOfRows =
                statement.executeUpdate(
                    "UPDATE USER04.PERSON SET VERSION = VERSION +1 WHERE ID = '9999'");
            connection.commit();
            transaction.rollback();With XA datasource or non-XA datasource, I was both getting exception (see below), hence the version is not updated.
java.sql.SQLException: DSRA9350E: Operation Connection.commit is not allowed during a global transactionThis seems to suggest (or confirm) that the WAS datasources are JTS datasources.
Any comment?
Haiwie

Non-jdbc datasource for MapViewer

Is it possible to specify a non-jdbc datasource for Oracle MapViewer?
That is, if I want Mapviewer to access the database through my own data layer, or with an ORM, is it possible?
Thanks,
Rupesh

I copied jdbcdrv.zip intp C:\Program Files\Sybase\SQL
Anywhere 9\java
and using Java page in CF admin, added C:\Program
Files\Sybase\SQL Anywhere 9\java to classpath, restarted CF
Application server.
I then defined new datasources using existing ODBC dsns as
described in
http://www.ianywhere.com/developer/product_manuals/sqlanywhere/0902/en/html/dbpgen9/000001 52.htm
(doesn't seem kosher but that's what my model showed).
It's not exactly speedy but I've not gotten any errors yet
(maybe because it isn't speedy)
Anybody have any idea if there is another way that doesn't
use anODBC dsn ?

HOWTO: Use BC4J With or Without DB Triggers

This HowTo describes how to use BC4J, database sequences and triggers
and what are the ramifications.
INTRODUCTION
BC4J has the ability to work with database sequences in order to obtain a
unique value when inserting records. BC4J also has the ability to
work either with a 'before insert' trigger which automatically creates
a new unique value for the primary key or without a trigger. When not using
a database trigger, BC4J also has the ability to obtain the sequence value
and set the primary key value.
Before discussing the ramifications of using one approach or the other, let's
show examples of how to use both approaches:
BC4J & sequences WITH a database trigger
and
BC4J & sequences WITHOUT a database trigger
HOWTO DEMONSTRATION STEPS
To illustrate both scenarios a simple database setup script is provided which
creates two tables:
CUSTOMER_NT which DOES NOT have a before insert trigger and
CUSTOMER_WT which DOES have a trigger.
Database Install Script:
<code>
drop trigger customer_insert_trigger;
drop table customer_wt;
drop table customer_nt;
drop sequence customer_wt_seq;
drop sequence customer_nt_seq;
create sequence customer_wt_seq start with 1;
create sequence customer_nt_seq start with 101;
create table customer_wt(
id number,
name varchar2(30),
constraint
customer_wt_pk
primary key (id)
create table customer_nt(
id number,
name varchar2(30),
constraint
customer_nt_pk
primary key (id)
prompt Inserting data...
insert into customer_wt (id, name)
values (customer_wt_seq.nextval, 'Mickey');
insert into customer_wt (id, name)
values (customer_wt_seq.nextval, 'Goofy');
insert into customer_nt (id, name)
values (customer_nt_seq.nextval, 'Daffy');
insert into customer_nt (id, name)
values (customer_nt_seq.nextval, 'Porky');
commit
prompt Creating trigger
create trigger customer_insert_trigger
before insert on customer_wt for each row
begin
select customer_wt_seq.nextval into :new.id from dual ;
end;
</code>
The next step is to create the DEFAULT Entity Objects and View Objects using
the Business Components Wizard.
USING BC4J WITH A DATABASE TRIGGER
Let's modify the entity object CustomerWt so it can use the database trigger.
Edit the entity object CustomerWt by right-clicking in the navigator.
Click on the 'Attribute Settings' tab and edit the ID attribute.
- Uncheck 'Mandatory'checkbox. This allows you to insert without a value for the primary key
- Check 'Refresh after Insert'. This obtains the value from the database generated by the trigger.
- Check 'Updateable While New'. Id is only updateable when inserting.
Click finish to complete the wizard. Save all and recompile the project.
Now let's test our work.
In the navigator right-click the application module and select 'Test..'. This will launch
BC4J's built in tester. Connect to the application.
In the tester double-click the CustomerWtView view object to run a test edit form.
After the edit form renders, navigate through the existing records using the navigate
buttons on the edit form. Now let's insert a record to execute the trigger.
click on the '+' button to insert a record. Enter a value in the 'Name' field and commit the change.
Observe that a new value has automatically been inserted into the Id field.
That's it! You have successfully used BC4J and a database trigger.
Now let's try it without a trigger..
USING BC4J WITHOUT A DATABASE TRIGGER
Now edit the entity object CustomerNT so it doesn't need a database trigger.
Similar to before, edit the entity object CustomerNt by right-clicking in the navigator.
Click on the 'Attribute Settings' tab and edit the ID attribute.
- Uncheck 'Mandatory'checkbox.
- Check 'Updateable While New'.
An additional step is also required. The Create method will have to be modified to extract
the value of the sequence.
In the Edit EntityObject Wizard click the Java tab and select Create method and click Finish.
The create method is generated in your Java fil e. In the Workspace view of the Navigator,
expand the CustomerNt entity object in the navigator. Double-click
CustomerNtImpl.java to open it in the Source Editor. In the Structure pane, double-click
create(AttributeList). Modify the Create method so it looks like this:
<code>
public void create(AttributeList attributeList) {
super.create(attributeList);
SequenceImpl s = new SequenceImpl("customer_nt_seq", getDBTransaction());
Integer next = (Integer)s.getData();
setId(new Number(next.intValue())); }
</code>
Save and compile the project.
Now test the ViewObject CustomerNtView using the tester as before.
In the edit form of CustomerNTView click on the '+' to insert a record. Observe that
just as before a new value has automatically been inserted in the ID field!
TO USE A DB TRIGGER OR NOT TO USE A DB TRIGGER.
Using a Database trigger sometimes preferable if you have non BC4J applications
also sharing the database. In this case it is still safest to just let the database
update it's own primary keys.
If you don't have any other non-BC4J applications sharing the database, then not using
a database trigger is perfectly acceptable and can have slightly better performance.
The important thing to remember is that the option is yours to use either approach!
null

Thank you for the reply Jonathon. I am using a ViewObject which
consist of several tables. I haven't tried the DB trigger
approach but just using the BC4 approach in overriding the
create method.
Here is the parent class create as a part of the
FasNameImpl.java file which does the job correctly.
public void create(AttributeList attributeList) {
super.create(attributeList);
SequenceImpl l_seq = new SequenceImpl
("SEQ_CUSTOMER_ID",getDBTransaction());
Integer l_next = (Integer)l_seq.getData();
setCustomerId(new Number(l_next.intValue()));
This is when I triedpassing the value to the child table. But I
can't figure it out. I think the link is working fine if I had a
ViewLink deployed but it doesn't look like it's doing the job
for ViewObject.
I am trying to call the childclass.method
(FasCustomer.setCustomerId(l_next);
But I am getting error.
Thanks a lot for your suggestions,
Kamran
703 696 1121

Help with seting up a Data Sorce can't be created with non-existent Pool

I am wanting to use an Oracle 9i with WebLogic 7
I have the following in my config.xml:
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
Name="Thin.Pool" Password="{3DES}C3xDZIWIABA="
Properties="user=SYSTEM" TestTableName="OID"
URL="jdbc:oracle:thin:@localhost:1521:DB_SID"/>
<JDBCDataSource JNDIName="DB_DS" Name="DB_DS" PoolName="Thin.Pool"/>
The console seems happy, no error mesages but in the log I get:
####<Mar 31, 2003 6:33:45 PM MST> <Info> <HTTP> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <101047>
<[ServletContext(id=4110316,name=console,context-path=/console)]
FileServlet: Using standard I/O>
####<Mar 31, 2003 6:35:37 PM MST> <Info> <JDBC> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <001082> <Creating Data Source named DB_DS for pool
Thin.Pool>
####<Mar 31, 2003 6:35:37 PM MST> <Error> <JDBC> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(DB_DS) can't be created
with non-existent Pool (connection or multi) (Thin.Pool)
     at weblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:127)
     at weblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:260)
     at weblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:293)
     at weblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:375)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:154)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:732)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:714)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:417)
     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.invoke(RemoteMBeanServerImpl.java:952)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:578)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:419)
     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.invoke(RemoteMBeanServerImpl.java:952)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
     at $Proxy16.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.unprotectedUpdateDeployments(DynamicMBeanImpl.java:1784)
     at weblogic.management.internal.DynamicMBeanImpl.access$0(DynamicMBeanImpl.java:1737)
     at weblogic.management.internal.DynamicMBeanImpl$1.run(DynamicMBeanImpl.java:1715)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1711)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:1035)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:353)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1358)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1333)
     at weblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanServerImpl.java:898)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:324)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:193)
     at $Proxy13.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:145)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1058)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:401)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5445)
     at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:780)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3105)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2588)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Why does it say:
can't be created with non-existent Pool
Thanks,

Add "Targets" attribute to the connection pool. You may
get an idea how it looks like by searching config.xml
for "targets". If target servers are not set, the pool won't be
deployed and can not be used to a create datasource.
Regards,
Slava Imeshev
"BBaker" <[email protected]> wrote in message
news:[email protected]...
I am wanting to use an Oracle 9i with WebLogic 7
I have the following in my config.xml:
<JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
Name="Thin.Pool" Password="{3DES}C3xDZIWIABA="
Properties="user=SYSTEM" TestTableName="OID"
URL="jdbc:oracle:thin:@localhost:1521:DB_SID"/>
<JDBCDataSource JNDIName="DB_DS" Name="DB_DS" PoolName="Thin.Pool"/>
The console seems happy, no error mesages but in the log I get:
####<Mar 31, 2003 6:33:45 PM MST> <Info> <HTTP> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <101047>
<[ServletContext(id=4110316,name=console,context-path=/console)]
FileServlet: Using standard I/O>
####<Mar 31, 2003 6:35:37 PM MST> <Info> <JDBC> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <001082> <Creating Data Source named DB_DS for pool
Thin.Pool>
####<Mar 31, 2003 6:35:37 PM MST> <Error> <JDBC> <blue> <GameServe>
<ExecuteThread: '1' for queue: '__weblogic_admin_html_queue'> <kernel
identity> <> <001059> <Error during Data Source creation:
weblogic.common.ResourceException: DataSource(DB_DS) can't be created
with non-existent Pool (connection or multi) (Thin.Pool)
atweblogic.jdbc.common.internal.JdbcInfo.validateConnectionPool(JdbcInfo.java:
127)
atweblogic.jdbc.common.internal.JdbcInfo.startDataSource(JdbcInfo.java:260)
atweblogic.jdbc.common.internal.JDBCService.addDeploymentx(JDBCService.java:29
3)
atweblogic.jdbc.common.internal.JDBCService.addDeployment(JDBCService.java:270
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:375)
atweblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentT
arget.java:154)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl
.java:732)
atweblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:7
14)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:417)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerI
mpl.java:952)
atweblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(Confi
gurationMBeanImpl.java:578)
atweblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBea
nImpl.java:419)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
atcom.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
atweblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerI
mpl.java:952)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:470)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:198)
at $Proxy16.addDeployment(Unknown Source)
atweblogic.management.internal.DynamicMBeanImpl.unprotectedUpdateDeployments(D
ynamicMBeanImpl.java:1784)
atweblogic.management.internal.DynamicMBeanImpl.access$0(DynamicMBeanImpl.java
:1737)
atweblogic.management.internal.DynamicMBeanImpl$1.run(DynamicMBeanImpl.java:17
15)
atweblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:780)
atweblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBean
Impl.java:1711)
atweblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.
java:1035)
atweblogic.management.internal.ConfigurationMBeanImpl.setAttribute(Configurati
onMBeanImpl.java:353)
atcom.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:135
8)
atcom.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:133
3)
atweblogic.management.internal.RemoteMBeanServerImpl.setAttribute(RemoteMBeanS
erverImpl.java:898)
atweblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:324)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:193)
at $Proxy13.setTargets(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
atweblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanA
ttribute.java:92)
atweblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMB
eanAction.java:145)
atweblogic.management.console.actions.internal.ActionServlet.doAction(ActionSe
rvlet.java:171)
atweblogic.management.console.actions.internal.ActionServlet.doPost(ActionServ
let.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
atweblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(Servle
tStubImpl.java:1058)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:401)
atweblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
:306)
atweblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(W
ebAppServletContext.java:5445)
atweblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManage
r.java:780)
atweblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
ntext.java:3105)
atweblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
:2588)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
Why does it say:
can't be created with non-existent Pool
Thanks,

Problem using DG4ODBC with named SQL Server instance

I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
ORA-02063: preceding 2 lines from DEVMISC
odbc.ini
[GENERALI_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = CLTDMJCWBYZ.eu.scor.local
User                    = everest
Password                = everest
Database                = Everest_Generali
[DEVMISC_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = [USVCLTDEVSQL02\DEVMISC]
User                    = link_user
Password                = password1
Database                = DBA
initDG4ODBC2.ora
# HS init parameters
HS_FDS_CONNECT_INFO = DEVMISC_DSN
HS_FDS_TRACE_LEVEL = DEBUG
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
listener.ora
SID_LIST_LISTENER_GW =
   (SID_LIST =
      (SID_DESC =
       (SID_NAME=DG4ODBC)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
soft/sqlncli/lib)
      (PROGRAM=dg4odbc)
      (SID_DESC =
       (SID_NAME=DG4ODBC2)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
osoft/sqlncli/lib)
      (PROGRAM=dg4odbc)
LISTENER_GW =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
tnsnames.ora
DG4ODBC =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC))
      (HS=OK)
DG4ODBC2 =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC2))
      (HS=OK)
I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
who states that named instance connections are not supported using that driver.
- Klaus

Problems with non-ASCII characters on Linux Unit Test Import

I found a problem with non-ASCII characters in the Unit Test Import for Linux. This problem does not appear in the Unit Test Import for Windows.
I have attached a Unit Test export called PROC1.XML It tests a procedure that is included in another attachment called PROC1.txt. The unit test includes 2 implementations. Both implementations pass non-ASCII characters to the procedure and return them unchanged.
In Linux, the unit test import will change the non-ASCII characters in the XML file to xFFFD. If I copy/paste the the non-ASCII characters into the Unit Test after the import, they will be stored and executed correctly.
Amazon Ubuntu 3.13.0-45-generic / lubuntu-core
Oracle 11g Express Edition - AL32UTF8
SQL*Developer 4.0.3.16 Build MAIN-16.84
Java(TM) SE Runtime Environment (build 1.7.0_76-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.76-b04, mixed mode)
In Windows, the unit test will import the non-ASCII characters unchanged from the XML file.
Windows 7 Home Premium, Service Pack 1
Oracle 11g Express Edition - AL32UTF8
SQL*Developer 4.0.3.16 Build MAIN-16.84
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
If SQL*Developer is coded the same between Windows and Linux, The JVM must be causing the problem.

Set the System property "mail.mime.decodeparameters" to "true" to enable the RFC 2231 support.
See the javadocs for the javax.mail.internet package for the list of properties.
Yes, the FAQ entry should contain those details as well.

BC4J with non-SQL datasource

Similar Messages

Maybe you are looking for