OracleDS is not bound

[cnsxxx09]

Hi,

I'm upgrading from JBoss 3 alpha to RC1 and trying to get my Oracle8 connection Pool working (it worked in alpha)...but when i deploy my Bean I get the error that OracleDS is not bound.

I got the latest config oracle-service.xml example from CVS (dated Mon Apr 29 00:03:28 2002 UTC).
OracleDS was the name I was using before so the only things I have changed/touched are in attribute ManagedConnectionFactoryProperties as follows:
1. ConnectionUrl
2. UserName
3. Password
(I don't use JAAS so I haven't touched that part at all)

When I go to http://localhost:8082 under jboss.jca I can see:
service=LocalTxCM,name=OracleDS
service=LocalTxDS,name=OracleDS
service=LocalTxPool,name=OracleDS

LocalTxPool is ok (Started/3).
LocalTxCM says that it is Stopped - and when I try clicking on the start button I get the following error:

472 MBean Failure
----------------------
The MBean [jboss.jca:service=LocalTxCM,name=OracleDS] throws an MBeanException when calling [start]:
org.jboss.deployment.DeploymentException: couldn't get oldRarDeployment!; - nested throwable is: javax.management.InstanceNotFoundException: jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper is not registered

When I try to view OldRarDeployment in LocalTxDS I get the error:
459 Instance Not Found
----------------------
Unable to get MBeanInfo for [null]

...I've spent some time seraching the archives and trying things but still no joy...

Can someone enlighten me on what i forgot to do before I go crazy! Many TIA

Chris
-=-=-=

[cnsxxx09]

plan B was to try editing and adding the <application-policy> into login-conf.xml - but that made absolutely no difference whatsoever :-(

Chris
-=-=-

[cnsxxx09]

could the following be significant?

17:55:15,915 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=OracleDS does not implement any Service methods

???

[rockhopper]

Hi,

I've exactly the same problem (even if no problem in 3.0Beta).
Here is my configuration file (i've commented out the section because i want to use default values in the ManagedConnectionFactoryProperties).

I set 5 then I should get at least an attempt to connect as soon as oracle-service.xml is deployed, but nothing appears.
Whatever no error has occured.
Something is wrong?

Here is server.log.


Configuration:
- JDK 1.3.1_03
- JBoss 3.0.0RC1
- Oracle8i
- (Redhat 7.2)

[davidjencks]

There is a new local transaction jca-jdbc wrapper added since rc1. I suggest you upgrade to cvs version of jboss 3, or see if there is a rc1 tagged oracle-service.xml file. Getting the cvs version will save you reconfiguring twice, because the old local jca wrapper is now gone.

checkout should be

cvs co -r Branch_3_0 jboss-all

[ibruell]

Check the examples at: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/manual/src/examples/resources/jca/

[cnsxxx09]

Thanks for the reply...

Unfortunately CVS is blocked from work...so I'll have to look for rc1 tagged example DS file.

Thanks (I thought I was going mad there for a minute!)

Chris
-=-=-=

[bjs_pd]

Hi All!

I'm also using Jboss3.0RC1 with a Oracle 9i Database. While I'm trying to connect to this DB I always get the same Exception "OracleDS not bound" although the JndiView show it as marked. After trying the oracle-service.xml form the above SourceForge address I got a new ClassNotFound exception. The server-log shows:

About to create bean: jboss.jca:service=ConnectionFactoryLoader,name=OracleDS

org.jboss.resource.ConnectionFactoryLoader

Class not found for mbean: jboss.jca:service=ConnectionFactoryLoader,name=OracleDS

Is there a newer jboss-jca.jar out there including this class. CVS ist also block from office-firewall.

Trying to modify the hpersonic service file 'hsqldb-service.xml' with the Oracle settings and changing the 'datasource'-tag in 'standardjbosscmp-jdbc.xml' to 'OracleDS' shows alwys the 'OracleDS'-Not-Bound exception.

Is there a way to get a connection via RC1 or is this a general bug?

Hope you can help

CU
Bj

[davidjencks]

Please use rc2 and start from the sample configs included in the zip. The examples from the manual are now OUT OF DATE and WILL NOT WORK.

Perhaps your ejb dd settings are not quite right -- maybe you need java:/OracleDS rather than OracleDS or vice versa. If you see java:/OracleDS bound in jndi view, then it is bound, and errors that it is not indicate that some other dd is looking in the wrong place.

[jweis]

> Please use rc2 and start from the sample configs
> included in the zip. The examples from the manual
> are now OUT OF DATE and WILL NOT WORK.
>
> Perhaps your ejb dd settings are not quite right --
> maybe you need java:/OracleDS rather than OracleDS or
> vice versa. If you see java:/OracleDS bound in jndi
> view, then it is bound, and errors that it is not
> indicate that some other dd is looking in the wrong
> place.

Same Problem: with 3.0.0RC1

I have read all the posts (as many as I could find) regarding this problem and now I am really lost as to how to resolve it. I did not see anything in the log that would give me a clue. I do not see anything in the log that says OracleDS has been bound. Clearly it is not being bound and I am trying to find out why. Is there an RC2 available (bundled with Tomcat4.0.3) somewhere that has resolved this?

I have made the appropriate adjustments to login-conf.xml as you had suggested, but no success. Here is the file I am using:

<?xml version="1.0" encoding="UTF-8"?>

<!-- ===================================================================== -->
<!-- -->
<!-- JBoss Server Configuration -->
<!-- -->
<!-- ===================================================================== -->



<!-- ==================================================================== -->
<!-- ConnectionManager setup for Oracle dbs -->
<!-- Build jmx-api (build/build.sh all) and view for config documentation -->
<!-- Thanks to Steven Coy -->
<!-- ==================================================================== -->


<!--make the rar deploy! hack till better deployment-->
jboss.jca:service=RARDeployer

<!-- Include a login module configuration named OracleDbRealm.
Update your login-conf.xml, here is an example for a
ConfiguredIdentityLoginModule:

<application-policy name = "OracleDbRealm">

<login-module code = "org.jboss.resource.security.ConfiguredIdentityLoginModule" 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=LocalTxCM,name=OracleDS</module-option>
</login-module>

</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.
-->
<!--comment out this line if you want component managed security or want
to use the default values in the ManagedConnectionFactoryProperties -->
OracleDbRealm

<depends optional-attribute-name="ManagedConnectionFactoryName">
<!--embedded mbean-->


OracleDS



<config-property name="ConnectionURL" type="java.lang.String">jdbc:oracle:thin:@bucket:1521:ORCL</config-property>
<config-property name="DriverClass" type="java.lang.String">oracle.jdbc.driver.OracleDriver</config-property>
<!--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>
-->




<!--Below here are advanced properties -->
<!--hack-->
<depends optional-attribute-name="OldRarDeployment">jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper



<depends optional-attribute-name="ManagedConnectionPool">
<!--embedded mbean-->


0
50
5000
15
<!--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)-->
ByContainer



<depends optional-attribute-name="CachedConnectionManager">jboss.jca:service=CachedConnectionManager

<!-- Get error if following not commented out
<depends optional-attribute-name="JaasSecurityManagerService">jboss.security:name=JaasSecurityManager -->

java:/TransactionManager








Thanks in advance.

[davidjencks]

After you get rc2 and try it out I will look further to see if I can see something wrong. Look at sf file download page. Example configs are at docs/examples/jca in the zip.

[bjs_pd]

Hi All!

Thanks for helping. After downloading the RC2 from

http://sourceforge.net/project/showfiles.php?group_id=22866

using the oracle-service.xml from examples everything worked fine with the Oracle9i database.

Really thanks a lot!!!!

CU
BJ

[prilmeie]

Hello,

I can't manage it either. I'm using the most recent JBoss3.0.0RC2; My database is an Oracle 8i.

These are the steps I have taken:

1. Copied classes12.zip into the lib folder
2. Took the oracle-service.xml from the docs/examples/jca folder
3. Adapted the values for ConnectionURL. I have also explicitly set the username and the password. These are the values which are used for connecting to oracle, right?
4. I commented out the SecurityDomainJndiName attribute.

My EJB are trying to get their javax.sql.DataSource resp. Connection via JNDI lookup. The significant code is:

InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup( "java:comp/env/jdbc/lisaPool" );
Connection con = ds.getConnection();

I have declared this name in the ejb-jar.xml:

<resource-ref>
The LiSa database connection pool

<res-ref-name>jdbc/lisaPool</res-ref-name>

<res-type>javax.sql.DataSource</res-type>

<res-auth>Container</res-auth>
</resource-ref>

In the jboss.xml of the EJB I wrote:

[...]
<resource-ref>
<res-ref-name>jdbc/lisaPool</res-ref-name>

<jndi-name>OracleDS</jndi-name>
</resource-ref>
[...]

During deployment of oracle-service.xml the log output is:

16:42:27,740 INFO [MainDeployer] Starting deployment of package: file:/C:/Programme/Server/httpd/jboss-3.0.0RC2/server/default/deploy/oracle-service.xml
16:42:28,241 WARN [ServiceController] jboss.jca:service=LocalTxDS,name=OracleDS
does not implement any Service methods
16:42:28,271 INFO [JBossManagedConnectionPool] Creating
16:42:28,291 INFO [JBossManagedConnectionPool] Created
16:42:28,311 INFO [LocalTxConnectionManager] Creating
16:42:28,341 INFO [LocalTxConnectionManager] Created
16:42:28,361 INFO [JBossManagedConnectionPool] Starting
16:42:28,371 INFO [JBossManagedConnectionPool] Started
16:42:28,391 INFO [LocalTxConnectionManager] Starting
16:42:29,002 INFO [OracleDS] Bound connection factory for resource adapter 'JBoss LocalTransaction JDBC Wrapper' to JNDI name 'java:/OracleDS'
16:42:29,032 INFO [LocalTxConnectionManager] Started
16:42:29,052 INFO [MainDeployer] Successfully completed deployment of package:
file:/C:/Programme/Server/httpd/jboss-3.0.0RC2/server/default/deploy/oracle-serv
ice.xml

Something is missconfigured, but I cannot figure it out what.

Can you help me?

[davidjencks]

Well, you neglected to say what wasn't working or include a stack trace, which makes it a bit difficult.

If the jndi lookup is failing try java:/OracleDS

If there's no username/pw try setting up the login module per instructions.

[prilmeie]

Sorry,

what I forgot to mention is, that this error occurs independent from the fact that the Database is running or not I have worked with WebLogic (5.1) before and the server actually checked whether a connection to a database was possible or not.

Here the complete Stack Trace:

16:38:31,541 ERROR [LogInterceptor] TransactionRolledbackException, causedBy:
de.tum.in.lisa.util.LisaDataException: DBConnector connect: Naming Exception while getting DataSource: java:comp/env/jdbc/lisaPool: OracleDS not bound
at de.tum.in.lisa.util.DBConnector.openConnection(DBConnector.java:72)
at de.tum.in.lisa.workproductSearch.ejb.impl.WorkProductSearchDAO.openCo
nnection(WorkProductSearchDAO.java:554)
at de.tum.in.lisa.workproductSearch.ejb.impl.WorkProductSearchDAO.getDir
ectSuccessorsByParentID(WorkProductSearchDAO.java:465)
at de.tum.in.lisa.workproductSearch.ejb.impl.WorkProductSearchEJB.getDir
ectSuccessorsByParentID(WorkProductSearchEJB.java:120)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(S
tatelessSessionContainer.java:664)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo
ke(CachedConnectionInterceptor.java:147)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Stat
elessSessionInstanceInterceptor.java:77)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte
rceptor.java:96)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxIntercep
torCMT.java:167)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:6
1)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.
java:129)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContai
ner.java:313)
at org.jboss.ejb.Container.invoke(Container.java:706)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.jav
a:102)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.
java:73)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:7
6)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessi
onInterceptor.java:111)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy76.getDirectSuccessorsByParentID(Unknown Source)
at de.tum.in.lisa.lisamanager.ejb.impl.LisaManagerEJB.getDirectSuccessor
sByParentID(LisaManagerEJB.java:398)
at java.lang.reflect.Method.invoke(Native Method)
at org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invoke(S
tatelessSessionContainer.java:664)
at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invo
ke(CachedConnectionInterceptor.java:147)
at org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invoke(Stat
elessSessionInstanceInterceptor.java:77)
at org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInte
rceptor.java:96)
at org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxIntercep
torCMT.java:167)
at org.jboss.ejb.plugins.TxInterceptorCMT.invoke(TxInterceptorCMT.java:6
1)
at org.jboss.ejb.plugins.SecurityInterceptor.invoke(SecurityInterceptor.
java:129)
at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:166)
at org.jboss.ejb.StatelessSessionContainer.invoke(StatelessSessionContai
ner.java:313)
at org.jboss.ejb.Container.invoke(Container.java:706)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:491)
at org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98)
at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.jav
a:102)
at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.
java:73)
at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:7
6)
at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessi
onInterceptor.java:111)
at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76)
at $Proxy65.getDirectSuccessorsByParentID(Unknown Source)
at de.tum.in.lisa.web.WorkProductSearchBean.getChildren(WorkProductSearc
hBean.java:88)
at org.apache.jsp.MenuTree_0005fbelow$jsp._jspService(MenuTree_0005fbelo
w$jsp.java:254)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:107)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspSer
vlet.java:202)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:3
82)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:474)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:326
)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:5
95)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1357)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1309)
at org.mortbay.http.HttpServer.service(HttpServer.java:744)
at org.jboss.jetty.Jetty.service(Jetty.java:527)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:743)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:916)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:758)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:
145)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:287)
at org.mortbay.util.ThreadPool$JobRunner.run(ThreadPool.java:715)
at java.lang.Thread.run(Thread.java:484)