January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPM-823) Provide *nix support in the Starters Kit

by Micah Modell (JIRA)

Provide *nix support in the Starters Kit ---------------------------------------- Key: JBPM-823 URL: http://jira.jboss.com/jira/browse/JBPM-823 Project: JBoss jBPM Issue Type: Feature Request Components: Training Environment: RHEL 5 Beta Sun JDK 1.5.0.09 Reporter: Micah Modell Assigned To: Tom Baeyens The Starters Kit and associated documentation is very windows-centric. This is explained adequately and the issues are simple enough to compensate for, but providing the bash scripts would make it that much easier for developers and it's easy to provide them. -- 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, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (JBPM-821) ProcessClassLoader.getResourceAsStream throws JbpmException when the resource is not found in DB

by V?ctor Su?rez (JIRA)

ProcessClassLoader.getResourceAsStream throws JbpmException when the resource is not found in DB ------------------------------------------------------------------------------------------------ Key: JBPM-821 URL: http://jira.jboss.com/jira/browse/JBPM-821 Project: JBoss jBPM Issue Type: Bug Components: Core Engine Affects Versions: jBPM 3.1.2 Reporter: V?ctor Su?rez Assigned To: Tom Baeyens "ProcessClassLoader.getResourceAsStream(String name)" must return null when the resource is not found <link>http://java.sun.com/j2se/1.4.2/docs/api/java/lang/ClassLoader.html#getRes...</link>. But when the resource look up must be performed in the DB, if that resource is not found I get a JbpmException. "ProcessClassLoader.getResourceAsStream(String name)" delegates in "fileDefinition.getBytes(name)" for searching the resource, and this calls to "getBytesFromDb(name)", and finally, this calls to "getByteArray(name)", that performs this code: if (byteArray == null) { throw new JbpmException("file '" + name + "' not found in db"); } I think that a possible solution could be: byte[] getBytesFromDb(String name) { byte[] bytes; //refactored this line ByteArray byteArray = doGetByteArray(name); bytes = byteArray.getBytes(); return bytes; } ByteArray getByteArray(String name) { //extract method refactoring ByteArray byteArray = doGetByteArray(name); if (byteArray == null) { throw new JbpmException("file '" + name + "' not found in db"); } return byteArray; } //extracted method ByteArray doGetByteArray(String name) { ByteArray byteArray = (ByteArray) (processFiles != null ? processFiles.get(name) : null); return byteArray; } I let with no modifications "getByteArray(String name)" because is referenced in the rest of code. Thanks -- 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, 8 months

5
5
0 / 0

[JBoss JIRA] Created: (JGRP-347) TCP bundling with FLUSH not working

by Bela Ban (JIRA)

TCP bundling with FLUSH not working ----------------------------------- Key: JGRP-347 URL: http://jira.jboss.com/jira/browse/JGRP-347 Project: JGroups Issue Type: Bug Affects Versions: 2.3 SP1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 We can make TCP with bundling *on* work (timeout 0) if we exchange order of passUp/passDown of the view for a new member in Gms line 509. Since bundler is sending messages in bundles it screws up synchronous step process required for a new member when doing START_FLUSH, view installation, STOP_FLUSH. We have a thread race here on line 509. In order to circumvent that we can *first* pass a view from a join response up to FLUSH and then pass it down. I am not sure how this affects other 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

18 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-3940) Use the JGroups multiplexer in the 4.2 branch

by Brian Stansberry (JIRA)

Use the JGroups multiplexer in the 4.2 branch --------------------------------------------- Key: JBAS-3940 URL: http://jira.jboss.com/jira/browse/JBAS-3940 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-4.2.0.CR1 Branch_4_2 will use JGroups 2.4.1, so we can use the multiplexer and multiplex the various channels. Only code change for this is in ClusterPartition; other services use JBoss Cache where it is just a config change. -- 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, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-823) Unable to call ejb remotely

by Sureshbabu Thyvalappil (JIRA)

Unable to call ejb remotely --------------------------- Key: EJBTHREE-823 URL: http://jira.jboss.com/jira/browse/EJBTHREE-823 Project: EJB 3.0 Issue Type: Bug Environment: JBOSS 4.0.5 with EJB 3.0 Reporter: Sureshbabu Thyvalappil I'm using JBOSS 4.0.5GA with ejb3. I am running into weird behavior when running java client from remote machine. If I run it from the same machine where the jboss server is running, no problem. So here is the behavior I'm noticing. FOr the jndi lookup of ejb, it is connecting the remote server and gets a reference to the ejb. But when I call a method on the ejb reference, it is trying to call a method on the local machine( I mean the same machine where the client is running). Sounds very weird to me. Any help is appreciated from EJB3 experts. I upgraded to EJB3 RC9 patch1, but same behavior. Here is the client code .. try { Properties p=new Properties(); p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); p.put(Context.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces"); p.put(Context.PROVIDER_URL,"jnp://remote-host:1099"); InitialContext ctx = new InitialContext(p); IReportService report = (IReportService) ctx.lookup( "ejb3/xxx/ReportService"); System.out.println("Got the ejb remote reference = "+report); System.out.println("report.resubmit.."+report.resubmit(null,0L)); ReportJob reportJob = new ReportJob(); System.out.println("B4 report.submitRequest.."); report.submitRequest(reportJob); System.out.println("After report.submitRequest.."); } catch (Exception e) { e.printStackTrace(); } -- 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, 8 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3572) Fix the NPEs (better error handling) identified by the new ServiceController testsuite

by Adrian Brock (JIRA)

Fix the NPEs (better error handling) identified by the new ServiceController testsuite -------------------------------------------------------------------------------------- Key: JBAS-3572 URL: http://jira.jboss.com/jira/browse/JBAS-3572 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Reporter: Adrian Brock The new testsuite in system[-jmx] has identifies a number of areas where the old Service deployment (including the impl in JBoss4) does not give a reasonable error message, e.g. it throws an NPE These need to be fixed. -- 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, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBPM-738) jboss.com and jboss.org show different download versions

by Ronald van Kuijk (JIRA)

jboss.com and jboss.org show different download versions -------------------------------------------------------- Key: JBPM-738 URL: http://jira.jboss.com/jira/browse/JBPM-738 Project: JBoss jBPM Issue Type: Bug Environment: JBoss sites Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Priority: Critical http://www.jboss.com/products/jbpm/downloads shows jBPM 3.0.4, 3.1.2 and GPD 3.0.11 http://labs.jboss.com/portal/jbossjbpm/download/ shows jBPM 3.1 and GPD 3.0.8 (bpel version is also wrong) Please can somebody fix this. No wonder old errors pop up know and then. -- 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, 8 months

5
6
0 / 0

[JBoss JIRA] Created: (JBPM-793) refresh the bare bones tutorial

by Tom Baeyens (JIRA)

refresh the bare bones tutorial ------------------------------- Key: JBPM-793 URL: http://jira.jboss.com/jira/browse/JBPM-793 Project: JBoss jBPM Issue Type: Feature Request Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM 3.2 Here's a good example of how it should look like: http://www.springframework.org/docs/MVC-step-by-step/Spring-MVC-step-by-s... No graphical designer, start from the bare jbpm download, jdk 1.4.2 and ant. Work out a minimal example. The main target audience is developers that want to see what jbpm does and how it works. Tooling should be excluded to prevent unnecessary noise for this use case. The getting started that is currently on the wiki will be kept in coexistence. That shows jbpm step by step WITH the tooling. -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (HIBERNATE-55) No way to specify Connection Release Mode in HMBean

by Mohammed Sadiq (JIRA)

No way to specify Connection Release Mode in HMBean --------------------------------------------------- Key: HIBERNATE-55 URL: http://jira.jboss.com/jira/browse/HIBERNATE-55 Project: Hibernate Issue Type: Feature Request Reporter: Mohammed Sadiq Assigned To: Steve Ebersole In my application I have employed an Hibernate MBean for session factory creation and binding it to JNDI and I've added a new overload for the SessionFactory.openSession(Interceptor, ConnectionReleaseMode) method to oveeride the default connection release mode. The default connection release mode for any Hibernate session created using the session factory deployed through a Hibernate MBean configuration is taken as "after_statement". It will be more helpful, if there exists an MBean attribute "ConnectionReleaseMode" which can thake the enumerated values from the org.hibernate.ConnectionReleaseMode. -- 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, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-641) re-implement the callback polling for http transport to reduce latency

by Tom Elrod (JIRA)

re-implement the callback polling for http transport to reduce latency ---------------------------------------------------------------------- Key: JBREM-641 URL: http://jira.jboss.com/jira/browse/JBREM-641 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: callbacks Affects Versions: 2.0.0.GA (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Per forum thread, would be nice to have a more "real-time" way to get callbacks from server when using http transport so don't have to wait on ping period. -- 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, 8 months

2
12
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 January 2007