Re: Deploying application-scoped db pool with an ear
Sorry what's a JIRA, and where do I submit it? Lin Sun-2 wrote: Great to know that!! Thanks for the feedback Can you open a JIRA so that we can fix the instruction in the console to remind our user that - for application scope db, a user would also need to add module and connector tags into the standard deployment desp? Here's our tutorial page -http://cwiki.apache.org/GMOxDOC21/tutorials.html. I saw other folks have been creating task JIRAs for tutorialls, for example GERONIMO-4159. Thanks, Lin On 6/26/08, purdticker [EMAIL PROTECTED] wrote: Hey I got it working! I forgot that I had some issues with geronimo so I reinstalled (so my driver was no longer installed in the same place my ebs-plan.xml said it was. Also, looks like the module and connector tags did need to go into application.xml. That piece of info should be updated via console when user clicks Show Plan. I'd be happy to write up a tutorial for an application-scoped database pool, how do I go about doing that? -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18139461.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18161241.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
Here is a general guidance for finding a bug - http://geronimo.apache.org/found-a-bug.html Here is the link to our JIRA (bug tracker) system - http://issues.apache.org/jira/browse/GERONIMO Thanks, Lin On Fri, Jun 27, 2008 at 2:30 PM, purdticker [EMAIL PROTECTED] wrote: Sorry what's a JIRA, and where do I submit it? Lin Sun-2 wrote: Great to know that!! Thanks for the feedback Can you open a JIRA so that we can fix the instruction in the console to remind our user that - for application scope db, a user would also need to add module and connector tags into the standard deployment desp? Here's our tutorial page -http://cwiki.apache.org/GMOxDOC21/tutorials.html. I saw other folks have been creating task JIRAs for tutorialls, for example GERONIMO-4159. Thanks, Lin On 6/26/08, purdticker [EMAIL PROTECTED] wrote: Hey I got it working! I forgot that I had some issues with geronimo so I reinstalled (so my driver was no longer installed in the same place my ebs-plan.xml said it was. Also, looks like the module and connector tags did need to go into application.xml. That piece of info should be updated via console when user clicks Show Plan. I'd be happy to write up a tutorial for an application-scoped database pool, how do I go about doing that? -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18139461.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18161241.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
On 6/25/08, purdticker [EMAIL PROTECTED] wrote:
djencks wrote:
no, you should use whatever rar you picked at the beginning. I'm not
sure if we make this very obvious, but I assume you picked one of the
oracle rars.
Actually, this is where I'm confused. When was using the wizard, I did not
use any rar. I used a jdbc jar file which I downloaded from oracle's site.
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc9201.html
ojdbc14.jar
Yes, you need the ojdbc14.jar copied to your geronimo repo. But, at
the beginning of creating the database pool, you selected a type,
right? It has a few values for oracle, like oracle thin, oracle xa,
and so on. What did you select?
If you select oracle local, then you are using the
tranql-connector-oracle-local-{version}.rar. If you select oracle XA,
then you are using the tranql-connector-oracle-xa-{version}.rar;
otherwise, you are using tranql-connector-ra-{version}.rar.
Does the show plan button generated the right rar file there based on
what you selected?
HTH,
Lin
Re: Deploying application-scoped db pool with an ear
Lin Sun-2 wrote:
Yes, you need the ojdbc14.jar copied to your geronimo repo. But, at
the beginning of creating the database pool, you selected a type,
right? It has a few values for oracle, like oracle thin, oracle xa,
and so on. What did you select?
If you select oracle local, then you are using the
tranql-connector-oracle-local-{version}.rar. If you select oracle XA,
then you are using the tranql-connector-oracle-xa-{version}.rar;
otherwise, you are using tranql-connector-ra-{version}.rar.
Does the show plan button generated the right rar file there based on
what you selected?
HTH,
Lin
I chose thin. The other drivers have been known to cause problems with
our database.
So, yes the show plan button generated the correct rar file:
tranql-connector-ra-{version}.rar.
Jarek Gawor-2 wrote:
Can you send the actual deployment descriptor which was giving you
problems?
Jarek
Sure!
geronimo-application.xml:
?xml version=1.0 encoding=UTF-8 standalone=yes?
app:application
xmlns:conn=http://geronimo.apache.org/xml/ns/j2ee/connector-1.2;
xmlns:dep=http://geronimo.apache.org/xml/ns/deployment-1.2;
xmlns:name=http://geronimo.apache.org/xml/ns/naming-1.2;
xmlns:ejb=http://openejb.apache.org/xml/ns/openejb-jar-2.2;
xmlns:pkgen=http://openejb.apache.org/xml/ns/pkgen-2.1;
xmlns:app=http://geronimo.apache.org/xml/ns/j2ee/application-2.0;
xmlns:sec=http://geronimo.apache.org/xml/ns/security-2.0;
xmlns:web=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1;
xmlns:pers=http://java.sun.com/xml/ns/persistence;
xmlns:client=http://geronimo.apache.org/xml/ns/j2ee/application-client-2.0;
application-name=EBSPortal
dep:environment
dep:moduleId
dep:groupIddefault/dep:groupId
dep:artifactIdEBSPortal/dep:artifactId
dep:version1.0/dep:version
dep:typecar/dep:type
/dep:moduleId
/dep:environment
app:module
app:connectortranql-connector-ra-1.4.rar/app:connector
app:alt-ddebs-plan.xml/app:alt-dd
/app:module
/app:application
--
View this message in context:
http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18138307.html
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
Perhaps I'm getting this error because something needs to be in the application.xml? I tried putting this into the application.xml: module connectortranql-connector-ra-1.4.rar/connector /module But I get this error: Distribution of module failed. See log for details. Unable to create configuration for deployment org.apache.geronimo.common.DeploymentException: Unable to create configuration for deployment at org.apache.geronimo.deployment.DeploymentContext.createTempConfiguration(DeploymentContext.java:120) -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18139012.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
Hey I got it working! I forgot that I had some issues with geronimo so I reinstalled (so my driver was no longer installed in the same place my ebs-plan.xml said it was. Also, looks like the module and connector tags did need to go into application.xml. That piece of info should be updated via console when user clicks Show Plan. I'd be happy to write up a tutorial for an application-scoped database pool, how do I go about doing that? -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18139461.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
On Jun 26, 2008, at 1:44 PM, purdticker wrote: Hey I got it working! I forgot that I had some issues with geronimo so I reinstalled (so my driver was no longer installed in the same place my ebs-plan.xml said it was. Also, looks like the module and connector tags did need to go into application.xml. That piece of info should be updated via console when user clicks Show Plan. I'd be happy to write up a tutorial for an application-scoped database pool, how do I go about doing that? Hi Purdticker, Glad to hear it. A tutorial would be great and much appreciated! To insure appropriate IP of our documentation, we request that contributors submit an Apache ICLA -- http://www.apache.org/licenses/icla.txt . After the ICLA is on file, we can grant you write access to our Wiki. Alternative is to submit documentation as a patch, attach it to a Jira issue, click the assign license to the ASF button, and have somebody incorporate the documentation. The ICLA/Wiki approach is much preferred... --kevan
Re: Deploying application-scoped db pool with an ear
Great to know that!! Thanks for the feedback Can you open a JIRA so that we can fix the instruction in the console to remind our user that - for application scope db, a user would also need to add module and connector tags into the standard deployment desp? Here's our tutorial page -http://cwiki.apache.org/GMOxDOC21/tutorials.html. I saw other folks have been creating task JIRAs for tutorialls, for example GERONIMO-4159. Thanks, Lin On 6/26/08, purdticker [EMAIL PROTECTED] wrote: Hey I got it working! I forgot that I had some issues with geronimo so I reinstalled (so my driver was no longer installed in the same place my ebs-plan.xml said it was. Also, looks like the module and connector tags did need to go into application.xml. That piece of info should be updated via console when user clicks Show Plan. I'd be happy to write up a tutorial for an application-scoped database pool, how do I go about doing that? -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18139461.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Deploying application-scoped db pool with an ear
) at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18124359.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
) at javax.management.remote.rmi.RMIConnectionImpl.doOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.access$200(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl $PrivilegedOperation.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at javax .management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(Unknown Source) at javax.management.remote.rmi.RMIConnectionImpl.invoke(Unknown Source) at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18124359.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
djencks wrote: no, you should use whatever rar you picked at the beginning. I'm not sure if we make this very obvious, but I assume you picked one of the oracle rars. Actually, this is where I'm confused. When was using the wizard, I did not use any rar. I used a jdbc jar file which I downloaded from oracle's site. http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc9201.html ojdbc14.jar djencks wrote: We should be fixing up the namespace for you. It won't hurt to use the correct namespace anyway. How do I fix the namespace? Prepend app: before module and subelements? djencks wrote: This is a remarkably obtuse error message. Does using the correct rar help at all? Which rar is the correct rar? Do I need it? The wizard never asked for a rar. -- View this message in context: http://www.nabble.com/Deploying-application-scoped-db-pool-with-an-ear-tp18124359s134p18125829.html Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deploying application-scoped db pool with an ear
We should be fixing up the namespace for you. It won't hurt to use the correct namespace anyway. How do I fix the namespace? Prepend app: before module and subelements? Can you send the actual deployment descriptor which was giving you problems? Jarek
