March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4010) XATerminator interrface of TxManager is not including error codes in XAExceptions thrown

by Adrian Brock (JIRA)

XATerminator interrface of TxManager is not including error codes in XAExceptions thrown ---------------------------------------------------------------------------------------- Key: JBAS-4010 URL: http://jira.jboss.com/jira/browse/JBAS-4010 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-4.0.5.GA Reporter: Adrian Brock Assigned To: Weston Price Attachments: XAException.diff According to the javadoc for XATerminator, it should include an error code in the XAException thrown: e.g. see http://java.sun.com/j2ee/1.4/docs/api/javax/resource/spi/XATerminator.htm... This is similar to the fix for the JBossXALocalException done in JBAS-2807 However, our XATerminator impl in TxManager is not including the error code in the thrown XAException. I'm attaching a diff that shows how to fix this for prepare(), i.e. add XA_RBROLLBACK but this also needs doing for the other methods commit/forget/rollback and tests creating to prevent regression. -- 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

18 years, 1 month

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3406) JMX Console throws 500 exception on regular expressions

by gregorypierce (JIRA)

JMX Console throws 500 exception on regular expressions ------------------------------------------------------- Key: JBAS-3406 URL: http://jira.jboss.com/jira/browse/JBAS-3406 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Environment: OSX 10.4.7 Reporter: gregorypierce When going through the Getting Started guide there is a note to search for service=JNDIView. After bringing up the JNDIView I entered a regular expression to search for all of the JNDI services and the server threw a 500 exception as opposed to saying that that format was not supported. -- 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

18 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-3829) The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed.

by Jean-Frederic Clere (JIRA)

The cookie containing the JSESSIONID is missing when the JVMRoute has to be changed. ------------------------------------------------------------------------------------ Key: JBAS-3829 URL: http://jira.jboss.com/jira/browse/JBAS-3829 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Environment: A cluster of 2 nodes with mod_jk. Reporter: Jean-Frederic Clere Assigned To: Jean-Frederic Clere Priority: Minor When a request comes to node2 and has a JVMRoute in JSESSIONID set to node1 the JVMRoute has to be changed to the node2 to make sure that following request will go to node2. That seems to work only for the first request going to node2 further requests does not send the cookie with JSESSIONID. -- 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

18 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4189) @EJB doesn't work inside a servlet

by Juergen Zimmermann (JIRA)

@EJB doesn't work inside a servlet ---------------------------------- Key: JBAS-4189 URL: http://jira.jboss.com/jira/browse/JBAS-4189 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB3 Affects Versions: JBossAS-4.2.0.CR1 Environment: JBossAS 4.2.0CR1, JDK 5.0_11, WinXP SP2, Eclipse WTP 1.5.3 Reporter: Juergen Zimmermann Assigned To: Bill Burke When a servlet tries to invoke a proxa referencing a stateless session bean I get a null pointer. 1) Stateless session bean: @Stateless @Local(EjbRefLocal.class) public class EjbRefBean implements EjbRefLocal { public String foo() { return "ok"; } } 2) Local interface public interface EjbRefLocal { String foo(); } 3) Servlet public class MyServlet extends HttpServlet { @EJB private EjbRefLocal proxy; @Override protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { final String result = proxy.foo(); System.out.println("RESULT = " + result); } } -- 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

18 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-919) deplace JBossXB descriptor processing with JAXB

by William DeCoste (JIRA)

deplace JBossXB descriptor processing with JAXB ----------------------------------------------- Key: EJBTHREE-919 URL: http://jira.jboss.com/jira/browse/EJBTHREE-919 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.0 CR1 Reporter: William DeCoste Assigned To: William DeCoste -- 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

18 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3637) Way to set JNDI properties for twiddle

by Owen Taylor (JIRA)

Way to set JNDI properties for twiddle -------------------------------------- Key: JBAS-3637 URL: http://jira.jboss.com/jira/browse/JBAS-3637 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Owen Taylor Priority: Minor It is frequently useful to be able to set JDNI properties when running twiddle - for example, you might want to set jnp.disableDiscovery when checking the status of a particular server that might not be running. Right now, this is difficult to do. You can export a JBOSS_CLASSPATH which contains a jndi.properties file before running twiddle.sh, but then you have to include all the standard jars in it, which is quite annoying. A pssible fixes would be one of: A) A way to prepend elements to JBOSS_CLASSPATH without disabling the default construction (also useful for getting a log4j.properties that doesn't drop twiddle.log in the cwd, perhaps) B) A command line option for specifying a particular properties file to load and pass to 'new InitialContext()' (slightly more convenient than A) C) A command line option to define particular properties: twiddle.sh -jnpProperty=jnp.disableDiscovery=true (Or some better syntax) The twiddle code actually does: Properties props = new Properties(System.getProperties()); props.put(Context.PROVIDER_URL, serverURL); ctx = new InitialContext(props); In the case where a server URL is set, so there may have been intention that twiddle.sh -Djnp.disableDiscovery=true would work, but AFAIK property inheritance doesn't work in that place - only the properties directly in props take effect, and system properties won't be looked at in the other code path either. -- 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

18 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-989) Create performance test suite to test failover

by Manik Surtani (JIRA)

Create performance test suite to test failover ---------------------------------------------- Key: JBCACHE-989 URL: http://jira.jboss.com/jira/browse/JBCACHE-989 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0.GA Should be ideally integrated into cruise control builds, and should test a variety of configurations including sync and async replication, BR, etc. -- 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

18 years, 1 month

1
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-105) Refactor the VFS.isArchive and structural deployers

by Scott M Stark (JIRA)

Refactor the VFS.isArchive and structural deployers --------------------------------------------------- Key: JBMICROCONT-105 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-105 Project: JBoss MicroContainer Issue Type: Task Reporter: Scott M Stark We have been arguing about the ambiguity/utility of the vfs isArchive with regard to determing deployment strucutre. Proper separation of behavior would remove isArchive from the vfs and update the structural deployment spi to allow reuse of the structural parse without having to pull in jboss5/MainDeployer + all deployers. A related structure deployer discussion: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92529 VFS visiting: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92141 VFS isArchive removal: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=92139 -- 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

18 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-759) Create a set of deadlock-detecting unit tests

by Manik Surtani (JIRA)

Create a set of deadlock-detecting unit tests --------------------------------------------- Key: JBCACHE-759 URL: http://jira.jboss.com/jira/browse/JBCACHE-759 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 1.4.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 >From email thread: "Okay, found out that jconsole also supports it: MBeans --> java.lang --> Threading --> Operations --> findMonitorDeadlockedThreads(). Of course, if we could integrate this into our test suites to regularly check for deadlocks..." Article from JavaSpecialists: http://www.javaspecialists.co.za/archive/newsletter.do?issue=130&locale=e... -- 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

18 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-152) Dependency names need to be validated earlier

by Scott M Stark (JIRA)

Dependency names need to be validated earlier --------------------------------------------- Key: JBMICROCONT-152 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-152 Project: JBoss MicroContainer Issue Type: Bug Components: Dependency Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossMC_2_0_0 Beta3 I'm seeing an error like the following testing profileservice attachments overrides: Caused by: java.lang.IllegalArgumentException: Null name at org.jboss.dependency.plugins.AbstractController.getContext(AbstractController.java:129) at org.jboss.kernel.plugins.dependency.AbstractKernelController.getContext(AbstractKernelController.java:101) at org.jboss.dependency.plugins.AbstractDependencyItem.resolve(AbstractDependencyItem.java:117) at org.jboss.dependency.plugins.AbstractDependencyInfo.resolveDependencies(AbstractDependencyInfo.java:128) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:595) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:531) at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:489) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:289) at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:192) at org.jboss.system.ServiceController.doInstall(ServiceController.java:638) at org.jboss.system.ServiceController.install(ServiceController.java:271) This error regarding the invalid dependency item name not showing up until there is an attempt to resolve it makes it impossible to debug the problem as there is no context in the dependency to understand why its null. -- 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

18 years, 1 month

3
11
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2007