August 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1024) Distributed queue stops working when node is killed

by Tim Fox (JIRA)

Distributed queue stops working when node is killed --------------------------------------------------- Key: JBMESSAGING-1024 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1024 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 If start a test with 3 nodes, then kill one of them then the distributed queue doesn't work. Try starting DistributedRequestResponseTest with 3 nodes then killing to replicate. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBFORUMS-165) jboss.com forums migration

by Ryszard Kozmik (JIRA)

jboss.com forums migration -------------------------- Key: JBFORUMS-165 URL: http://jira.jboss.com/jira/browse/JBFORUMS-165 Project: JBoss Forums Issue Type: Task Components: Forum Model Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Priority: Blocker Fix For: 1.1.0 Alpha We need to update migration scripts and test them properly. -- 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, 11 months

3
3
0 / 0

[JBoss JIRA] Deleted: (JBAS-4532) Track JBoss and thirdparty dependencies for JBossAS 4.4.x

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4532?page=all ] Dimitris Andreadis deleted JBAS-4532: ------------------------------------- > Track JBoss and thirdparty dependencies for JBossAS 4.4.x > --------------------------------------------------------- > > Key: JBAS-4532 > URL: http://jira.jboss.com/jira/browse/JBAS-4532 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > > Parent task to track jboss and thirdparty library dependencies/upgrades for JBossAS 4.4.x -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (BPEL-190) webservice descriptors generation tool

by Alejandro Guizar (JIRA)

[ http://jira.jboss.com/jira/browse/BPEL-190?page=all ] Alejandro Guizar updated BPEL-190: ---------------------------------- Summary: webservice descriptors generation tool (was: web app generation tool) > webservice descriptors generation tool > -------------------------------------- > > Key: BPEL-190 > URL: http://jira.jboss.com/jira/browse/BPEL-190 > Project: JBoss jBPM BPEL > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Engine > Affects Versions: jBPM BPEL 1.1 beta 1 > Reporter: Alejandro Guizar > Assigned To: Alejandro Guizar > Fix For: jBPM BPEL 1.2 GA > > > create a tool for generating web application artifacts -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1036) Consider createing JBossDestination interface

by Tim Fox (JIRA)

Consider createing JBossDestination interface --------------------------------------------- Key: JBMESSAGING-1036 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1036 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 To solve forum issue -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1042) Investigate possible casting issue with message bridge

by Tim Fox (JIRA)

Investigate possible casting issue with message bridge ------------------------------------------------------ Key: JBMESSAGING-1042 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1042 Project: JBoss Messaging Issue Type: Bug Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.4.0.CR2 -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JGRP-573) Draw blocks with FLUSH (join & state transfer)

by Bela Ban (JIRA)

Draw blocks with FLUSH (join & state transfer) ---------------------------------------------- Key: JGRP-573 URL: http://jira.jboss.com/jira/browse/JGRP-573 Project: JGroups Issue Type: Bug Affects Versions: 2.6 Reporter: Bela Ban Assigned To: Vladimir Blagojevic Fix For: 2.6 To reproduce: #1 Get the latest from CVS head #2 Start 1 Draw: java org.jgroups.demos.Draw -props ./flush-udp.xml -state -use_blocking - The flush-udp.xml config was copied from JGroups/conf and not modified - use_blocking sets the Channel to use blocking #3 Draw some points into Draw #4 Start a second instance of Draw RESULT: the second instance does join correctly and also transfers the state correctly, but it hangs on FLUSH: [linux]/home/bela$ draw -props ./flush-udp.xml -state -use_blocking ------------------------------------------------------- GMS: address is 192.168.0.5:33755 ------------------------------------------------------- -- received BlockEvent ** View=[192.168.0.5:33754|1] [192.168.0.5:33754, 192.168.0.5:33755] read state: 139 entries -- received UnblockEvent 0 [WARN] [main] JChannel.connect(): 192.168.0.5:33755 waiting on UNBLOCK after connect timed out -- 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, 11 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1294) JBP_CMS_WSP_PROP.PK unique contraint violated

by Ian White (JIRA)

JBP_CMS_WSP_PROP.PK unique contraint violated --------------------------------------------- Key: JBPORTAL-1294 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1294 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.6.Alpha2 Environment: AS 4.0.5.GA Oracle 9i Reporter: Ian White Assigned To: Roy Russo Try to create a content item using the CMS Admin Portlet. Get oracle sql exception - primary key unique contraint violated - JBP_CMS_SWP_PROP.PK: 16:32:14,171 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-80 16:32:14,328 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:9 16:32:14,343 INFO [JkMain] Jk running ID=0 time=0/78 config=null 16:32:14,359 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 1m:12s:797ms 16:32:57,671 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000 16:32:57,671 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (JBPORTAL26.SYS_C0032370) violated 16:32:57,671 WARN [JDBCExceptionReporter] SQL Error: 1, SQLState: 23000 16:32:57,671 ERROR [JDBCExceptionReporter] ORA-00001: unique constraint (JBPORTAL26.SYS_C0032370) violated 16:32:57,671 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:249) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:235) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:139) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultAutoFlushEventListener.onAutoFlush(DefaultAutoFlushEventListener.java:41) at org.hibernate.impl.SessionImpl.autoFlushIfRequired(SessionImpl.java:969) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1114) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.loadManagedNode(PortalCMSCacheLoader.java:757) at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.saveWSPPropNodeEntry(PortalCMSCacheLoader.java:560) at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.put(PortalCMSCacheLoader.java:305) at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.put(PortalCMSCacheLoader.java:389) at org.jboss.portal.cms.hibernate.state.PortalCMSCacheLoader.prepare(PortalCMSCacheLoader.java:479) at org.jboss.cache.interceptors.CacheStoreInterceptor.prepareCacheLoader(CacheStoreInterceptor.java:296) at org.jboss.cache.interceptors.CacheStoreInterceptor.invoke(CacheStoreInterceptor.java:130) at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:68) at org.jboss.cache.interceptors.TxInterceptor.runPreparePhase(TxInterceptor.java:804) at org.jboss.cache.interceptors.TxInterceptor$LocalSynchronizationHandler.beforeCompletion(TxInterceptor.java:1069) at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:75) at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1491) at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1110) at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:324) at org.jboss.tm.TxManager.commit(TxManager.java:240) at org.jboss.aspects.tx.TxPolicy.endTransaction(TxPolicy.java:175) at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:87) at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262) at org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java) at org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java) -- 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, 11 months

4
5
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1629) NullPointerException after adding a google portlet to dashboard

by Roman Kalyakin (JIRA)

NullPointerException after adding a google portlet to dashboard --------------------------------------------------------------- Key: JBPORTAL-1629 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1629 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.8 Final Reporter: Roman Kalyakin Assigned To: Julien Viet Attachments: JBPORTAL-1629.patch When adding a "widget/google" type portlet to dashboard in the "configure dashboard" screen and switching back to dasboard, NullPointer exception is thrown. It is displayed in the browser window instead of dashboard. -- 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, 11 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-4607) Transaction timeout is not raising a JMSException in the JBossMQ Persistence manager or StateManager

by Adrian Brock (JIRA)

Transaction timeout is not raising a JMSException in the JBossMQ Persistence manager or StateManager ---------------------------------------------------------------------------------------------------- Key: JBAS-4607 URL: http://jira.jboss.com/jira/browse/JBAS-4607 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.Beta3, JBossAS-4.2.2.GA In JBossMQ, if something other than the jdbc2 PersistenceManager or StateManager marks a transaction as "setRollbackOnly", e.g. a transaction timeout then they both silently rollback the exception without throwing an Exception. An Exception should be thrown to tell the caller that the operation failed. -- 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, 11 months

1
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 August 2007