Rich,
I haven't had any problem connecting to MSSQL7, as well as MSSQL2000. I
believe we're using the SQL 2000 JDBC drivers from Microsoft (three jars,
msbase.jar, mssqlserver.jar, and msutil.jar), and they seem to work
for both databases. My configuration file is nearly identical to yours,
Typo: that config was for JBoss 3.2.1 and MSSQL 7.
- Original Message -
From: Michael Jara [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 02, 2003 2:43 PM
Subject: Re: [JBoss-user] Microsoft SQL Server 7 Connection Problems
Rich,
I haven't had any problem
as 1.x CMP, but I
guess I can't expect perfect backward compatibility.
Thanks!
Mike
- Original Message -
From: Alexey Loubyansky [EMAIL PROTECTED]
To: Michael Jara [EMAIL PROTECTED]
Sent: Monday, August 04, 2003 2:39 AM
Subject: Re: [JBoss-user] Re: Reentrant method call detected
I've been wrestling with a problem for almost a week now, and I'm hoping
someone may have some insight into this...
In porting our application from JBoss 2.2.2 to JBoss 3.2.1, I've found what
seems to be a major concurrency bug in JBoss. The app consists of a session
bean acting as a facade for
slipping by everyone for so
long! I really don't want to revert my app to use JBoss 2.2.2 again, so any
help is appreciated.
Thanks!
Mike
- Original Message -
From: Michael Jara [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, August 03, 2003 7:38 PM
Subject: Reentrant method call
We used JBoss with non-embeded Tomcat by simply writing a servlet that acts
as an EJB client. To do it this way, your servlet will have to log-in to
JBoss (with JAAS) at the beginning of the request, execute the request, and
then log-out again.
A concise example is right here:
I've had no problems with transactions, doing the type of thing that you
describe, in earlier versions of JBoss and CMP... I haven't dealt much with
BMP though, or JBoss versions past 2.4 beta, so maybe the issue is
different. Have you trie posting your question on the forums?
You're right,
It sounds like you are just reading data from your
entity beans throughout this transaction. Is that correct? If so,
have you tried implementing "IsModified"?
Mike
- Original Message -
From:
Kris Kristensen
To: Jboss-support ; Kris
Kristensen
Sent: Thursday, January
with both JBoss and WLS and other
app-servers, so avoiding container specific implementations would be preferred
(required).
-Kris
- Original Message -
From:
Michael Jara
To: Kris Kristensen ; Jboss-support
Sent: Friday, January 18, 2002 12:46
I don't think you should need to setRollbackOnly in this case. I beleive
database errors in CMP trigger an EJBException or a RemoteException(, I
forget which one.) Both should auto-rollback the transaction.
I've done very little EJB work since JBoss 2.2.2, but transactions
definitely worked
I'm pretty sure that's by design. XML cdata includes whitespace. If an
application chooses to ignore whitespace, I beleive DOM spec complient
parsers can auto-ignore whitespace.
It makes though that JBoss would accept whitespace in an env-entry-value
for java.lang.String, since whitespace
I beleive that's according to spec, ejb1.1 and
2.0. RuntimeException is treated as a non-application
exception.
Mike
- Original Message -
From:
Vinodh
Lakshminarayan
To: [EMAIL PROTECTED]
Sent: Thursday, January 03, 2002 3:13
AM
Subject: [JBoss-user] Runtime
I have used JBoss 2.2.2 on Win2K connected to Sybase ASE on Win2K and HP
Unix. I don't recall having to do anything special, though I did specify
CHARSET=utf8. This is what my config looks like in jboss.jcml:
mbean code=org.jboss.jdbc.XADataSourceLoader
I think that this is all explained in the manual. See the JAAS how to for
an explanation and example:
http://www.jboss.org/documentation/HTML/ch13s70.html
- Original Message -
From: storck [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 11, 2001 7:36 AM
Subject:
Assuming you're talking about persistent entity bean relationships, I don't
know of anything automatic (aside from persistence tools which cost money.)
For 1:1 relationships, you can store another entity bean's primary key in a
persistent field, and translate it into an EJBObject (via
Maybe I missed something, but I didn't think that there was any requirement
for application servers to be J2EE licensed. As I understood it, the
licensing was just to get the full compatibility suite from Sun, and to get
them to post the app server's logo on their page. There are probably
deploy together when testing?
Thanks
david jencks
On 2001.08.08 22:35:37 -0400 Michael Jara wrote:
I usually just implement my JUnit tests as standard EJB clients, one for
each EJB. Setup gets the connection, creates any required EJBs, the
test
calls methods on that EJB, and teardown
?
thanks
david jencks
On 2001.08.09 12:14:10 -0400 Michael Jara wrote:
In standalone JBoss 2.2.2, I don't actually do anything special with the
EJBs to use JUnit. To test, I deploy my jar or ear as usual. I then
run
my
JUnit test class, which is just a normal JUnit test class
I usually just implement my JUnit tests as standard EJB clients, one for
each EJB. Setup gets the connection, creates any required EJBs, the test
calls methods on that EJB, and teardown cleans up.
There is info and an extension to JUnit which is especially for testing
EJBs. I beleive that it
I recently used JavaService for JBoss 2.2.2 and standalone Tomcat. It seems
to be better than the other NT service runners that I looked at. I haven't
been able to get it to call the JBoss shutdown class (in jboss.jar)
though... I get a bunch of exceptions if I include jboss.jar in the
You will also need to remove or rename your jboss-auto.jcml. (At least,
that is true as of release 2.2.2.) If you don't do this, JBoss will look
for Hypersonic and you'll get errors on startup.
Mike
- Original Message -
From: Maraya Michael [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This is sounding like it might be a JBoss bug? I think that what you're
doing seems reasonable. I did a quick search through the archives, and I
found a couple of messages which might be similar to your problem. No
solutions were presented though, and I didn't see a bug logged on it.
If you
I haven't dealt with HTTP authentication, so I'm not sure if there are any
problems with that. But if you are using the DatabaseServerLoginModule, the
reason is probably that it caches userIDs and passwords. It's been a while
since I've looked at the code, but it might be reading the user ID +
Hmm, that does seem strange that you can serialize the home pk, but not
the handle. I'm afraid I have never used EJB handles, so I won't be much
help there. Every time I have though that I should use a handle, it has
turned out that an EJB reference (a javax.ejb.EJBObject, actually) would
work
The only way to pass something by reference, sort of, in EJB is to use a
remote object. You create an interface for your object which implements
Remote, use that as a parameter in the EJB, and then send int an instance of
that remote object's implementation. This way, the actual object will sit
Passivation should definitely not kill a stateful session bean. (Does JBoss
do this? So far, I haven't deployed anything in JBoss that is idle for that
long a period.) However, I wouldn't be surprised if JBoss periodically
aged-out unused stateful session beans. I think that most good app
I needed to persist some arrays as part of an entity bean too. I was
formerly using Orion, which does that automatically. With JBoss, it looks
like you have to do it one of three ways:
1. Save it yourself using JDBC to write to another table, keyed to your
bean. (requires a certain amount of
I haven't done much experimenting with performance settings, but you might
be able fix this with some adjustments the container cache policy. See
http://www.jboss.org/documentation/HTML/ch06s08.html, the section on
Advanced cache configuration. You might try adjusting the max-bean-age
setting.
You can look at the source code here:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/jboss/jbosssx/src/main/org/jb
oss/security/auth/spi/DatabaseServerLoginModule.java
I have used it without any problems in JBoss release 2.2.2.
Mike
- Original Message -
From: Nicolai P Guba [EMAIL
I'm trying to use "isCallerInRole" inside an EJB,
but it doesn't seem to return the correct information unless a role-link
is present. I beleive the EJB 1.1 spec says that role-link is
optional (although role-ref is required.) If role-link is
not present, the value role-ref is treated as a
?
Thanks,
Mike
- Original Message -
From: Scott M Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, July 10, 2001 9:41 PM
Subject: Re: [JBoss-user] role-link required?
Show your ejb-jar.xml descriptor.
- Original Message -
From: Michael Jara
To: [EMAIL PROTECTED
) from another business method, still it will
be
included in the transaction of calling method. Thus this way doesn't seem
to
be a good solution especially in case of getting DB connection which is
used
in many transacted business methods.
Therefore please say sth more about your solution.
Edka
I've been trying to solve a problem similar to this. In my case I'm using
Sybase and a database JAAS login module. If I leave my app client running
for several hours, which periodically polls the server via a SOAP servlet
(login-poll-logout), I eventually get an auth failed message followed by
, 2001 11:02 PM
Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
Michael Jara wrote:
I've run into a problem previously mentioned in the archives here:
http://www.mail-archive.com/jboss-user@lists.sourceforge.net/msg03141.html
Does anyone have a good workaround
]]On Behalf Of Michael Jara
|Sent: Thursday, June 28, 2001 1:05 PM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-user] LOCKING-WAITING after setRollbackOnly()
|
|
|Yes, Sybase ASE is case sensitive as to table and column names. (SQL
|keywords may be any case.) I beleive this is not unique
35 matches
Mail list logo
