Call UserTransaction.commit or .rollback, which you should be doing in a
finally block anyhow. Unless it's CMT, in which case this is a container bug.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4234517#4234517
Reply to the post :
1) yes
2) It's the default setting for connections outside a managed tx, per the JDBC
spec
3) no
4) You can't, the AS connection management code needs to be fixed fixed so it
invalidates the connection. https://jira.jboss.org/jira/browse/JBAS-5080
5) You're crazy, but you can use a CheckedAction
In JBossAS branch5x the class javax.xml.ws.Service21 seems to have vanished
from jbossws-native-jaxws-ext.jar Was this intentional? It's broken things
that work fine on AS 5.0.GA.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4206588#4206588
Reply to the
I'm having issues when running
org.jboss.test.jca.test.TxConnectionManagerStressTestCase with the CORBA based
transaction service (JBossTS JTS). I can make the test pass, but to do so I
need to mess with various combinations of:
ulimit -s
ulimit -u
java -Xss
jacorb.poa.queue_max
Also setting jacorb.poa.queue_wait=on may reduce the number of Threads we need
in the pool to keep up with the test, which in turn may reduce the need to mess
with -Xss and ulimit in order to avoid the 'java.lang.OutOfMemoryError: unable
to create new native thread' problem.
View the original
http://www.jboss.com/index.html?module=bbop=viewtopict=119313
Use transactionManager.commit|rollback, not transaction.commit|rollback, that
will probably sidestep the issue.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197586#4197586
Reply to the post :
Hello JBossCache gurus
I've been toying with the idea of using in-memory replication across a cluster
to preserve transaction log information for JBossTS, as an alternative to
writing it to disk. What follows is my current thinking on the matter, which
you can poke holes in at your leisure.
This approach works
.. but only as long as your application can tolerate invocations of the web
service without the corresponding database updates. The server may crash after
invoking the web service but before committing the database updates. Or the
commit on the database may fail.
View the
https://jira.jboss.org/jira/browse/JBAS-5801
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4170036#4170036
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4170036
___
jboss-user
This is critical for the next JBossTS release. I'd really like to see it fixed
in 3.0.3, not 3.0.4. Please consider rescheduling
http://jira.jboss.com/jira/browse/JBWS-2246
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4164186#4164186
Reply to the post :
BTW, do you expect the database connections used by your app to participate in
the managed transaction?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4163622#4163622
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4163622
But no extra module should be needed.
Actually that depends exactly what version of the server you are running and
what the transaction encompasses. JBM has its own recovery module, but it's not
enabled by default. The JCA used for database connections also has one, but
it's only bundled in
/labs/labs/jbosstm/workspace/jhalliday/tomcat-integration/
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4155615#4155615
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4155615
http://wiki.jboss.org/wiki/JBoss42FAQ
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4148335#4148335
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4148335
___
jboss-user mailing
It already exists: http://jira.jboss.com/jira/browse/JBAS-5235
The issue came up a JBossWorld but is on the back burner until we get on top of
the transaction system feature work needed for AS 5.0
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4139257#4139257
Any thread in particular, or do I need to set aside a week or two to wade
through the whole thing?
You are right that what I did is a hack. The real solution in my view requires
changes to the transactions integration spi. We can't do that in a CP release -
any short term solution for EAP 4.x
Ahh, cool, thanks. That's not quite what I need, but it's close enough to give
be a good idea on how to proceed. Ideally I'd like to be able to call
XAManagedConnectionFactory.getXADataSource but since it's not possible I'll
settle for getXADataSourceClass plus getXADataSourceProperties which
Adrian or whoever is the resident JCA guru in this post-Weston era:
Is there a way to get from the AS (4.2), a real XADataSource rather than the
WrapperDataSource that is in JNDI? To do transaction recovery I need methods
that are only on the XADataSource. Right now I'm facing the prospect of
Hmm, those bean entries don't get seen if they are in jboss-service.xml and
putting them in the bootstrap means adding lots of new stuff to the classpath
there. That leaves the option of putting them in deploy, which probably means
moving things that depend on the TransactionManager too i.e.
You are missing the point and some code/xml
Yes, thanks Ales, the missing link seems to be the functionality in
TestServiceControllerLifecycleCallback. I had assumed that declaring the
annotation was sufficient, but it seems that nothing in the current AS trunk
actually does anything with
Yes, I follow (but don't necessarily agree with) the argument that the
TransactionManager should be in deploy, but given that we can't put it there in
the short term we need an alternative solution.
Can the ServiceControllerLifecycleCallback stuff be moved such that it is
available for use in
Hmm yes, that would work. All i'm trying to avoid is duplicating the java code.
Duplicating a bit of xml bothers me a lot less. From the sounds of things it
would be feasible to declare a bean with
class=org.jboss.system.microcontainer.jmx.ServiceControllerLifecycleCallback in
the
The JMX annotation seems a good approach at first, but when I replace the old
mbean
| mbean code=com.arjuna.ats.jbossatx.jta.TransactionManagerService
| name=jboss:service=TransactionManager
| attribute name=TransactionTimeout300/attribute
| attribute
Why the mbean XML?
Umm, because I want operations on it exposed via. JMX? Just because we use MC
internally in the app server, that does not mean JMX goes away. There are still
likely to be 3rd party tools wanting to use JMX to manage the server, so I need
some way to wire the service up as
Fair enough. So I can't do much of my setup in the service constructor, as I
don't have the information yet at that time. I need to do the work in the start
method instead. That's actually less effort for me, as it's how things
currently work.
The problem with that is: many other services
ok, so I must be doing something wrong then. I take a class that previously
extended ServiceMBeanSupport. I change it so it no longer does so. I change
startService() to start(). I drop it into the app server and hey presto, thing
that depend upon it break.
12:29:28,517 INFO [JMXKernel]
I don't have a createService/create method. Besides, the invoker bean is moving
into the run state, which means the transaction manger should have had start()
called on it? It does not seem to get that call. I can add a create() to see if
that gets called, but I'm not clear what help that would
hmm, create() does not get called either. Is it possible there is something odd
with lifecycle callbacks to mbeans?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4108868#4108868
Reply to the post :
mbean name=jboss:service=TransactionManager
code=com.arjuna.ats.jbossatx.jta.TransactionManagerService
| property name=mbeanServerinject bean=JMXKernel
property=mbeanServer//property
| property name=transactionTimeout300/property
| property
And an example of dependency?
look at jboss-service.xml in AS trunk and take your pick.
|mbean code=org.jboss.invocation.local.LocalInvoker
| name=jboss:service=invoker,type=local
| dependsjboss:service=TransactionManager/depends
|/mbean
|
Dunno how lifecycle works
Thanks Ales
For the MBeanServer, I've opted to try injecting. That should work, but I can't
figure out the correct xml.
mbean name=jboss:service=TransactionManager
| code=com.arjuna.ats.jbossatx.jta.TransactionManagerService
| constructor
| parameter
Scott
That value is write once i.e. I want it set through the constructor, not
exposed as a setter on the bean. Are you saying that's not possible currently?
Thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4108364#4108364
Reply to the post :
I'm migrating some existing code that used to use JBossAS ServiceMBeanSupport
to the microcontainer. I'd appreciate any information on the best approach to
the following two issues:
The software is used standalone as well as in JBossAS. Internally we will
continue to use MBeans as that's
I'm trying to get to grips with the MC in order to rewrite the JBossTS
integration code for AS 5.0...
I've read through the reference docs and also seen mention of some examples and
a getting started guide. I can't find either of those online though, and there
is some implication that they are
# Initial Java Heap Size (in MB)
#wrapper.java.initmemory=1024
# Maximum Java Heap Size (in MB)
#wrapper.java.maxmemory=2048
remove the comments? :-)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4080869#4080869
Reply to the post :
Give me the full trace from that java.lang.NullPointerException please
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4075183#4075183
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4075183
Trying to run wsconsume from 2.0.0.GA I got
javax.xml.stream.FactoryConfigurationError: Provider
com.ctc.wstx.stax.WstxInputFactory not found
so I went and downloaded wstx-lgpl-3.1.2.jar, put in on the classpath and tried
again. This time I got:
$ wsconsume.sh -v -k wsctx.wsdl
JBossWS-Native
I wonder if anyone could give me any suggestion
Here is a suggestion: try reading the docs.
http://wiki.jboss.org/wiki/Wiki.jsp?page=JBoss42FAQ
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4066144#4066144
Reply to the post :
Do you really think a bit of cut-and-paste is going to get you any more
attention? If you want urgent help please try doing something more useful,
like providing a test case that reproduces the behavior. Or buying a support
contract.
View the original post :
I would like to switch it to JTS in order to get XA support for database
activity and JMS message creation in one atomic transaction.
You don't need JTS for that unless you are using more than one JBoss instance.
If the database and JMS are communicated to from the same JBoss server then JTA
Dave
I'm not able to reproduce that. What you should get at startup is:
10:30:07,036 INFO [TransactionManagerService] JBossTS Transaction Service (JTA
version) - JBoss Inc.
10:30:07,036 INFO [TransactionManagerService] Setting up property manager
MBean and JMX layer
10:30:07,297 INFO
Hi Dave
I'm not able to reproduce that error. Please can you post the diff between your
bossjta-properties.xml and the original, plus some more information on where
the error occurs. I'm assuming it's at the point where your application is
deployed, in which case a test application that
helgaw, what specifically are the issues you are getting? It's difficult to
offer advice without having a clear description of the problem and the
environment in which it occurs.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4053499#4053499
Reply to the post
This has the hallmarks of a classloading issue. Is the problem only with
xa-datasource? i.e. does the create work ok with local-tx-datasource? If so
that would point towards an issue with XA support in the driver.
View the original post :
The issues you are seeing are consistent with mixing XA and non-XA transactions
on the same connection, which earlier versions of Oracle have a problem with.
Please check your datasource configuration is as per.
http://wiki.jboss.org/wiki/Wiki.jsp?page=IHaveProblemsWithOracleXA
If it is and you
That looks like a classloader issue. Does your .war contain the
javax.transaction classes, perhaps from hibernate's jta.jar? If so, try
removing them.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4049689#4049689
Reply to the post :
There is a config flag for JBossTS to allow multiple last resources. However,
it's really not recommended. If you need transactions at all you probably need
them to work properly! What are the issues you found when converting to XA?
View the original post :
Olivier, please can you post the part of the stack trace that comes before
this? At the start of the trace above, the transaction is already active, but
we don't know what has previously been done with it. I suspect hibernate has
enlisted a LastResource into it earlier and is trying to do so
48 matches
Mail list logo
