November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4936) Editing application.xml does not restart EAR deployment (touching the EAR directory does)

by Gavin King (JIRA)

Editing application.xml does not restart EAR deployment (touching the EAR directory does) ------------------------------------------------------------------------------------------ Key: JBAS-4936 URL: http://jira.jboss.com/jira/browse/JBAS-4936 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Environment: JBoss 4.2.2.GA, Mac Reporter: Gavin King Priority: Critical When I edit or touch the application.xml file, the exploded directory deployment does not restart. If I touch the .ear directory, it does. This is a change from all previous versions of JBoss, and breaks JBoss Tools. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1756) port jacc contention workaround that was made for Intuit to 2.6.2

by Prabhat Jha (JIRA)

port jacc contention workaround that was made for Intuit to 2.6.2 ----------------------------------------------------------------- Key: JBPORTAL-1756 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1756 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Security Affects Versions: 2.6.2 Final Reporter: Prabhat Jha Assigned To: Sohil Shah As agreed during today's portal QA call, please port jacc fix that was done for Intuit to 2.6.2. We will test to make sure everything works as expected and then make it mainstream in 2.6. -- 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

16 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-835) Interceptor API

by David Lloyd (JIRA)

Interceptor API --------------- Key: JBREM-835 URL: http://jira.jboss.com/jira/browse/JBREM-835 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-713) Check if jbossweb can replace tomcat jars for the http server invoker

by Ron Sigal (JIRA)

Check if jbossweb can replace tomcat jars for the http server invoker --------------------------------------------------------------------- Key: JBREM-713 URL: http://jira.jboss.com/jira/browse/JBREM-713 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta2 (Bluto) Reporter: Ron Sigal Assigned To: Tom Elrod Fix For: 2.2.0.Beta2 (Bluto) See if jbossweb has API compatible to tomcat connectors, which would allow it to replace the tomcar jars for CoyoteInvoker. See JBREM-705. -- 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

16 years, 6 months

1
6
0 / 0

[JBoss JIRA] Closed: (JBREM-63) Get rid of the legacy configuration that embeds xml parsing

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-63?page=all ] Ron Sigal closed JBREM-63. -------------------------- Resolution: Done > Get rid of the legacy configuration that embeds xml parsing > ----------------------------------------------------------- > > Key: JBREM-63 > URL: http://jira.jboss.com/jira/browse/JBREM-63 > Project: JBoss Remoting > Issue Type: Task > Affects Versions: 1.0.1 beta > Reporter: Scott M Stark > Assigned To: Ron Sigal > Priority: Blocker > Fix For: 2.4.0.Beta1 (Pinto) > > > I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (BPEL-204) Add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution.

by Kartik Mecheri (JIRA)

Add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution. ---------------------------------------------------------------------------- Key: BPEL-204 URL: http://jira.jboss.com/jira/browse/BPEL-204 Project: JBoss jBPM BPEL Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kartik Mecheri Assigned To: Alejandro Guizar Please add org.jbpm.webapp.servlet.UploadServlet as part of the bpel distribution. This will enable us to deploy a bpel process on a remote server. -- 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

16 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (JGRP-610) Problems with large return value and FC

by Bela Ban (JIRA)

Problems with large return value and FC --------------------------------------- Key: JGRP-610 URL: http://jira.jboss.com/jira/browse/JGRP-610 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 When sending a return value whose size is larger than FC.max_credits, the call hangs. Unit test RpcDispatcher.testLargeReturnValueUnicastCall() reproduces the issue. -- 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

16 years, 6 months

2
10
0 / 0

[JBoss JIRA] Created: (JGRP-614) FC: deadlock with synchronous RPCs and exhausted credits

by Bela Ban (JIRA)

FC: deadlock with synchronous RPCs and exhausted credits -------------------------------------------------------- Key: JGRP-614 URL: http://jira.jboss.com/jira/browse/JGRP-614 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.1 SP5 # Members A and B # A makes a *synchronous* clustered RPC # B handles the RPC by placing the message into a queue where it is processed by the one and only incoming handler thread. # The handler thread dequeues the message and passes it up the stack # In NAKACK, a lock(A) is acquired and the message is passed up # The app receives the message, invokes the method and - since it is synchronous - passes the response down # In FC.down(), we happen to run out of credits and block # FC.down() periodically requests credits from A. # A receives B's credit request and sends new credits to B # B receives the credits and places them into the incoming handler's queue # HOWEVER, B will never get the credits because its incoming handler thread is still stuck in FC.down() and never has a chance to process that message We currently suggest not to use FC with synchronous RPCs on JGroups 2.4.1 (note that 2.5 and higher doesn't have this issue). However, I think a lot of customers don't know this and will run into this issue. I mean, if you think about it, just one time you don't get credits sent to you by the receiver(s), and block in FC.down() and you will block forever ! Solution: introduce a 'minimal' OOB flag into messages, and when an OOB message is received, use a separate thread to pass it up the stack. Since we don't have many OOB messages, there shouldn't be too many threads spawned. -- 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

16 years, 6 months

1
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1100) local-home-jndi-name

by Shane Preater (JIRA)

local-home-jndi-name -------------------- Key: EJBTHREE-1100 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1100 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Environment: Windows XP Reporter: Shane Preater jboss.xml version 3.0 local-home-jndi-name does not work as expected. The proxy which ends up deployed under the given name is actually the local interface not the local home interface. Code to reproduce: Remote bean: public class RemoteHomeTestEJB implements SessionBean { private SessionContext context = null; /* * (non-Javadoc) * * @see javax.ejb.SessionBean#ejbActivate() */ public void ejbActivate() throws EJBException, RemoteException { // TODO Auto-generated method stub } /* * (non-Javadoc) * * @see javax.ejb.SessionBean#ejbPassivate() */ public void ejbPassivate() throws EJBException, RemoteException { // TODO Auto-generated method stub } /* * (non-Javadoc) * * @see javax.ejb.SessionBean#ejbRemove() */ public void ejbRemove() throws EJBException, RemoteException { // TODO Auto-generated method stub } public void ejbCreate() { //Do nothing. } /* * (non-Javadoc) * * @see javax.ejb.SessionBean#setSessionContext(javax.ejb.SessionContext) */ public void setSessionContext(SessionContext ctx) throws EJBException, RemoteException { context = ctx; } public String getHello() { try { LocalHomeTestHome home = null; home = ServiceLocator.locateHome(LocalHomeTestHome.class, "java:comp/env/local/LocalHomeTest"); return home.create().getHello(); } catch (Exception e) { StringWriter stringWriter = new StringWriter(); PrintWriter writer = new PrintWriter(stringWriter); e.printStackTrace(writer); return stringWriter.toString(); } } } ServiceLocater.java: public class ServiceLocator { private static final Logger LOG = Logger.getLogger(ServiceLocator.class); @SuppressWarnings("unchecked") public static <T> T locateHome(Class<T> clazz, String location) throws NamingException { T home = null; Context ic = new InitialContext(); Object potentialHome = ic.lookup(location); if (clazz.isInstance(potentialHome)) { home = (T) potentialHome; } else { home = (T) PortableRemoteObject.narrow(potentialHome, clazz); } return home; } } Local bean: public class LocalHomeTestEJB implements SessionBean { /* (non-Javadoc) * @see javax.ejb.SessionBean#ejbActivate() */ public void ejbActivate() throws EJBException, RemoteException { // TODO Auto-generated method stub } /* (non-Javadoc) * @see javax.ejb.SessionBean#ejbPassivate() */ public void ejbPassivate() throws EJBException, RemoteException { // TODO Auto-generated method stub } public void ejbCreate() { //Do nothing. } /* (non-Javadoc) * @see javax.ejb.SessionBean#ejbRemove() */ public void ejbRemove() throws EJBException, RemoteException { // TODO Auto-generated method stub } /* (non-Javadoc) * @see javax.ejb.SessionBean#setSessionContext(javax.ejb.SessionContext) */ public void setSessionContext(SessionContext ctx) throws EJBException, RemoteException { // TODO Auto-generated method stub } public String getHello() { return "Hello from Aerosystems"; } } ejb-jar.xml: <ejb-jar version="3.0" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd"> <description>Simple migration testing to see how to move to EJB 3</description> <display-name>EjbMigration</display-name> <enterprise-beans> <session> <description><![CDATA[EcardGenerationFacadeSessionEJB Bean]]></description> <display-name>LocalHomeTest</display-name> <ejb-name>LocalHomeTest</ejb-name> <remote>com.aeroint.ejbtest.common.RemoteHomeTestInterface</remote> <local-home>com.aeroint.ejbtest.server.session.LocalHomeTestHome</local-home> <local>com.aeroint.ejbtest.server.session.LocalHomeTestInterface</local> <ejb-class>com.aeroint.ejbtest.server.session.LocalHomeTestEJB</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> </session> <session> <description><![CDATA[EcardUpdateFacadeSessionEJB Bean]]></description> <display-name>RemoteHomeTest</display-name> <ejb-name>RemoteHomeTest</ejb-name> <home>com.aeroint.ejbtest.common.RemoteHomeTestHome</home> <remote>com.aeroint.ejbtest.common.RemoteHomeTestInterface</remote> <ejb-class>com.aeroint.ejbtest.server.facade.RemoteHomeTestEJB</ejb-class> <session-type>Stateless</session-type> <transaction-type>Container</transaction-type> <ejb-local-ref > <ejb-ref-name>local/LocalHomeTest</ejb-ref-name> <ejb-ref-type>Session</ejb-ref-type> <local-home>com.aeroint.ejbtest.server.session.LocalHomeTestHome</local-home> <local>com.aeroint.ejbtest.server.session.LocalHomeTestInterface</local> <ejb-link>LocalHomeTest</ejb-link> </ejb-local-ref> </session> </enterprise-beans> </ejb-jar> jboss.xml: <jboss xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss_5_0.xsd" version="3.0"> <enterprise-beans> <session> <ejb-name>RemoteHomeTest</ejb-name> <home-jndi-name>remote/RemoteHomeTest</home-jndi-name> </session> <session> <ejb-name>LocalHomeTest</ejb-name> <local-home-jndi-name>local/LocalHomeTest</local-home-jndi-name> </session> </enterprise-beans> </jboss> -- 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

16 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBFORUMS-255) Arrows in admin page are displayed wrongly

by Ryszard Kozmik (JIRA)

Arrows in admin page are displayed wrongly ------------------------------------------ Key: JBFORUMS-255 URL: http://jira.jboss.com/jira/browse/JBFORUMS-255 Project: JBoss Forums Issue Type: Bug Components: Forum View Layer Reporter: Ryszard Kozmik Priority: Minor Fix For: 1.0.1 RC, 1.1.0 Alpha Arrows for changing order of forums and categories are messed up after admin panel view refactoring. -- 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

16 years, 6 months

1
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007