Menu
▾
▴
Re: [JBoss-user] problem with oracle-xa-ds.xml
|
From: Stefano M. <ste...@ja...> - 2003-04-30 08:03:20
|
Yes it works. Just released in production enviroment. Thanks for your time. Is the bug of *-ds.xml fixed in cvs and so on next release, or how may time have we to wait before we could use the simplier *-ds.xml descriptor? Thak you very much. Stefano On Thursday 24 April 2003 19:57, David Jencks wrote: > On 2003.04.24 06:35 Stefano Maestri wrote: > > Ok, np. Could you explain a little what have I to do with > > <depends optional-attribute-name="ManagedConnectionFactoryName"> > > It seems to don't work in Jboss 3.2.0 final. I read that I have to move > > the > > embedded bean, but what have I to do with the "depends"? > > And exactly where have I to move it? > > I attached my oracle-xa-service.xml working with RC4, but not with final. > > > > Thanks a lot > > I think this will work: > > <?xml version="1.0" encoding="UTF-8"?> > > <!-- ===================================================================== > --> > <!-- > --> > <!-- JBoss Server Configuration > --> > <!-- > --> > <!-- ===================================================================== > --> > > <server> > > <!-- ==================================================================== > --> > <!-- ConnectionManager setup for xa oracle dbs > --> > <!-- Thanks to igor fedorenko <ife...@th...> > --> > <!-- Build jmx-api (build/build.sh all) and view for config documentation > --> > <!-- YOU MUST CHANGE THE XidFactoryMBean config to this: > --> > <!-- > <mbean code="org.jboss.tm.XidFactory" > name="jboss:service=XidFactory"> > <attribute name="Pad">true</attribute> > </mbean> > --> > <!-- ==================================================================== > --> > > <mbean code="org.jboss.resource.connectionmanager.XATxConnectionManager" > name="jboss.jca:service=XATxCM,name=OracleDB"> > > <attribute name="JndiName">OracleDB</attribute> > > <attribute name="TrackConnectionByTx">true</attribute> > > > <depends optional-attribute-name="ManagedConnectionPool"> > <!--embedded mbean--> > <mbean > code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" > > name="jboss.jca:service=XATxPool,name=OracleDB"> > > <depends optional-attribute-name="ManagedConnectionFactoryName"> > <!--embedded mbean--> > <mbean code="org.jboss.resource.connectionmanager.RARDeployment" > name="jboss.jca:service=XATxDS,name=OracleDB"> > > <attribute > name="ManagedConnectionFactoryClass">org.jboss.resource.adapter.jdbc.xa.ora >cle.XAOracleManagedConnectionFactory</attribute> > > <!--real attributes--> > <attribute name="ManagedConnectionFactoryProperties"> > <properties> > <config-property name="XADataSourceProperties" > > type="java.lang.String">URL=jdbc:oracle:thin:@192.168.0.124:1521:SVIL</conf >ig-property> <config-property name="XADataSourceClass" > > type="java.lang.String">oracle.jdbc.xa.client.OracleXADataSource</config-pr >operty> <!--set these only if you want only default logins, not through JAAS > --> > <config-property name="UserName" > type="java.lang.String"></config-property> > <config-property name="Password" > type="java.lang.String"></config-property> > <!-- > Do not try to set transaction isolation level here or you'll > get > java.sql.SQLException: ORA-01453: SET TRANSACTION must be > first statement of transaction > Read committed is a default isolation level for Oracle, so > there > is not real need to set it here. I'll take a look into it > later ...maybe. > <config-property name="TransactionIsolation" > > type="java.lang.String">TRANSACTION_READ_COMMITTED</config-property> --> > </properties> > </attribute> > </mbean> > </depends> > <attribute name="MinSize">1</attribute> > <attribute name="MaxSize">20</attribute> > <attribute name="BlockingTimeoutMillis">5000</attribute> > <attribute name="IdleTimeoutMinutes">1</attribute> > <!--criteria indicates if Subject (from security domain) or app > supplied > parameters (such as from getConnection(user, pw)) are used to > distinguish > connections in the pool. Choices are > ByContainerAndApplication (use both), > ByContainer (use Subject), > ByApplication (use app supplied params only), > ByNothing (all connections are equivalent, usually if adapter > supports > reauthentication)--> > <attribute name="Criteria">ByContainer</attribute> > </mbean> > </depends> > <depends > optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedC >onnectionManager</depends> > > <!-- Include a login module configuration named InformixXaDbRealm. > Update your login-conf.xml, here is an example for a > ConfiguredIdentityLoginModule: > --> > <application-policy name = "OracleRealm"> > <authentication> > <login-module code = > "org.jboss.resource.security.CallerIdentityLoginModule" flag = "required"> > <module-option name = > "principal">yourprincipal</module-option> <module-option name = > "userName">yourusername</module-option> <module-option name = > "password">yourpassword</module-option> <module-option name = > "managedConnectionFactoryName">jboss.jca:service=XATxCM,name=OracleDB</modu >le-option> </login-module> > </authentication> > </application-policy> > <!-- > NOTE: the application-policy name attribute must match > SecurityDomainJndiName, and the > module-option name = "managedConnectionFactoryName" > must match the object name of the ConnectionManager you are configuring > here. > --> > <!--uncomment out this line ifyou are using the InformixXaDbRealm above > --> > <attribute name="SecurityDomainJndiName">client-login</attribute> > > <!--<attribute name="SecurityDomainJndiName">client-login</attribute>--> > <depends > optional-attribute-name="JaasSecurityManagerService">jboss.security:service >=JaasSecurityManager</depends> > > <attribute > name="TransactionManager">java:/TransactionManager</attribute> </mbean> > > <mbean code="org.jboss.resource.connectionmanager.XATxConnectionManager" > name="jboss.jca:service=XATxCM,name=RapportiDB"> > > <attribute name="JndiName">RapportiDB</attribute> > > <attribute name="TrackConnectionByTx">true</attribute> > > <depends optional-attribute-name="ManagedConnectionFactoryName"> > <!--embedded mbean--> > <mbean code="org.jboss.resource.connectionmanager.RARDeployment" > name="jboss.jca:service=XATxDS,name=RapportiDB"> > > <attribute > name="ManagedConnectionFactoryClass">org.jboss.resource.adapter.jdbc.xa.ora >cle.XAOracleManagedConnectionFactory</attribute> > > <!--real attributes--> > <attribute name="ManagedConnectionFactoryProperties"> > <properties> > <config-property name="XADataSourceProperties" > > type="java.lang.String">URL=jdbc:oracle:thin:@192.168.0.124:1521:SVIL</conf >ig-property> <config-property name="XADataSourceClass" > > type="java.lang.String">oracle.jdbc.xa.client.OracleXADataSource</config-pr >operty> <!--set these only if you want only default logins, not through JAAS > --> > <config-property name="UserName" > type="java.lang.String">lynxowner</config-property> > <config-property name="Password" > type="java.lang.String">owner</config-property> > <!-- > Do not try to set transaction isolation level here or you'll > get > java.sql.SQLException: ORA-01453: SET TRANSACTION must be > first statement of transaction > Read committed is a default isolation level for Oracle, so > there > is not real need to set it here. I'll take a look into it > later ...maybe. > <config-property name="TransactionIsolation" > > type="java.lang.String">TRANSACTION_READ_COMMITTED</config-property> --> > </properties> > </attribute> > </mbean> > </depends> > > <depends optional-attribute-name="ManagedConnectionPool"> > <!--embedded mbean--> > <mbean > code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" > > name="jboss.jca:service=XATxPool,name=RapportiDB"> > > <attribute name="MinSize">1</attribute> > <attribute name="MaxSize">30</attribute> > <attribute name="BlockingTimeoutMillis">5000</attribute> > <attribute name="IdleTimeoutMinutes">1</attribute> > <!--criteria indicates if Subject (from security domain) or app > supplied > parameters (such as from getConnection(user, pw)) are used to > distinguish > connections in the pool. Choices are > ByContainerAndApplication (use both), > ByContainer (use Subject), > ByApplication (use app supplied params only), > ByNothing (all connections are equivalent, usually if adapter > supports > reauthentication)--> > <attribute name="Criteria">ByContainer</attribute> > </mbean> > </depends> > <depends > optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedC >onnectionManager</depends> > > <!-- Include a login module configuration named InformixXaDbRealm. > Update your login-conf.xml, here is an example for a > ConfiguredIdentityLoginModule: > --> > <!-- > NOTE: the application-policy name attribute must match > SecurityDomainJndiName, and the > module-option name = "managedConnectionFactoryName" > must match the object name of the ConnectionManager you are configuring > here. > --> > <!--uncomment out this line ifyou are using the InformixXaDbRealm above > --> > <!--<attribute name="SecurityDomainJndiName">client-login</attribute> > --> > <!--<attribute name="SecurityDomainJndiName">client-login</attribute>--> > <depends > optional-attribute-name="JaasSecurityManagerService">jboss.security:service >=JaasSecurityManager</depends> > > <attribute > name="TransactionManager">java:/TransactionManager</attribute> </mbean> > > </server> > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > JBoss-user mailing list > JBo...@li... > https://lists.sourceforge.net/lists/listinfo/jboss-user -- --------------- all work and no play makes Jack a dull boy --------------- bye Stefano ste...@ja... www.javalinux.it MSN messanger: mae...@ho... ICQ uin: 122192578 Jabber: canezen Yahoo MSN: canezen #jedit IRC channel as <maeste> |