April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBBUILD-263) Common pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-263?page=all ] Paul Gier closed JBBUILD-263. ----------------------------- Resolution: Out of Date Common has been re factored into it's own project, and the mavenization is complete. > Common pom > ---------- > > Key: JBBUILD-263 > URL: http://jira.jboss.com/jira/browse/JBBUILD-263 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > -- 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 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-264) Common pom

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-264?page=all ] Paul Gier closed JBBUILD-264. ----------------------------- Resolution: Duplicate Issue > Common pom > ---------- > > Key: JBBUILD-264 > URL: http://jira.jboss.com/jira/browse/JBBUILD-264 > Project: JBoss Build System > Issue Type: Sub-task > Components: Maven > Reporter: Ruel Loehr > Assigned To: Paul Gier > Fix For: MavenBuild 2.0 > > -- 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 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBBUILD-176) Look into populating the public maven repository with jboss release binaries

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-176?page=all ] Paul Gier closed JBBUILD-176. ----------------------------- Resolution: Deferred IT will set this up when they have the available resources. This is now listed as one of the requirements for the maven based build system. (http://wiki.jboss.org/wiki/Wiki.jsp?page=MavenITRequirements) > Look into populating the public maven repository with jboss release binaries > ---------------------------------------------------------------------------- > > Key: JBBUILD-176 > URL: http://jira.jboss.com/jira/browse/JBBUILD-176 > Project: JBoss Build System > Issue Type: Feature Request > Reporter: Scott M Stark > Assigned To: Paul Gier > Fix For: MavenBuild 1.2 > > > look into populating the public maven repository with the jboss release binaries. > http://maven.apache.org/maven-1.x/reference/repository-upload.html -- 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 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBPM-395) SwimlaneInstance PooledActor assignment bug (not re-assignment issue)

by Britt Miner (JIRA)

[ http://jira.jboss.com/jira/browse/JBPM-395?page=comments#action_12360076 ] Britt Miner commented on JBPM-395: ---------------------------------- Tom, that is correct. I've been running without the workaround for a few weeks now. > SwimlaneInstance PooledActor assignment bug (not re-assignment issue) > --------------------------------------------------------------------- > > Key: JBPM-395 > URL: http://jira.jboss.com/jira/browse/JBPM-395 > Project: JBoss jBPM > Issue Type: Bug > Components: Core Engine > Affects Versions: jBPM 3.0.1 > Environment: JDK 1.5, Postgresql, JBoss 4.0.2 > Reporter: Britt Miner > Assigned To: Tom Baeyens > > Initializing swimlaneInstances at process creation (or perhaps any time prior to creation of an associated task) will persist any configured actorId to the database, but configured PooledActors are not persisted. The AssignmentHandler functionality seems to work fine--the newly initialized swimlaneInstance has both actorId and pooledActors set correctly; however, the pooledActors will not be persisted. Allowing the swimlaneInstance to be initialized at creation of a related task does result in both actorId and pooledActors being properly persisted. > This issue is similar, though not identical, to http://jira.jboss.com/jira/browse/JBPM-375 and http://jira.jboss.com/jira/browse/JBPM-378 which are both related to swimlane assignment issues. > Why initialize swimlaneInstances at process creation? So that swimlane assignments can be made based on the initiator of the process (responsibilities broken down by regional groups, etc.), and so that those assignments are available for reporting/forcasting purposes. > This is the code fragment used to initialize the swimlanes: > ... > Map swimlanes = processDefinition.getTaskMgmtDefinition().getSwimlanes(); > Iterator itr = swimlanes.keySet().iterator(); > while(itr.hasNext()) { > Swimlane swimlane = (Swimlane)swimlanes.get(itr.next()); > SwimlaneInstance swi = pi.getTaskMgmtInstance().getInitializedSwimlaneInstance(new Execution > Context(pi.getRootToken()), swimlane); > //at this point, swi contains both actors and PooledActors that were specified in configuration and > populated with an appropriate AssignmentHandler > } > graphSession.saveProcessInstance(pi); > jbpmSession.commitTransaction(); > Thanks, > Britt -- 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 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4356) web-console crashes on accessing EJB cause the component is not found (wrong jndi name)

by Ingo Bruell (JIRA)

web-console crashes on accessing EJB cause the component is not found (wrong jndi name) --------------------------------------------------------------------------------------- Key: JBAS-4356 URL: http://jira.jboss.com/jira/browse/JBAS-4356 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-4.0.5.GA Environment: Windows XP SP2, jdk1.6,jdk1.5 Linux kernel 2.6.20.x,jdk1.6 Reporter: Ingo Bruell Assigned To: Darran Lofthouse if i try to access the statistics of a enterprise java bean the web-console crashes. the cause is that the jndi name is not correctly created. here the error from the browser: org.apache.jasper.JasperException: Exception in JSP: /StatelessEjb.jsp:3 1: <%@ taglib uri="/webconsole" prefix="jb" %> 2: <jb:mbean id="ejb" intf="org.jboss.management.j2ee.StatelessSessionBeanMBean" /> 3: <jb:mbean id="container" mbean='<%="jboss.j2ee:service=EJB,jndiName=" + (new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name"))%>' intf="org.jboss.ejb.ContainerMBean" /> 4: <% 5: String ejbName = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("name"); 6: String ejbModule = new javax.management.ObjectName(request.getParameter("ObjectName")).getKeyProperty ("EJBModule"); here the stacktrace: javax.servlet.jsp.JspTagException: org.jboss.mx.util.MBeanProxyCreationException: Object name jboss.j2ee:service=EJB,jndiName=fonet.server.ejb.MasterdataLogic not found: javax.management.InstanceNotFoundException: jboss.j2ee:service=EJB,jndiName=fonet.server.ejb.MasterdataLogic is not registered. at org.jboss.console.plugins.helpers.servlet.MBeanTag.doStartTag(MBeanTag.java:95) at org.apache.jsp.StatelessEjb_jsp._jspService(StatelessEjb_jsp.java:110) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:334) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:619) -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-885) Connecting to two JBoss messaging servers causes interference

by Ben Anderson (JIRA)

Connecting to two JBoss messaging servers causes interference ------------------------------------------------------------- Key: JBMESSAGING-885 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-885 Project: JBoss Messaging Issue Type: Bug Components: JMS Client Manager Affects Versions: 1.0.1.SP4 Environment: Windows XP, Java 1.4.2-b28, JBoss 4.0.4.GA, Pentium 4 2GB RAM Reporter: Ben Anderson Assigned To: Ovidiu Feodorov When connected to two JBoss messaging servers, shutting down one server can affect (i.e. stop) the message listeners connected to the other 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

19 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-944) Messages ending up on different connections when there is more than one server

by Tim Fox (JIRA)

Messages ending up on different connections when there is more than one server ------------------------------------------------------------------------------ Key: JBMESSAGING-944 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-944 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.1.SP5 If a single jms client is connected to more than one 1.0.x server and consuming messages. Then messags can be consumed on the wrong consumer or acked on the wrong server. This is because there is only one callbackserver per remoting protocol and we key only on the consumer id. The fix is to key on the server id too. -- 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 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-195) Unexpected exception thrown with single readonly participant

by Kevin Conner (JIRA)

Unexpected exception thrown with single readonly participant ------------------------------------------------------------ Key: JBTM-195 URL: http://jira.jboss.com/jira/browse/JBTM-195 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: WS-T Implementation Affects Versions: 4.2.2 Reporter: Kevin Conner Assigned To: Kevin Conner An AT transaction with a single readonly participant results in an unexpected exception being through from the completion client. More details can be found in the associated forum entry. -- 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 months

2
2
0 / 0

[JBoss JIRA] Created: (JBTM-189) transaction manager is not properly closing connections on slave server when slave server has exceptions.

by Quande Ren (JIRA)

transaction manager is not properly closing connections on slave server when slave server has exceptions. --------------------------------------------------------------------------------------------------------- Key: JBTM-189 URL: http://jira.jboss.com/jira/browse/JBTM-189 Project: JBoss Transaction Manager Issue Type: Bug Security Level: Public (Everyone can see) Components: JTS Implementation Environment: JBossAS4.0.5, JBossTS4.2.2, multiple servers, distributed transactions. Reporter: Quande Ren Assigned To: Mark Little Priority: Critical This is fully discussed at the forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=97856 I am using JBoss4.0.5.GA and JBossTS4.2.2. I have a ServerA and ServerB and a client. here is my flow senario: Code: 1. client call a stateless session BeanA on ServerA, 2. BeanA do some pre work, 3. BeanA then call another stateless session BeanB on serverB, 4. BeanB do some work, 5. BeanA do some post work. the result shows that if either step 2 or step 5 failed, then the whole transaction get rollbacked correctly. but if step 4 failed, then transaction on ServerA rollback, but the transaction on ServerB does not get rollbacked or committed, we can see the debug information says the xa datasource transaction get started but never get rollbacked. and the database connection remains in use, and when we run the test several times, all the database connections will used up. -- 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 months

4
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1027) InvalidationInterceptor should not replicate putForExternalRead()

by Brian Stansberry (JIRA)

InvalidationInterceptor should not replicate putForExternalRead() ----------------------------------------------------------------- Key: JBCACHE-1027 URL: http://jira.jboss.com/jira/browse/JBCACHE-1027 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Replication Affects Versions: 1.4.1.SP3, 2.0.0.BETA2 Reporter: Brian Stansberry Assigned To: Manik Surtani >From looking at the code, it seems InvalidationInterceptor will send an invalidation message for a putForExternalRead or putFailFast call. That basically means only one node in the cluster will have a given entity cached. The interceptor should just ignore these methods. (Forgive me if I missed something; haven't tested this, just looked at code.) -- 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 months

2
1
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 April 2007