[JBoss JIRA] (JBTM-2065) TestExternManageDestination::test_stored_message_schedule() hangs on Windows
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2065?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-2065:
---------------------------------
[~clebert] It looks like the hornetq 2.4.1.Final has not release to the nexus so I build it with the following steps
{noformat}
git clone https://github.com/hornetq/hornetq
git reset --hard 0796fe91b094ffe9b45fcc7f7520eaeaa7230462
mvn clean install
{noformat}
but it fails when building the wildfly-messaging with hornetq 2.4.1.Final
{noformat}
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/BridgeAdd.java:[134,20] no suitable constructor found for BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,boolean,int,java.lang.String,boolean,java.lang.String,java.lang.String)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,int,boolean,int,java.lang.String,boolean,java.lang.String,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,int,boolean,int,java.util.List<java.lang.String>,boolean,java.lang.String,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration() is not applicable
(actual and formal argument lists differ in length)
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/BridgeAdd.java:[143,20] no suitable constructor found for BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,boolean,int,java.util.List<java.lang.String>,boolean,java.lang.String,java.lang.String)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,int,boolean,int,java.lang.String,boolean,java.lang.String,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration(java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,long,long,long,long,double,int,int,int,boolean,int,java.util.List<java.lang.String>,boolean,java.lang.String,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.BridgeConfiguration.BridgeConfiguration() is not applicable
(actual and formal argument lists differ in length)
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/BridgeAdd.java:[165,30] method createBridge in interface org.hornetq.api.core.management.HornetQServerControl cannot be applied to given types;
required: java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,long,double,int,int,boolean,int,long,java.lang.String,boolean,boolean,java.lang.String,java.lang.String
found: java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,long,double,int,boolean,int,long,java.lang.String,boolean,boolean,java.lang.String,java.lang.String
reason: actual and formal argument lists differ in length
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/BridgeAdd.java:[182,30] method createBridge in interface org.hornetq.api.core.management.HornetQServerControl cannot be applied to given types;
required: java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,long,double,int,int,boolean,int,long,java.lang.String,boolean,boolean,java.lang.String,java.lang.String
found: java.lang.String,java.lang.String,java.lang.String,java.lang.String,java.lang.String,long,double,int,boolean,int,long,java.lang.String,boolean,boolean,java.lang.String,java.lang.String
reason: actual and formal argument lists differ in length
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/ClusterConnectionAdd.java:[118,20] no suitable constructor found for ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,long,long,boolean,boolean,int,int,java.lang.String,long,int)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,int,long,long,boolean,boolean,int,int,java.lang.String,long,int) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,long,boolean,boolean,int,int,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,int,long,long,boolean,boolean,int,int,java.util.List<java.lang.String>,boolean,long,int) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,long,boolean,boolean,int,int,java.util.List<java.lang.String>,boolean) is not applicable
(actual and formal argument lists differ in length)
[ERROR] /home/zhfeng/src/zhfeng/jboss-as/messaging/src/main/java/org/jboss/as/messaging/ClusterConnectionAdd.java:[123,20] no suitable constructor found for ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,long,long,boolean,boolean,int,int,java.util.List<java.lang.String>,boolean,long,int)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,int,long,long,boolean,boolean,int,int,java.lang.String,long,int) is not applicable
(actual argument long cannot be converted to int by method invocation conversion)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,long,boolean,boolean,int,int,java.lang.String) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,int,long,long,long,double,long,int,int,long,long,boolean,boolean,int,int,java.util.List<java.lang.String>,boolean,long,int) is not applicable
(actual and formal argument lists differ in length)
constructor org.hornetq.core.config.ClusterConnectionConfiguration.ClusterConnectionConfiguration(java.lang.String,java.lang.String,java.lang.String,long,boolean,boolean,int,int,java.util.List<java.lang.String>,boolean) is not applicable
(actual and formal argument lists differ in length)
[INFO] 6 errors
{noformat}
> TestExternManageDestination::test_stored_message_schedule() hangs on Windows
> ----------------------------------------------------------------------------
>
> Key: JBTM-2065
> URL: https://issues.jboss.org/browse/JBTM-2065
> Project: JBoss Transaction Manager
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: BlackTie
> Reporter: Amos Feng
> Assignee: Amos Feng
> Fix For: 6.0.0.Alpha1
>
>
> http://172.17.131.2/job/btny-pulls-narayana-windows2008/523/consoleText
> http://172.17.131.2/job/btny-pulls-narayana-windows2008/524/consoleText
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-2069) Review BlackTie docs
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/JBTM-2069?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on JBTM-2069:
---------------------------------
Hi Tom,
It looks like more changes such as:
1. we do not use rhq plugin in the administration
2. we introduce the TXN_CFG to support the rts
3. we remove the ACE
Amos
> Review BlackTie docs
> --------------------
>
> Key: JBTM-2069
> URL: https://issues.jboss.org/browse/JBTM-2069
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: BlackTie, Documentation
> Reporter: Tom Jenkinson
> Assignee: Amos Feng
> Fix For: 6.0.0.Alpha1
>
>
> Ensure no erroneous information
> Update AS7 references to WildFly
> For example:
> run.sh -> standalone.sh (changed parameters too)
> JBossAS->WildFly
> paths, are they up-to-date (for example what apps should be deployed and where)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month
[JBoss JIRA] (JBTM-1593) Most top level subsystem folders in the quickstart repo are missing README.md files
by Gytis Trikleris (JIRA)
[ https://issues.jboss.org/browse/JBTM-1593?page=com.atlassian.jira.plugin.... ]
Gytis Trikleris closed JBTM-1593.
---------------------------------
Resolution: Done
> Most top level subsystem folders in the quickstart repo are missing README.md files
> -----------------------------------------------------------------------------------
>
> Key: JBTM-1593
> URL: https://issues.jboss.org/browse/JBTM-1593
> Project: JBoss Transaction Manager
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Demonstrator
> Affects Versions: 5.0.0.M2
> Reporter: Michael Musgrove
> Assignee: Michael Musgrove
> Fix For: 5.0.0.Final
>
>
> Top level subsystem folders in the quickstart repo are missing README.md files (except XTS).
> Use the XTS README.md as an example of what they should look like. I suggest the workload assignments for completing this task as follows:
> ArjunaCore - Mike
> ArjunaJTA - Mike
> ArjunaJTS - Mike
> atsintegration - Mike
> ObjectStore - Mike
> blacktie Amos
> rest-tx - Mike
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 1 month