Sorry for the delay in looking into this. Some of the
examples had a mistake, namely xa-tx-datasource tags instead
of xa-datasource. I fixed the ones I found in cvs.
Thank you, David, for investigating the issue and fixing what you found.
I'll try again today and post my results.
You
Hello again everyone,
If anyone can deploy an XA data source on SQL Server 2000, please tell me
about it. No matter what I try, my data source is never bound in JNDI (as
viewed in the jmx-console in the JCA section) and therefore is never usable
by any application. I'm growing increasingly
David,
Have you found anything out of the ordinary with the files that I sent or
JBoss itself? Thanks for looking into this.
Craig
---
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las
The log output you show shouldn't get in the way of anything
except maybe jsr 77 monitoring features. Can you set the log
level to at least debug and show the server.log for the
*-ds.xml file being deployed? I don't have any XADataSources
handy to try this with.
David,
Thanks for the
Greetings everyone,
I have never successfully deployed a *-ds.xml file on 3.2.0 for an XA data
source. I've failed again today with 3.2.0 RC4. I'm using the JSQLConnect
driver to connect to MS SQL Server 2000. The *-ds.xml file is attached. Of
course, I've replaced the relevant property
Hello,
I'm using JBoss 3.2.0 RC3, and I'm trying to deploy a *-ds.xml file for a
SQL Server XA datasource using the JSQLConnect driver. I've taken the JBoss
3.2 examples from the JSQLConnect 3.30 driver, and I've modified them for my
desired JNDI name, server name, database name and
Title: Message
I'm
not sure about how you would like to work with user names and passwords.
However, I do believe that you should not include mdb-client-id on JBoss
3.x. I noticed that you already have mdb-subscription-id; try
removing mdb-client-id.
Craig
-Original
I've been migrating an application from 2.4.x to 3.0.x. The users here have
been very helpful. I hope that with one more answer, I can complete the
migration.
In 2.4.x, we deployed our EAR to the deploy directory and our MBeans to the
lib directory. In jboss.jcml, we could place our MBean
I spoke too soon; I have not found enough information to create a working
durable subscription configuration. I would appreciate very much if someone
would post working examples of the relevant files or would provide some
instructions. I just can't tell at this point if I have one thing wrong in
I want to migrate my application from 2.4.10 to 3.0.x. I have a few durable
topics to configure, but I can't find instructions for doing so. I've
looked at jbossmq-destinations-service.xml, jbossmq-service.xml and
jms-service.xml. I've searched this list and the JMS forum at jboss.org.
However,
I forgot to include jbossmq-state.xml in the list of files that I've
inspected.
Thanks again,
Craig
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code
Many thanks to all who replied. I've been very busy, but I have read the
responses. If we change our approach to this problem, I'll try to remember
to post the results to the list.
Regards,
Craig
---
This SF.NET email is sponsored by:
Greetings,
We're using JBoss 2.4.10. One of my colleagues has implemented an MBean
that spawns a thread to periodically poll a database table for new rows
based on criteria that we control. I see two disadvantages: one, when we
hot redeploy our EAR, the MBean can no longer communicate with
My colleague tells me that the home interface is cached in the MBean.
Although the home interface has not changed, is the caching the source of
the problem? Since the MBean is not in the EAR, we generally shut down
JBoss, redeploy the EAR, restart JBoss; the MBean is then reinitialized and
can
Christian,
Feel free to try this very simple test EAR (attached) that I developed for
the jboss-user thread entitled EAR works in 2.4.10 but not in 3.0.6. It
deploys for me on 3.2.0RC1. Please let me know if you have any problems or
questions.
Craig
us_state_service.ear
Description: Binary
Rod,
As I mentioned in our private email exchange, here are my results for the
community to see. Thanks for investigating with me. Thanks also to others
who replied.
In the manifest of the EJB JAR file, I referred to my library JARs relative
to the EJB instead of relative to the root of the
Rod,
The way that our Ant build script has always been configured is below. I
believe that we're doing what you recommend, yet I did not resolve my
problem with JBoss 3.x until I referred to library JARs in manifest.txt
relative to the EJB JARs instead of the EAR root. I'm sharing this
Frederik,
Thanks for posting your test. By inspection and based on my earlier post
(which arrived out of order for me) showing my BEFORE and AFTER scenarios, I
believe your test will work. (I'll try it as soon as I have the chance).
Below are some observations on the structure of our EAR files,
Great, Frederik and Rod! Let me summarize what we've learned: all seems
well if you follow the advice in this FAQ
(http://www.jboss.org/faq.jsp#FAQ-BEANDEV-NORMALJARS) about library JARS,
AND in the EJB JARs' manifest file you specify paths ***relative to the
EJBs***, NOT relative to the root of
As promised, I tried my test application on 2.4.10. Using the EAR structure
below, I can deploy on both 2.4.10 and 3.x.
root
META-INF
application.xml
MANIFEST.MF
ejb
us_state_service.jar
lib
apogent-common.jar
eif-ejb.jar
/root
As I noted
Fredrik,
As Rod replied, we already know what we should do according to the
documentation/FAQs. However, those rules/steps simply don't work for me on
JBoss 3.0.4, 3.0.5, 3.0.6, 3.2RC1. I've tried an existing application that
deploys on 2.4.10, and I've tried a very carefully built, very simple
Here's the structure of my EAR file:
root
META-INF
MANIFEST.MF
application.xml
ejb
BatchAddition.jar
...
eif-service_locator.jar
/root
Please, does anyone have any ideas why the EAR structure above works in
2.4.x but not in 3.0.5,
Rod,
Attached is my application.xml.
The floating JAR, eif-service_locator.jar, does not have a module type; it's
a JAR that contains dependencies for many of the EJBs. Check this reference
(http://www.jboss.org/faq.jsp#FAQ-BEANDEV-NORMALJARS) for how I have my EAR
structured. All EJBs listed
Thanks, Rod, for taking the time to investigate with me. I've just finished
trying a contrived application on 3.0.6, but it failed to deploy as well.
Perhaps I'll try 3.0.4.
JBoss gurus, please help!!!
Craig
---
This SF.NET email is
3.0.4 did not work either. Like Rod, the EAR will work if I include all
library JARs in application.xml as java modules. According to the FAQ
that I cited earlier (http://www.jboss.org/faq.jsp#FAQ-BEANDEV-NORMALJARS),
though, the use of application.xml is NOT appropriate. However, I know of
no
Let me add more information.
- Win XP Pro SP1 + hotfixes
- Java 2 SDK 1.4.1_01
- created custom server config from default
I tried 3.2RC1 and received the same errors as in my original post. I plan
to try 3.0.5 as soon as I can. Also, I seek to know the *correct* way to
deploy the EAR that I
3.0.5 failed in the same way that 3.0.6 and 3.2RC1 have failed. Please
share any thoughts that you may have.
Thanks,
Craig
---
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
Hello everyone,
Here's the structure of my EAR file:
root
META-INF
MANIFEST.MF
application.xml
ejb
BatchAddition.jar
...
eif-service_locator.jar
/root
When I deploy my EAR and start JBoss 3.0.6, I receive the following
warnings, which
Many thanks to Scott and the rest of the JBoss team!!! I'm very much
looking forward to the 3.2.0 release. I want to try RC1, but I haven't been
able to download it yet. I've received messages that the connection has
been reset by the peer. Any thoughts?
Thanks again,
Craig
- what is the best (i.e. most stable) JDBC Driver for
connecting to MS SQL Server (free or commercial)
JSQLConnect (http://www.j-netdirect.com/JSQLFeatures.html) has worked best
for us. We had a few problems with the Opta
(http://www.inetsoftware.de/English/produkte/OPTA/default.htm) drivers.
Jim,
I currently do not unit test either Entity or Session Beans. Entity Beans
are trivial to write, and I trust that the application server will persist
them as advertised. To unit test Session Beans would require that they be
deployed. Since deployment complicates unit testing and
Igor,
I'm not sure whether I consider the problem that you describe as one for
unit tests, at least not for me and not now. I'll have to think about it
more when I'm doing EJB work again. So far, the Session Beans that I've
coded have not suffered from this problem, somewhat to my surprise: I
Jim,
I've never written a web app. If I planned to write one, I would do my best
to separate the user interface parts from the business logic parts from the
persistence layer parts. I know that it may not be entirely possible to
achieve a complete separation of layers, but we should strive to
Its finally working . Thanks to Boris for pointing me to jvm options.
I'm glad to hear that you've solved your problems.
4) use Thread.sleep(100) -- if the MDB is iterating over long
collections
Please elaborate: explicit thread control is not allowed/highly discouraged
in EJBs. Perhaps
We really can't use the 1.4 exception class because we need
to support
1.3 for a long time.
-dain
At my place, we write exception classes patterned after the
changes to SDK 1.4.x so that we can use them in either 1.3.x
or 1.4.x. We based our work on Item 43 of Joshua Bloch's
-Original Message-
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 27, 2002 1:12 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Running Junit tests inside the same VM
...
Junit internals suck. I would love to rewrite it, but don't
have the time.
, September 27, 2002 12:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-user] Running Junit tests inside the same VM
Demyanovich, Craig - Apogent wrote:
-Original Message-
From: Dain Sundstrom [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 27, 2002 1:12 AM
To: [EMAIL PROTECTED
You have found all I did when I last looked. Then, though, I was using
JBuilder 5 Enterprise. Sorry I can't offer another option to try or place
to look.
Beware of JBuilder and EJB development, unless the severe shortcomings of
version 5 have been addressed by version 7. In version 5
Clients can do a JNDI lookup on a UserTransaction suitable for client use.
You can see the UserTransaction listed in the Global JNDI Namespace of the
JNDIView service available from the Agent View management interface. This
is also documented in the JBoss documentation that can be purchased for
I'm using JBoss 2.4.8 with Tyrex as the TM. In the Tyrex domain.xml file, I
set the timeout to 360 seconds (6 minutes). In code, I set the transaction
timeout to 600 seconds (10 minutes). After 120 seconds (2 minutes), the
default timeout for Tyrex (http://tyrex.exolab.org/configuration.html),
I'm using JBoss 2.4.8 and Tyrex, and I have something
like this in a message-driven bean:
someMethod(...) {
try {
...
conn1 = connectionToDataSource(name1);
conn2 = connectionToDataSource(name2);
...
data = readData(conn1, ...);
trans.begin();
.
The behavior here should not depend in any way on which tx
manager you are using.
Thanks
david jencks
On 2002.08.21 12:55:48 -0400 Demyanovich, Craig - Apogent wrote:
I'm using JBoss 2.4.8 and Tyrex, and I have something
like this in a message-driven bean:
someMethod(...) {
try
If I want to use Tyrex instead of the JBoss TM, what configuration must be
done in jboss.jcml, and what configuration must be done in domain.xml?
Unless I've been looking in all of the wrong places, the documentation on
how to use JBoss and Tyrex together is lacking or incomplete at best. I
I had the same problem and when I changed
lookup(TopicConnectionFactory) to lookup(ConnectionFactory)
it worked for jboss3.
Mark made the original post on my behalf, as my subscription request was
taking quite some time. Now that I'm here, let me carry on the discussion.
I neglected to
44 matches
Mail list logo
