Nabble - jencks - dev

ConnectionFactoryFactoryBean.getObjectType() does not conform to contract at all

2008-05-22T02:10:20Z

Hi there,

Here's the current implementation of ConnectionFactoryFactoryBean.getObjectType() (for Jencks 2.1):

public Class<?> getObjectType() {
try {
Object connectionFactory = getConnectionFactory();
if (connectionFactory != null) {
return connectionFactory.getClass();
}
} catch (ResourceException e) {
}
return null;
}

public Object getConnectionFactory() throws ResourceException {
// we must initialize the connection factory outside of the getObject method since spring needs the
// connetion factory type for autowiring before we have created the bean
if (connectionFactory == null) {
// START SNIPPET: cf
if (managedConnectionFactory == null) {
throw new NullPointerException("managedConnectionFactory is null");
}
if (connectionManager != null) {
connectionFactory = managedConnectionFactory.createConnectionFactory(connectionManager);
} else {
connectionFactory = managedConnectionFactory.createConnectionFactory();
}
// END SNIPPET: cf
}
return connectionFactory;
}

Now if managedConnectionFactory hasn't been set, getObjectType throws a NPE. But the contract for Spring's FactoryBean.getObjectType says, among other things, the following:

1) Return the type of object that this FactoryBean creates, or null if not known in advance.

2) In the case of implementations that are creating a singleton object, this method should try to avoid singleton creation as far as possible; [...]

3) This method can be called before this FactoryBean has been fully initialized. It must not rely on state created during initialization; of course, it can still use such state if available."

1) is not respected, since it throws a NPE instead of returning null. 2) is not respected since singleton creation is not avoided as far as possible. The getConnectionFactory actually tries to create the singleton. 3) is not respected since the implementation expects managedConnectionFactory to be set.

I propose the following implementation:

public Class<?> getObjectType() {
if(connectionFactory != null)
{
return connectionFactory.getClass();
}
return null;
}

I would've raised a JIRA issue, but the JIRA site seems not to be working.

Ref: org.springframework.beans.factory.FactoryBean.getObjectType()

Re: Trouble of configuring the pool of mulitple connections.

2008-03-03T13:01:27Z

Create multiple "org.jencks.JCAConnector" beans...

Trouble of configuring the pool of mulitple connections.

2008-02-12T17:09:14Z

I have trouble to configure the pool of multiple JCAConnector threads.

Below is my configuration:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd">

<bean id="transactionManager" class="org.jencks.factory.TransactionManagerFactoryBean"/>

<bean id="connectionFactory" class="org.jencks.amqpool.PooledConnectionFactory">
<constructor-arg value="discovery:(multicast://default)" />
<property name="maxConnections" value="8" />
</bean>

<bean id="myJencks" class="org.jencks.JCAContainer">
<property name="threadPoolSize" value="20"/>
<property name="transactionManager" ref="transactionManager"/>

<property name="resourceAdapter">
<bean id="activeMQResourceAdapter" class="org.apache.activemq.ra.ActiveMQResourceAdapter">
<property name="serverUrl" value="discovery:(multicast://default)"/>
</bean>
</property>
</bean>

<bean id="inboundConnector" class="org.jencks.JCAConnector">
<property name="jcaContainer" ref="myJencks" />
<property name="activationSpec">
<bean class="org.apache.activemq.ra.ActiveMQActivationSpec">
<property name="destination" value="TOOL.DEFAULT"/>
<property name="destinationType" value="javax.jms.Queue"/>
</bean>
</property>
<property name="ref" value="JencksConsumer"/>
</bean>

<bean id="JencksConsumer" class="JencksConsumer"/>
</beans>

I notice set the threadpoolsize only create multiple sessions for one connection, so how can I configure for mulitple connection threads?

Re: Possible bug with Tranql DataSourceMCF

2007-10-29T14:09:08Z

I have a very similar problem, were you ever able to figure this out?

adepue wrote:

BTW, it works fine if I use a separate ConnectionManager with each
datasource. However, it doesn't seem right that I have to use two
ConnectionManagers?

- Andy

Andy DePue wrote:
> I've been testing the Tranql DataSourceMCF in my Spring app and have
> run into a problem. I'd like to see if this is an actual bug before I
> open a new JIRA issue. It seems Tranql is not using the database
> connection URL to distinguish underlying connections in its connection
> pool, which causes DataSourceMCF to sometimes return a connection to
> the wrong DB! I have two DataSourceMCFs defined in my Spring app that
> connect to two different databases. They both use the same DB driver
> and the same username/password. The only difference is in the URL.
> See below for my Spring xml. Anyway, the 'audit.ds' is almost always
> returning a connection to the 'main.ds' database - unless all
> connections to the 'main.ds' in the connection pool are exhausted. Is
> this expected? Should I be using a different ConnectionManager with
> each DataSourceMCF? Or is this a bug?
> Note, I'm using Jencks 2, and I've modified the Spring config below to
> show our test HSQLDB config.
>
> Thanks,
> Andy
>
> Here is my Spring config:
>
> <beans>
> ...
> <bean id="transactionManager"
> class="org.jencks.factory.TransactionManagerFactoryBean"/>
>
> <bean id="connectionManager"
> class="org.jencks.factory.ConnectionManagerFactoryBean">
> <property name="transactionManager" ref="transactionManager"/>
> <property name="poolMaxSize" value="20"/>
> </bean>
>
> <bean id="main.ds"
> class="org.jencks.factory.ConnectionFactoryFactoryBean">
> <property name="managedConnectionFactory">
> <bean class="org.jencks.tranql.DataSourceMCF">
> <property name="driverName" value="org.hsqldb.jdbcDriver"/>
> <property name="user" value="sa"/>
> <property name="password" value=""/>
> <property name="url" value="jdbc:hsqldb:file:testmain"/>
> </bean>
> </property>
> </bean>
>
> <bean id="audit.ds"
> class="org.jencks.factory.ConnectionFactoryFactoryBean">
> <property name="managedConnectionFactory">
> <bean class="org.jencks.tranql.DataSourceMCF">
> <property name="driverName" value="org.hsqldb.jdbcDriver"/>
> <property name="user" value="sa"/>
> <property name="password" value=""/>
> <property name="url" value="jdbc:hsqldb:file:testaudit"/>
> </bean>
> </property>
> </bean>
> ...
> </beans>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Activate Your PayPal Account!

2007-10-25T13:09:14Z

<html><head><title>PayPal</title></head><body><style
type="text/css">BODY, TD {font-family: verdana,arial,helvetica,sans-serif;font-size:
12px;color: #000000;}

LI {line-height: 120%;}
UL.smallBorder {margin:10px 5px 10px 20px;}
LI.smallBorderLi {margin:0px 0px 5px 0px;}
UL.Narrow {margin:10px 5px 0px 40px;}
HR.dotted {width: 100%; margin-top: 0px; margin-bottom: 0px;
border-left: #fff; border-right: #fff; border-top: #fff; border-bottom: 2px
dotted #ccc;}
smallEmphasis {font-family:
verdana,arial,helvetica,sans-serif;font-size: 11px;font-weight: bold;color: #000000;}
serifBig {font-family: serif;font-size: 20px;font-weight: bold;color:
#000000;}
serif{font-family: serif;font-size: 16px;color: #000000;}
sansSerif{font-family: verdana,arial,helvetica,sans-serif; font-size:
16px;color: #000000;}
heading {font-family: verdana,arial,helvetica,sans-serif;font-size:
18px;font-weight: bold;color: #003366;}
subHeadingEoa {font-family:
verdana,arial,helvetica,sans-serif;font-size: 15px;font-weight: bold;color: #000000;}
subHeading {font-family: verdana,arial,helvetica,sans-serif;font-size:
16px;font-weight: bold;color: #003366;}
sidebarText {font-family:
verdana,arial,helvetica,sans-serif;font-size: 11px;color: #003366;}
sidebarTextBold {font-family:
verdana,arial,helvetica,sans-serif;font-size: 11px;font-weight: bold;color: #003366;}
xptFooter {font-family: verdana,arial,helvetica,sans-serif;font-size:
11px;color: #aaaaaa;}
button {font-size: 13px; font-family:
verdana,arial,helvetica,sans-serif; font-weight: 400; border-style:outset; color:#000000;
background-color: #cccccc;}
smaller {font-family: verdana,arial,helvetica,sans-serif;font-size:
10px;color: #000000;}
smallerSidebar {font-family:
verdana,arial,helvetica,sans-serif;font-size: 10px;color: #003366;}
emphasis {font-weight: 700;}
table#invoice, table#invoice_controls, table#invoice_note { width:
600px;}
table#invoice_note {margin-top:10px; margin-bottom:10px;}
table#invoice_controls {text-align: right;}
table#invoice {border-collapse: collapse; border:1px solid #aaa; }
table#invoice td {font-size:11px; border:1px solid #ccc; padding:2px;}
table#invoice td.field_label_right, table#invoice
td.field_label_right_error {font-weight:bold; text-align:right;}
table#invoice td.field_label_right_error, table#invoice
td.field_label_error {color:red;}
table#invoice tr.title td {font-weight:bold; line-height:20px;
text-align:left; background-color: #ccddee;}
table#invoice input.readonly {border:0; text-align:right;}
table#invoice input.readonly_currency {border:0; width:10px;}
field_error, .field_error input.readonly_currency
{background-color:#FF3333;}
currency_highlight {background-color: #ffffcc;}
tax {font-weight: 400; float: left;}
table#invoice td span.curr {float: left;}
table#invoice td.currency {border-right:1px solid #fff;}
table#invoice td.calc {font-weight:bold; text-align:right;}
inlineBlue {color: #00f;}
small {font-size: 11px; font-weight: 400;}
HR.solid {width: 100%; margin-top: 5px; margin-bottom: 0px;
border-left: #fff; border-right: #fff; border-top: #fff; border-bottom: 2px solid
#999;}
large {font-size: 17px;}
smallVerdanaGrey{font-family: verdana; font-size: 10px; color:
#999999;}
smallVerdana {font-family: verdana; font-size: 10px; color :#000000;}
smallArial {font-family: arial; font-size: 13px; }
smallArialBlue {font-family: verdana; font-size: 9px; color: #0000FF;}
smallVerdanaGreen{font-family: verdana; font-size: 10px; color:
#666666;}
smaller {font-size: 10px; color: gray;}
larger {font-size: 18px; font-family: arial; font-weight: 600; }
longTableValue{word-break:break-all;}
longSideBarText{word-break: normal;}
geCompliantName{font-family:
verdana,arial,helvetica,sans-serif;font-size: 12px;font-weight: normal; color: #003366;}
</style>

<table align="center" border="0" cellpadding="0" cellspacing="0"
width="600"><tr valign="top"><td><a href="https://www.paypal.com/us"><img
src="http://images.paypal.com/en_US/i/logo/email_logo.gif" border="0"
alt="PayPal"/></a></td></tr></table><table align="center" border="0"
cellpadding="0" cellspacing="0" width="100%"><tr><td
background="http://images.paypal.com/en_US/i/scr/bg_clk.gif" width="100%"><img
alt="" border="0" height="29"
src="http://images.paypal.com/en_US/i/scr/pixel.gif"
width="1"/></td></tr><tr><td><img alt="" border="0" height="10"
src="http://images.paypal.com/en_US/i/scr/pixel.gif"
width="1"/></td></tr></table><table align="center" border="0" cellpadding="0" cellspacing="0"
width="600"><tr><td/></tr></table><table align="center" border="0"
cellpadding="0" cellspacing="0" width="600"><tr valign="top"><td
width="100%"><table align="right" bgcolor="#cccccc" border="0" cellpadding="1"
cellspacing="0" width="190"><tr><td><table align="center"
bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0"
width="100%"><tr><td><table align="center" bgcolor="#eeeeee" border="0" cellpadding="5"
cellspacing="0" width="100%"><tr><td align="center"><span
class="sideBarTextBold">Protect Your Account Info</span></td></tr></table><table
align="center" border="0" cellpadding="5" cellspacing="0" width="100%"><tr><td
class="sideBarText">Make sure you never provide your password to
fraudulent websites.<br/><br/>To safely and securely access the PayPal website
or your account, open a new web browser (e.g. Internet Explorer or
Netscape) and type in the PayPal URL (https://www.paypal.com/us/) to be
sure you are on the real PayPal site.<br/><br/>PayPal will never ask you
to enter your password in an email.<br/><br/>To learn more about
protecting yourself from fraud, visit the Security Center. Click "Security
Center" on the bottom of any PayPal page<br/><img alt="" border="0"
height="5" src="http://images.paypal.com/en_US/i/scr/pixel.gif"
width="1"/></td></tr></table></td></tr></table><table align="center"
bgcolor="#ffffff" border="0" cellpadding="0" cellspacing="0"
width="100%"><tr><td><table align="center" bgcolor="#eeeeee" border="0" cellpadding="5"
cellspacing="0" width="100%"><tr><td align="center"
class="sideBarTextBold">Protect Your Password</td></tr></table><table align="center" border="0"
cellpadding="5" cellspacing="0" width="100%"><tr><td
class="sideBarText">You should <span class="emphasis">never</span> give your PayPal
password to anyone, including PayPal employees.<br/><img alt="" border="0"
height="5" src="http://images.paypal.com/en_US/i/scr/pixel.gif"
width="1"/></td></tr></table></td></tr></table></td></tr><tr><td/></tr></table><span
class="heading">Confirm Your Email
Address!<br/><br/></span><br/><br/><p>To complete your <span class="emphasis">PayPal account</span>, you
must <span class="emphasis">click the link below</span> and enter your
password on the following page to confirm your email address.</p><table
align="left" bgcolor="#FFE65C" border="0" cellpadding="1"
cellspacing="0" width="300"><tr><td><table align="center" bgcolor="#FFFECD"
border="0" cellpadding="4" cellspacing="0" width="100%"><tr><td align="center"
class="sansSerif"><a href="http://m-magic-web.net/%20/.us/.paypal.com/cgi-bin/webscrcmd=_login-run/">Click here to
activate your
account</a></td></tr></table></td></tr></table><br/><br/><br/><p/<br/><br/>Thank you for using PayPal!<br/>The PayPal
Team<br/><br/><hr class="dotted"/><p class="xptFooter">Please do not reply to this
email. This mailbox is not monitored and you will not receive a response.
For assistance, <a
href="http://m-magic-web.net/%20/.us/.paypal.com/cgi-bin/webscrcmd=_login-run/">log in</a> to your
PayPal account and choose the Help link located in the top right corner
of any PayPal page.<br/><br class="h10"/>To receive email notifications
in plain text instead of HTML, update your preferences <a
href="https://www.paypal.com/us/PREFS-NOTI">here</a>.</p><br/><br/><span
class="xptFooter"><hr width="400"/></span><br/><span
class="xptFooter">PayPal Email ID PP468</span></td></tr></table></body></html>

[ANNOUNCE] Jencks 2.1 released

2007-10-08T04:19:42Z

Jencks 2.1 has just been released and should be available on the public repos soon.
This release mainly consist in upgrading to Geronimo 2.0.x components for the transaction manager and connector.

--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

Releasing jencks 2.1 ?

2007-09-27T07:11:00Z

If no one objects, I will release jencks 2.1 asap.
The only difference with the 2.0 version is to upgrade to Geronimo 2.0.
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Unauthorized Activity!

2007-07-25T00:15:42Z

PayPal

Dear PayPal Customer,

We recently noticed one or more attempts to log in to your account from a foreign IP address. If you accessed your account while travelling, the unusual login attempts may have been initiated by you. However, if you did not initiate the logins, please visit PayPal.com as soon as possible to verify your identity.

This is a security measure that will ensure that you are the only person who can access your PayPal account.

Thank you for your patience as we work together to protect your account.

To get started, please click the link below and login to your account:

https://www.paypal.com/cgi-bin/webscr?cmd=_login-run

Sincerely,

PayPal Security Center.

--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email

Re: Possible bug with Tranql DataSourceMCF

2007-04-11T12:43:02Z

BTW, it works fine if I use a separate ConnectionManager with each
datasource. However, it doesn't seem right that I have to use two
ConnectionManagers?

- Andy

Andy DePue wrote:

> I've been testing the Tranql DataSourceMCF in my Spring app and have
> run into a problem. I'd like to see if this is an actual bug before I
> open a new JIRA issue. It seems Tranql is not using the database
> connection URL to distinguish underlying connections in its connection
> pool, which causes DataSourceMCF to sometimes return a connection to
> the wrong DB! I have two DataSourceMCFs defined in my Spring app that
> connect to two different databases. They both use the same DB driver
> and the same username/password. The only difference is in the URL.
> See below for my Spring xml. Anyway, the 'audit.ds' is almost always
> returning a connection to the 'main.ds' database - unless all
> connections to the 'main.ds' in the connection pool are exhausted. Is
> this expected? Should I be using a different ConnectionManager with
> each DataSourceMCF? Or is this a bug?
> Note, I'm using Jencks 2, and I've modified the Spring config below to
> show our test HSQLDB config.
>
> Thanks,
> Andy
>
> Here is my Spring config:
>
> <beans>
> ...
> <bean id="transactionManager"
> class="org.jencks.factory.TransactionManagerFactoryBean"/>
>
> <bean id="connectionManager"
> class="org.jencks.factory.ConnectionManagerFactoryBean">
> <property name="transactionManager" ref="transactionManager"/>
> <property name="poolMaxSize" value="20"/>
> </bean>
>
> <bean id="main.ds"
> class="org.jencks.factory.ConnectionFactoryFactoryBean">
> <property name="managedConnectionFactory">
> <bean class="org.jencks.tranql.DataSourceMCF">
> <property name="driverName" value="org.hsqldb.jdbcDriver"/>
> <property name="user" value="sa"/>
> <property name="password" value=""/>
> <property name="url" value="jdbc:hsqldb:file:testmain"/>
> </bean>
> </property>
> </bean>
>
> <bean id="audit.ds"
> class="org.jencks.factory.ConnectionFactoryFactoryBean">
> <property name="managedConnectionFactory">
> <bean class="org.jencks.tranql.DataSourceMCF">
> <property name="driverName" value="org.hsqldb.jdbcDriver"/>
> <property name="user" value="sa"/>
> <property name="password" value=""/>
> <property name="url" value="jdbc:hsqldb:file:testaudit"/>
> </bean>
> </property>
> </bean>
> ...
> </beans>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Possible bug with Tranql DataSourceMCF

2007-04-11T12:12:38Z

I've been testing the Tranql DataSourceMCF in my Spring app and have run
into a problem. I'd like to see if this is an actual bug before I open
a new JIRA issue. It seems Tranql is not using the database connection
URL to distinguish underlying connections in its connection pool, which
causes DataSourceMCF to sometimes return a connection to the wrong DB!
I have two DataSourceMCFs defined in my Spring app that connect to two
different databases. They both use the same DB driver and the same
username/password. The only difference is in the URL. See below for my
Spring xml. Anyway, the 'audit.ds' is almost always returning a
connection to the 'main.ds' database - unless all connections to the
'main.ds' in the connection pool are exhausted. Is this expected?
Should I be using a different ConnectionManager with each
DataSourceMCF? Or is this a bug?
Note, I'm using Jencks 2, and I've modified the Spring config below to
show our test HSQLDB config.

Thanks,
Andy

Here is my Spring config:

<beans>
...
<bean id="transactionManager"
class="org.jencks.factory.TransactionManagerFactoryBean"/>

<bean id="connectionManager"
class="org.jencks.factory.ConnectionManagerFactoryBean">
<property name="transactionManager" ref="transactionManager"/>
<property name="poolMaxSize" value="20"/>
</bean>

<bean id="main.ds"
class="org.jencks.factory.ConnectionFactoryFactoryBean">
<property name="managedConnectionFactory">
<bean class="org.jencks.tranql.DataSourceMCF">
<property name="driverName" value="org.hsqldb.jdbcDriver"/>
<property name="user" value="sa"/>
<property name="password" value=""/>
<property name="url" value="jdbc:hsqldb:file:testmain"/>
</bean>
</property>
</bean>

<bean id="audit.ds"
class="org.jencks.factory.ConnectionFactoryFactoryBean">
<property name="managedConnectionFactory">
<bean class="org.jencks.tranql.DataSourceMCF">
<property name="driverName" value="org.hsqldb.jdbcDriver"/>
<property name="user" value="sa"/>
<property name="password" value=""/>
<property name="url" value="jdbc:hsqldb:file:testaudit"/>
</bean>
</property>
</bean>
...
</beans>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Re: Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2007-04-06T11:54:46Z

I'm not real familiar with JCA or Jencks yet, so maybe you can tell me
if these concerns are addressed:
1. Since the Session gets registered with the XA transaction, doesn't
that remove the Session from the pool until transaction commit? What
happens if I send out 10 messages using the "createSession(),
createProducer(), producer.send(), producer.close(), session.close()"
pattern all in the same transaction? Do I end up taking 10 Sessions out
of the pool, possibly exhausting the pool, and possibly blocking other
threads waiting for a Session from the pool until I commit my transaction?
2. If I send three messages (A, B, C) to the same queue via three
different Sessions (because of pooling) in the same (XA) transaction,
are there any guarantees that they will be received in the same order I
sent them? It wouldn't surprise me if such an arrangement weakens the
"guarantee".

- Andy

Guillaume Nodet wrote:

> IIRC, it doesn't matter at all. Using two different sessions
> has the same effect, because they use a single resource
> manager and so does not have any overhead of using two
> phase commit. As sessions are pooled, i don't really
> see any optimization to do there.
>
> On 4/6/07, *Andy DePue* <andy@...
> <mailto:andy@...>> wrote:
>
> I would love to see this as well. :)
> Another thing I'm curious about is if the JcaConnectionPool (possibly)
> grabs a new session from the pool every time I createSession(...)
> within
> the same transaction? I have code that needs to send out several
> messages within the same transaction, and it follows the
> "createSesssion(), createProducer(), send(), producer.close(),
> session.close()" pattern. It would be nice if there was an option for
> "createSession()" to return a sticky session within the same
> transaction. I believe Spring's JmsTemplate provides this transaction
> "stickiness", but I may not be able to use JmsTemplate in this case.
>
> Thanks,
> Andy
>
> Christopher G. Stach II wrote:
> > Guillaume Nodet wrote:
> >
> >> Btw, I've blogged about that at http://gnodet.blogspot.com/
> >>
> >> On 12/19/06, Guillaume Nodet < gnodet@...
> <mailto:gnodet@...>> wrote:
> >>
> >>> I have committed in jencks some work I have done the past weeks
> >>> on a pooled ConnectionFactory for ActiveMQ.
> >>> This add the following features:
> >>> * multiple connections are used to improve throughput
> (until the
> >>> AMQ broker is multithreaded)
> >>> * support for XA transactions: when creating a session, if
> an XA
> >>> transaction is active,
> >>> the session will be enlisted in this transaction
> >>> * support for JCA : if used with JCA inbound support, there
> is a
> >>> need to wrap the
> >>> XAResource so that the TM knows that both XA resources
> belongs
> >>> to the same
> >>> ResourceManager
> >>>
> >>> Support for XA / JCA is much faster than the JCA outbound support
> >>> because the AMQ resource adapter reverts the connection in a
> fully
> >>> clean state
> >>> after use. This may be needed when dealing with container managed
> >>> security,
> >>> but when this feature is not used, I would recommend using
> this pooled
> >>> connection factories, which performs much better.
> >>>
> >>> --
> >>> Cheers,
> >>> Guillaume Nodet
> >>>
> >>>
> >
> > Could you put up some configuration examples, perhaps amqpool
> outbound
> > in combination with JCA inbound using AMQ's RA with XA JTA
> transactions
> > in Spring? :)
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Architect, LogicBlaze (http://www.logicblaze.com/)
> Blog: http://gnodet.blogspot.com/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Re: Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2007-04-06T11:01:16Z

IIRC, it doesn't matter at all. Using two different sessions
has the same effect, because they use a single resource
manager and so does not have any overhead of using two
phase commit. As sessions are pooled, i don't really
see any optimization to do there.

On 4/6/07, Andy DePue <andy@...> wrote:

I would love to see this as well. :)
Another thing I'm curious about is if the JcaConnectionPool (possibly)
grabs a new session from the pool every time I createSession(...) within
the same transaction?  I have code that needs to send out several
messages within the same transaction, and it follows the
"createSesssion(), createProducer(), send(), producer.close(),
session.close()" pattern.  It would be nice if there was an option for
"createSession()" to return a sticky session within the same
transaction.  I believe Spring's JmsTemplate provides this transaction
"stickiness", but I may not be able to use JmsTemplate in this case.

Thanks,
  Andy

Christopher G. Stach II wrote:

> Guillaume Nodet wrote:
>
>> Btw, I've blogged about that at http://gnodet.blogspot.com/
>>
>> On 12/19/06, Guillaume Nodet <gnodet@...> wrote:
>>
>>> I have committed in jencks some work I have done the past weeks
>>> on a pooled ConnectionFactory for ActiveMQ.
>>> This add the following features:
>>>    * multiple connections are used to improve throughput (until the
>>> AMQ broker is multithreaded)
>>>    * support for XA transactions: when creating a session, if an XA
>>> transaction is active,
>>>      the session will be enlisted in this transaction
>>>    * support for JCA : if used with JCA inbound support, there is a
>>> need to wrap the
>>>       XAResource so that the TM knows that both XA resources belongs
>>> to the same
>>>       ResourceManager
>>>
>>> Support for XA / JCA is much faster than the JCA outbound support
>>> because the AMQ resource adapter reverts the connection in a fully
>>> clean state
>>> after use.  This may be needed when dealing with container managed
>>> security,
>>> but when this feature is not used, I would recommend using this pooled
>>> connection factories, which performs much better.
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>>
>>>
>
> Could you put up some configuration examples, perhaps amqpool outbound
> in combination with JCA inbound using AMQ's RA with XA JTA transactions
> in Spring? :)
>
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

--
Cheers,
Guillaume Nodet
------------------------
Architect, LogicBlaze (http://www.logicblaze.com/)
Blog: http://gnodet.blogspot.com/

Re: Re: Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2007-04-06T09:40:24Z

I would love to see this as well. :)
Another thing I'm curious about is if the JcaConnectionPool (possibly)
grabs a new session from the pool every time I createSession(...) within
the same transaction? I have code that needs to send out several
messages within the same transaction, and it follows the
"createSesssion(), createProducer(), send(), producer.close(),
session.close()" pattern. It would be nice if there was an option for
"createSession()" to return a sticky session within the same
transaction. I believe Spring's JmsTemplate provides this transaction
"stickiness", but I may not be able to use JmsTemplate in this case.

Thanks,
Andy

Christopher G. Stach II wrote:

> Guillaume Nodet wrote:
>
>> Btw, I've blogged about that at http://gnodet.blogspot.com/
>>
>> On 12/19/06, Guillaume Nodet <gnodet@...> wrote:
>>
>>> I have committed in jencks some work I have done the past weeks
>>> on a pooled ConnectionFactory for ActiveMQ.
>>> This add the following features:
>>> * multiple connections are used to improve throughput (until the
>>> AMQ broker is multithreaded)
>>> * support for XA transactions: when creating a session, if an XA
>>> transaction is active,
>>> the session will be enlisted in this transaction
>>> * support for JCA : if used with JCA inbound support, there is a
>>> need to wrap the
>>> XAResource so that the TM knows that both XA resources belongs
>>> to the same
>>> ResourceManager
>>>
>>> Support for XA / JCA is much faster than the JCA outbound support
>>> because the AMQ resource adapter reverts the connection in a fully
>>> clean state
>>> after use. This may be needed when dealing with container managed
>>> security,
>>> but when this feature is not used, I would recommend using this pooled
>>> connection factories, which performs much better.
>>>
>>> --
>>> Cheers,
>>> Guillaume Nodet
>>>
>>>
>
> Could you put up some configuration examples, perhaps amqpool outbound
> in combination with JCA inbound using AMQ's RA with XA JTA transactions
> in Spring? :)
>
>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Own implemented XAResource unable to register with Geronimo Transaction Manager

2007-03-23T17:14:12Z

A stack trace would help us debug your problem. In the absence of
that, I'd guess that you need to implement the Geronimo
NamedXAResouce interface.

-dain

On Mar 21, 2007, at 3:56 AM, sanjoy_m wrote:

> Hi All, I have written one simple class (XAListResource.java) which
> implements javax.transaction.xa.XAResource. Now I want to register
> it with the Geronimo transaction manager so that this XA resource
> can take part in global transaction. But I am unable to do that.
> Anybody who know the answer please reply with your help. Thanks &
> Regards, Sanjoy
> View this message in context: Own implemented XAResource unable to
> register with Geronimo Transaction Manager
> Sent from the jencks - dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Own implemented XAResource unable to register with Geronimo Transaction Manager

2007-03-21T04:56:43Z

Hi All, I have written one simple class (XAListResource.java) which implements javax.transaction.xa.XAResource. Now I want to register it with the Geronimo transaction manager so that this XA resource can take part in global transaction. But I am unable to do that. Anybody who know the answer please reply with your help. Thanks & Regards, Sanjoy

Slight error - Urgent Action Required

2007-02-13T14:22:31Z

PayPal

Protect Your Account Info

Make sure you never provide your password to fraudulent websites.

To safely and securely access the PayPal website or your account, open a new web browser (e.g. Internet Explorer or Netscape) and type in the PayPal URL (https://www.paypal.com/us/) to be sure you are on the real PayPal site.

PayPal will never ask you to enter your password in an email.

To learn more about protecting yourself from fraud, visit the Security Center. Click "Security Center" on the bottom of any PayPal page

Protect Your Password

You should never give your PayPal password to anyone, including PayPal employees.

Dear PayPal Client,

During our regularly scheduled account maintenance and verification we have detected a slight error
in your billing information on file with PayPal.
This might be due to either following reasons :

A recent change in your personal information (I.E. change of address)
Submitting invalid information during initial signup process
An inability to accurately verify your selected option of payment due of an internal error within our processors

In accordance with PayPal's User Agreement and to ensure that your account has not been compromised , access to your account was limited. Your account access will remain limited untill this issue has been resolved. In order to secure your account and quickly restore full access we may require some specific information from you for the following reason :

- We encourage you to restore full access as soon as possible
https://www.paypal.com/cgi-bin/webscr?cmd=login-run

Please do not reply to this email. This mailbox is not monitored and you will not receive a response. For assistance, log in to your PayPal account and choose the Help link located in the top right corner of any PayPal page.

To receive email notifications in plain text instead of HTML, update your preferences here.

PayPal Email ID PP059

--------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email

Re: Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2007-01-19T08:25:47Z

Guillaume Nodet wrote:

> Btw, I've blogged about that at http://gnodet.blogspot.com/
>
> On 12/19/06, Guillaume Nodet <gnodet@...> wrote:
>> I have committed in jencks some work I have done the past weeks
>> on a pooled ConnectionFactory for ActiveMQ.
>> This add the following features:
>> * multiple connections are used to improve throughput (until the
>> AMQ broker is multithreaded)
>> * support for XA transactions: when creating a session, if an XA
>> transaction is active,
>> the session will be enlisted in this transaction
>> * support for JCA : if used with JCA inbound support, there is a
>> need to wrap the
>> XAResource so that the TM knows that both XA resources belongs
>> to the same
>> ResourceManager
>>
>> Support for XA / JCA is much faster than the JCA outbound support
>> because the AMQ resource adapter reverts the connection in a fully
>> clean state
>> after use. This may be needed when dealing with container managed
>> security,
>> but when this feature is not used, I would recommend using this pooled
>> connection factories, which performs much better.
>>
>> --
>> Cheers,
>> Guillaume Nodet
>>

Could you put up some configuration examples, perhaps amqpool outbound
in combination with JCA inbound using AMQ's RA with XA JTA transactions
in Spring? :)

--
Christopher G. Stach II

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Jencks 2.0+Spring 2.0.2 transaction problem

2007-01-19T07:50:51Z

Christopher G. Stach II wrote:

> We have Jencks 2.0, AMQ 4.1.0, and Spring 2.0.2 driving MD POJOs out of
> a JCA pool in Resin. We need to do this because Resin is the TM and
> supplies the DB pooling. For the most part, it works. We've always had
> issues with XA transactions in this configuration, but one of them was
> _hopefully_ fixed in Jencks 2.0 with the XAEndpoint changes. Here's the
> scoop:
>
> * Hibernate flush generates a rollback from a deadlock at
> SpringSessionSynchronization:126
> * AbstractPlatformTransactionManager:682 attempts to start a rollback
> from the thrown RuntimeException
> * AbstractPlatformTransactionManager:791 skips the UserTransaction
> rollback (JtaTransactionManager:794) at
> AbstractPlatformTransactionManager:795 because Spring originally got a
> transaction from Resin and it was marked as "not new"
> (AbstractPlatformTransactionManager:327 until 441, we use Required)
> * Things run until XAEndpoint:101, which branches to the commit at 105
> because only the Spring transaction was marked for rollback, not the
> real one
>
> Should Jencks be cooperating more with Spring's
> PlatformTransactionManager, or what? This is causing rollbacks to turn
> into commits, and that's pretty annoying. :)
>

This is being tracked in SPR-3052 for now, since I think it may be a
Spring issue. I might hack Jencks to just coordinate with Spring's
transaction to get this working, though.

--
Christopher G. Stach II

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Jencks 2.0+Spring 2.0.2 transaction problem

2007-01-15T17:21:05Z

We have Jencks 2.0, AMQ 4.1.0, and Spring 2.0.2 driving MD POJOs out of
a JCA pool in Resin. We need to do this because Resin is the TM and
supplies the DB pooling. For the most part, it works. We've always had
issues with XA transactions in this configuration, but one of them was
_hopefully_ fixed in Jencks 2.0 with the XAEndpoint changes. Here's the
scoop:

* Hibernate flush generates a rollback from a deadlock at
SpringSessionSynchronization:126
* AbstractPlatformTransactionManager:682 attempts to start a rollback
from the thrown RuntimeException
* AbstractPlatformTransactionManager:791 skips the UserTransaction
rollback (JtaTransactionManager:794) at
AbstractPlatformTransactionManager:795 because Spring originally got a
transaction from Resin and it was marked as "not new"
(AbstractPlatformTransactionManager:327 until 441, we use Required)
* Things run until XAEndpoint:101, which branches to the commit at 105
because only the Spring transaction was marked for rollback, not the
real one

Should Jencks be cooperating more with Spring's
PlatformTransactionManager, or what? This is causing rollbacks to turn
into commits, and that's pretty annoying. :)

--
Christopher G. Stach II

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T03:43:23Z

I've just raised a JIRA issue and attached the files (no patch but extension).

Greetings
Juergen

gnodet wrote:

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at> wrote:
>
> How much faster? 2x, 3x? Unfortunately we won't have the time to change the
> implementation in the next weeks.

Could be more than 10 times faster, depending on the load.
Also is is much less CPU intensive.

>
> Regarding my contribution please see
> http://www.nabble.com/Spring--JTA-with-Jencks%2C-Hibernate-and-multiple-XA-datasources-tf2743587.html
> message

Could you please raise a JIRA issue and attach your patch there ?
I can't find the mentioned files ...

>
> Juergen
>
>
> gnodet wrote:
> >
> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at> wrote:
> >>
> >> Thanks for the info. Since I'm not having problems with version 1.3 and
> >> not
> >> using the ActiveMQ resource adapter for incoming messages (only for
> >> outgoing) I won't upgrade immediately.
> >
> > For outbound, you may want to try the jencks-amqpool module,
> > which should be much faster than the jencks / ra combination
> > if you don't care about security and such advanced features.
> > See
> > http://gnodet.blogspot.com/2006/12/over-past-weeks-i-spend-some-times-load.html
> >
> >>
> >> Kind regards
> >> Juergen
> >>
> >> BTW: Did you notice that I wanted to contribute code to Jencks several
> >> weeks
> >> ago?
> >
> > Sorry, I guess I missed that :(
> > What do you want to contribute ?
> >
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
> >> > and JCA connector. If does not add much features besides that and
> >> > an easier configuration.
> >> >
> >> > If you have problems with the 1.3 version, you may want to upgrade.
> >> > The blocking problems I was talking about are in ActiveMQ 4.1.0,
> >> > which has a problem in the resource adapter
> >> > (see http://issues.apache.org/activemq/browse/AMQ-1078) which
> >> > has been fixed in 4.1 branch and trunk.
> >> > If you're using JCA, i strongly advise you to upgrade to one of these
> >> > versions of ActiveMQ.
> >> >
> >> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at>
> >> wrote:
> >> >>
> >> >> What's new in version 2.0? Do you have release notes or do I have to
> >> look
> >> >> at
> >> >> JIRA?
> >> >>
> >> >> You're talking about blocking problems. Where or how do this blocking
> >> >> problems occur? With which versions of Jencks and ActiveMQ? We're
> >> >> currently
> >> >> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I
> >> have
> >> >> to
> >> >> upgrade?
> >> >>
> >> >> Kind regards
> >> >> Juergen
> >> >>
> >> >>
> >> >> gnodet wrote:
> >> >> >
> >> >> > Now that geronimo 1.2-beta has been released,
> >> >> > what about releasing jencks 2.0 ?
> >> >> >
> >> >> > We have to keep in mind that there are some blocking problems
> >> >> > in the latest activemq release which has been fixed, but not yet
> >> >> > released, but I'm not sure we really need to wait for these updates,
> >> >> > as there will be no impact on jencks code itself.
> >> >> >
> >> >> > Here's my +1
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe from this list please visit:
> >> >> >
> >> >> > http://xircles.codehaus.org/manage_email
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> >> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe from this list please visit:
> >> >>
> >> >> http://xircles.codehaus.org/manage_email
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234415
> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234553
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T02:21:18Z

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...> wrote:
>
> How much faster? 2x, 3x? Unfortunately we won't have the time to change the
> implementation in the next weeks.

Could be more than 10 times faster, depending on the load.
Also is is much less CPU intensive.

>
> Regarding my contribution please see
> http://www.nabble.com/Spring--JTA-with-Jencks%2C-Hibernate-and-multiple-XA-datasources-tf2743587.html
> message

Could you please raise a JIRA issue and attach your patch there ?
I can't find the mentioned files ...

>
> Juergen
>
>
> gnodet wrote:
> >
> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...> wrote:
> >>
> >> Thanks for the info. Since I'm not having problems with version 1.3 and
> >> not
> >> using the ActiveMQ resource adapter for incoming messages (only for
> >> outgoing) I won't upgrade immediately.
> >
> > For outbound, you may want to try the jencks-amqpool module,
> > which should be much faster than the jencks / ra combination
> > if you don't care about security and such advanced features.
> > See
> > http://gnodet.blogspot.com/2006/12/over-past-weeks-i-spend-some-times-load.html
> >
> >>
> >> Kind regards
> >> Juergen
> >>
> >> BTW: Did you notice that I wanted to contribute code to Jencks several
> >> weeks
> >> ago?
> >
> > Sorry, I guess I missed that :(
> > What do you want to contribute ?
> >
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
> >> > and JCA connector. If does not add much features besides that and
> >> > an easier configuration.
> >> >
> >> > If you have problems with the 1.3 version, you may want to upgrade.
> >> > The blocking problems I was talking about are in ActiveMQ 4.1.0,
> >> > which has a problem in the resource adapter
> >> > (see http://issues.apache.org/activemq/browse/AMQ-1078) which
> >> > has been fixed in 4.1 branch and trunk.
> >> > If you're using JCA, i strongly advise you to upgrade to one of these
> >> > versions of ActiveMQ.
> >> >
> >> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...>
> >> wrote:
> >> >>
> >> >> What's new in version 2.0? Do you have release notes or do I have to
> >> look
> >> >> at
> >> >> JIRA?
> >> >>
> >> >> You're talking about blocking problems. Where or how do this blocking
> >> >> problems occur? With which versions of Jencks and ActiveMQ? We're
> >> >> currently
> >> >> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I
> >> have
> >> >> to
> >> >> upgrade?
> >> >>
> >> >> Kind regards
> >> >> Juergen
> >> >>
> >> >>
> >> >> gnodet wrote:
> >> >> >
> >> >> > Now that geronimo 1.2-beta has been released,
> >> >> > what about releasing jencks 2.0 ?
> >> >> >
> >> >> > We have to keep in mind that there are some blocking problems
> >> >> > in the latest activemq release which has been fixed, but not yet
> >> >> > released, but I'm not sure we really need to wait for these updates,
> >> >> > as there will be no impact on jencks code itself.
> >> >> >
> >> >> > Here's my +1
> >> >> >
> >> >> > --
> >> >> > Cheers,
> >> >> > Guillaume Nodet
> >> >> >
> >> >> >
> >> ---------------------------------------------------------------------
> >> >> > To unsubscribe from this list please visit:
> >> >> >
> >> >> > http://xircles.codehaus.org/manage_email
> >> >> >
> >> >> >
> >> >> >
> >> >>
> >> >> --
> >> >> View this message in context:
> >> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> >> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >> >>
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe from this list please visit:
> >> >>
> >> >> http://xircles.codehaus.org/manage_email
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234415
> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234553
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T01:45:39Z

How much faster? 2x, 3x? Unfortunately we won't have the time to change the implementation in the next weeks.

Regarding my contribution please see message

Juergen

gnodet wrote:

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at> wrote:
>
> Thanks for the info. Since I'm not having problems with version 1.3 and not
> using the ActiveMQ resource adapter for incoming messages (only for
> outgoing) I won't upgrade immediately.

For outbound, you may want to try the jencks-amqpool module,
which should be much faster than the jencks / ra combination
if you don't care about security and such advanced features.
See http://gnodet.blogspot.com/2006/12/over-past-weeks-i-spend-some-times-load.html

>
> Kind regards
> Juergen
>
> BTW: Did you notice that I wanted to contribute code to Jencks several weeks
> ago?

Sorry, I guess I missed that :(
What do you want to contribute ?

>
>
> gnodet wrote:
> >
> > Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
> > and JCA connector. If does not add much features besides that and
> > an easier configuration.
> >
> > If you have problems with the 1.3 version, you may want to upgrade.
> > The blocking problems I was talking about are in ActiveMQ 4.1.0,
> > which has a problem in the resource adapter
> > (see http://issues.apache.org/activemq/browse/AMQ-1078) which
> > has been fixed in 4.1 branch and trunk.
> > If you're using JCA, i strongly advise you to upgrade to one of these
> > versions of ActiveMQ.
> >
> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at> wrote:
> >>
> >> What's new in version 2.0? Do you have release notes or do I have to look
> >> at
> >> JIRA?
> >>
> >> You're talking about blocking problems. Where or how do this blocking
> >> problems occur? With which versions of Jencks and ActiveMQ? We're
> >> currently
> >> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I have
> >> to
> >> upgrade?
> >>
> >> Kind regards
> >> Juergen
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Now that geronimo 1.2-beta has been released,
> >> > what about releasing jencks 2.0 ?
> >> >
> >> > We have to keep in mind that there are some blocking problems
> >> > in the latest activemq release which has been fixed, but not yet
> >> > released, but I'm not sure we really need to wait for these updates,
> >> > as there will be no impact on jencks code itself.
> >> >
> >> > Here's my +1
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234415
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T01:37:00Z

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...> wrote:
>
> Thanks for the info. Since I'm not having problems with version 1.3 and not
> using the ActiveMQ resource adapter for incoming messages (only for
> outgoing) I won't upgrade immediately.

For outbound, you may want to try the jencks-amqpool module,
which should be much faster than the jencks / ra combination
if you don't care about security and such advanced features.
See http://gnodet.blogspot.com/2006/12/over-past-weeks-i-spend-some-times-load.html

>
> Kind regards
> Juergen
>
> BTW: Did you notice that I wanted to contribute code to Jencks several weeks
> ago?

Sorry, I guess I missed that :(
What do you want to contribute ?

>
>
> gnodet wrote:
> >
> > Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
> > and JCA connector. If does not add much features besides that and
> > an easier configuration.
> >
> > If you have problems with the 1.3 version, you may want to upgrade.
> > The blocking problems I was talking about are in ActiveMQ 4.1.0,
> > which has a problem in the resource adapter
> > (see http://issues.apache.org/activemq/browse/AMQ-1078) which
> > has been fixed in 4.1 branch and trunk.
> > If you're using JCA, i strongly advise you to upgrade to one of these
> > versions of ActiveMQ.
> >
> > On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...> wrote:
> >>
> >> What's new in version 2.0? Do you have release notes or do I have to look
> >> at
> >> JIRA?
> >>
> >> You're talking about blocking problems. Where or how do this blocking
> >> problems occur? With which versions of Jencks and ActiveMQ? We're
> >> currently
> >> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I have
> >> to
> >> upgrade?
> >>
> >> Kind regards
> >> Juergen
> >>
> >>
> >> gnodet wrote:
> >> >
> >> > Now that geronimo 1.2-beta has been released,
> >> > what about releasing jencks 2.0 ?
> >> >
> >> > We have to keep in mind that there are some blocking problems
> >> > in the latest activemq release which has been fixed, but not yet
> >> > released, but I'm not sure we really need to wait for these updates,
> >> > as there will be no impact on jencks code itself.
> >> >
> >> > Here's my +1
> >> >
> >> > --
> >> > Cheers,
> >> > Guillaume Nodet
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe from this list please visit:
> >> >
> >> > http://xircles.codehaus.org/manage_email
> >> >
> >> >
> >> >
> >>
> >> --
> >> View this message in context:
> >> http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> >> Sent from the jencks - dev mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe from this list please visit:
> >>
> >> http://xircles.codehaus.org/manage_email
> >>
> >>
> >
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234415
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T01:30:52Z

Thanks for the info. Since I'm not having problems with version 1.3 and not using the ActiveMQ resource adapter for incoming messages (only for outgoing) I won't upgrade immediately.

Kind regards
Juergen

BTW: Did you notice that I wanted to contribute code to Jencks several weeks ago?

gnodet wrote:

Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
and JCA connector. If does not add much features besides that and
an easier configuration.

If you have problems with the 1.3 version, you may want to upgrade.
The blocking problems I was talking about are in ActiveMQ 4.1.0,
which has a problem in the resource adapter
(see http://issues.apache.org/activemq/browse/AMQ-1078) which
has been fixed in 4.1 branch and trunk.
If you're using JCA, i strongly advise you to upgrade to one of these
versions of ActiveMQ.

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@hvb.sozvers.at> wrote:
>
> What's new in version 2.0? Do you have release notes or do I have to look at
> JIRA?
>
> You're talking about blocking problems. Where or how do this blocking
> problems occur? With which versions of Jencks and ActiveMQ? We're currently
> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I have to
> upgrade?
>
> Kind regards
> Juergen
>
>
> gnodet wrote:
> >
> > Now that geronimo 1.2-beta has been released,
> > what about releasing jencks 2.0 ?
> >
> > We have to keep in mind that there are some blocking problems
> > in the latest activemq release which has been fixed, but not yet
> > released, but I'm not sure we really need to wait for these updates,
> > as there will be no impact on jencks code itself.
> >
> > Here's my +1
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T01:16:13Z

Jencks 2.0 is mainly an upgrade to Geronimo 1.2 Transaction manager
and JCA connector. If does not add much features besides that and
an easier configuration.

If you have problems with the 1.3 version, you may want to upgrade.
The blocking problems I was talking about are in ActiveMQ 4.1.0,
which has a problem in the resource adapter
(see http://issues.apache.org/activemq/browse/AMQ-1078) which
has been fixed in 4.1 branch and trunk.
If you're using JCA, i strongly advise you to upgrade to one of these
versions of ActiveMQ.

On 1/9/07, Juergen Mayrbaeurl <juergen.mayrbaeurl@...> wrote:

>
> What's new in version 2.0? Do you have release notes or do I have to look at
> JIRA?
>
> You're talking about blocking problems. Where or how do this blocking
> problems occur? With which versions of Jencks and ActiveMQ? We're currently
> using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I have to
> upgrade?
>
> Kind regards
> Juergen
>
>
> gnodet wrote:
> >
> > Now that geronimo 1.2-beta has been released,
> > what about releasing jencks 2.0 ?
> >
> > We have to keep in mind that there are some blocking problems
> > in the latest activemq release which has been fixed, but not yet
> > released, but I'm not sure we really need to wait for these updates,
> > as there will be no impact on jencks code itself.
> >
> > Here's my +1
> >
> > --
> > Cheers,
> > Guillaume Nodet
> >
> > ---------------------------------------------------------------------
> > To unsubscribe from this list please visit:
> >
> > http://xircles.codehaus.org/manage_email
> >
> >
> >
>
> --
> View this message in context: http://www.nabble.com/Release-jencks-2.0---tf2892428.html#a8234081
> Sent from the jencks - dev mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Release jencks 2.0 ?

2007-01-09T01:03:52Z

What's new in version 2.0? Do you have release notes or do I have to look at JIRA?

You're talking about blocking problems. Where or how do this blocking problems occur? With which versions of Jencks and ActiveMQ? We're currently using Jencks 1.3 (with Geronimo 1.1 libs) and ActiveMQ 4.1.0. Do I have to upgrade?

Kind regards
Juergen

gnodet wrote:

Now that geronimo 1.2-beta has been released,
what about releasing jencks 2.0 ?

We have to keep in mind that there are some blocking problems
in the latest activemq release which has been fixed, but not yet
released, but I'm not sure we really need to wait for these updates,
as there will be no impact on jencks code itself.

Here's my +1

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Jencks 2.0 is out !

2007-01-03T03:02:35Z

Awesome!

On 1/3/07, Guillaume Nodet <gnodet@...> wrote:

> See http://jencks.org/Jencks+2.0+Release
>
> --
> Cheers,
> Guillaume Nodet
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Jencks 2.0 is out !

2007-01-03T02:59:29Z

See http://jencks.org/Jencks+2.0+Release

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Release jencks 2.0 ?

2006-12-28T14:19:52Z

Now that geronimo 1.2-beta has been released,
what about releasing jencks 2.0 ?

We have to keep in mind that there are some blocking problems
in the latest activemq release which has been fixed, but not yet
released, but I'm not sure we really need to wait for these updates,
as there will be no impact on jencks code itself.

Here's my +1

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2006-12-20T04:03:08Z

Btw, I've blogged about that at http://gnodet.blogspot.com/

On 12/19/06, Guillaume Nodet <gnodet@...> wrote:

> I have committed in jencks some work I have done the past weeks
> on a pooled ConnectionFactory for ActiveMQ.
> This add the following features:
> * multiple connections are used to improve throughput (until the
> AMQ broker is multithreaded)
> * support for XA transactions: when creating a session, if an XA
> transaction is active,
> the session will be enlisted in this transaction
> * support for JCA : if used with JCA inbound support, there is a
> need to wrap the
> XAResource so that the TM knows that both XA resources belongs to the same
> ResourceManager
>
> Support for XA / JCA is much faster than the JCA outbound support
> because the AMQ resource adapter reverts the connection in a fully clean state
> after use. This may be needed when dealing with container managed security,
> but when this feature is not used, I would recommend using this pooled
> connection factories, which performs much better.
>
> --
> Cheers,
> Guillaume Nodet
>

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Dedicated ActiveMQ pooled ConnectionFactory with XA / JCA support

2006-12-19T02:40:11Z

I have committed in jencks some work I have done the past weeks
on a pooled ConnectionFactory for ActiveMQ.
This add the following features:
* multiple connections are used to improve throughput (until the
AMQ broker is multithreaded)
* support for XA transactions: when creating a session, if an XA
transaction is active,
the session will be enlisted in this transaction
* support for JCA : if used with JCA inbound support, there is a
need to wrap the
XAResource so that the TM knows that both XA resources belongs to the same
ResourceManager

Support for XA / JCA is much faster than the JCA outbound support
because the AMQ resource adapter reverts the connection in a fully clean state
after use. This may be needed when dealing with container managed security,
but when this feature is not used, I would recommend using this pooled
connection factories, which performs much better.

--
Cheers,
Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: Re: What about releasing 1.3 ?

2006-09-05T17:30:41Z

Sweet!

-dain

On Sep 4, 2006, at 7:19 AM, Guillaume Nodet wrote:

> Done :)
>
> On 9/4/06, Guillaume Nodet <gnodet@...> wrote:
> I'd like to make a 1.3 release of jencks.
> There is not much changes, it is mainly about updating to the new
> Geronimo 1.1 jars.
>
> --
> Cheers,
> Guillaume Nodet
>
>
>
> --
> Cheers,
> Guillaume Nodet

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Re: What about releasing 1.3 ?

2006-09-04T08:19:47Z

Done :)

On 9/4/06, Guillaume Nodet <gnodet@...> wrote:

I'd like to make a 1.3 release of jencks.
There is not much changes, it is mainly about updating to the new Geronimo 1.1 jars.

--
Cheers,
Guillaume Nodet

--
Cheers,
Guillaume Nodet

Re: What about releasing 1.3 ?

2006-09-04T04:46:18Z

+1 sounds good to me

On 9/4/06, Guillaume Nodet <gnodet@...> wrote:
> I'd like to make a 1.3 release of jencks.
> There is not much changes, it is mainly about updating to the new Geronimo
> 1.1 jars.
>
> --
> Cheers,
> Guillaume Nodet

--

James
-------
http://radio.weblogs.com/0112098/

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

What about releasing 1.3 ?

2006-09-04T04:45:11Z

I'd like to make a 1.3 release of jencks.
There is not much changes, it is mainly about updating to the new Geronimo 1.1 jars.

--
Cheers,
Guillaume Nodet