[Design of Messaging on JBoss (Messaging/JBoss)] - Valve on HAAspect
by clebert.suconic@jboss.com
I have implemented a Valve (class org.jboss.jms.util.Valve) which will prevent two threads to enter in the same block, where the second thread will just ignore the routine.
Valve.open will return true only once... and it will wait until the first thread to execute open calls a close.
I have implemented this routine into HAAspect::handleConnectionException, however I don't know what to do if two subsequent failures happen, but not at the same time.
If two failures happen at the same time the method I added is ok, but if a second failure happens seconds after the method is done, then the method will assume another failover is happening. On that case hpping logic should take care of that.
Ok.. I guess I'm drunk and maybe my explanation is too confused. Let me explain through an example:
Example I:
- Thread A and B, both got an IOException at the same time from ConnectionListener.
On this case the valve will ignore one of the exceptions and will perform the client failover in only one exception
- Thread A get an exception...
- Failover happens
- Thread B get an exception after failover on client is done
- Failover will be called again, and I'm expecint hopping will be smart enough to ignore the second failover event.
if you could please take a look at the code (Ovidiu, Tim, contributors) to verify if the implementation is correct. Maybe you thought about something I didn't think.
Cheers,
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993214#3993214
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993214
19 years, 4 months
[Design of JBossCache] - Re: Serialization Compatibility Tests
by bstansberry@jboss.com
The tests under tests/compatibility/org/jboss/cache/compatibility sounds fine.
The varia part seems odd. That creates a whole new directory structure just for two classes. How about tests/compatibility/org/jboss/tools instead?
Also, packaging the 2 classes (I assume we're talking about ClassVersionInfo and SerialVersionUID) under org.jboss.tools is a bit strange. I understand the desire to do that -- it's the same classes as the ones under the AS codebase. But actually, it's not the same classes -- it's a copy. It's not going to automatically be developed/maintained along with the AS version.
So, I'd say
1) If it's QA's intent to someday unify this stuff by doing something like putting these classes in the test project where they can be shared by AS and JBC, then leave them in org.jboss.tools. Even if you guys think you might do that someday, go ahead and leave them in org.jboss.tools.
2) Otherwise, they should be packaged in org.jboss.cache.compatibility.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993185#3993185
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993185
19 years, 4 months
[Design the new POJO MicroContainer] - Re: Other IoC containers support
by alesj
Found the problem.
I needed to put xml.xsd into my classpath.
So we should do this also in our dist or is this already in?
Or you can reference it some other way?
---------------------------
<?xml version='1.0'?>
<xs:schema targetNamespace="http://www.w3.org/XML/1998/namespace" xmlns:xs="http://www.w3.org/2001/XMLSchema" xml:lang="en">
<xs:annotation>
<xs:documentation>
See http://www.w3.org/XML/1998/namespace.html and
http://www.w3.org/TR/REC-xml for information about this namespace.
This schema document describes the XML namespace, in a form
suitable for import by other schema documents.
Note that local names in this namespace are intended to be defined
only by the World Wide Web Consortium or its subgroups. The
following names are currently defined in this namespace and should
not be used with conflicting semantics by any Working Group,
specification, or document instance:
base (as an attribute name): denotes an attribute whose value
provides a URI to be used as the base for interpreting any
relative URIs in the scope of the element on which it
appears; its value is inherited. This name is reserved
by virtue of its definition in the XML Base specification.
id (as an attribute name): denotes an attribute whose value
should be interpreted as if declared to be of type ID.
The xml:id specification is not yet a W3C Recommendation,
but this attribute is included here to facilitate experimentation
with the mechanisms it proposes. Note that it is _not_ included
in the specialAttrs attribute group.
lang (as an attribute name): denotes an attribute whose value
is a language code for the natural language of the content of
any element; its value is inherited. This name is reserved
by virtue of its definition in the XML specification.
space (as an attribute name): denotes an attribute whose
value is a keyword indicating what whitespace processing
discipline is intended for the content of the element; its
value is inherited. This name is reserved by virtue of its
definition in the XML specification.
Father (in any context at all): denotes Jon Bosak, the chair of
the original XML Working Group. This name is reserved by
the following decision of the W3C XML Plenary and
XML Coordination groups:
In appreciation for his vision, leadership and dedication
the W3C XML Plenary on this 10th day of February, 2000
reserves for Jon Bosak in perpetuity the XML name
xml:Father
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>This schema defines attributes and an attribute group
suitable for use by
schemas wishing to allow xml:base, xml:lang, xml:space or xml:id
attributes on elements they define.
To enable this, such a schema must import this schema
for the XML namespace, e.g. as follows:
<schema . . .>
. . .
Subsequently, qualified reference to any of the attributes
or the group defined below will have the desired effect, e.g.
<type . . .>
. . .
will define a type which will schema-validate an instance
element with any of those attributes</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>In keeping with the XML Schema WG's standard versioning
policy, this schema document will persist at
http://www.w3.org/2005/08/xml.xsd.
At the date of issue it can also be found at
http://www.w3.org/2001/xml.xsd.
The schema document at that URI may however change in the future,
in order to remain compatible with the latest version of XML Schema
itself, or with the XML namespace itself. In other words, if the XML
Schema or XML namespaces change, the version of this document at
http://www.w3.org/2001/xml.xsd will change
accordingly; the version at
http://www.w3.org/2005/08/xml.xsd will not change.
</xs:documentation>
</xs:annotation>
<xs:attribute name="lang">
<xs:annotation>
<xs:documentation>Attempting to install the relevant ISO 2- and 3-letter
codes as the enumerated possible values is probably never
going to be a realistic possibility. See
RFC 3066 at http://www.ietf.org/rfc/rfc3066.txt and the IANA registry
at http://www.iana.org/assignments/lang-tag-apps.htm for
further information.
The union allows for the 'un-declaration' of xml:lang with
the empty string.</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:union memberTypes="xs:language">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value=""/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="space">
<xs:simpleType>
<xs:restriction base="xs:NCName">
<xs:enumeration value="default"/>
<xs:enumeration value="preserve"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="base" type="xs:anyURI">
<xs:annotation>
<xs:documentation>See http://www.w3.org/TR/xmlbase/ for
information about this attribute.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="id" type="xs:ID">
<xs:annotation>
<xs:documentation>See http://www.w3.org/TR/xml-id/ for
information about this attribute.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attributeGroup name="specialAttrs">
<xs:attribute ref="xml:base"/>
<xs:attribute ref="xml:lang"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
</xs:schema>
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3993134#3993134
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3993134
19 years, 4 months