October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-234) Merge Invoker, Receiver and Replier into a single table

by Alejandro Guizar (JIRA)

Merge Invoker, Receiver and Replier into a single table ------------------------------------------------------- Key: BPEL-234 URL: http://jira.jboss.com/jira/browse/BPEL-234 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.GA -- 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, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (BPEL-217) make bpel-definition.xml optional

by Alejandro Guizar (JIRA)

make bpel-definition.xml optional --------------------------------- Key: BPEL-217 URL: http://jira.jboss.com/jira/browse/BPEL-217 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 the definition descriptor fills the gap of a document import mechanism in v1.1. v2 does provide such a mechanism, making the descriptor redundant for v2 deployments. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (BPEL-218) use imported documents as the default service catalog

by Alejandro Guizar (JIRA)

use imported documents as the default service catalog ----------------------------------------------------- Key: BPEL-218 URL: http://jira.jboss.com/jira/browse/BPEL-218 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 wsdl documents imported by a process are not examined during resolution of partner services, because an alternate, more dynamic service catalog (e.g. an XML registry) is expected to be in place. however, in trivial scenarios, such as deployment from the designer, no alternate catalog exists and the main, if not sole, source of partner information is the list of imported documents. -- 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, 7 months

2
9
0 / 0

[JBoss JIRA] Created: (BPEL-229) Migrate from a SAR to an EAR-based deployment

by Alejandro Guizar (JIRA)

Migrate from a SAR to an EAR-based deployment --------------------------------------------- Key: BPEL-229 URL: http://jira.jboss.com/jira/browse/BPEL-229 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.GA The current SAR-based deployment model is nonportable. Migrate to the new EAR-based deployment model introduced in jBPM jPDL 3.2. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (BPEL-216) integration with the eclipse bpel designer

by Alejandro Guizar (JIRA)

integration with the eclipse bpel designer ------------------------------------------ Key: BPEL-216 URL: http://jira.jboss.com/jira/browse/BPEL-216 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1 Enable one-step deployment of a bpel process + interface wsdl definitions. -- 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, 7 months

2
7
0 / 0

[JBoss JIRA] Created: (JBAS-4639) Optimized replication of ClusteredSession metadata

by Brian Stansberry (JIRA)

Optimized replication of ClusteredSession metadata -------------------------------------------------- Key: JBAS-4639 URL: http://jira.jboss.com/jira/browse/JBAS-4639 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Stop storing clustered session metadata as a single key value pair in JBossCache. Instead, separate those attributes prone to frequent change (s/b just the access timestamp) from those that are largely fixed at session creation. Call cache.put() with the "fixed" ones only on the first request (or in the less likely event that something changes in them, e.g. timeout interval, in a later request.) Store the timestamp with every request; perhaps less often if the request didn't change anything else in the session, i.e. no more often than every 30 secs. With this we can get rid of hacky stuff like using Subject/Observer to track FIELD granularity pojo attribute changes. We just do that so we know whether to replicate session the metadata. -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4068) Port JBAS-4067 fix to trunk

by Brian Stansberry (JIRA)

Port JBAS-4067 fix to trunk --------------------------- Key: JBAS-4068 URL: http://jira.jboss.com/jira/browse/JBAS-4068 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta2 -- 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, 7 months

3
5
0 / 0

[JBoss JIRA] Created: (JBAS-4650) JSFIntegrationUnitTestCase is failing for JBoss AS 5

by Stan Silvert (JIRA)

JSFIntegrationUnitTestCase is failing for JBoss AS 5 ---------------------------------------------------- Key: JBAS-4650 URL: http://jira.jboss.com/jira/browse/JBAS-4650 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Stan Silvert Assigned To: Stan Silvert Fix For: JBossAS-5.0.0.GA JSFIntegrationUnitTestCase fails. The specific assertion that fails is in the logging test. This was caused by setting a default logging level for JSF in log4j.xml. If you run the test twice, it will pass the second time because the test sets logging levels by hitting the Log4JService via HTTP. However, because the WAR for the test is deployed before the logging levels were changed, the WAR would be deployed with the old logging values. So the fix is to change the test to set the logging levels before the WAR is deployed. -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4525) JBossMQ WriteTask in UIL2 could block forever

by Adrian Brock (JIRA)

JBossMQ WriteTask in UIL2 could block forever --------------------------------------------- Key: JBAS-4525 URL: http://jira.jboss.com/jira/browse/JBAS-4525 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.2.1.GA Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.2.CR1 The JBossMQ UIL2 WriteTask shutdowns when it is signaled by the ReadTask using an Thread.interrupt(). If however, something "eats" that interrupt status of the thread then the WriteTask will block forever and never stop. This leads to thread leaks. The solution is not wait forever or an interrupt. Instead the thread should periodically wake up and check the "started" flag. e.g. Here is the suggest patch in outline while (true) { + synchronized (running) + { + if (WriteState != Started) + break; + } BaseMsg msg = null; try { - msg = (BaseMsg) sendQueue.take(); + // Only wait for 10 seconds + msg = (BaseMsg) sendQueue.poll(10000l); + if (msg == null) + continue; // re-start the loop when no message after 10 seconds -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-3517) Redeploy of Tomcat5 Service chokes with RuntimeException

by Anil Saldhana (JIRA)

Redeploy of Tomcat5 Service chokes with RuntimeException -------------------------------------------------------- Key: JBAS-3517 URL: http://jira.jboss.com/jira/browse/JBAS-3517 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.GA Suppose you change a flag in jboss-service.xml in deploy/jbossweb-tomcat55.sar/META-INF, a redeploy of the tomcat 5 service happens. You will notice the following Runtime Exception and the tomcat service fails to deploy. ============================================================================================== 13:33:30,421 INFO [Catalina] Initialization processed in 562 ms 13:33:30,421 INFO [StandardService] Starting service jboss.web 13:33:30,421 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.1 7 13:33:30,453 INFO [StandardHost] XML validation disabled 13:33:30,468 INFO [Catalina] Server startup in 47 ms 13:33:30,468 WARN [ServiceController] Problem starting service jboss.web:service=WebServer java.lang.IllegalArgumentException: Handler for key=javax.servlet.http.HttpServl etRequest, exists, handler: org.jboss.web.tomcat.security.HttpServletRequestPolicyContextHandler@1bb03ee at javax.security.jacc.PolicyContext.registerHandler(PolicyContext.java:185) at org.jboss.web.tomcat.tc5.Tomcat5.startService(Tomcat5.java:467) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) =================================================================================== Use the following api of PolicyContext in Tomcat5 service http://java.sun.com/j2ee/1.4/docs/api/javax/security/jacc/PolicyContext.h... -- 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, 7 months

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007