December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-713) PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException

by Ben Wang (JIRA)

PojoCache when it has been detached remotely, accessing it again will throw PojoCacheAlreadyDetachedException ------------------------------------------------------------------------------------------------------------- Key: JBCACHE-713 URL: http://jira.jboss.com/jira/browse/JBCACHE-713 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 This is the use case here: cacheA.attach(id, pojo); p = cacheB.find(id); cacheA.detach(id); p.getName(); // this will throw PojoCacheAlreadyDetachedException -- 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 month

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-624) Running on DB2

by Tomaz Cerar (JIRA)

Running on DB2 -------------- Key: JBMESSAGING-624 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-624 Project: JBoss Messaging Issue Type: Patch Components: Messaging Core Persistence Affects Versions: 1.0.1.GA Environment: jboss messaging 1.0.1GA, windows xp, DB2 8.2 iSeries Reporter: Tomaz Cerar Assigned To: Ovidiu Feodorov To make jboss messaging 1.0.1GA work with DB2 there must be attribute UsingBinaryStream in class JDBCPersistenceManager made configurable from service file. in JDBCPersistenceManager you add methods: /** * Managed attribute. */ public boolean isUsingBinaryStream()throws Exception { return usingBinaryStream; } /** * Managed attribute. */ public void setUsingBinaryStream(boolean usingBinaryStream)throws Exception { this.usingBinaryStream = usingBinaryStream; } and in JDBCPersistenceManager-xmbean.xml you have to add: <attribute access="read-write" getMethod="isUsingBinaryStream" setMethod="setUsingBinaryStream"> <description>Should JDBC read as binary stream be used?</description> <name>UsingBinaryStream</name> <type>boolean</type> </attribute> db2-persistence-service.xml -- 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 month

6
12
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-703) ServerManager.startRemoting should read the configuration from XML

by Clebert Suconic (JIRA)

ServerManager.startRemoting should read the configuration from XML ------------------------------------------------------------------ Key: JBMESSAGING-703 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-703 Project: JBoss Messaging Issue Type: Feature Request Affects Versions: 1.2.0.Beta1 Reporter: Clebert Suconic Priority: Optional Fix For: 1.2.1 Using the same XML configuration would be a better approach since it would validate the remoting configuration released. -- 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 month

3
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-467) Sort out JBoss AS dependencies

by Ovidiu Feodorov (JIRA)

Sort out JBoss AS dependencies ------------------------------ Key: JBMESSAGING-467 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-467 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 Currently we've imported JBossAS in the lib area of our project to keep the project compiling. This is hardly an acceptable solution. The proper solution involves: 1) Deciding what JBossAS depenencies we need and getting rid of arificially dependencies 2) Work with AS team to identifiy the AS interfaces that need to be isolated and exposed in the repository. -- 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 month

4
9
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-455) CVS to SVN repository migration

by Ovidiu Feodorov (JIRA)

CVS to SVN repository migration ------------------------------- Key: JBMESSAGING-455 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-455 Project: JBoss Messaging Issue Type: Task Components: Build System Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Alpha1 -- 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 month

4
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-771) TransactionManager is not bound error in Embedded EJB

by Tony Hillerson (JIRA)

TransactionManager is not bound error in Embedded EJB ----------------------------------------------------- Key: EJBTHREE-771 URL: http://jira.jboss.com/jira/browse/EJBTHREE-771 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: Embedded with Tomcat on Windows Reporter: Tony Hillerson I'm deploying a fairly simple web app with embedded ejb3 (RC9) to Tomcat 5.5.20. I get These errors: ERROR 06-10 15:53:41,437 (AbstractController.java:incrementState:440) -Error installing to Start: name=UserTransaction state=Create ... Caused by: javax.naming.NameNotFoundException: Name TransactionManager is not bound in this Context The relevent lines from web.xml: <context-param> <param-name>jboss-kernel-deployments</param-name> <param-value>embedded-jboss-beans.xml, jboss-jms-beans.xml</param-value> </context-param> <listener-class>org.jboss.ejb3.embedded.ServletBootstrapListener</listener-class> -- 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 month

3
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-585) WebServices is having trouble using Messaging

by Ovidiu Feodorov (JIRA)

WebServices is having trouble using Messaging --------------------------------------------- Key: JBMESSAGING-585 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-585 Project: JBoss Messaging Issue Type: Bug Components: AS Integration Reporter: Ovidiu Feodorov Assigned To: Clebert Suconic Fix For: 1.2.0.Alpha2 Thomas Diesler's report (1): ------------------------------------------------------------------------------------------------------------------------------------------------------------- Hi Folks, on jbossas/trunk this jboss-service.xml does not deploy <server> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> </server> 2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar 2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue 2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on 2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar >From the error output I cannot figure out what is missing. 2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED Hi Folks, on jbossas/trunk this jboss-service.xml does not deploy <server> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=RequestQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> <mbean code="org.jboss.jms.server.destination.Queue" name="jboss.messaging.destination:service=Queue,name=ResponseQueue" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer"> jboss.messaging:service=ServerPeer</depends> </mbean> </server> 2006-09-05 10:17:36,612 DEBUG [org.jboss.deployment.SARDeployer:292] Deploying SAR, start step: url file:/home/tdiesler/svn/jboss/jbossas/trunk/build/output/jboss-5.0.0.Beta/server/default/deploy/jbossws-samples-jmstransport.sar 2006-09-05 10:17:36,612 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=RequestQueue 2006-09-05 10:17:36,614 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=RequestQueue on 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:385] starting service jboss.messaging.destination:service=Queue,name=ResponseQueue 2006-09-05 10:17:36,615 DEBUG [org.jboss.system.ServiceController:636] Waiting in start of jboss.messaging.destination:service=Queue,name=ResponseQueue on 2006-09-05 10:17:36,631 DEBUG [org.jboss.deployment.MainDeployer:1032] End deployment start on package: jbossws-samples-jmstransport.sar >From the error output I cannot figure out what is missing. 2006-09-05 10:17:36,653 ERROR [org.jboss.deployment.scanner.URLDeploymentScanner:660] Incomplete Deployment listing: --- MBeans waiting for other MBeans --- ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM --- ObjectName: jboss.messaging.destination:service=Queue,name=ResponseQueue State: CONFIGURED ObjectName: jboss.messaging.destination:service=Queue,name=RequestQueue State: CONFIGURED ObjectName: jboss.j2ee:jndiName=local/OrganizationMDB@18849006,service=EJB State: INSTALLED ------------------------------------------------------------------------------------------------------------------------------------------------------------- Thomas Diesler's report (2): ------------------------------------------------------------------------------------------------------------------------------------------------------------- Please follow How can I build and install the latest? http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQBuildAndInstallJBoss50x Instead of Step 8, do 8. Run the jbossws testsuite cd jbossws/src/test ant main ant -Dtest=org.jboss.test.ws.samples.jmstransport.JMSTransportTestCase one-test You can also run ant tests-samples -- 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 month

6
11
0 / 0

[JBoss JIRA] Created: (JBAOP-310) JBoss Retro packaging

by Kabir Khan (JIRA)

JBoss Retro packaging --------------------- Key: JBAOP-310 URL: http://jira.jboss.com/jira/browse/JBAOP-310 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Kabir Khan Fix For: 2.0.0.alpha3 -- 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 month

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-557) Possible failure to correctly recover persistent messages on crash

by Ovidiu Feodorov (JIRA)

Possible failure to correctly recover persistent messages on crash ------------------------------------------------------------------ Key: JBMESSAGING-557 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-557 Project: JBoss Messaging Issue Type: Bug Components: Messaging Core Persistence Affects Versions: 1.0.1.CR5, 1.0.1.CR4 Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.Beta1 Created based a forum report that describes failure to correctly recover persistent messages after server failure. Need to create a specialized test and investigate. Forum thread: http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974282 -- 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 month

4
9
0 / 0

[JBoss JIRA] Created: (JBPM-799) Show (all) process instance's tokens in diagram

by David Lloyd (JIRA)

Show (all) process instance's tokens in diagram ----------------------------------------------- Key: JBPM-799 URL: http://jira.jboss.com/jira/browse/JBPM-799 Project: JBoss jBPM Issue Type: Sub-task Components: Web Interface Affects Versions: jBPM 3.2 alpha 1 Reporter: David Lloyd Assigned To: Tom Baeyens Right now only the root token is shown. -- 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 month

3
3
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 December 2006