March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-913) Improvements on documentation

by Clebert Suconic (JIRA)

Improvements on documentation ----------------------------- Key: JBMESSAGING-913 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-913 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.GA Reporter: Clebert Suconic Fix For: 1.2.1 -- 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-646) Testing: JBossMessaging and JBossTS stand-alone integration

by Juha Lindfors (JIRA)

Testing: JBossMessaging and JBossTS stand-alone integration ----------------------------------------------------------- Key: JBMESSAGING-646 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-646 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Juha Lindfors Assigned To: Juha Lindfors Test integration of stand-alone JBMessaging deployment with JBossTS as transaction coordinator. Utilize the existing MessagingXAResourceRecovery from patch in JBMESSAGING-407. -- 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-648) Testing: TX coordinator failure scenarios

by Juha Lindfors (JIRA)

Testing: TX coordinator failure scenarios ----------------------------------------- Key: JBMESSAGING-648 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-648 Project: JBoss Messaging Issue Type: Sub-task Reporter: Juha Lindfors Assigned To: Juha Lindfors Provide test suite that simulates TX coordinator failures and tests for correct behavior of XA recovery. -- 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-652) Register ResourceRecovery at runtime

by Juha Lindfors (JIRA)

Register ResourceRecovery at runtime ------------------------------------ Key: JBMESSAGING-652 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-652 Project: JBoss Messaging Issue Type: Sub-task Components: Messaging Core Reporter: Juha Lindfors Assigned To: Juha Lindfors Priority: Optional Register JBMessaging JTA integration layer to JBossTS dynamically at deploy/runtime. Currently this is a static lib integration at server startup. -- 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-654) Enable JBMessaging and JBossTS integration in AS 4.0.3.SP1

by Juha Lindfors (JIRA)

Enable JBMessaging and JBossTS integration in AS 4.0.3.SP1 ---------------------------------------------------------- Key: JBMESSAGING-654 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-654 Project: JBoss Messaging Issue Type: Sub-task Reporter: Juha Lindfors Assigned To: Ovidiu Feodorov Backport release admin changes (wrt JBossTS/JBossMessaging integration) from AS 4.0.5.GA to AS 4.0.3.SP1 -- 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-653) Enable JBMessaging and JBossTS integration in AS 4.0.4.GA

by Juha Lindfors (JIRA)

Enable JBMessaging and JBossTS integration in AS 4.0.4.GA --------------------------------------------------------- Key: JBMESSAGING-653 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-653 Project: JBoss Messaging Issue Type: Sub-task Components: AS Integration Reporter: Juha Lindfors Assigned To: Ovidiu Feodorov Backport release admin changes (wrt JBossTS/JBossMessaging integration) from AS 4.0.5.GA to AS 4.0.4.GA -- 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
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-647) Testing: JBMessaging failure scenarios

by Juha Lindfors (JIRA)

Testing: JBMessaging failure scenarios -------------------------------------- Key: JBMESSAGING-647 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-647 Project: JBoss Messaging Issue Type: Sub-task Components: Tests and Performance Reporter: Juha Lindfors Assigned To: Juha Lindfors Fix For: 1.0.2.CR1 Provide test suite that generates JBMessaging failure scenarios and executes XA recovery. -- 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
10
0 / 0

[JBoss JIRA] Created: (JBAS-4212) Missing file for tomcat-webctx server configuration

by Martin Vecera (JIRA)

Missing file for tomcat-webctx server configuration --------------------------------------------------- Key: JBAS-4212 URL: http://jira.jboss.com/jira/browse/JBAS-4212 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta2 Environment: JVM 1.5.0, RHEL5 Reporter: Martin Vecera Fix For: JBossAS-5.0.0.Beta2 During startup of tomcat-webctx server configuration I found this in server log: 2:18:52,333 ERROR [AbstractKernelController] Error installing to Configured: name=VFSDeployerScanner state=Instantiated java.io.FileNotFoundException: File does not exist: /trunk/build/output/jboss-5.0.0.Beta2/server/tomcat-webctx/deployers This file really doesn't exists. -- 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: (JBREM-645) Need to cleanup locatorURI parsing

by Scott M Stark (JIRA)

Need to cleanup locatorURI parsing ---------------------------------- Key: JBREM-645 URL: http://jira.jboss.com/jira/browse/JBREM-645 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.0.Alpha3 (Bluto) Reporter: Scott M Stark Assigned To: Tom Elrod Fix For: 2.2.0.Beta1 (Bluto) Remoting is using its own parsing logic to extract the host and port when it should be using a URI object, and have a ctor supporting a URI type. This URI which parses fine via the URI class: URI x = new URI("socket://succubus.starkinternational.com:4446?datatype=invocation"); int port = x.getPort(); fails to parse when passed to the InvokerLocator 370232 ERROR [DeploymentWorker] Operation Distribute failed on target org.jboss.deployment.remoting.StreamingTarget@11e9c82e java.lang.NumberFormatException: For input string: "4446?datatype=invocation" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:456) at java.lang.Integer.parseInt(Integer.java:497) at org.jboss.remoting.InvokerLocator.<init>(InvokerLocator.java:191) at org.jboss.deployment.remoting.StreamingTarget.getClient(StreamingTarget.java:254) at org.jboss.deployment.remoting.StreamingTarget.deploy(StreamingTarget.java:140) at org.jboss.deployment.spi.DeploymentWorker.run(DeploymentWorker.java:74) -- 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
6
0 / 0

[JBoss JIRA] Created: (JBAS-3848) jms message disappeared from db then exception is occured

by Ramil Israfilov (JIRA)

jms message disappeared from db then exception is occured --------------------------------------------------------- Key: JBAS-3848 URL: http://jira.jboss.com/jira/browse/JBAS-3848 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS service Affects Versions: JBossAS-4.0.5.GA Environment: JBOSS 4.0.5.GA, JDK1.5.0_06, solarisx86, clustered on two nodes Reporter: Ramil Israfilov Assigned To: Adrian Brock We running clustered jboss4.0.5 and JBOSS MQ is configured to run in clustered environment. The node which was running Jboss MQ went down. JBOSS MQ successfully restarted on second node.But deliver of JMS message failed with error: 2006-11-13 11:47:59,130 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (cludev02) (WorkManager(3)-28:) Unexpected error delivering message SpyTextMessage { Header { jmsDestination : QUEUE.certione/ExecutorQueue jmsDeliveryMode : 2 jmsExpiration : 0 jmsPriority : 4 jmsMessageID : ID:13-116341486898510 jmsTimeStamp : 1163414868985 jmsCorrelationID: null jmsReplyTo : null jmsType : CertioneAsyncProcessingMessage jmsRedelivered : false jmsProperties : {TrackItemId=738, ExecutorName=certione/PreProcessingProcessRemote, TokenId=19666, AuditRecord=137} jmsPropReadWrite: false msgReadOnly : true producerClientId: ID:13 } Body { text :null } } javax.ejb.EJBException: Failed to acquire the pool semaphore, strictTimeout=10000 at org.jboss.ejb3.StrictMaxPool.get(StrictMaxPool.java:106) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:54) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:245) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy272.onMessage(Unknown Source) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:183) at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:905) at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:170) at org.jboss.mq.SpySession.run(SpySession.java:323) at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:249) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743) at java.lang.Thread.run(Thread.java:595) And the most important is that JMS message disappeared after that from database ! -- 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

8
25
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 March 2007