Informix 10 & CFMX 6.1 & JDBC

[cfperson]

I'm getting following error on <cfapplication> tag in Application.cfm:

Reason of failure "java.sql.SQLException: [Macromedia][Informix JDBC
Driver]Exception generated during defered local transaction handling. See next
exception via SQLException.getNextException for details."

I'm using DataDirect 3.4 drivers for Informix. If I change JDBC driver to IBM
one,
this error is gone, but "COMPUTED_COLUMN" syntax ( legacy from CF5) does not
work with native IBM driver.

As a workaround I'm using IBM JDBC for client variable data storage and
DataDirect JDBC for all other data sources.

Officially 3.4 does not support Informix 10, it's interesting if somebody
experienced same behavior in 9.x

[cfperson]

Hi Macromedia,

After instaling 3.5 drivers I'm getting the same error... May be it will wake you up... 3.5 supports Informix 10...

[sdupre]

You don't say what version of CF you're using but I'm guessing 6.1. And I'm
assuming you're using client variables.

You should get the client variable upgrade hotfix.
[url]http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_17883#MX61U[/url]

This fix uses prepared statements and gets around this problem with CDATA,
CGLOBAL and Informix. Stay with the 3.5 drivers too since they have fixes for
handling dates (new DBDATE parameter).

Stephen Dupre
Macromedia QA

[cfperson]

I'm on 6.1 and fix was applied, but it did not work. I found message in WAS
SystemOut.log log:

[10/20/05 11:29:28:711 EDT] 0000004a ConnectionFac E J2CA0106E: A 5.0
DataSource was attempted to be used in a WebModule that was not level 2.3.

Detailed log info is included. WAS datasources are not in used, only CFMX.
I'm using WAS6.0 (please do not say it's not supported).

Thank you.






[10/20/05 11:29:28:711 EDT] 0000004a ConnectionFac E J2CA0106E: A 5.0
DataSource was attempted to be used in a WebModule that was not level 2.3.
[10/20/05 11:29:29:147 EDT] 0000004a Helpers W NMSV0605W: A Reference
object looked up from the context
"simba2Node01Cell/nodes/simba2Node01/servers/server1" with the name
"DefaultDatasource" was sent to the JNDI Naming Manager and an exception
resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl
Reference Factory Class Location URLs: <null>
Reference Class Name: javax.resource.cci.ConnectionFactory
Type: connectorName
Content: Default Datasource
Type: classpath
Content:
/opt/IBM/WebSphere/AppServer/lib/rsadapter.rar:/opt/IBM/WebSphere/AppServer/lib/
rsadapter.rar
Type: FactoryJndiName
Content: DefaultDatasource
Address Type: dd
AddressContents: ffffffac ffffffed 0 5 73 72 0 25 63 6f 6d 2e 69 62 6d 2e 65
6a 73 2e 6a 32 63 2e 52 65 73 6f 75 72 63 65 ...
Address Type: miscProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c
2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
Address Type: poolProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 27 63 6f 6d 2e 69 62 6d 2e 65
6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
Address Type: configProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 23 63 6f 6d 2e 69 62 6d 2e 65
6a 73 2e 6a 32 63 2e 43 6f 6e 6e 65 63 74 6f ...
Address Type: mmProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c
2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
Address Type: dsProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 14 6a 61 76 61 2e 75 74 69 6c
2e 50 72 6f 70 65 72 74 69 65 73 39 12 ffffffd0 7a ...
Address Type: mcfProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 2d 63 6f 6d 2e 69 62 6d 2e 65
6a 73 2e 6a 32 63 2e 4d 61 6e 61 67 65 64 43 ...
Address Type: mbeanProps
AddressContents: ffffffac ffffffed 0 5 73 72 0 1a 63 6f 6d 2e 69 62 6d 2e 65
6a 73 2e 6a 32 63 2e 4d 42 65 61 6e 50 72 6f ...

Exception data follows:
java.lang.Exception: Attempted to use a 5.0 DataSource outside of a 2.3 servlet
at
com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.valid Servlet(ConnectionFactoryBuild
erImpl.java:1109)
at
com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getCM ConfigData(ConnectionFactoryBu
ilderImpl.java:730)
at
com.ibm.ejs.j2c.ConnectionFactoryBuilderServerImpl .processObjectInstance(Connect
ionFactoryBuilderServerImpl.java:888)
at
com.ibm.ejs.j2c.ConnectionFactoryBuilderImpl.getOb jectInstance(ConnectionFactory
BuilderImpl.java:557)
at javax.naming.spi.NamingManager.getObjectInstance(N amingManager.java:301)
at
com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookupExt(Helpers.java:
874)
at
com.ibm.ws.naming.util.Helpers.processSerializedOb jectForLookup(Helpers.java:681
)
at
com.ibm.ws.naming.jndicos.CNContextImpl.processRes olveResults(CNContextImpl.java
:1937)
at
com.ibm.ws.naming.jndicos.CNBindingEnumeration.jnd iBindingData(CNBindingEnumerat
ion.java:154)
at
com.ibm.ws.naming.jndicos.CNNameEnumeration.addToB atch(CNNameEnumeration.java:37
3)
at
com.ibm.ws.naming.jndicos.CNNameEnumeration.initDi st(CNNameEnumeration.java:201)
at
com.ibm.ws.naming.jndicos.CNNameEnumeration.doInit (CNNameEnumeration.java:124)
at
com.ibm.ws.naming.util.WsnNamingEnumeration.init(W snNamingEnumeration.java:132)
at
com.ibm.ws.naming.jndicos.CNNameEnumeration.<init> (CNNameEnumeration.java:102)
at
com.ibm.ws.naming.jndicos.CNBindingEnumeration.<in it>(CNBindingEnumeration.java:
120)
at com.ibm.ws.naming.jndicos.CNContextImpl.doList(CNC ontextImpl.java:2917)
at
com.ibm.ws.naming.jndicos.CNContextImpl.listBindin gs(CNContextImpl.java:1247)
at com.ibm.ws.naming.util.WsnInitCtx.listBindings(Wsn InitCtx.java:304)
at javax.naming.InitialContext.listBindings(InitialCo ntext.java:396)
at coldfusion.sql.PoolManSqlExecutive.processEnum(Poo lManSqlExecutive.java:61)
at
coldfusion.sql.PoolManSqlExecutive.getJ2eeDataSour ces(PoolManSqlExecutive.java:1
51)
at coldfusion.sql.Executive.getJ2EEDataSources(Execut ive.java:39)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.jav
a:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at coldfusion.runtime.StructBean.resolveName(StructBe an.java:133)
at coldfusion.runtime.Scope.get(Scope.java:51)
at coldfusion.runtime.DotResolver.resolve(DotResolver .java:41)
at coldfusion.runtime.DotResolver.resolve(DotResolver .java:61)
at coldfusion.runtime.DotResolver.resolve(DotResolver .java:77)
at
coldfusion.runtime.NeoPageContext.SymTab_resolveSp litName(NeoPageContext.java:78
3)
at coldfusion.runtime.CfJspPage.resolveCanonicalName( CfJspPage.java:1060)
at coldfusion.runtime.CfJspPage._resolve(CfJspPage.ja va:1026)
at coldfusion.runtime.CfJspPage._resolveAndAutoscalar ize(CfJspPage.java:1125)
at
cfclientvariables2ecfm1629800640._factor23(/opt/IBM/WebSphere/AppServer/profiles
/default/installedApps/simba2Node01Cell/ColdFusionMX.ear/cfusion.war/CFIDE/admin
istrator/settings/clientvariables.cfm:273)
at
cfclientvariables2ecfm1629800640.runPage(/opt/IBM/WebSphere/AppServer/profiles/d
efault/installedApps/simba2Node01Cell/ColdFusionMX.ear/cfusion.war/CFIDE/adminis
trator/settings/clientvariables.cfm:1)
at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java :147)
at coldfusion.tagext.lang.IncludeTag.doStartTag(Inclu deTag.java:357)
at coldfusion.filter.CfincludeFilter.invoke(Cfinclude Filter.java:62)
at coldfusion.filter.ApplicationFilter.invoke(Applica tionFilter.java:107)
at coldfusion.filter.PathFilter.invoke(PathFilter.jav a:80)
at coldfusion.filter.ExceptionFilter.invoke(Exception Filter.java:47)
at
coldfusion.filter.ClientScopePersistenceFilter.inv oke(ClientScopePersistenceFilt
er.java:28)
at coldfusion.filter.BrowserFilter.invoke(BrowserFilt er.java:35)
at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilt er.java:43)
at coldfusion.filter.DatasourceFilter.invoke(Datasour ceFilter.java:22)
at coldfusion.CfmServlet.service(CfmServlet.java:105)
at coldfusion.bootstrap.BootstrapServlet.service(Boot strapServlet.java:89)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1282)
at
com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java
:673)
at com.ibm.ws.webcontainer.webapp.WebApp.handleReques t(WebApp.java:2905)
at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequ est(WebGroup.java:220)
at com.ibm.ws.webcontainer.VirtualHost.handleRequest( VirtualHost.java:204)
at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:1829)
at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:84)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpIn
boundLink.java:469)
at
com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpIn
boundLink.java:408)
at
com.ibm.ws.http.channel.inbound.impl.HttpICLReadCa llback.complete(HttpICLReadCal
lback.java:101)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.reque stComplete(WorkQueueManager.ja
va:566)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.attem ptIO(WorkQueueManager.java:619
)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager.worke rRun(WorkQueueManager.java:952
)
at
com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worke r.run(WorkQueueManager.java:10
39)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1455)

[sdupre]

See this thread:
[url]http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=274&threadid=918459&enterthr ead=y[/url]

Stephen Dupre
Macromedia QA

[cfperson]

Thread that you referring to says to ignore this message. Let's ignore it, but this message corresponds with my JDBC and cfapplication problem. Can you explain this? There is a problem.

[sdupre]

I meant this part from wlee:

>> If you're running CFMX on Websphere and are trying to use a Websphere

datasource, you must choose the attribute to make the datasource Websphere 4
compatible. <<

Stephen Dupre
Macromedia QA

[cfperson]

I do not use WAS datasource, only CFMX !!!

Do you have the ability to test this problem in your lab? If yes, please do, we have been posting for a week with no result.

Thank you.

[cfperson]

Hi Stephen and Macromedia/Adobe,

I'm planning to move CFMX6.1 in production. So I downgraded from WAS 6 to 5.1
to be in compliance with CFMX requirements. It still does not work. I'm getting
the same error. To remind you I do not get the error when using native Informix
JDBC drivers. All hot fixes and 3.5 drivers applied.

Should I pay $500.00 to get this classified as bug and resolved?