Hi,
according to the EJB 2.1 spec ejbRemove should be called either if remove is called on
the bean OR if the statefull session times out. (7.6 figure 6).
As far as I have been able to find out this is not the case in jboss 3.2.3.
1. ejbRemove is called from the Statefull PM (in
On 21 Nov, Jason Dillon wrote:
Bah... this sucks. Can't we get one build to function for both? Or do
we have to build a 1.3 and 1.4 version? Blah :(
Its the same for jaas. A version build för 1.4 will NOT work on 1.3,
because the JAAS classes will be missing!
//Peter
A side note, any
On 21 Nov, Scott M Stark wrote:
I'll look into what the issues are with building under 1.4 and running with 1.3.
This should
be possible and is something we need to work towards.
Great. As for the jaas stuff, I do think that it does not matter if the
1.3 jaas stuff is also build when building
On 18 Sep, David Jencks wrote:
[...]
(I think) the jars in lib rather than server/[conf]/lib are not going to be
versionable since they are used in jboss startup to set up the versioning
mechanism. Stuff in server/[conf]/lib should be versionable by deploying
it in a .sar, although you may
On 12 Sep, Scott M Stark wrote:
There is a service that does this in the testsuite. XMLLoginConfigs chain so
that multiple configs can be active.
Ah, that was a neat one, but one thing I do not get: say the
mysql-service.xml is installed and uses this scheme to install a new
root config with
Well, add to that: its is somethimes much better to be able to specify
the auth XML in the *-service.xml file and not have to have an external
file to load, this could ofcourse be fixed easilly by letting
XMLLoginConfig also take an Element to be set up from.
//Peter
On 12 Sep, Scott M Stark
: /home/pra/src/rw/jboss-all/build/build.xml
Detected Java version: 1.3 in: /usr/local/lib/jdk1.3.1/jre
Detected OS: Linux
[...]
compile-mbean-sources:
[xdoclet] Generating Javadoc
[xdoclet] Javadoc args: /usr/local/lib/jdk1.3.1/jre/../bin/javadoc
-private -c
lasspath /home/pra/src/rw
On 6 Mar, David Jencks wrote:
On 2002.03.06 10:03:30 -0500 [EMAIL PROTECTED] wrote:
On 6 Mar, David Jencks wrote:
I no longer have the clean checkout but I have never had this problem
with
many recompiles without cleans. I'm not sure what else I can do about
this.
Hi, changed
wanted to remove
the that one from the normal run I tought it would do to have it when
you run -Dtest=jbossmq test
Maybe I will change it later.
//Peter
xxxUnitTestCase
or
xxxStressTestCase
david jencks
On 2002.03.06 12:33:31 -0500 Peter Antman wrote:
User: pra
Date: 02/03/06
On 22 Feb, Scott M Stark wrote:
[...]
The new resource adaptor security will only be implemented in 3.x. The
current 2.4 code base does not matter.
Well, a connection hold in vm may possibly be used by different threads,
but the connection should, in case it was started with userid/pwd,
On 22 Feb, David Jencks wrote:
On 2002.02.22 14:50:00 -0500 [EMAIL PROTECTED] wrote:
[...]
(Do you remember our discussions earlier about this. I did infact
implement a DirContext impelementation and a DirContext JCA adapter wich
plugged in both as a JAAS LoginModule and made it easy to
On 22 Feb, Alexander Horuzhiy wrote:
Hi,
you have plane to implementing JDBC StateManager?
No, perhaps make it more pluggable. Then I would probably make an
DirContext/Ladap one...but thats for later. First we need to get
autentication pluggable.
//Peter
//Alexander
Hi all, but mostly Scott I guess ;-)
I am experimentally adding JAAS support for JBossMQ to handle
autentication and autorization. And I have some problem with how to
propagate and keep the principall around for the rmi and jvm invokation
layers (for OIL and OUL it seems easy beacuse you can use
On 22 Feb, Scott M Stark wrote:
I tried to look at the documentation for how to set up a JAAS aware
client, and then looked somewhat into the proxy, jrmp and
SecurityInterceptor code, and guess what, it looks to mee as we are
sending both the principall and the credentials on every
Hi, one reason it is taking so long is that it is testing all IL:s (I
thingk). If you do this move please split this test and run at least a
test on the OIL and preferably also the JVM IL, since these are the
defaults used by everyone.
//Peter
On 20 Feb, marc fleury wrote:
|to have testcases
On 16 Feb, Jason Dillon wrote:
Is there anything we can do to speed it up any?
Well, actually it is not slow enough ;-) since it does not catch all
bugs as it is setup today. To chatch current buggs in threading you have
to have testcases that send up to 100 000 messages, sometimes taking up
to
[The background to this mail, may be found in the message forum:
http://www.jboss.org/forums/thread.jsp?forum=48thread=4209]
Hi, Hiram and you other JBossMQ hackers. I have made a try to
reimplement the ServerSession(Pool) stuff so that it should potentially
become really (;-)) spec comliant and
On 23 Okt, Hiram Chirino wrote:
Hi Guys..
I've been working on a cache layer for JBossMQ and it's about 95% done.
What will this change in JBossMQ?? Well, it will allow you to send it
larger amounts of messages/larger messages with out running into Out of
Memory problems in the VM.
In reference to:
http://www.jboss.org/forums/thread.jsp?forum=48thread=3150
My first cut at this is that it has to do with the pool. The exception
happens when the pool is trying to clean up and the XA resource is no
longer tied to any sessionID. (any one interested in seeing the trace,
it's 1
:
java:user/sec1 (implicit the way the Jaas stuf works today)
java:comp/user (pointing to user data - a DirContext - for the currently
authenticated subject.)
Logged in as pra, with this in the servlet:
DirContext c = (DirContext)ctx.lookup(java:comp/env/user);
if (c!=null) {
System.out.println
Hi!
I'm using JBoss 2.4.3 and MDB's, which are connected to MQSeries. I
found out that when MQSeries is going down the MDB is not trying to
reconnect. The problem is that in
org.jboss.ejb.plugins.jms.JMSContainerInvoker.ExceptionListenerImpl the
notStoped (which should probably be
On 26 Sep, marc fleury wrote:
|A filesystem should just be another service just like JDBC. Ideally it
|should be
|accessed like any other securable managed resource via a resource factory.
|This
|is the direction we should be moving in.
interesting... yes, you are probably right here.
On 20 Sep, Sacha Labourey wrote:
Should instance pooling for SLSB MDB backported to Branch_2_4?
I think so, because the current behaviour is rather confusing (and
probably not spec compliant). But that's my 2c.
//Peter
___
Jboss-development
On 11 Sep, Jason Dillon wrote:
Should setRollbackOnly on an MDB with NotSupported simply be ignored rather
than throwing an exception?
If not, then an MDB would have to be written to handle exceptions for these
cases when it is configured to be Requires or NotSupported... which seems
like
On 19 Aug, David Jencks wrote:
Maybe if I try hard enough I can be a lttle clearer ;-)
Oh, I must have been writing in my sleep...
Lets say you are using jms in a situation where in a transaction you want
to do some work in a database and send a jms message. Normally this
requires 2 phase
On 19 Aug, David Jencks wrote:
Hi,
I'm planning to move the two jboss jca-jdbc resource adapter wrappers to
the connector module soon. I'm wondering if it would be appropriate to
move the jms-ra connector there also? I think that it should either be
with the other connectors or with
On 19 Aug, Jason Dillon wrote:
I'm planning to move the two jboss jca-jdbc resource adapter wrappers to
the connector module soon. I'm wondering if it would be appropriate to
move the jms-ra connector there also? I think that it should either be
with the other connectors or with jboss.mq.
On 8 Aug, Jason Dillon wrote:
Since JmsSession nor JmsManagedConnection needs to be synchronized to call
the underlying TopicSession or QueueSession object, lets drop it and let the
impl descide if it needs to be sync'd.
What do ya think.
OK for me.
//Peter
--jason
On Wed, 8 Aug
Hi, just a sidenote: deploying two MDB ataching to the same destination
has unspecifyed behaviour if a remember the EJB 2.0 spec correct - so we
are spec compliant ;-)
But it would be really good if this could be fixed.
If I remember correct we also have a problem with durable topics. I.e
On 7 Aug, Hiram Chirino wrote:
From: Jason Dillon [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] Retuning JMS RA connections?
Date: Tue, 7 Aug 2001 15:51:00 -0700 (PDT)
That sees like a bug, but it is important to remember that whats
On 7 Aug, Jason Dillon wrote:
That sees like a bug, but it is important to remember that whats
actually is pooled is the the session, and that should be closed after
each method invocation.
I was not closing the session properly.
Should the connection close all of its sessions?
No it
On 6 Aug, Jason Dillon wrote:
Where does a JMS RA managed connection get returned? I just ran into:
JmsXA [RMI TCP Connection(12)-192.168.0.124] INFO - Pool
org.jboss.jms.ra.JmsManagedConnectionFactory-1 is full (10/10)!
JmsXA [RMI TCP Connection(12)-192.168.0.124] INFO - Pool
On 7 Aug, Jason Dillon wrote:
I might not be closing the session property in some cases. On a related
note, there is an example from sun:
http://java.sun.com/products/jms/tutorial/examples/client_ses_mdb/PublisherBean.java
which calls close() on the connection in ejbRemove(), but the
On 24 Jul, Jason Dillon wrote:
On Tue, 24 Jul 2001, Peter Antman wrote:
On 24 Jul, Jason Dillon wrote:
Well, that depends on taste. When the JMS RA was written it was mean to
not be dependant on JBoss at all, but should be possible to use in any
App server. There was one (easy to fix
On 29 Jun, Jason Dillon wrote:
I am currently running everything on the same machine. I am correct in
beliving that this would not be a bug in the JMS RA? I am just trying to
narrow the scope of the hunt for this problem.
As far as I can see this has to do with MDB and therefore the
On 27 Jun, Jason Dillon wrote:
Hey, I had to stop playing with build systems and get some actual work done.
I was finishing up integrating the JMS RA support, so my application has
better JMS/EJB TX integration and I started getting messages like the
snippet below. The application seems to
Hi,
sorry I misses all the fun (we have had one of our christian hollidays,
and I have been banging nails into my summer cottage ;.)).
Let first state a simple fact. We should actually disuss two things:
1. Is it a good feature to have automatic creation of destinations for
MDB when JNDI
Hi,
due to several recent questions regarding JMS, MDB on both dev and user
I tought I would sum up the status of JMS in JBoss and how pluggable
it is.
The JMS architecture of JBoss looks like this.
1. The JMS provider consists of JBossMQ. This is the part of JBoss that
implements the JMS
reside, but it should never be reached during
normal execution.
I have tried to reproduce your problem, but can not do it:
(This is with 2.2.1, but should be the same with the 2.3.x)
Undeploy:
[Auto deploy] Auto undeploy of file:/home/pra/test/amsterdam-1.2/server/deploy/m
db.jar
[J2EE Deployer
User: pra
Date: 01/05/03 13:06:38
Modified:src/main/org/jboss/test/mdb/test Main.java
Log:
Fixed close of connections, to end thread in JMS
Revision ChangesPath
1.4 +31 -7 jbosstest/src/main/org/jboss/test/mdb/test/Main.java
Index: Main.java
On 3 Maj, Saint-Martin Cécile wrote:
Hello,
I'm testing MDB with Jboss, i wrote a MDB wich destination is a durable
topic. When i stop ContainerFactoy service, Jboss clear all instances of the
MDB and it's OK.
But when i restart this service, it doesn't re-create the pool of MDB
User: pra
Date: 01/04/26 13:57:42
jboss/src/main/org/jboss/jms/ra - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:02:56
jboss/src/resources/org/jboss/jms/ra - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:02:14
Added: src/main/org/jboss/jms/ra/client JmsConnectionFactory.java
JmsSessionFactory.java
Log:
Added classes for a JMS connector resource adapter
Revision ChangesPath
1.1 jboss/src/main/org
User: pra
Date: 01/04/26 14:02:43
jboss/src/resources/org/jboss/jms - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:02:13
Added: src/main/org/jboss/jms/ra JmsConnectionFactoryImpl.java
JmsConnectionManager.java
JmsConnectionRequestInfo.java JmsCred.java
JmsLocalTransaction.java JmsLogger.java
User: pra
Date: 01/04/26 13:58:35
jboss/src/main/org/jboss/jms/ra/client - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:05:57
Modified:src/build build.xml
Log:
Added build stuff for JMS resource adapter; installs jms-ra.rar in deploy/lib for
default deploy
Revision ChangesPath
1.68 +16 -1 jboss/src/build/build.xml
Index: build.xml
User: pra
Date: 01/04/26 14:04:07
Added: src/resources/org/jboss/jms/ra/META-INF ra.xml
Log:
Added resources for JMS connector ra
Revision ChangesPath
1.1 jboss/src/resources/org/jboss/jms/ra/META-INF/ra.xml
Index: ra.xml
User: pra
Date: 01/04/26 14:06:54
Modified:src/etc/conf/default jboss.jcml
Log:
Added entry for JMS connector ra with TX support
Revision ChangesPath
1.27 +34 -0 jboss/src/etc/conf/default/jboss.jcml
Index: jboss.jcml
User: pra
Date: 01/04/26 14:09:54
jbosstest/src/main/org/jboss/test/jmsra/test - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:09:32
jbosstest/src/main/org/jboss/test/jmsra - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:09:54
jbosstest/src/main/org/jboss/test/jmsra/bean - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:11:59
jbosstest/src/resources/jmsra - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:12:40
jbosstest/src/resources/jmsra/META-INF - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: pra
Date: 01/04/26 14:18:53
Added: src/main/org/jboss/test/jmsra/test AllJUnitTest.java
TestRa.java
Log:
Added small testsuite for JMS Connector ra, will only work against the current cvs
JBoss
Revision ChangesPath
1.1
User: pra
Date: 01/04/26 14:18:53
Added: src/resources/jmsra/META-INF ejb-jar.xml jboss.xml
Log:
Added small testsuite for JMS Connector ra, will only work against the current cvs
JBoss
Revision ChangesPath
1.1 jbosstest/src/resources/jmsra/META
User: pra
Date: 01/04/26 14:18:52
Added: src/bin jmsratest.sh
Log:
Added small testsuite for JMS Connector ra, will only work against the current cvs
JBoss
Revision ChangesPath
1.1 jbosstest/src/bin/jmsratest.sh
Index: jmsratest.sh
User: pra
Date: 01/04/26 14:18:52
Added: src/main/org/jboss/test/jmsra/bean Publisher.java
PublisherBean.java PublisherCMP.java
PublisherCMPBean.java PublisherCMPHome.java
PublisherHome.java
User: pra
Date: 01/04/26 14:18:53
Added: src/resources/jmsra client.policy jndi.properties
Log:
Added small testsuite for JMS Connector ra, will only work against the current cvs
JBoss
Revision ChangesPath
1.1 jbosstest/src/resources/jmsra
User: pra
Date: 01/04/26 14:18:52
Modified:src/build build.xml
Log:
Added small testsuite for JMS Connector ra, will only work against the current cvs
JBoss
Revision ChangesPath
1.24 +16 -0 jbosstest/src/build/build.xml
Index: build.xml
User: pra
Date: 01/04/10 03:41:17
Modified:src/docs howtomdb.xml
Log:
Changed some erounous deployment descriptor examples
Revision ChangesPath
1.3 +315 -312 manual/src/docs/howtomdb.xml
Index: howtomdb.xml
62 matches
Mail list logo
