March 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss Web Services] - Re: JBAS-4109, jbossws-2.0.0.CR4?

by scott.stark＠jboss.org

The jbossas trunk version has been reverted back to snapshot by Thomas. I need a release version this week. Also, the declared mc dependencies for the 2.0.x line seem questionable: | <import componentref="jboss/microcontainer"> | <compatible version="snapshot"/> | <compatible version="2.0.0.Beta3"/> | <compatible version="1.0.2"/> | </import> | I added the 2.0.0.Beta3 to the snapshot, but the 1.0.2 compatibility cannot be correct for the mc-2.0.x deployers. We will need to split up environment specific artifiacts like deployers from the core to be able to declare property dependencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025551#4025551 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025551

19 years, 1 month

1
0
0 / 0

[Design of JBoss Profiler] - Long processing time for runtime and memory profiler

by mnewcomb

When can I tell that the memory profiler is complete in JBoss Profiler? I watched it count up to like 5.8 million registers and then it started counting 'swaps'. It hat not completed after 15min+ and so I figured I'd ask how long a large dump (process size was 300mb) would take. Also, I did a runtime profile and after going to lunch and coming back, it was at 5% processed and so I thought I'd ask what was taking so long in processing the files? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025549#4025549 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025549

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - Major transaction problem

by david.lloyd＠jboss.com

While working on bug JBPM-877 I discovered a bad problem. I ran a test in the web console which hit an error - probably a local configuration error - but the transaction committed even though the web console called jbpmContext.setRollbackOnly(). Could this be a consequence of the new transaction code? Maybe it is due to using JTA rather than CMT in the jbpm-enterprise.ear (which is where I saw this problem)? Any ideas? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025543#4025543 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025543

19 years, 1 month

1
0
0 / 0

[Design of JBoss Web Services] - Re: ws-rm and ws-po dependency

by palin

Hi Thomas, OK, we're reading ws-policy too. May be we could talk togheter in future, as soon as we've analyzed these specs, in order to better understand how to proceed and start contributing on this issue. Thank you Alessio Soldano View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025542#4025542 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025542

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

by weston.price＠jboss.com

anonymous wrote : | Maybe this is a debug feature we could leave to the new JCA implementation? | Since it will be easier to plugin as an optional interceptor to do the extra tracking | Makes sense from a sheer refactoring/testing standpoint. So again, the rules for the new 'workaround' are 1) Add incrementing counter to WrappedStatement as an easy way to determine outstanding work 2) During the 2PC/Local lifecycle cancel statements that currently working and may interfefere with the transaction protocol. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025534#4025534 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025534

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

by adrian＠jboss.org

"weston.price(a)jboss.com" wrote : | Tricky because we would effectively be asserting that we *know* how to handle this situation better than the RDBMS. Again, perhaps a config option? | In the old transaction manager this type of thing was an optional plugin see org.jboss.tm.integrity.* except here we doing the integrity check for the resource usage rather than transaction thread association. But this is really a 1% usecase. You do still see people that put a connection in a HTTP Session and then end up using it concurrently when the client opens mulitple browser windows. Obviously, this is probably broken if the servlet does setAutoCommit(false) and it is something we could detect in the resource adapter. Maybe this is a debug feature we could leave to the new JCA implementation? Since it will be easier to plugin as an optional interceptor to do the extra tracking (it requires tracking all connection, statement, result set invocations not just executeXXX). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025529#4025529 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025529

19 years, 1 month

1
0
0 / 0

[Design of JBoss jBPM] - JPDL based web services example

by bgphp

I am new to JBPM. I am investigating to find out on how i can use JPDL to call Web Services. I would appreciate if someone point me to JBPM examples that use JPDL to call webservices. thanks BP View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025527#4025527 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025527

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

by weston.price＠jboss.com

Just so we are on the same page. The new options will allow us to terminate any outstanding statement work prior to prepare/commit/rollback. Anything else is config options to support edge cases. You know, this is where aspects would be really nice. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025525#4025525 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025525

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

by weston.price＠jboss.com

anonymous wrote : | The other part is whether this should be optional | I think it definitely should be. Note, this is the only provider that is exhibiting this behavior. I follow the rule of 'Always be able to shut it off' in JCA. anonymous wrote : | The most optimal way of doing it (and also the most generic) | would be store an "inExecute" reference count inside the WrappedStatement | for the number of times the execute method is being invoked concurrently. | Yep. I agree. anonymous wrote : | Another issue is whether we should force a rollback of the transaction | when somebody tries to commit but there are statements still being executed. | Tricky because we would effectively be asserting that we *know* how to handle this situation better than the RDBMS. Again, perhaps a config option? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025524#4025524 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025524

19 years, 1 month

1
0
0 / 0

[Design of JCA on JBoss] - Re: JDBC/XA changes to better support MSSQL Server

by adrian＠jboss.org

Another issue is whether we should force a rollback of the transaction when somebody tries to commit but there are statements still being executed. Although the db driver should handle the current usage correctly this probably represents a logic error by the user (again in multithreaded uses). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4025521#4025521 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4025521

19 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums March 2007