June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-1052) Ergonomics

by Bela Ban (JIRA)

Ergonomics ---------- Key: JGRP-1052 URL: https://jira.jboss.org/jira/browse/JGRP-1052 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 3.0 The goal is to (a) reduce the number of properties needed and (b) determine the values dynamically. Examples: - Determine the best min/max size of a thread pool - Find out what the best timeout values are for retransmission, e.g. based on average retransmission times - Determine the optimal number of credits in FC This is similar to the JVM setting where, starting with 1.5, the initial values can be set, but over time, the JVM dynamically changes them. In the best case, a config contains only a list of protocols without any properties, and JGroups will figure out the correct values. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] (AS7-4179) Ability to easily change AS7 log levels when running the tests

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4179: ----------------------------------- Summary: Ability to easily change AS7 log levels when running the tests Key: AS7-4179 URL: https://issues.jboss.org/browse/AS7-4179 Project: Application Server 7 Issue Type: Feature Request Components: Test Suite Reporter: Stuart Douglas Assignee: Ondrej Zizka Not a high priority, but I think it would be a useful feature to be be able to specify something like -Djbossas.debug.log=org.jboss.ejb,org.jboss.jmx and have the XSLT transforms automatically add debug logging config for the specified packages. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2438) loading multiple sheets of single Excel book by one change-set xml

by Toshiya Kobayashi (JIRA)

loading multiple sheets of single Excel book by one change-set xml ------------------------------------------------------------------ Key: JBRULES-2438 URL: https://jira.jboss.org/jira/browse/JBRULES-2438 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: Toshiya Kobayashi Assignee: Mark Proctor I'm trying to use rules via DecisionTable using change-set. I wrote rules in multiple sheets of single Excel book. Then I configured my change-set xml like: ... <add> <resource source='classpath:data/dtable.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="sheet1" /> </resource> <resource source='classpath:data/dtable.xls' type="DTABLE"> <decisiontable-conf input-type="XLS" worksheet-name="sheet2" /> </resource> </add> ... But only rules of sheet1 were loaded. As far as I observed source codes, KnowledgeAgentImpl.java puts resource into "Map<Resource, ResourceMapping> resources". But even if multiple resources are configured in change-set, it appears to me like those resources are considered as the same resource and eventually only one resource will be registered. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
22
0 / 0

[JBoss JIRA] (JBRULES-3565) drools-spring.xsd references old (incorrect) spring-beans.xsd

by Vinod Kiran Paidimarry (JIRA)

Vinod Kiran Paidimarry created JBRULES-3565: ----------------------------------------------- Summary: drools-spring.xsd references old (incorrect) spring-beans.xsd Key: JBRULES-3565 URL: https://issues.jboss.org/browse/JBRULES-3565 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-spring Reporter: Vinod Kiran Paidimarry Assignee: Mark Proctor drools-spring has been upgraded to Spring Framework 3.0.6 (JBRULES-3446?) but the drools-spring.xsd still references the 2.0 version of spring-beans.xsd {code:xml|title=Current|borderStyle=solid} <xsd:import namespace='http://www.springframework.org/schema/beans' schemaLocation='http://www.springframework.org/schema/beans/spring-beans-2.0.xsd'/> {code} {code:xml|title=Should be |borderStyle=solid} <xsd:import namespace="http://www.springframework.org/schema/beans" schemaLocation="http://www.springframework.org/schema/beans/spring-beans-3.0.xsd"/> {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
2
0 / 0

[JBoss JIRA] (AS7-5063) AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink

by Craig Ringer (JIRA)

Craig Ringer created AS7-5063: --------------------------------- Summary: AS7 should pass the property "eclipselink.target-server = JBoss" to persistence providers, or at least EclipseLink Key: AS7-5063 URL: https://issues.jboss.org/browse/AS7-5063 Project: Application Server 7 Issue Type: Enhancement Components: JPA / Hibernate Affects Versions: 7.1.1.Final Reporter: Craig Ringer Assignee: Scott Marlow Priority: Minor For EclipseLink to properly identify the container and set up correct transaction integration, etc, it needs the property "eclipselink.target-server" to be set to "JBoss". There's an open issue asking EclipseLink to auto detect the container (https://bugs.eclipse.org/bugs/show_bug.cgi?id=383257) but right now, a simple solution to making EclipseLink work well on AS7 is for AS7 to pass that property to EclipseLink. That'll help prevent issues and confusion like this: https://bugs.eclipse.org/bugs/show_bug.cgi?id=365704 Users can set it as a system property right now as shown on bug 383257, but really it'd be best if JBoss passed it to the persistence unit during creation. Time permitting I'll give this a go. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
28
0 / 0

[JBoss JIRA] (AS7-4981) Server instance cannot start after host-contoroller and server instance processes are killed at once in domain mode

by Masafumi Miura (JIRA)

Masafumi Miura created AS7-4981: ----------------------------------- Summary: Server instance cannot start after host-contoroller and server instance processes are killed at once in domain mode Key: AS7-4981 URL: https://issues.jboss.org/browse/AS7-4981 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.2.Final (EAP) Environment: This issue is reproducible in the following versions: * EAP 6.0.0 Beta2 * jboss-as-7.1.2.Final * jboss-as-7.1.3.Final-SNAPSHOT Reporter: Masafumi Miura Assignee: Brian Stansberry When host-contoroller and server instance processes are killed at once in domain mode, the host-controller process is auto-restarted successfully by process-controller but the server instance process is not auto-restarted with the following ERROR in process-controller.log: {noformat:title=process-controller.log|borderStyle=solid} 16:24:47,599 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012010: Process 'Host Controller' finished with an exit status of 137 16:24:47,601 INFO [org.jboss.as.process-controller.server] (reaper for Host Controller) JBAS012020: Waiting 1 seconds until trying to restart process Host Controller. 16:24:47,624 INFO [org.jboss.as.process.Server:server-one.status] (reaper for Server:server-one) JBAS012010: Process 'Server:server-one' finished with an exit status of 137 16:24:48,602 INFO [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) JBAS012017: Starting process 'Host Controller' 16:24:57,088 ERROR [org.jboss.as.process.Server:server-one.status] (ProcessController-threads - 4) JBAS012007: Failed to send reconnect message to process 'Server:server-one' input stream: java.io.IOException: Broken pipe at java.io.FileOutputStream.writeBytes(Native Method) [rt.jar:1.6.0_24] at java.io.FileOutputStream.write(FileOutputStream.java:297) [rt.jar:1.6.0_24] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82) [rt.jar:1.6.0_24] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140) [rt.jar:1.6.0_24] at org.jboss.as.process.ManagedProcess.reconnect(ManagedProcess.java:170) [jboss-as-process-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.process.ProcessController.sendReconnectProcess(ProcessController.java:336) [jboss-as-process-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.process.ProcessControllerServerHandler$InitMessageHandler$ConnectedMessageHandler.handleMessage(ProcessControllerServerHandler.java:224) [jboss-as-process-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.process.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:269) [jboss-as-process-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.process.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:223) [jboss-as-process-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] {noformat} After the above happens, server instance proccess cannot start. When I try to invoke stop and start operation by cli (For instance, /host=slave/server-config=server-one:stop and /host=slave/server-config=server-one:start), the following ERROR is thrown in host-controller.log: {noformat:title=host-controller.log|borderStyle=solid} 16:26:02,501 INFO [org.jboss.as.host.controller] (domain-connection-threads - 1) JBAS010923: Stopping server server-one 16:26:11,211 ERROR [org.jboss.as.controller.management-operation] (domain-connection-threads - 1) JBAS014612: Operation ("start") failed - address: ([ ("host" => "slave"), ("server-config" => "server-one") ]): java.lang.IllegalStateException at org.jboss.as.host.controller.ManagedServer.start(ManagedServer.java:192) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:166) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.host.controller.DomainModelControllerService$DelegatingServerInventory.startServer(DomainModelControllerService.java:557) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.host.controller.operations.ServerStartHandler$1.execute(ServerStartHandler.java:80) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.executeDirect(OperationCoordinatorStepHandler.java:161) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.OperationCoordinatorStepHandler.execute(OperationCoordinatorStepHandler.java:112) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.domain.controller.operations.coordination.PrepareStepHandler.execute(PrepareStepHandler.java:85) [jboss-as-host-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:126) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:111) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler.doExecute(TransactionalProtocolOperationHandler.java:112) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.controller.remote.TransactionalProtocolOperationHandler$ExecuteRequestHandler$1.execute(TransactionalProtocolOperationHandler.java:95) [jboss-as-controller-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:286) [jboss-as-protocol-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:491) [jboss-as-protocol-7.1.3.Final-SNAPSHOT.jar:7.1.3.Final-SNAPSHOT] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.6.0_24] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.6.0_24] at java.lang.Thread.run(Thread.java:679) [rt.jar:1.6.0_24] at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA.jar:2.0.0.GA] {noformat} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
2
0 / 0

[JBoss JIRA] (AS7-4201) Cannot be cast org.apache.cxf.jaxws.context.WrappedMessageContext to javax.xml.ws.handler.soap.SOAPMessageContext

by Will Tatam (JIRA)

Will Tatam created AS7-4201: ------------------------------- Summary: Cannot be cast org.apache.cxf.jaxws.context.WrappedMessageContext to javax.xml.ws.handler.soap.SOAPMessageContext Key: AS7-4201 URL: https://issues.jboss.org/browse/AS7-4201 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.1.Final Reporter: Will Tatam Assignee: Alessio Soldano SOAPMessageContext jaxwsContext = (SOAPMessageContext) wsContext.getMessageContext(); Caused by: java.lang.ClassCastException: org.apache.cxf.jaxws.context.WrappedMessageContext cannot be cast to javax.xml.ws.handler.soap.SOAPMessageContext This was working fine on AS 5.1. If I check the docs for WrappedMessageContext it's sub sclass is SOAPMessageContextImpl which does implement javax.xml.ws.handler.soap.SOAPMessageContext. See http://cxf.apache.org/javadoc/latest/org/apache/cxf/jaxws/context/Wrapped... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
10
0 / 0

[JBoss JIRA] (AS7-4126) double values cannot be read from dmr response

by Rob Cernich (JIRA)

Rob Cernich created AS7-4126: -------------------------------- Summary: double values cannot be read from dmr response Key: AS7-4126 URL: https://issues.jboss.org/browse/AS7-4126 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.Final Reporter: Rob Cernich Assignee: Heiko Braun This appears to be a bug in the GWT compiler. The compiler turns the following: {code:java|title=DataInput.readDouble()} return IEEE754.toDouble(bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++]); {code} into: (effectively; the GWT compiler is adding a set of parentheses around the parameters passed to the native function) {code:java|title=DataInput.readDouble() compiled} return IEEE754.toDouble(new byte[] {bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++], bytes[pos++]}); {code} This results in all double values in the model being interpreted as NaN. I've patched the code I'm using in SwitchYard as follows: {code:java|title=DataInput.java} public double readDouble() throws IOException { byte doubleBytes[] = new byte[8]; readFully(doubleBytes); return IEEE754.toDouble(doubleBytes); } {code} {code:java|title=IEEE754.java} public static native double toDouble(byte[] bytes) /*-{ var ebits = 11; var fbits = 52; // Bytes to bits var bits = []; //snip... } {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1287) SOA-P test suite failures

by Aleksandar Kostadinov (JIRA)

SOA-P test suite failures ------------------------- Key: JBMESSAGING-1287 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1287 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP01 Reporter: Aleksandar Kostadinov Assigned To: Tim Fox I'm running the JBM test suite against the binaries in the SOA-P Platform 4.2 CP01. I see 4 failures. * TEST-org.jboss.test.messaging.jms.bridge.BridgeTest-Remote-bisocket.xml. * org.jboss.test.messaging.jms.clustering.MultipleFailoverTest(Clustering).testFailoverFloodTwoServers * org.jboss.test.messaging.jms.clustering.NoFailoverTest(Clustering).testCrashNoFailover * org.jboss.test.messaging.jms.ManifestTest.testManifestEntries Failure details in here http://hudson.qa.jboss.com/hudson/job/jboss-soa-platform-JBM-testsuite/73... 3 of the failures are timeout (see console log for BridgeTest). We are running on a 2 CPU DualCore physical machine so system speed should not be an 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

13 years, 6 months

6
30
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1491) add support for Ingres RDBMS to JBoss Messaging

by murray armfield (JIRA)

add support for Ingres RDBMS to JBoss Messaging ----------------------------------------------- Key: JBMESSAGING-1491 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1491 Project: JBoss Messaging Issue Type: Patch Affects Versions: 1.4.0.SP3.CP06, EAP/SOA-P Integration, 2.0.0 Beta, 1.4.3.GA, 2.0.0.GA, Unscheduled, AS 5.0 Integration Environment: N/A Reporter: murray armfield Assignee: Tim Fox Priority: Minor I've been working on JBoss support on Ingres. I've written an ingres-persistence-service.xml file for use with Ingres for inclusion as part of JBoss Messaging -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

6
44
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 June 2012