Hello,
some day ago I added a bug report at sourceforge. The first line in file
jBoss/conf/default and jboss/conf/tomcat
reads
?xml version=1.0 encoding=UTF8?
instead of
?xml version=1.0 encoding=UTF-8?
because of this jBossmq doesn't start with xerces.
The binary distribution version
Feature Requests item #453650, was opened at 2001-08-21 00:58
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=376688aid=453650group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous
On Monday, 20. August 2001 19:20, Dain Sundstrom wrote:
Thanks, checked it in.
-dain
snip
It is simply two functions
position(?2 in substring(?1 from ?3))+?3
Sorry for complaining so late, but it is not as simple as this.
position( 'findme' , 'wheretolookfor', 3) should be 0 and
Nope your right. When I first wrote the function I did not have the + ?3
at the end so it worked fine ...
Marco Ladermann wrote:
On Monday, 20. August 2001 19:20, Dain Sundstrom wrote:
Thanks, checked it in.
-dain
snip
It is simply two functions
position(?2 in substring(?1 from
Dain in server/src/main/org/jboss/ejb/plugins/cmp/ejbql/Parser.java line
66 you have an extra ';' terminating the return statement. It is causing
jikes to complain.
Found 1 semantic error compiling
/home/dave/jboss/server/src/main/org/jboss/ejb/plugins/cmp/ejbql/Parser.java:
[javac]
The bundle that I pulled down from SF :
http://prdownloads.sourceforge.net/jboss/JBoss-2.4.0.zip
contains 2 entire JBoss distribs and hence is twice
the size of a normal download...
I diffed them.
lib/ext/jboss.jar differed between them.
the one with the BETA suffix had a load of extra dirs
This does not exist in the 2.4.0 final release made yesterday.
- Original Message -
From: Schouten, Andreas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 21, 2001 12:06 AM
Subject: [JBoss-dev] bug in jbossmq.xml
Hello,
some day ago I added a bug report at
Not intended. I gues the dist target doesn't clean out any existing dirs
before creating the archive. I'll repackage it.
- Original Message -
From: Julian Gosnell [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 21, 2001 4:56 AM
Subject: Re: [JBoss-dev] 2.4.0 has been
User: starksm
Date: 01/08/21 08:37:52
Modified:src/etc/conf/default Tag: Branch_2_4 mail.properties
Log:
Don't use Simone's mail info as the default
Revision ChangesPath
No revision
No revision
1.2.4.1 +12 -6
User: starksm
Date: 01/08/21 08:57:19
Modified:src/etc/conf/default mail.properties
Log:
Change the default properties from Simone's to values that
must be customized
Revision ChangesPath
1.4 +13 -7 jboss/src/etc/conf/default/mail.properties
Index:
User: starksm
Date: 01/08/21 09:13:33
Modified:.binary.jsp
Log:
Update the size and dates of the 2.4.0 release
Revision ChangesPath
1.9 +4 -4 newsite/binary.jsp
Index: binary.jsp
The new package has been placed on sourceforge. This should appear soon
under the
Files section, but is available now via
http://prdownloads.sourceforge.net/jboss/JBoss-2.4.0.zip
- Original Message -
From: Scott M Stark [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 21,
Jason,
I'm going to combine multiple email replies into one. Please switch back to
QueuedPessimisticEJBLock. We're trying to make this the default for JBoss
since it scales better.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Is there an archive where the results of the jboss discussion on
how clustering will be implemented (and when) in JBoss?
I assume that the clustering is for horizontal load balancing, fail over,
etc.
and that vertical mechanism are already done.
Is there a summary of the discussion as to why a
-Ursprüngliche Nachricht-
Von: Richard Emberson [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 21. August 2001 18:35
An: [EMAIL PROTECTED]
Betreff: [JBoss-dev] Clustering and SOAP
Is there a summary of the discussion as to why a separate SOAP
implementation was done (zoap) rather than
I'm not sure about the clustering stuff, but ZOAP was developed before
Apache SOAP was very usable. Since apache SOAP has become more functional
ZOAP is no longer under development. Search for posts by Dr. Jung.
On 2001.08.21 12:34:58 -0400 Richard Emberson wrote:
Is there an archive where
To fully fix that bug, I recently changed the:
jbossmq\src\main\org\jbossmq\xml\XElement.java
file. JBossMQ was incorrectly rewriting the jbossmq.xml with the UTF8
string. I commited the change to the 2.4 branch.. But I don't know if it
was rebuilt and included in the jboss libs for the
User: patriot1burke
Date: 01/08/21 11:35:51
Modified:src/main/org/jboss/ejb/plugins/lock
QueuedPessimisticEJBLock.java
Log:
Needed to set tx after obtaining lock
Revision ChangesPath
1.3 +12 -9
I'm going to combine multiple email replies into one. Please switch back to
QueuedPessimisticEJBLock. We're trying to make this the default for JBoss
since it scales better.
Ok. I was not sure if one was more stable than the other.
I am using commit option B, since it might be possible
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Sent: Tuesday, August 21, 2001 4:36 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbLoad() on a modified bean w/o ejbStore()
I'm going to combine multiple email replies into
I have not seen this problem again... so far. I am running larger tests to
confirm.
--jason
On Tue, 21 Aug 2001, Bill Burke wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason
Dillon
Sent: Tuesday, August 21, 2001 4:36 PM
To:
I have pushed close to 600x3 transactions through our system and have not
run into any problems yet. Once I get to 1000x3 I will know for sure.
Looks really good so far!
--jason
On Tue, 21 Aug 2001, Jason Dillon wrote:
I have not seen this problem again... so far. I am running larger
Hi,
Is there anybody trying to make the manual build run correctly?
I give it a (painful) try.
I succeed to build a part of html and printable-html (hum simply the
preface,intro, cmp and jaws for the moment)
I choose to move to ant 1.4 that use JAXP 1.1 to avoid problems with style,
xsl, ...
I
Hello again, I am running into a problem with the latest JBossMQ wrt using
it to load balance across machines.
I have one machine which acts as a message router, running JBossMQ. All
other machines use it for their JMSProvider. When I have more than one MDB
attached to a single queue, and a
User: user57
Date: 01/08/21 16:16:18
Modified:src/main/org/jboss/mq/cluster/jms ClusterTopicSession.java
ClusterTopicSubscriber.java
Log:
o removed org.jboss.mq.selectors.Selector from import, was not being used.
Revision ChangesPath
1.3
User: user57
Date: 01/08/21 16:16:17
Modified:src/main/org/jboss/mq SpyMessageConsumer.java
SpyTopicSession.java SpyTopicSubscriber.java
Log:
o removed org.jboss.mq.selectors.Selector from import, was not being used.
Revision ChangesPath
1.7
User: user57
Date: 01/08/21 16:21:51
Modified:src/main/org/jboss/mq Subscription.java
Log:
o changed comments to javadocs
Revision ChangesPath
1.3 +32 -24jbossmq/src/main/org/jboss/mq/Subscription.java
Index: Subscription.java
Hi Jason,
The way we implemented the message delivery this behaviour could happen, but
only when messages are arriving more slowly than they are being requested.
This is because the set of receivers waiting for messages is a HashSet so
that if a receiver sends a request for a message more
User: user57
Date: 01/08/21 16:47:10
Modified:src/main/javax/jms JMSException.java
Log:
o fixed setLinkedException sig to be serial compatible with JMS 1.0.2
(needed to be synchronized and have its param name as 'ex' instead of
'linkedException').
Revision
User: user57
Date: 01/08/21 16:51:22
Modified:src/main/javax/jms JMSException.java
Log:
o needed to change field names too (removed leading _)
Revision ChangesPath
1.3 +7 -7 jboss-j2ee/src/main/javax/jms/JMSException.java
Index: JMSException.java
User: dmaplesden
Date: 01/08/21 17:07:18
Modified:src/main/org/jboss/mq SpyConnectionConsumer.java
Log:
Implement the loading of multiple messages into each session when under heavy load.
Revision ChangesPath
1.5 +26 -9
Interesting, today I worked on the manual build also. I have it working
with jdk 1.3.1, ant 1.3, some updated xml jars.
problems I still have:
html files end up in manual instead of manual/output/html
jbossjms.xml has a syntax error.
Problems I fixed:
build.sh does not set ANT_HOME
I am not an expert Is this sharing of a message queue receiving end
really spec compliant? How does it relate to order-of-messages guarantees?
It seems to me this may be the conceptual difference between message queues
and javaspaces..??
david jencks
On 2001.08.21 19:06:08 -0400 Jason
Where is the source for the selector parser? It looks like it is not
parsing the literals true and false, it only looks for TRUE and
FALSE.
I am contemplating modifiying parser.java int yylex() under the //CST group
group, but I would rather modify the grammer source and regenerate the
parser.
User: user57
Date: 01/08/21 17:44:44
Modified:src/main/org/jboss/mq/selectors Operator.java
Log:
o Operator.equal() will properly compute the equality when using Boolean
types.
Revision ChangesPath
1.3 +3 -1
User: user57
Date: 01/08/21 17:52:31
Modified:src/main/org/jboss/mq/selectors parser.java
Log:
o Added support for the true and false boolean literals.
Revision ChangesPath
1.3 +2 -2 jbossmq/src/main/org/jboss/mq/selectors/parser.java
Index:
User: user57
Date: 01/08/21 17:53:35
Modified:src/main/org/jboss/mq/selectors Selector.java
Log:
o added some commented logging (too verbose to leave it for now)
o changed exceptions to return a bit more detail
Revision ChangesPath
1.3 +105 -62
What xml jars did you have to update? Where did you update them?
XSLTransform, in ant.jar, uses several classes from Optional.jar, so
build.sh also has to include optional.jar on the local classpath.
By adding optional.jar to the system classpath, all support jars will also
have to be on the
It does not say... this is one of the grey-areas of the spec. Most
providers will round-robin over multipule recievers. It is really too bad
that this is not more concreate, as JMS would provide a nice mech. for
distributing over a large group of machines, and allow for ordering and
such.
I
I'm not up-to-date on javaspaces but with jms you can certainly have
multiple receivers on the same message queue, you can also have multiple
senders. The JMS spec does not specify any policy for how messages are
distributed between different receivers though.
As for message order, it is only
Change Notes item #454045, was opened at 2001-08-21 18:24
You can respond by visiting:
http://sourceforge.net/tracker/?func=detailatid=381174aid=454045group_id=22866
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Jason Dillon (user57)
Assigned to: Nobody/Anonymous (nobody)
What this means is that if you have multiple receivers waiting for a message
from a queue and a message arrives then it will be immediately delivered to
receiver A. Receiver A is now removed from the HashSet, however if receiver
A finishes its processing and requests another message before
On 2001.08.21 21:07:53 -0400 Jason Dillon wrote:
What xml jars did you have to update? Where did you update them?
I'll get back to you on that- mostly remove parser.jar and include
xalan/xerces from previous manual build.
XSLTransform, in ant.jar, uses several classes from Optional.jar, so
Basically because of efficiency.
Because the possibility exists that when a receive is done the receiver may
already be in the list of receivers (due to receives with timeouts) we have
to check that a receiver is not already in the list before adding them to
the list. This search O(n) for a
Hi,
Interesting, today I worked on the manual build also. I have it working
with jdk 1.3.1, ant 1.3, some updated xml jars.
problems I still have:
html files end up in manual instead of manual/output/html
I had to change the copy todir task and some others as well.
If you run one by one
45 matches
Mail list logo
