July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBMESSAGING-343) Stress test with a large number of clients accessing the server in parallel

by Clebert Suconic (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-343?page=all ] Clebert Suconic reassigned JBMESSAGING-343: ------------------------------------------- Assignee: Clebert Suconic > Stress test with a large number of clients accessing the server in parallel > --------------------------------------------------------------------------- > > Key: JBMESSAGING-343 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-343 > Project: JBoss Messaging > Issue Type: Sub-task > Components: Tests and Performance > Reporter: Ovidiu Feodorov > Assigned To: Clebert Suconic > Fix For: 1.4.0.CR1 > > > Push the limit of concurent clients to limit -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-2957) Replace HA-JNDI AutoDiscovery with JGroups based implementation

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2957?page=all ] Brian Stansberry updated JBAS-2957: ----------------------------------- Fix Version/s: No Release (was: JBossAS-5.0.0.CR1) I don't see this happening any time soon. The initial work Jerry did on it found as many issues as it would resolve. > Replace HA-JNDI AutoDiscovery with JGroups based implementation > --------------------------------------------------------------- > > Key: JBAS-2957 > URL: http://jira.jboss.com/jira/browse/JBAS-2957 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Jerry Gauthier > Assigned To: Brian Stansberry > Priority: Minor > Fix For: No Release > > > HA-JNDI AutoDiscovery uses its own IP multicasting-based discovery mechanism. This is error-prone code and should be replaced with the well-tested JGroups framework. > See JIRA issue JBCLUSTER-43 for further details. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1010) ORA-01000: maximum open cursors exceeded when adding messages to a queue

by Jay Howell (JIRA)

ORA-01000: maximum open cursors exceeded when adding messages to a queue ------------------------------------------------------------------------ Key: JBMESSAGING-1010 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1010 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.3.0.GA Reporter: Jay Howell Assigned To: Tim Fox When users create a large amount of messages and don't consume them, oracle users will get an error telling them that there are too many cursors open. The test was done with 20,000 text messages. In JDBCPersistenceManager::pageReferences we need to create the prepared statement once. We need to move the prepared statement out side of the loop. This will reduce the number of cursors open and should alleviate the problem. -- 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

19 years

3
4
0 / 0

[JBoss JIRA] Created: (JBPM-1012) The web interface should support multiple logins from a single browser

by Micah Modell (JIRA)

The web interface should support multiple logins from a single browser ---------------------------------------------------------------------- Key: JBPM-1012 URL: http://jira.jboss.com/jira/browse/JBPM-1012 Project: JBoss jBPM Issue Type: Bug Components: Web Interface Affects Versions: jBPM jPDL 3.2.1 Environment: Fedora Core 6 + Firefox 1.5.0.12 + Sun Java 1.5.0.12 Reporter: Micah Modell Assigned To: Tom Baeyens If one logs in to the jbpm-console and then opens a new tab or window, they are already logged in in that window. If they then log out, both windows are effectively logged out. If one opens two tabs on the login screen, logs in on one and then tries to log in on the other, they get the JSP error: HTTP Status 404 - /jbpm-console/sa/j_security_check type Status report message /jbpm-console/sa/j_security_check description The requested resource (/jbpm-console/sa/j_security_check) is not available. Apache Tomcat/5.5.17 -- 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

19 years

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4512) PartitionRestartUnitTestCase should have its own Partition

by Brian Stansberry (JIRA)

PartitionRestartUnitTestCase should have its own Partition ---------------------------------------------------------- Key: JBAS-4512 URL: http://jira.jboss.com/jira/browse/JBAS-4512 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 Everything in PartitionRestartUnitTestCase should be using a special partition built for the test. This will ensure the stopping of the partition during the test doesn't affect subsequent tests. -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4513) Cluster module's JChannelFactory should inject NamingService port

by Brian Stansberry (JIRA)

Cluster module's JChannelFactory should inject NamingService port ----------------------------------------------------------------- Key: JBAS-4513 URL: http://jira.jboss.com/jira/browse/JBAS-4513 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.0.0.Beta2 Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.Beta3 The org.jboss.ha.framework.server.JChannelFactory needs to know the NamingService port so it can use it to construct a unique node name. Currently it gets it by doing a JMX query on the NamingService. We should just dependency inject the value. -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBBUILD-392) Seam to be replicated into jboss repository

by Michael Neale (JIRA)

Seam to be replicated into jboss repository ------------------------------------------- Key: JBBUILD-392 URL: http://jira.jboss.com/jira/browse/JBBUILD-392 Project: JBoss Build System Issue Type: Task Components: JBossBuild Reporter: Michael Neale Assigned To: Paul Gier We have been using http://maven.softeu.cz/ as a repository which has a mavenised version of Seam 1.2 - could this repository be replicated to the jboss maven2 repository so we can remove our reference to it? The specific dependency we are using is: <dependency> <groupId>jboss.seam.profiles</groupId> <artifactId>seam-nopersistence</artifactId> <version>1.2.0.GA</version> <scope>compile</scope> </dependency> -- 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

19 years

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1554) user 'directory_title' instead of 'title' attribute in for google widgets selection

by Boleslaw Dawidowicz (JIRA)

user 'directory_title' instead of 'title' attribute in for google widgets selection ----------------------------------------------------------------------------------- Key: JBPORTAL-1554 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1554 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: 2.6 Final Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.1 Final, 2.8 Final During gadgets selection some of them have '__UP_xxx__' name. To solve this 'directory_title' should be used instead of 'title' attribute -- 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

19 years

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1557) drop the 'title' parameter when rendering a gadget so the best default will be resolved

by Boleslaw Dawidowicz (JIRA)

drop the 'title' parameter when rendering a gadget so the best default will be resolved --------------------------------------------------------------------------------------- Key: JBPORTAL-1557 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1557 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Commented: (JBPM-457) Parent process deployment does not link process-state with subprocess definition

by Tyler Mendenhall (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-457?page=comments#action_12368281 ] Tyler Mendenhall commented on JBPM-457: --------------------------------------- This is still an issue in jbpm-jpdl-3.2.1 and causes the same null pointer issue when deploying a process definition that references a subflow in the jbpm console. I have implemented similar code to resolve the problem in a unit test. I have a deploy process method: protected void deployProcess() { this.dbPersistenceServiceFactory.createSchema(); JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try { String processDef = this.getProcessDefinitionLocation(); if (processDef==null) throw new IllegalArgumentException("unspecified process name"); ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource(processDef); jbpmContext.deployProcessDefinition(processDefinition); this.deploySubProcesses(processDefinition); } finally { jbpmContext.close(); } } private void deploySubProcesses(ProcessDefinition superProcessDef){ JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext(); try{ // for each subprocess defined in the map there will be a node definition in the key // and the process definition xml location in the value Map subProcessMap = this.getSubProcessMap(); for (Iterator iter = subProcessMap.keySet().iterator(); iter.hasNext();) { String nodeName = (String) iter.next(); String definitionLocation = (String)subProcessMap.get(nodeName); if (definitionLocation==null){ throw new IllegalArgumentException("Node:"+nodeName+" is missing the processdefinition.xml location"); } ProcessDefinition processDefinition = ProcessDefinition.parseXmlResource(definitionLocation); jbpmContext.deployProcessDefinition(processDefinition); ProcessState node = (ProcessState)superProcessDef.getNode(nodeName); if (node!=null){ node.setSubProcessDefinition(processDefinition); } else { String superName = superProcessDef.getName(); throw new IllegalArgumentException("Node:"+nodeName+" does not exist in "+superName); } } } finally { jbpmContext.close(); } } However it requires the user to set up the association between process nodes in the parent process definition with individual sub classes. Hopefully this will help out a bit. Thanks, Tyler > Parent process deployment does not link process-state with subprocess definition > -------------------------------------------------------------------------------- > > Key: JBPM-457 > URL: http://jira.jboss.com/jira/browse/JBPM-457 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Reporter: Eduardo Jimenez > Assigned To: Tom Baeyens > > From the ProcessState code: > Code: > if (jbpmSession != null) { > > // now, we must be able to find the sub-process > if (subProcessName != null) { > > // if the name and the version are specified > if (subProcessVersion != null) { > > try { > int version = Integer.parseInt(subProcessVersion); > // select that exact process definition as the subprocess definition > subProcessDefinition = jbpmSession.getGraphSession().findProcessDefinition(subProcessNam > e, version); > } catch (NumberFormatException e) { > jpdlReader.addWarning("version in process-state was not a number: " + processStateElement.asXML()); > } > > } else { // if only the name is specified > // select the latest version of that process as the subprocess > // definition > subProcessDefinition = jbpmSession.getGraphSession().findLatestProcessDefinition(subProces > sName); > } > } else { > jpdlReader.addWarning("no sub-process name specified in process-state " + processStateElement.asXML()); > } > } > > if there is no session open, it simply won't look for the parent process. > Now, from the ProcessArchiveDeployer: > Code: > public static void deployZipInputStream(ZipInputStream zipInputStream, JbpmSessionFactory jbpmSessio > nFactory) { > ProcessDefinition processDefinition = ProcessDefinition.parseParZipInputStream(zipInputStream); > deployProcessDefinition(processDefinition, jbpmSessionFactory); > } > > It reads the process definition first, then calls deploy, which opens the first jbpmSession!!!. The session must be open first before attempting to deploy!. > Now, you might say, use the ant task, but the bug is still there: > Code: > private void deploy(File file, JbpmSessionFactory jbpmSessionFactory) throws IOException, FileNotFou > ndException { > ZipInputStream zipInputStream = new ZipInputStream(new FileInputStream(file)); > ProcessArchiveDeployer.deployZipInputStream(zipInputStream,jbpmSessionFactory); > } > > See, the ant task doens't open a jbpmSession either, so its up to ProcessArchiveDeployer.deployZipInputStream() to do it, which is the same method I'm having an issue with. > Examining ProcessArchiveDeployer, every way of deploying a process would have the same problem. -- 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

19 years

1
0
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 July 2007