ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Butler" <jeffgbut...@gmail.com>
Subject Re: Migr WAS 5.0->6.0
Date Mon, 06 Nov 2006 16:05:31 GMT
iBATIS works fine on WAS 6.0.  There is some information on this WIKI page
about configuring iBATIS in different WAS scenarios:

http://opensource.atlassian.com/confluence/oss/display/IBATIS/Environment+Specific+Information


Jeff Butler



On 11/6/06, Paul Carr <Paul.Carr@express-gifts.co.uk> wrote:
>
> More News....
>
> I tried changing to a stand-alone transaction manager (not using JTA)
> and it works fine....
>
> <transactionManager type="JDBC">
>                <dataSource type="SIMPLE">
>                        <property name="JDBC.Driver"
> value="com.ibm.db2.jcc.DB2Driver" />
>                        <property name="JDBC.ConnectionURL"
> value="jdbc:db2://ukclawv01:50003/crd01" />
>                        <property name="JDBC.Username" value="upca" />
>                        <property name="JDBC.Password" value="bccbcbbc"
> />
>                        <property name="JDBC.DefaultAutoCommit"
> value="true" />
>                        <property name="Pool.MaximumActiveConnections"
> value="10" />
>                        <property name="Pool.MaximumIdleConnections"
> value="5" />
>                        <property name="Pool.MaximumCheckoutTime"
> value="120000" />
>                        <property name="Pool.TimeToWait" value="500" />
>                        <property name="Pool.PingQuery" value="select 1
> from ACCOUNT" />
>                        <property name="Pool.PingEnabled" value="false"
> />
>                        <property name="Pool.PingConnectionsOlderThan"
> value="1" />
>                        <property name="Pool.PingConnectionsNotUsedFor"
> value="1" />
>                </dataSource>
>        </transactionManager>
>
>
> Has anyone got a SqlMapConfig using UserTransactions that works OK on
> Was 6.0 ?
>
>
> Best Regards
> Paul.
>
>
> -----Original Message-----
> From: Hariharan, Vadivelu (IE10)
> [mailto:Hariharan.Vadivelu@honeywell.com]
> Sent: 06 November 2006 14:16
> To: user-java@ibatis.apache.org
> Subject: RE: Migr WAS 5.0->6.0
>
> I migrated one of the apps recently to WAS 6.0.2.5
> I use Spring + iBatis.
>
>
> Datasource are created by Apache basic datasource
> I'm yet to check it with WAS connection will let you know.
>
> Thx
> -Hari
>
> -----Original Message-----
> From: Paul Carr [mailto:Paul.Carr@express-gifts.co.uk]
> Sent: Monday, November 06, 2006 7:39 PM
> To: user-java@ibatis.apache.org
> Subject: RE: Migr WAS 5.0->6.0
>
> Hi Nathan,
>           I was running fine on WAS 5.0 with JDK 1.3.1, so I doubt it's
> a JDK issue. When I started trying to move to WAS 6.0 I had some naming
> difficulties ... my sqlmapconfig had "java:comp" in the JNDI names and
> it didn't like it....so I went from :-
>
> <transactionManager type="JTA" commitRequired="true">
> <property name="java:comp/UserTransaction"
>     value="UserTransaction"/>
> <dataSource type="JNDI">
>    <property name="DataSource"
>      value="java:comp/jdbc/db2Connection"/>
> </dataSource>
> </transactionManager>
>
> TO THIS :-
>
> <transactionManager type="JTA" commitRequired="true">
> <property name="UserTransaction"
>     value="UserTransaction"/>
> <dataSource type="JNDI">
>    <property name="DataSource"
>      value="jdbc/db2Connection"/>
> </dataSource>
> </transactionManager>
>
> Which seemed to get me past the initial naming Exceptions.... but now
> it's giving these "java.lang.IllegalStateException: Null
> ComponentMetaData" messages ????
>
>
> -----Original Message-----
> From: Nathan Ward [mailto:nward@resqsoft.com]
> Sent: 06 November 2006 13:58
> To: user-java@ibatis.apache.org
> Subject: RE: Migr WAS 5.0->6.0
>
> WAS 6.0 uses JDK 1.4 doesn't it? Does iBATIS require JDK 1.5? I doubt
> it,
> but thought I'd mention it.
>
> I attended a NFJS conference that past weekend where Ted Neward said
> that
> WAS has a very complicated classloader structure. I had a problem
> recently
> with static variables in a class that worked fine under Tomcat 5.5, but
> WAS
> 6.0 got ClassNotFound exception.
>
>   Nathan
>
> -----Original Message-----
> From: Paul Carr [mailto:Paul.Carr@express-gifts.co.uk]
> Sent: Monday, November 06, 2006 8:42 AM
> To: user-java@ibatis.apache.org
> Subject: RE: Migr WAS 5.0->6.0
>
> News...
> Since creating this problem I've deployed an older app ( which doesn't
> use
> iBatis) to the same env and it works perfectly well with my DataSource.
> Therefore the problem must lie in the iBatis config somewhere ????
>
> Has anyone else experienced difficulties migrating to WAS 6  ( 6.0.2.3
> to be
> exact)
>
> Best Regards
> Paul.
>
> -----Original Message-----
> From: Paul Carr [mailto:Paul.Carr@express-gifts.co.uk]
> Sent: 06 November 2006 12:45
> To: user-java@ibatis.apache.org
> Subject: Migr WAS 5.0->6.0
>
> Hi All,
>          I'm having trouble moving from a working WAS 5.0 env to WAS
> 6.0.
> First I had to change my sqlmapconfig so that it used
> "jdbc/db2Connection"
> rather than "java:comp/jdbc/db2Connection" ....
> which got me past my first problem, but now I keep getting NULL
> Component
> MetaData whenever I try to create the DaoManager.(see stack below).
>
> Has anyone got a valid SqlMapConfig.xml ,  and instructions on how to
> create
> the Datasource in WAS , that will work ok together (I've tried 2
> different
> datasources so far, and both gave the same problem)
>
> Thanks
> Paul.
>
> STACK TRACE :-
>
> Exception data follows:
> java.lang.IllegalStateException: Null ComponentMetaData
>        at
> com.ibm.ejs.cm.DSFactoryImpl.verifyConfiguration(DSFactoryImpl.java:266)
>        at
> com.ibm.websphere.advanced.cm.factory.DataSourceFactory$ResourceReferenc
> eObjectFactory.getObjectInstance(DataSourceFactory.java:946)
>        at
> javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:314)
>        at
> com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookupExt(Helpe
> rs.java:874)
>        at
> com.ibm.ws.naming.util.Helpers.processSerializedObjectForLookup(Helpers.
> java:681)
>        at
> com.ibm.ws.naming.jndicos.CNContextImpl.processResolveResults(CNContextI
> mpl.java:1937)
>        at
> com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1792
> )
>        at
> com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1707
> )
>        at
> com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:141
> 2)
>        at
> com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1290)
>        at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:145)
>        at javax.naming.InitialContext.lookup(InitialContext.java:361)
>        at
> com.ibatis.sqlmap.engine.datasource.JndiDataSourceFactory.initialize(Jnd
> iDataSourceFactory.java:48)
>        at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser$9.process(SqlMap
> ConfigParser.java:301)
>        at
> com.ibatis.common.xml.NodeletParser.processNodelet(NodeletParser.java:11
> 2)
>        at
> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:96)
>        at
> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:93)
>        at
> com.ibatis.common.xml.NodeletParser.process(NodeletParser.java:93)
>        at
> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:63)
>        at
> com.ibatis.common.xml.NodeletParser.parse(NodeletParser.java:51)
>        at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConf
> igParser.java:78)
>        at
> com.ibatis.sqlmap.engine.builder.xml.SqlMapConfigParser.parse(SqlMapConf
> igParser.java:69)
>        at
> com.ibatis.sqlmap.client.SqlMapClientBuilder.buildSqlMapClient(SqlMapCli
> entBuilder.java:78)
>        at
> com.ibatis.dao.engine.transaction.sqlmap.SqlMapDaoTransactionManager.con
> figure(SqlMapDaoTransactionManager.java:52)
>        at
> com.ibatis.dao.engine.builder.xml.XmlDaoManagerBuilder.parseTransactionM
> anager(XmlDaoManagerBuilder.java:193)
>        at
> com.ibatis.dao.engine.builder.xml.XmlDaoManagerBuilder.parseContext(XmlD
> aoManagerBuilder.java:157)
>        at
> com.ibatis.dao.engine.builder.xml.XmlDaoManagerBuilder.buildDaoManager(X
> mlDaoManagerBuilder.java:102)
>        at
> com.ibatis.dao.client.DaoManagerBuilder.buildDaoManager(DaoManagerBuilde
> r.java:59)
>        at egl.writer.SQLWriter.<clinit>(SQLWriter.java:32)
>        at egl.treetable.WebFacade.getNumberFailed(WebFacade.java:54)
>
> _____________________________________________________________________
> NOTE:  This email and any information contained within or attached in a
> separate file is confidential and intended solely for the Individual to
> whom
> it is addressed. The information or data included is solely for the
> purpose
> indicated or previously agreed. Any information or data included with
> this
> e-mail remains the property of Findel PLC and the recipient will refrain
> from utilising the information for any purpose other than that indicated
> and
> upon request will destroy the information and remove it from their
> records.
> Any views or opinions presented are solely those of the author and do
> not
> necessarily represent those of Findel PLC. If you are not the intended
> recipient, be advised that you have received this email in error and
> that
> any use, dissemination, forwarding, printing, or copying of this email
> is
> strictly prohibited. No warranties or assurances are made in relation to
> the
> safety and content of this e-mail and any attachments.  No liability is
> accepted for any consequences arising from it. Findel Plc reserves the
> right
> to monitor all e-mail communications through its internal and external
> networks.If you have received this email in error please notify our IT
> helpdesk on
> +44(0) 1254 303030
>
> _____________________________________________________________________
> NOTE:  This email and any information contained within or attached in a
> separate file is confidential and intended solely for the Individual to
> whom
> it is addressed. The information or data included is solely for the
> purpose
> indicated or previously agreed. Any information or data included with
> this
> e-mail remains the property of Findel PLC and the recipient will refrain
> from utilising the information for any purpose other than that indicated
> and
> upon request will destroy the information and remove it from their
> records.
> Any views or opinions presented are solely those of the author and do
> not
> necessarily represent those of Findel PLC. If you are not the intended
> recipient, be advised that you have received this email in error and
> that
> any use, dissemination, forwarding, printing, or copying of this email
> is
> strictly prohibited. No warranties or assurances are made in relation to
> the
> safety and content of this e-mail and any attachments.  No liability is
> accepted for any consequences arising from it. Findel Plc reserves the
> right
> to monitor all e-mail communications through its internal and external
> networks.If you have received this email in error please notify our IT
> helpdesk on +44(0) 1254 303030
>
>
>
> _____________________________________________________________________
> NOTE:  This email and any information contained within or attached in a
> separate file is confidential and intended solely for the Individual to
> whom it is addressed. The information or data included is solely for the
> purpose indicated or previously agreed. Any information or data included
> with this e-mail remains the property of Findel PLC and the recipient
> will refrain from utilising the information for any purpose other than
> that indicated and upon request will destroy the information and remove
> it from their records.  Any views or opinions presented are solely those
> of the author and do not necessarily represent those of Findel PLC. If
> you are not the intended recipient, be advised that you have received
> this email in error and that any use, dissemination, forwarding,
> printing, or copying of this email is strictly prohibited. No warranties
> or assurances are made in relation to the safety and content of this
> e-mail and any attachments.  No liability is accepted for any
> consequences arising from it. Findel Plc reserves the right to monitor
> all e-mail communications through its internal and external networks.If
> you have received this email in error please notify our IT helpdesk on
> +44(0) 1254 303030
>
> _____________________________________________________________________
> NOTE:  This email and any information contained within or attached in a
> separate file is confidential and intended solely for the Individual to whom
> it is addressed. The information or data included is solely for the purpose
> indicated or previously agreed. Any information or data included with this
> e-mail remains the property of Findel PLC and the recipient will refrain
> from utilising the information for any purpose other than that indicated and
> upon request will destroy the information and remove it from their
> records.  Any views or opinions presented are solely those of the author and
> do not necessarily represent those of Findel PLC. If you are not the
> intended recipient, be advised that you have received this email in error
> and that any use, dissemination, forwarding, printing, or copying of this
> email is strictly prohibited. No warranties or assurances are made in
> relation to the safety and content of this e-mail and any attachments.  No
> liability is accepted for any consequences arising from it. Findel Plc
> reserves the right to monitor all e-mail communications through its internal
> and external networks.If you have received this email in error please
> notify our IT helpdesk on +44(0) 1254 303030
>

Mime
View raw message