May 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4776) Error during (re) adding connection factory using CLI

by Stefano Maestri (JIRA)

Stefano Maestri created AS7-4776: ------------------------------------ Summary: Error during (re) adding connection factory using CLI Key: AS7-4776 URL: https://issues.jboss.org/browse/AS7-4776 Project: Application Server 7 Issue Type: Bug Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Priority: Critical Fix For: 7.1.3.Final (EAP) /subsystem=resource-adapters/resource-adapter=wsDS:add(archive=teiid-connector-ws.rar, transaction-support=NoTransaction) /subsystem=resource-adapters/resource-adapter=wsDS/connection-definitions=wsDS:add(jndi-name=java:/wsDS, class-name=org.teiid.resource.adapter.ws.WSManagedConnectionFactory, enabled=true, use-java-context=true) /subsystem=resource-adapters/resource-adapter=wsDS/connection-definitions=wsDS/config-properties=EndPoint:add(value={end_point}) /subsystem=resource-adapters/resource-adapter=wsDS:activate /subsystem=resource-adapters/resource-adapter=wsDS:remove 20:48:02,169 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.ra.deployment."teiid-connector-ws.rar_1": org.jboss.msc.service.StartException in service jboss.ra.deployment."teiid-connector-ws.rar_1": org.jboss.jca.core.spi.mdr.NotFoundException: IJ000855: teiid-connector-ws isn't registered at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:127) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26] Caused by: org.jboss.jca.core.spi.mdr.NotFoundException: IJ000855: teiid-connector-ws isn't registered at org.jboss.jca.core.mdr.SimpleMetadataRepository.getResourceAdapter(SimpleMetadataRepository.java:150) at org.jboss.as.connector.metadata.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:87) ... 5 more The problem is present when there is only one RA definitions (added and activated explicitly by :activate operation after deployment of rar) and it's removed. -- 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

14 years, 2 months

2
3
0 / 0

[JBoss JIRA] (AS7-4133) Unable to write attribute redelivery-delay of a messaging addressing setting

by Jan Martiska (JIRA)

Jan Martiska created AS7-4133: --------------------------------- Summary: Unable to write attribute redelivery-delay of a messaging addressing setting Key: AS7-4133 URL: https://issues.jboss.org/browse/AS7-4133 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.1.Final Reporter: Jan Martiska Assignee: Alexey Loubyansky [standalone@localhost:9999 /] /subsystem=messaging/hornetq-server=default/address-setting=#/:write-attribute(name="redelivery-delay", value=50) { "outcome" => "failed", "failure-description" => "JBAS014749: Operation handler failed: JBAS014779: Stage MODEL is already complete", "rolled-back" => true } tried on latest nightly snapshot.. for example in EAP6 ER3 it works fine. -- 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

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] (AS7-4761) CMR relation lost within creating transaction

by Klaus Benary (JIRA)

Klaus Benary created AS7-4761: --------------------------------- Summary: CMR relation lost within creating transaction Key: AS7-4761 URL: https://issues.jboss.org/browse/AS7-4761 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build Reporter: Klaus Benary Assignee: jaikiran pai When creating a CMR related parent *and* child bean in the same transaction, the related child is not visible if it is accessed immediately after creation. After such an immediate access, the relation remains inaccessible within the same transaction even when re-reading the parent by PK. In a new transaction the relation is fine. -- 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

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (AS7-1748) CLI usability: accidental CTRL + C terminates entire session

by Radoslav Husar (JIRA)

CLI usability: accidental CTRL + C terminates entire session ------------------------------------------------------------ Key: AS7-1748 URL: https://issues.jboss.org/browse/AS7-1748 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Environment: Linux Reporter: Radoslav Husar Assignee: Alexey Loubyansky I am not sure if this is possible to not terminate on CTRL+C but its extremely annoying, everyone here is accidentally terminating the whole session all the time. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
8
0 / 0

[JBoss JIRA] (JBRULES-3450) Planner: Terminate Solver as soon as a feasible score is found

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created JBRULES-3450: ----------------------------------------- Summary: Planner: Terminate Solver as soon as a feasible score is found Key: JBRULES-3450 URL: https://issues.jboss.org/browse/JBRULES-3450 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Priority: Minor [This is a newbie contributor issue: it's easy to solve for new contributors] HardAndSoftScore has a method isFeasible(), but it's currently hard to specify that a solver should terminate when a feasible score is attained, because you have to use Integer.MIN_VALUE: {code} <termination> <scoreAttained>0hard/-2147483648soft</scoreAttained> <termination> {code} Adjust org.drools.planner.config.termination.TerminationConfig to support this: {code} <termination> <hardAndSoftScoreFeasible>true</hardAndSoftScoreFeasible> <termination> {code} And copy org.drools.planner.core.termination.ScoreAttainedTermination to org.drools.planner.core.termination.HardAndSoftScoreFeasibleTermination to implement it. Note: the Score will need to be cast to HardAndSoftScore. Bonus points: write a unit test for it (for inspiration, look at PlanningEntityTabuAcceptorTest). -- 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

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2573) Planner should support phasing several solvers after each other

by Geoffrey De Smet (JIRA)

Planner should support phasing several solvers after each other --------------------------------------------------------------- Key: JBRULES-2573 URL: https://jira.jboss.org/browse/JBRULES-2573 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Fix For: FUTURE First start with a 80% of the time simulateted annealing phase and then do 20% of the time tabu search. Notice that initialization is also a phase (a special phase). Needs to get a good name. Alternative naming proposals: * phasing * chaining (not really correct with GoF definition?) * ... (more welcome!) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2427) Extract the commons parts of a deterministic StartingSolutionInitizalizer into a build-in class

by Geoffrey De Smet (JIRA)

Extract the commons parts of a deterministic StartingSolutionInitizalizer into a build-in class ----------------------------------------------------------------------------------------------- Key: JBRULES-2427 URL: https://jira.jboss.org/jira/browse/JBRULES-2427 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.0.M1 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet It's always the same thing (see manual) Meanwhile fix the need to provide the internal LocalSearchSolverScope to a method of a public interface which we expect more then 80% of the users to implement: void initializeSolution(LocalSearchSolverScope localSearchSolverScope); -- 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

14 years, 2 months

1
2
0 / 0

[JBoss JIRA] (JBEE-112) jboss-javaee-web Leaking Dependency to Nexus

by Andrew Rubinger (JIRA)

Andrew Rubinger created JBEE-112: ------------------------------------ Summary: jboss-javaee-web Leaking Dependency to Nexus Key: JBEE-112 URL: https://issues.jboss.org/browse/JBEE-112 Project: JBoss JavaEE Spec APIs Issue Type: Bug Reporter: Andrew Rubinger Assignee: Paul Gier org.jboss.spec:jboss-javaee-web-6.0 (which is propagated to Maven Central) is leaking a dependency to xalan:xalan:2.7.1.jbossorg-2, which is not present in Maven Central. {code}[DEBUG] org.ocpsoft.rewrite:rewrite-parent:pom:1.0.6-SNAPSHOT [DEBUG] org.jboss.spec:jboss-javaee-web-6.0:pom:3.0.1.Final:test [DEBUG] xalan:xalan:jar:2.7.1.jbossorg-2:test{code} Either fix to the correct dependency (something in Central) or push the dependent artifact to Central as well. -- 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

14 years, 2 months

3
2
0 / 0

[JBoss JIRA] (AS7-4587) Remoting subsystem is not consistent with XSD, and not fully exposed in Management API

by Misty Stanley-Jones (JIRA)

Misty Stanley-Jones created AS7-4587: ---------------------------------------- Summary: Remoting subsystem is not consistent with XSD, and not fully exposed in Management API Key: AS7-4587 URL: https://issues.jboss.org/browse/AS7-4587 Project: Application Server 7 Issue Type: Bug Components: Remoting Affects Versions: 7.1.1.Final Reporter: Misty Stanley-Jones Assignee: David Lloyd 1. The XSD says that at the authentication-provider is an element: <authentication-provider name="myprovider" /> However, the Management GUI will only change it with a command like the following, which is operating on an attribute: /profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider) 2. The <sasl> element of the <connector> element of the remoting subsystem is not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here is the configuration which I pasted into my domain.xml to get it working. <sasl> <include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" /> <qop value="auth" /> <strength value="medium" /> <reuse-session value="false" /> <server-auth value="false" /> <policy> <forward-secrecy value="true" /> <no-active value="false" /> <no-anonymous value="false" /> <no-dictionary value="true" /> <no-plain-text value="false" /> <pass-credentials value="true" /> </policy> <properties> <property name="myprop1" value="1" /> <property name="myprop2" value="2" /> </properties> </sasl> 3. Individual properties under the <properties> elements of <connector> and <sasl> will not allow me to have only a name, but requires a value as well. Here is an entire subsystem configuration which seems to work (at least the server starts). I do not have the infrastructure of skills to test it thoroughly. <subsystem xmlns="urn:jboss:domain:remoting:1.1"> <connector name="remoting-connector" socket-binding="remoting" \ security-realm="ApplicationRealm"> <authentication-provider name="myprovider"/> <properties> <property name="myprop3" value="baz"/> </properties> <sasl> <include-mechanisms value="GSSAPI PLAIN DIGEST-MD5"/> <qop value="auth"/> <strength value="medium"/> <server-auth value="false"/> <reuse-session value="false"/> <policy> <forward-secrecy value="true"/> <no-active value="false"/> <no-anonymous value="false"/> <no-dictionary value="true"/> <no-plain-text value="false"/> <pass-credentials value="true"/> </policy> <properties> <property name="myprop1" value="1"/> <property name="myprop2" value="2"/> </properties> </sasl> </connector> <outbound-connections> <outbound-connection name="my-outbound-connection" uri="http://myhost:7777/"/> <remote-outbound-connection name="my-remote-connection" outbound-socket-binding-ref="my-remote-socket" username="myUser" security-realm="myRealm"/> <local-outbound-connection name="myLocalConnection" outbound-socket-binding-ref="my-outbound-socket"/> </outbound-connections> </subsystem> -- 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

14 years, 2 months

3
7
0 / 0

[JBoss JIRA] (AS7-4774) Cannot deploy EJB's if the remoting subsystem is not installed

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-4774: ----------------------------------- Summary: Cannot deploy EJB's if the remoting subsystem is not installed Key: AS7-4774 URL: https://issues.jboss.org/browse/AS7-4774 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.2.Final (EAP) Reporter: Stuart Douglas Assignee: jaikiran pai Priority: Critical Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 -- 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

14 years, 2 months

2
2
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 May 2012