[JBoss Tools (users)] - Feedback on the Smooks editor
by mzeijen
The last couple of days I have been evaluating the Smooks Eclipse plugin in JBoss Tools RC2. You may have noticed that from the number of Jira issues I have raised for the plugin ;). I would like to share some of my feedback. My interest for the editor comes from the fact that I'm one of the core developers on Smooks, plus the fact that the company I work for uses Smooks and JBoss ESB extensively in a number of production environments.
I must say that I find it great that JBoss is developing the Eclipse tooling for Smooks. A good tool should make it a lot easier to use Smooks and should open Smooks up for a lot more people. Doing transformations within the ESB should also become a lot easier.
While using the editor I ran into quite a few issues while trying to do some quite basic things. There where a number of bugs that made the editor practically unusable. I understand that some of these bugs probably only appear in some environments and that there aren't a lot of people out there that are testing it. I added Jira bug reports for these issues. I hoped that the most critical ones would be fixed in the version that gets released with JBoss Tools 3.0.0 GA. Some of the bugs I've added have been fixed already, which is great, but the fix version is for the Smooks editor that gets released in JBoss Tools 3.1.0 GA. Does that mean that JBoss Tools 3.0.0.GA is going to be released with a very buggy Smooks editor?
I noticed that the editor at this moment for the biggest part concentrate around the XML/Java to Java mapping. Javabean binding is only a small part of what Smooks has to offer. Is it really valid then that the editor gets a 1.0.0 release number? If I think of a 1.0.0 release of the Smooks editor then I would expect that the editor has support for most of the features that Smooks has to offer. It is understandable that the first stable public releases of the editor don't have all the features. But wouldn't it be better to give this editor a version number like 0.1? That at least indicates that the editor doesn't have all the features one can expect.
Regards,
Maurice
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216351#4216351
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216351
17 years, 1 month
[JBoss Cache: Core Edition] - Re: is it possible for MVCCInvocationContext to have null mv
by dukehoops
Well, it appears that the above *is* possible - but I wonder whether that is a bug. Basically, because of failSilently==true putForExternalRead ends up adding Node to MVCCInvocationContext.lookedUpNodes but subsequent evictNode() uses MVCCInvocationContext.mvccTCtx to look up the same node (and fails to find it)
Setup: Hibernate, JBC 3.0.3.GA; MVCC; JTA tm injected; REPEATABLE_READ iso
Consider the following scenario:
pre: cache is empty
tx.begin()
cache.putForExternalRead(fqnA, val);
cache.evictNode(fqnA) //expect eviction to succeed
tx.commit()
1. By the time invocationContextInteceptor invokes next interceptor, mvccInvocationContext.mvccTCtx is null!
Given failSilently=true in putForExternalRead:
getInvocationContext().getOptionOverrides().setFailSilently(true);
| getInvocationContext().getOptionOverrides().setForceAsynchronous(true);
| PutForExternalReadCommand command = commandsFactory.buildPutForExternalReadCommand(null, fqn, key, value);
| invoker.invoke(ctx, command);
... InvocationContextInterceptor sets transactionalContext twice in handleAll (at lines 150 and 164):
if (txManager != null)
| {
| Transaction tx = getTransaction();
| GlobalTransaction realGtx = getGlobalTransaction(tx, gtx);
| if (tx == null && realGtx != null && realGtx.isRemote()) tx = txTable.getLocalTransaction(gtx);
| setTransactionalContext(tx, realGtx, null, ctx);
| }
..and
if (optionOverride != null && optionOverride.isFailSilently())
| {
| log.debug("FAIL_SILENTLY Option is present - suspending any ongoing transaction.");
| suppressExceptions = true;
| if (ctx.getTransaction() != null)
| {
| suspendedTransaction = txManager.suspend();
| setTransactionalContext(null, null, null, ctx);
| if (trace) log.trace("Suspending transaction " + suspendedTransaction);
| resumeSuspended = true;
| }
The first invocation of setTransactionalContext injects valid TransactionContext, Transaction into MVCCInvocationContext. but the second invocation clears them, such that invocationContext.getTransaction() will return null henceforth.
Subsequently other interceptors are invoked, including TxInterceptor, whose attachGtxAndPassUpChain does not attach anything because ctx.getTransaction()==null. For the remainder of this invocation MVCCInvocationContext.mvccTCtx remains null and ctx.lookedUpNodes is used.
2. Cache.evictNode fails to evict because ctx.lookUpNode looks in mvccTCtx and does not find Node.
Subsequent Cache.evictNode(fqn) does not use failSilently option, so setTransactionalContext in InvocationContextInterceptor is NOT called twice and valid transactionContext remains injected into invocationContext. So, when ctx.lookUpNode() is called from EvictCommand.perform, existing ctx.mvccTCtx is consulted (and NOT 'lookUpNodes'). And thus, the node is not found, and eviction is not performed. NOTE: seems like any command that uses ctx.lookUpNode and is NOT invoked with failSilently==true will fail to lookup this node for the same reason.
Also note that in NotifierImpl.resetInvocationContext lookedUpNodes are copied, so the above not-evicted-node would be copied as well.
Thoughts?
If the does seem like a bug, the obvious solution seems to be not to use failSilently option in Cache.putForExternalRead (and in other places?). What would be the implication?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216349#4216349
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216349
17 years, 1 month
[Tomcat, HTTPD, Servlets & JSP] - Migration from Tomcat to Jboss 4.0.4
by gfca
Hi people,
in my company i have a web application running in Tomcat 6. That application connects to an oracle database. These configuration is defined in context.xml:
<Context path="/ngincard" reloadable="true" docBase="ngincard.war"
| antiJARLocking = "true" antiResourceLocking = "true">
| <Resource name="jdbc/ngincard" auth="Container"
| type="oracle.jdbc.pool.OracleConnectionPoolDataSource"
| driverClassName="oracle.jdbc.OracleDriver"
| factory="oracle.jdbc.pool.OracleDataSourceFactory"
| url="jdbc:oracle:thin:clicardv2_06/xxxxxxx@xxx.xxx.xxx.xxx:1521:YYYY"
| maxActive="20" maxIdle="10" maxWait="-1"
| />
| <Environment name="userDb" value="ADMINCARDV2_06"
| type="java.lang.String" override="false" />
| <WatchedResource>WEB-INF/web.xml</WatchedResource>
| </Context>
|
But now, because company policy, we are migrating the application to run in JBOSS 4.0.4.
My question is... where can i define these parameters/configuration in Jboss to make possible my application run?
Thanks a lot for your time.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216348#4216348
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216348
17 years, 1 month
[JCA/JBoss] - Re: ConnectionCount and InUseConnectionCount behavior
by jguser
"PeterJ" wrote : The ConnectionCount is the total number of connections that have been established since JBoss AS started. Consider this scenario. An app accesses the database so 5 connections (min-pool-size) are created. Then the app gets busy and it needs more connections, let's say a total of 20 connections. At this point both InUseConnectionCount and ConnectionCount are 20. The the app is no longer busy, so after 5 minutes (idle-timeout-minutes) the number of connections in use (InUseConnectionCount) goes back down to 5. At this point ConnectionCount is still 20. Later the app gets busy again and let's assume that 25 connections are required. Thus 20 new connections were created. At this point ConnectionCount is 40 and InUseConnectionCount is 25. Then the app is no longer busy and those connections are no longer needed, so the InUseConnectionCount goes back down to 5. But ConnectionCount is still at 40.
|
| Hope this helps.
I think you are confused with the ConnectionCreatedCount parameter.
The ConnectionCount is the number of connection established to the database, but not necessarily in use. Every idle-timeout-millis time the connections that was idle for more than that time, es be destroyed, so ConnectionCount decrease.
I have a graphic showing the value of this two parameters in time, but i don't know how to put it here to show you what I meen to say.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4216338#4216338
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4216338
17 years, 1 month