+++ PersistenceManager.java 2001/07/16 02:51:46 1.2
@@ -25,7 +25,7 @@
* @author Hiram Chirino ([EMAIL PROTECTED])
* @author Paul Kendall ([EMAIL PROTECTED])
*
- * @version $Revision: 1.1 $
+ * @version $Revision: 1.2 $
*/
public interface PersistenceManager {
1.2
User: chirino
Date: 01/07/15 19:51:44
Modified:src/build build.xml
Log:
Moved the rest of JBossMQ over to log4j logging.
- The jbossmq-client.jar now includes a log4j.properties which sets up the logging
subsystems on the client side. To chanage the logging levels, just place
User: chirino
Date: 01/07/15 19:51:44
Removed: src/client jbossmq.properties
Log:
Moved the rest of JBossMQ over to log4j logging.
- The jbossmq-client.jar now includes a log4j.properties which sets up the logging
subsystems on the client side. To chanage the logging levels, j
User: chirino
Date: 01/07/15 19:41:14
jbossmq/src/resources - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
Jason,
then I have a feeling that this could have something to do with the changes
that I recently made to the threading model that JBossMQ uses.
What's the easiest way you think I could reproduce the bug on my systems??
Regards,
Hiram
>From: Jason Dillon <[EMAIL PROTECTED]>
>Reply-To: [EMAI
[disp/TradingPartner] at
com.commercequest.disp.servlet.TradingPartnerServlet.doEJBDelete(Unknown
Source)
[disp/TradingPartner] at
com.commercequest.disp.servlet.TradingPartnerServlet.service(Unknown Source)
.
Regards,
Hiram
>From: "Hiram Chirino" <[EMAIL PROTECTED]>
>Repl
User: chirino
Date: 01/07/10 20:49:42
Modified:src/examples cluster-run.bat
Log:
Moved the jbossmq-cluster.xml to the client directory since it is only used by
clients.
Revision ChangesPath
1.2 +10 -1 jbossmq/src/examples/cluster-run.bat
Index: cluster-r
User: chirino
Date: 01/07/10 20:49:42
Added: src/client jbossmq-cluster.xml
Log:
Moved the jbossmq-cluster.xml to the client directory since it is only used by
clients.
Revision ChangesPath
1.1 jbossmq/src/client/jbossmq-cluster.xml
Index: jboss
User: chirino
Date: 01/07/10 20:49:42
Removed: src/etc/conf/default jbossmq-cluster.xml
Log:
Moved the jbossmq-cluster.xml to the client directory since it is only used by
clients.
___
Jboss-development mailing list
[EMAIL PROTECTED]
ht
User: chirino
Date: 01/07/10 20:38:56
Modified:src/etc/conf/default jboss.jcml
Log:
Added back the default queues and topics
Revision ChangesPath
1.6 +38 -8 jbossmq/src/etc/conf/default/jboss.jcml
Index: jboss.jcml
==
User: chirino
Date: 01/07/10 20:23:40
Modified:src/etc/conf/default jboss.jcml
Added: src/etc/conf/default jbossmq-state.xml
Log:
Change so that the state file used is configurable via JMX
Revision ChangesPath
1.5 +1 -0 jbossmq/src/etc/conf/default/jb
@@
import javax.management.*;
import java.io.File;
+import java.net.URL;
+
/**
* This class is a simple User Manager. It handles credential issues.
*
* @author Norbert Lataille ([EMAIL PROTECTED])
* @author Hiram Chirino ([EMAIL PROTECTED])
*
- * @version
User: chirino
Date: 01/07/10 20:05:58
Modified:src/build build.xml
Log:
Adjustment in rmic since the package org change some
Revision ChangesPath
1.9 +6 -9 jbossmq/src/build/build.xml
Index: build.xml
===
RefAddr object.
*
- * @author Hiram Chirino ([EMAIL PROTECTED])
+ * @author Scott M Stark ([EMAIL PROTECTED])
+ * @author Hiram Chirino ([EMAIL PROTECTED])
*
- * @version $Revision: 1.2 $
+ * @version $Revision: 1.3 $
*/
public class ObjectRefAddr extends RefAddr
User: chirino
Date: 01/07/10 19:52:16
Added: src/main/org/jbossmq/pm/file MessageLog.java
PersistenceManager.java
PersistenceManagerMBean.java TxLog.java
Log:
These are the 3 PersistenceManager implementations we have so far. The a
e log with the OutputStream returned by
* getOutputStream(). The EOF for the InputStream is the
* last commited point of the OutputStream.
*
* @author: Hiram Chirino ([EMAIL PROTECTED])
* @version $Revision: 1.1 $
*/
public class Integri
User: chirino
Date: 01/07/10 19:52:17
Added: src/main/org/jbossmq/pm/jdbc MessageLog.java
PersistenceManager.java
PersistenceManagerMBean.java TxLog.java
Log:
These are the 3 PersistenceManager implementations we have so far. The a
User: chirino
Date: 01/07/10 19:47:27
jbossmq/src/main/org/jbossmq/pm/file - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:47:11
jbossmq/src/main/org/jbossmq/pm/jdbc - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
class allows provides the base for user supplied persistence packages.
*
*@author Hiram Chirino ([EMAIL PROTECTED])
* @author Paul Kendall ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public interface PersistenceManager
User: chirino
Date: 01/07/10 19:46:29
jbossmq/src/main/org/jbossmq/pm/logged - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:26:25
jbossmq/src/main/org/jbossmq/il/uil - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:26:15
jbossmq/src/main/org/jbossmq/il/rmi - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:31:04
Removed: src/main/org/jbossmq/persistence IntegrityLog.java
ObjectIntegrityLog.java PersistenceManager.java
SpyMessageLog.java SpyMessageLogTester.java
SpyTxLog.java
Log:
T
User: chirino
Date: 01/07/10 19:31:42
jbossmq/src/main/org/jbossmq/pm - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:30:52
Removed: src/main/org/jbossmq/filepersistence MessageLog.java
PersistenceManager.java TxLog.java
Log:
This package has been moved under the pm package
___
Jboss-development ma
User: chirino
Date: 01/07/10 19:30:59
Removed: src/main/org/jbossmq/jdbcpersistence MessageLog.java
PersistenceManager.java TxLog.java
Log:
This package has been moved under the pm package
___
Jboss-development ma
User: chirino
Date: 01/07/10 19:29:31
Removed: src/main/org/jbossmq/multiplexor DemuxInputStream.java
MultiplexorTest.java MuxOutputStream.java
SocketMultiplexor.java StreamDemux.java
StreamMux.java
Log:
This p
*
*@author Norbert Lataille ([EMAIL PROTECTED])
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public class OILClientIL implements ClientIL, java.io.Serializable {
public void close() throws Exception
RMI implementation of the ConnectionReceiver object
*
*@author Norbert Lataille ([EMAIL PROTECTED])
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public class RMIClientIL extends java.rmi.server.UnicastRemoteObject implements
StreamDemux object.
*
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
class DemuxInputStream extends InputStream {
StreamDemux streamDemux;
short streamId;
boolean atEOF = false;
Object bufferMutex = new Object
Lataille ([EMAIL PROTECTED])
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public class UILClientIL implements ClientIL, java.io.Serializable {
public void close() throws Exception {
}
synchronized public void
*
*@author Norbert Lataille ([EMAIL PROTECTED])
*@author Hiram Chirino ([EMAIL PROTECTED])
*
*@version $Revision: 1.1 $
*/
public class JVMClientIL implements ClientIL {
// A reference to the connection
Connection connection;
// Are we running
;
import org.jbossmq.ReceiveRequest;
import org.jbossmq.SpyDestination;
/**
*This interface defines the methods that the server can make
* asynchronouly to a client. (ie. to deliver messages)
*
*@author Hiram Chirino ([EMAIL PROTECTED])
*@author Norbert Lataille ([EMAIL
User: chirino
Date: 01/07/10 19:26:04
jbossmq/src/main/org/jbossmq/il/oil - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:26:40
jbossmq/src/main/org/jbossmq/il/uil/multiplexor - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:25:53
jbossmq/src/main/org/jbossmq/il/jvm - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:25:14
Removed: src/main/org/jbossmq/distributed/interfaces
ConnectionReceiver.java
ConnectionReceiverSetup.java
DistributedConnectionFactory.java
DistributedC
User: chirino
Date: 01/07/10 19:25:15
Removed: src/main/org/jbossmq/distributed/server
ConnectionReceiverINVM.java
ConnectionReceiverOIL.java
ConnectionReceiverOILClient.java
ConnectionRecei
User: chirino
Date: 01/07/10 19:25:37
jbossmq/src/main/org/jbossmq/il - New directory
___
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
User: chirino
Date: 01/07/10 19:07:40
Modified:src/etc/conf/default jboss.jcml jndi.properties
Removed: src/etc/conf/default jbossmq.properties jbossmq.xml
Log:
JBossMQ is now tottaly configured via JMX. Changing config files to reflect that
Revision ChangesPath
User: chirino
Date: 01/07/10 19:05:10
Modified:src/examples TestClient.java SampleUtilities.java run.bat
Log:
Adjusted where the client classpath and what the where the connection factories are
named in JNDI
Revision ChangesPath
1.3 +2 -2 jbossmq/src/example
User: chirino
Date: 01/07/10 19:03:16
Added: src/client jndi.properties jbossmq.properties
Log:
Adding these files here since client need them in thier CLASSPATH
Revision ChangesPath
1.1 jbossmq/src/client/jndi.properties
Index: jndi.properties
simple
>autoconfig, that would setup a PrintLogger or NullLogger where Log4j was
>not
>available on the client side.
>
>Either way, the JBossMQ code should use a more robust logging system. I
>was
>going to blanket replace all of the logging in JBossMQ with Log4j until I
&
BossMQ and Log4j
>Date: Mon, 9 Jul 2001 23:16:44 -0700
>
>Log4j will be configured as a service of JBoss.
>
>- Original Message -
>From: "Hiram Chirino" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, July 09, 2001 10:34 PM
>
Jul 2001 23:16:44 -0700
>
>Log4j will be configured as a service of JBoss.
>
>- Original Message -
>From: "Hiram Chirino" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, July 09, 2001 10:34 PM
>Subject: Re: [JBoss-dev] JBossMQ and Lo
Ah... I did not know that! I've allready moved most of the server over to
log4j. Can I just assume that log4j will be confiurged for me by the
client??
Regards,
Hiram
>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev]
Talking about spooky cache problems, I've run into this problem:
I disable the cache by using the 'NoPassivationCachePolicy' and Commit
option 'C'. I create a new bean instance. Later I try to remove it but I
fail (If you guys want, I'll get you guys a stack trace). I am workin
around the
The OIL (stands for Optimized Invocation Layer). Just means that we use a
custom socket level protocol to talk to the server. Every connection
established uses 2 sockets (#1 for the client to talked to the server, and
#2 for the server to 'push' async messages to the client). The seconds
s
Talking about pools, While looking at the ASF stuff, it looks like every
depolyed MDB gets it's own Thread Pool.. I have a feeling that this is NOT
how it's soposed to be.
Regards,
Hiram
>From: "marc fleury" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject:
>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev] Two issues with MDB/ASF
>Date: Tue, 26 Jun 2001 13:49:10 -0700
>
>These are gone. See the last reply to Hiram's cleanup work.
>All that remains is a trivial leak of ASF Thr
le problem is that there
>appears
>to be a leak of "ASF Session Pool Threads" objects as the number
>of these shown on by the Info mbean listThreadDump keeps increasing
>with each run.
>
>What classes in the jboss module are required to use the latest jbossmq
>modu
t;24: org.jboss.util.WorkerQueue.getJobImpl
>
>HSQL
>10: org.hsql.ServerConnection.run(ServerConnection.java:53)
>
>- Original Message -
>From: "Hiram Chirino" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Thursday, June 21, 2001 10:31 PM
>Subject:
Yo, dude check out the title, that's the jndi.properties in the jbossmq
tree. The only folks doing JNDI lookups in the standalone jbossmq are the
clients that are running as separate processes anyways.
Regards,
Hiram
>On Sun, 24 Jun 2001, marc fleury wrote:
>
> > | User: chirino
> > | Date:
Ok, I think that JBossMQ is stable again. What -r tag name should I use
with cvs to get the 2.4 branch??
Regards,
Hiram
>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "JBoss Dev" <[EMAIL PROTECTED]>
>Subject: [JBoss-dev] Merging a JBossMQ to 2.4
>Date: Sat, 23 J
gt;Subject: Re: [JBoss-dev] JMS thread usage
>Date: Sun, 24 Jun 2001 23:10:28 +0200 (CEST)
>
>On Fri, 22 Jun 2001, Hiram Chirino wrote:
>
> > Well, there's nothing like being embarsed to get my lazy but workin.
> >
> > I've allready commited some severa
I feel that t is easier to maintain code that uses explicit imports, I
don't have to go hunting to find out in what jar/directory the "Foo" class
is at.
Regards,
Hiram
>From: "Matt Veitas" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: [JBoss-dev] Reasons
One of the test in the test suite is now failing.. Let me track that bug
down and then it will be ok.
Regards,
Hiram
>From: "Scott M Stark" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: "JBoss Dev" <[EMAIL PROTECTED]>
>Subject: [JBoss-dev] Merging a JBossMQ to 2.4
>Date: Sat, 23 Jun 2
lt;[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: Re: [JBoss-dev] JMS thread usage
>Date: Sat, 23 Jun 2001 00:03:42 -0700
>
>By sending a SIGQUIT go the IBM VM. The Sun VM is crashing
>after 1 or 2 dumps so I am using the IBM 1.3 v
r.ConnectionReceiverOIL.run(ConnectionReceiverO
IL.java:97)
>
> JMS ASF
> 24: org.jboss.jms.asf.ThreadPool$Slot.waitWhileEmpty(ThreadPool.java:181)
>
> Passivator Threads
> 24: org.jboss.util.WorkerQueue.getJobImpl
>
> HSQL
> 10: org.hsql.ServerConnection.run(ServerConnectio
ork.TestResult.run(TestResult.java:103)
> at junit.framework.TestCase.run(TestCase.java:120)
> at junit.framework.TestSuite.run(TestSuite.java:144)
> at
>org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:209)
> at
>org.apache.tools.ant.t
I have updated jboss to to include the latest fixes that I have just maked
to jbossqm for those threading issues.
Could you update the jars in the jbosstest module and test again and let me
know if the situation improved?
Regards,
Hiram
- Original Message -
From: "Scott M Stark" <[EMAIL
AIL PROTECTED]>
Sent: Thursday, June 21, 2001 10:57 PM
Subject: Re: [JBoss-dev] JMS thread usage
> Chris' nightly test runs have only been failing with these OutOfMemory
> exceptions for the last couple of nights. Either it was a recent change
> that caused this or a recently a
I'm embarased.
I'll look into it right away. Since the JMS client and server stuff is
running in the same VM when using ASF I should be able to get rid of the
socket calls and thus free up the threads that are polling the sockets.
I'll also see if I can get rid of the SpySession Threads when us
Eric,
The development list for the jboss JMS implementation is
[EMAIL PROTECTED] <[EMAIL PROTECTED]>
Regards,
Hiram
- Original Message -
From: "Eric Chiu" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, June 02, 2001 5:45 PM
Subject: [JBoss-dev] Re: Jboss-development
> I'm
My vote on the issue is turn the feature OFF by default.
A JMS queue is like a database table: I don't want the thing getting
created and destroyed every time I deploy and undeploy a bean. This is
mainly doe to the time indepenent processing "feature" JMS usually gives
you. If you are creating
I totally agree with peter. If the container takes the
"Dups-ok-acknowledge" setting and implements it just like the
"Auto-acknowledge" setting, the container's contract with the client would
still be vaild.
Regards,
Hiram
- Original Message -
From: "Peter Antman" <[EMAIL PROTECTED]>
To
Yes, that "jboss/src/main/org/jboss/jms/jndi/JBossMQProvider.java" is so
that JBossMQ can deliver messages to
the MDBs. But if you wish to use SonicMQ from your EJBs that way that it is
documented in the EJB 2.0 spec, then
you ne to write a resource adapter for SonicMQ also. Take a look at the
o
It would be for application development. Say I'm not the Buisness Analyst
(BA), but I know that the BA has a shit load of buisness rules he wants to
get implemented... It might be easier for me to hook in a Rules Engine and
then explain to the BA how to use the Rules Engine so that he can setup
601 - 669 of 669 matches
Mail list logo
