September 2008 - jbossts-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBTM-29) Separate JTS/WS-T plugin for JBoss 5

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-29?page=com.atlassian.jira.plugin... ] Jonathan Halliday closed JBTM-29. --------------------------------- Resolution: Done JTS binaries will be bundled with JBossAS 5.0.GA, along with install instructions. (JBAS-5919) XTS remains a separate download for now, but runs on either JTA or JTS. Version mismatch issues with adding a later XTS release into an AS that is running an earlier JTA/JTS remain a concern. Eventually we may bundle XTS as a .sar in the AS, but not for AS 5.0.GA. > Separate JTS/WS-T plugin for JBoss 5 > ------------------------------------ > > Key: JBTM-29 > URL: https://jira.jboss.org/jira/browse/JBTM-29 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation, WS-T Implementation > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.4.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-358) Update documentation to describe support for OASIS 1.1 WSTX protocols

by Andrew Dinn (JIRA)

Update documentation to describe support for OASIS 1.1 WSTX protocols --------------------------------------------------------------------- Key: JBTM-358 URL: http://jira.jboss.com/jira/browse/JBTM-358 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Demonstrator, Documentation Affects Versions: 4.3.0.GA Reporter: Andrew Dinn Assigned To: Andrew Dinn Fix For: 4.4.CR1 This being raised to allow JBTM-37 (which includes all the required code changes) to be closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBTM-121) Check XTS recovery

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-121?page=com.atlassian.jira.plugi... ] Jonathan Halliday closed JBTM-121. ---------------------------------- Resolution: Done Recovery is now in place for WS-AT (JBTM-346, JBTM-385). Further work is needed for WS-BA (JBTM-404). Work is also ongoing for a test framework (JBTM-387) > Check XTS recovery > ------------------ > > Key: JBTM-121 > URL: https://jira.jboss.org/jira/browse/JBTM-121 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: WS-T Implementation > Affects Versions: 4.2.1 > Reporter: Mark Little > Assignee: Jonathan Halliday > Priority: Critical > Fix For: 4.4.0.GA > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBTM-393) Clarify use of Business Agreement GetStatus and Status messages and relation to BAParticipant interface

by Andrew Dinn (JIRA)

Clarify use of Business Agreement GetStatus and Status messages and relation to BAParticipant interface ------------------------------------------------------------------------------------------------------- Key: JBTM-393 URL: https://jira.jboss.org/jira/browse/JBTM-393 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.4.CR1 Reporter: Andrew Dinn Assignee: Andrew Dinn Fix For: 4.4 The BAWithXXXCompletionParticipant interfaces which define the API implemented by Web service-specific participant implementations (and also the participant stubs on the coordinator side) include methods with the following signatures: public String status() throws SystemException; public String unknown() throws SystemException; public String error() throws SystemException; These appear to relate (vaguely) to the BA protocol message pair GetStatus (request) and Status (response) which can be initiated from either the coordinator or the participant. If so then they appear to be inappropriate as part of the Web service-specific API. The application does not and, indeed, should not need to know about the state model employed by the protocol implementation. status() probably ought to be dropped and maybe also the other two. However, it may be that error and unknown are intended to be called during recovery processing or,perhaps, even normal processing (e.g. if the participant receives an InvalidState fault or a Failed message). So, this needs to be clarified first. The message handlers for the i) GetStatus and ii) Status messages are currently implemented, respectively, i) to dispatch a Status message with the current (service or coordinator-side) participant engine state and ii) to do nothing. The current implementation does not ever dispatch a GetStatus message -- it was not necessary to do so for the purpose of implementing recovery on either the coordinatro or the participant side. Since the BA spec provides no details as to when or how these messages are to be used the current implementation is, perhaps, appropriate, This needs to be clarified and, if necessary, the code modified to verify its use. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

3
4
0 / 0

[JBoss JIRA] Closed: (JBTM-220) Run performance suite

by Michael Musgrove (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-220?page=com.atlassian.jira.plugi... ] Michael Musgrove closed JBTM-220. --------------------------------- Fix Version/s: 4.4.CR2 Resolution: Done The performance test suite has been retrieved from back up and integrated into the qa directory. > Run performance suite > --------------------- > > Key: JBTM-220 > URL: https://jira.jboss.org/jira/browse/JBTM-220 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assignee: Michael Musgrove > Fix For: 4.4.CR2 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Work started: (JBTM-220) Run performance suite

by Michael Musgrove (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-220?page=com.atlassian.jira.plugi... ] Work on JBTM-220 started by Michael Musgrove. > Run performance suite > --------------------- > > Key: JBTM-220 > URL: https://jira.jboss.org/jira/browse/JBTM-220 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Testing > Reporter: Mark Little > Assignee: Michael Musgrove > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBTM-219) Update JacORB support

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-219?page=com.atlassian.jira.plugi... ] Jonathan Halliday closed JBTM-219. ---------------------------------- Resolution: Done > Update JacORB support > --------------------- > > Key: JBTM-219 > URL: https://jira.jboss.org/jira/browse/JBTM-219 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation > Affects Versions: 4.2.3 > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.4.0.GA > > > Try patch 2 of the current release we use and then the next major release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBTM-219) Update JacORB support

by Jonathan Halliday (JIRA)

[ https://jira.jboss.org/jira/browse/JBTM-219?page=com.atlassian.jira.plugi... ] Jonathan Halliday commented on JBTM-219: ---------------------------------------- JBossAS 5.0 trunk now uses JacORB 2.3.0-patch5. However, the additional fixes do not change the API we use, nor provide required behaviour for us running standalone. No point upgrading JBossTS to the new patch at this time. > Update JacORB support > --------------------- > > Key: JBTM-219 > URL: https://jira.jboss.org/jira/browse/JBTM-219 > Project: JBoss Transaction Manager > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JTS Implementation > Affects Versions: 4.2.3 > Reporter: Mark Little > Assignee: Jonathan Halliday > Fix For: 4.4.0.GA > > > Try patch 2 of the current release we use and then the next major release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 7 months

1
0
0 / 0

Help: Configuration of Jboss with corba failed

by touma2007

Hi all, I am trying to configure the jboss server (4.2.0) to use corba instead of RMI. So , I have done the following changes: - I modify the file jndi.properties by adding the following lines: java.naming.factory.initial=com.sun.jndi.cosnaming.CNCtxFactory java.naming.provider.url=corbaloc::lidev206:5528/JBoss/Naming/root and in the jboss.xml file I have included for each bean description the following entry: <invoker> <invoker-proxy-binding-name>iiop</invoker-proxy-binding-name> </invoker> But when starting the jboss server, I have the exception described below: WARNING: "IOP00410201: (COMM_FAILURE) Connection failure: socketType: IIOP_CLEAR_TEXT; hostname: lidev206; port: 5528" org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 201 completed: No at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2172) at com.sun.corba.se.impl.logging.ORBUtilSystemException.connectFailure(ORBUtilSystemException.java:2193) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:205) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:218) at com.sun.corba.se.impl.transport.SocketOrChannelContactInfoImpl.createConnection(SocketOrChannelContactInfoImpl.java:101) at com.sun.corba.se.impl.protocol.CorbaClientRequestDispatcherImpl.beginRequest(CorbaClientRequestDispatcherImpl.java:152) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.request(CorbaClientDelegateImpl.java:118) at com.sun.corba.se.impl.protocol.CorbaClientDelegateImpl.is_a(CorbaClientDelegateImpl.java:211) at org.omg.CORBA.portable.ObjectImpl._is_a(ObjectImpl.java:112) at org.omg.CosNaming.NamingContextHelper.narrow(NamingContextHelper.java:69) at com.sun.jndi.cosnaming.CNCtx.setOrbAndRootContext(CNCtx.java:345) at com.sun.jndi.cosnaming.CNCtx.initOrbAndRootContext(CNCtx.java:205) at com.sun.jndi.cosnaming.CNCtx.<init>(CNCtx.java:69) at com.sun.jndi.cosnaming.CNCtxFactory.getInitialContext(CNCtxFactory.java:32) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:175) at org.jboss.security.plugins.JaasSecurityManagerService.lookupCachePolicy(JaasSecurityManagerService.java:540) at org.jboss.security.plugins.JaasSecurityManagerService.registerSecurityDomain(JaasSecurityManagerService.java:498) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.security.plugins.JaasSecurityDomain.startService(JaasSecurityDomain.java:403) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:595) Caused by: java.net.ConnectException: Connection refused at sun.nio.ch.Net.connect(Native Method) at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:464) at java.nio.channels.SocketChannel.open(SocketChannel.java:146) at com.sun.corba.se.impl.transport.DefaultSocketFactoryImpl.createSocket(DefaultSocketFactoryImpl.java:60) at com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.<init>(SocketOrChannelConnectionImpl.java:188) ... 75 more Best Regards,

15 years, 7 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbossts-issues September 2008