If you are trying to use the DataSource on the server,
you should be using new InitialContext().
JBoss does not support using a DataSource outside of the virtual
machine.
That is why your ds is actually bound at java:/MYDATASOURCE
Personally I don't see the point of using a ds in a seperate proce
Title: Message
Correct.
Here's
my oracle-ds.xml content:
xml version="1.0"
encoding="UTF-8"?>
MYDATASOURCE
jdbc:oracle:thin:@101.33.214:1521:TEST
oracle.jdbc.driver.OracleDriver
testt
test
10
100
true
org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter
Here's
my code.
Title: Message
if i'm
understanding your question properly, you define all the database information in
a datasource file which is then placed in
the
your deployment directory. (see docs/examples/jca for example data
sources)
when
jboss starts up, it reads the datasource and builds the app
Title: Message
You can use localhost as you're doing
with your weblogic stuff but better to use the configurable hostname:
jboss.bind.address
try
{ properties = new
Properties();
properties.put("java.naming.factory.initial",
"org.jnp.interfaces.NamingContextFactory");
properti
I was wonder, with
the default installation of JBOSS, what is the jndi factory lookup for a
datasource, the url, username and the password.
E.G. for
Weblogic:
private
Context getInitialContext(){
Properties properties = null; Context ctx
=null;
String
weblogic_url="t3:/
Can someone explain what scenario(s) would result in the following error?
"Could not enlist in transaction on entering meta-aware
object!javax.transaction.SystemException: enlistResource failed; - nested
throwable: (javax.resource.ResourceException: Could not enlist in
transaction on entering meta
Hi all,
I was wondering if anyone knows if it is possible to stop a recompile of all
web apps if a virtual host is added. Currently you add a virtual host by
changing
deploy\jbossweb-tomcat41.sar\META-INF\jboss-service.xml by adding the
following:
However this reloads all the services and
Forget this problem. I am nearly certain that it was caused by crossing
transaction boundaries. That is: the finder executed in one transaction,
and the sort occurred in another transaction. When I moved the sort into
the session bean doing the finding, it worked much better.
Ciao,
Jonathan O'Co
Adrian,
again, you saved me a lot of time by sending a single line
of text :-) Thank you so much ! It is really people like you who
make Jboss a better choice than other app-servers (among other things).
Regards,
Stefan
> http://sourceforge.net/tracker/index.php?func=detail&aid=744455&group_id=
http://sourceforge.net/tracker/index.php?func=detail&aid=744455&group_id=22866&atid=381174
Regards,
Adrian
On Tue, 2004-01-13 at 15:13, [EMAIL PROTECTED] wrote:
> Hi,
>
> is there a possibility to tell Jboss to redeliver
> a message N times to a MDB ? Something like:
> message.setProperty(JBOSS_
Hi,
is there a possibility to tell Jboss to redeliver
a message N times to a MDB ? Something like:
message.setProperty(JBOSS_JMS_REDELIVERY_COUNT,) ?
Thanks in advance
Stefan
---
This SF.net email is sponsored by: Perforce Software.
Perforce
Alex (Oracle of the CMP engine!),
I'm trying to get these load groups working in JBoss 3.2.2. I've
successfully set up two load groups on a CMP entity bean, "sortKeys" and
"most". sortKeys has 3 fields, and most has most, but not all, of the
other CMP fields. I have set read-ahead on my query (@
It doesn't matter how many times you post the exception
you are not adding any new information.
You need to provide more information.
Show your code or the part of it that deals with the connection.
Regards,
Adrian
On Mon, 2004-01-12 at 23:25, Sasidharan, Manoj wrote:
> Hello Adrian,
>
> This i
Alex,
That works wonderfully! Thanks. However,
this is not documented on the XDoclet site with their new 1.2 documentation.
Its also not documented in the JBoss doc set. And there has been almost
no mention of load-groups in this mailing list either. So, is there a definitive
list of @jboss tags a
Craig,
You should take a look at Marc Fleury's paper "Why I love EJBs" (should be
easy to find on jboss.org). Between the egocentric pub stories (they are
interesting too), there is a recommendation to keep the web server in the
same JVM as the EJB server. His thesis is: serialisation is the rea
Thanks for the info,
I was able to deploy all my beans in JBoss 3.2.3 by switching off the
StrictVerifier in jboss-service.xml and also changing the datasource file as
mentioned.
But currently I getting the following exception while I try to login (when
LoginContext.login() is called), which use
2 things come to mind. If you have any custom container configurations,
this has changed in 3.2. You should probably switch to the *-ds.xml
format for data pools as it is easier to manage
Shashi Kiran wrote:
Hi All,
We are planning to move our application which is already in production
env
17 matches
Mail list logo
