January 2007 - jboss-jira - Jboss List Archives

[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

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

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

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

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

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

4
10
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

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

8
25
0 / 0

[JBoss JIRA] Created: (JBAS-3738) On Windows: timer.test.BasicTimerUnitTestCase fails

by Prabhat Jha (JIRA)

On Windows: timer.test.BasicTimerUnitTestCase fails --------------------------------------------------- Key: JBAS-3738 URL: http://jira.jboss.com/jira/browse/JBAS-3738 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Environment: Windows 2003, Sun JDK1.4 Reporter: Prabhat Jha Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.5.GA Test Class: org.jboss.test.timer.test.BasicTimerUnitTestCase Test Name: testMDBTimer Message property 'UNIQUE_ID' not set. java.lang.NumberFormatException: Message property 'UNIQUE_ID' not set. at org.jboss.mq.SpyMessage.getIntProperty(SpyMessage.java:581) at org.jboss.test.timer.test.BasicTimerUnitTestCase.testMDBTimer(BasicTimerUnitTestCase.java:332) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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
4
0 / 0

[JBoss JIRA] Created: (JBRULES-532) Query feature doesnt seem to work if there is more than one query.

by Sridhar Chandrasekharan (JIRA)

Query feature doesnt seem to work if there is more than one query. ------------------------------------------------------------------ Key: JBRULES-532 URL: http://jira.jboss.com/jira/browse/JBRULES-532 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sridhar Chandrasekharan Assigned To: Mark Proctor Consider the following:- ******************************************************************************* 1) Foo.java package com.foo; public class Foo { private int a; private int b; public Foo(int a, int b) { super(); this.a = a; this.b = b; } public boolean test() { return (a > b); } public int getA() { return a; } public int getB() { return b; } } ******************************************************************************************* 2) FooTest.java package com.foo; import java.io.InputStreamReader; import java.io.*; import java.util.*; import org.drools.RuleBase; import org.drools.RuleBaseFactory; import org.drools.WorkingMemory; import org.drools.compiler.PackageBuilder; import org.drools.rule.Package; import org.drools.QueryResults; import org.drools.QueryResult; public class FooTest { /** * This is a sample file to launch a rule package from a rule source file. */ public static final void main(String[] args) { try { //load up the rulebase RuleBase ruleBase = readRule(); WorkingMemory workingMemory = ruleBase.newWorkingMemory(); //go ! workingMemory.fireAllRules(); QueryResults results = workingMemory.getQueryResults( "Foo query" ); if(results == null) { System.out.println("Result is null"); return; } System.out.println( "we have " + results.size() ); for ( Iterator it = results.iterator(); it.hasNext(); ) { QueryResult result = ( QueryResult ) it.next(); Foo foo = ( Foo ) result.get( "foo" ); System.out.println( "A="+foo.getA() + " B=" + foo.getB()); } } catch (Throwable t) { t.printStackTrace(); } } /** * Please note that this is the "low level" rule assembly API. */ private static RuleBase readRule() throws Exception { //read in the source Reader source = new InputStreamReader( FooTest.class.getResourceAsStream( "/Foo.drl" ) ); //optionally read in the DSL (if you are using it). //Reader dsl = new InputStreamReader( DroolsTest.class.getResourceAsStream( "/mylang.dsl" ) ); //Use package builder to build up a rule package. //An alternative lower level class called "DrlParser" can also be used... PackageBuilder builder = new PackageBuilder(); //this wil parse and compile in one step //NOTE: There are 2 methods here, the one argument one is for normal DRL. builder.addPackageFromDrl( source ); //Use the following instead of above if you are using a DSL: //builder.addPackageFromDrl( source, dsl ); //get the compiled package (which is serializable) Package pkg = builder.getPackage(); //add the package to a rulebase (deploy the rule package). RuleBase ruleBase = RuleBaseFactory.newRuleBase(); ruleBase.addPackage( pkg ); return ruleBase; } } ************************************************** 3) Foo.drl #created on: Oct 9, 2006 package com.foo rule "Initialization rule" when #conditions then assert(new Foo(1,1)); assert(new Foo(2,1)); assert(new Foo(2,3)); assert(new Foo(3,2)); assert(new Foo(3,4)); assert(new Foo(4,3)); end query "Foo query" foo : Foo() end **************************************** The output is as follows:- we have 6 A=1 B=1 A=2 B=1 A=2 B=3 A=3 B=2 A=3 B=4 A=4 B=3 ***************************************** Now add another query to the Foo.drl file query "Bar query" foo : Foo() end and the output is Result is null Adding a second query caused the first query to stop working 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

19 years

4
5
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