jboss-jira August 2012

jboss-jira@lists.jboss.org

1 participants
1276 discussions

[JBoss JIRA] Created: (JBRULES-2553) CompositeSelector should support weighting the selection of each sub selector.

by Geoffrey De Smet (JIRA)

CompositeSelector should support weighting the selection of each sub selector. ------------------------------------------------------------------------------ Key: JBRULES-2553 URL: https://jira.jboss.org/browse/JBRULES-2553 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.1.0.M2 Reporter: Geoffrey De Smet Assignee: Geoffrey De Smet Priority: Minor Fix For: FUTURE Before the simulated annealing support refactor, this was possible, now it's not because the new CompositeSelector weights them all the same. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5286) Provide BundleContext through framework services

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5286: ----------------------------------- Summary: Provide BundleContext through framework services Key: AS7-5286 URL: https://issues.jboss.org/browse/AS7-5286 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 Currently the framework services Framework.CREATE Framework.INIT Framework.ACTIVE have a value that is internal to the framework and cannot be used by AS7. The SYSTEM_BUNDLE and SYSTEM_CONTEXT services provide the value they suggest. However these are internal to the framework and suggest but don't guarantee a certain framework state. This should be changed such that the system BundleContext is available through the respective framework services -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-4163) could not get connection using ConnectionFactory which from remote jndi lookup; just using RemoteConnectionFactory

by 国清吴 (JIRA)

国清吴 created AS7-4163: ------------------------- Summary: could not get connection using ConnectionFactory which from remote jndi lookup; just using RemoteConnectionFactory Key: AS7-4163 URL: https://issues.jboss.org/browse/AS7-4163 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.1.1.Final Reporter: 国清吴 Assignee: Andy Taylor Priority: Blocker Fix For: 7.1.2.Final the server side configuration: <connectors> <netty-connector name="netty" socket-binding="messaging" /> <netty-connector name="netty-throughput" socket-binding="messaging-throughput"> <param key="batch-delay" value="50"/> </netty-connector> <in-vm-connector name="in-vm" server-id="0"/> </connectors> <acceptors> <netty-acceptor name="netty" socket-binding="messaging" /> <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput"> <param key="batch-delay" value="50"/> <param key="direct-deliver" value="false"/> </netty-acceptor> <in-vm-acceptor name="in-vm" server-id="0"/> </acceptors> .... <interfaces> <interface name="management"> <inet-address value="${jboss.bind.address.management:10.50.50.13}"/> </interface> <interface name="public"> <inet-address value="${jboss.bind.address:10.50.50.13}"/> </interface> <interface name="unsecure"> <inet-address value="${jboss.bind.address.unsecure:10.50.50.13}"/> </interface> </interfaces> <socket-binding-group name="standard-sockets" default-interface="public" port-offset="${jboss.socket.binding.port-offset:0}"> <socket-binding name="management-native" interface="management" port="${jboss.management.native.port:9999}"/> <socket-binding name="management-http" interface="management" port="${jboss.management.http.port:9990}"/> <socket-binding name="management-https" interface="management" port="${jboss.management.https.port:9443}"/> <socket-binding name="ajp" port="8009"/> <socket-binding name="http" port="8080"/> <socket-binding name="https" port="8443"/> <socket-binding name="jacorb" interface="unsecure" port="3528"/> <socket-binding name="jacorb-ssl" interface="unsecure" port="3529"/> <socket-binding name="messaging" port="5445"/> <socket-binding name="messaging-throughput" port="5455"/> <socket-binding name="osgi-http" interface="management" port="8090"/> <socket-binding name="remoting" port="4447"/> <socket-binding name="txn-recovery-environment" port="4712"/> <socket-binding name="txn-status-manager" port="4713"/> <outbound-socket-binding name="mail-smtp"> <remote-destination host="localhost" port="25"/> </outbound-socket-binding> </socket-binding-group> my client side jndi.properties java.naming.factory.initial=org.jboss.naming.remote.client.InitialContextFactory java.naming.provider.url=remote://222.92.115.15:4447 java.naming.security.principal=uname java.naming.security.credentials=pword when i use jndi to lookup an ConnectionFactory,I got the factory like this: HornetQConnectionFactory [serverLocator=ServerLocatorImpl [initialConnectors=[org-hornetq-core-remoting-impl-netty-NettyConnectorFactory?port=5445&host=10-50-50-13], discoveryGroupConfiguration=null], clientID=null, dupsOKBatchSize=1048576, transactionBatchSize=1048576, readOnly=false] but when i use the factory to create an connection,it failed: Caused by: HornetQException[errorCode=2 message=Cannot connect to server(s). Tried with all available servers.] it used ip 10.50.50.13 to create an connection, but i want to use ip 222.92.115.15 to create an connection. I have not found any place to configure this ip for RemoteConnectionFactory -- 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, 9 months

5
9
0 / 0

[JBoss JIRA] (AS7-5283) CLONE - Parameter -server is not added for PC and HC when running on IBM JDK 6 and 7

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/AS7-5283?page=com.atlassian.jira.plugin.s... ] Brian Stansberry moved JBPAPP-9607 to AS7-5283: ----------------------------------------------- Project: Application Server 7 (was: JBoss Enterprise Application Platform) Key: AS7-5283 (was: JBPAPP-9607) Workflow: GIT Pull Request workflow (was: jira) Affects Version/s: 7.1.2.Final (EAP) 7.1.1.Final (was: EAP 6.0.0 ER 7) Release Notes Docs Status: (was: Documented as Known Issue) Release Notes Text: (was: When using the IBM JDK version 6 or 7, the <code>-server</code> parameter is not added to the process controller or host controller commands, when using a managed domain. The error is found in the <filename>domain.sh</filename> script, starting at line 76. The workaround is to edit the <filename>domain.sh</filename> script to add the <code>-server</code> parameter. This will be fixed in a future release.) Component/s: Scripts (was: Scripts and Commands) Security: (was: Public) Fix Version/s: 7.1.3.Final (EAP) 7.2.0.Alpha1 (was: TBD EAP 6) Docs QE Status: (was: NEW) > CLONE - Parameter -server is not added for PC and HC when running on IBM JDK 6 and 7 > ------------------------------------------------------------------------------------ > > Key: AS7-5283 > URL: https://issues.jboss.org/browse/AS7-5283 > Project: Application Server 7 > Issue Type: Bug > Components: Scripts > Affects Versions: 7.1.2.Final (EAP), 7.1.1.Final > Reporter: Rostislav Svoboda > Assignee: Brian Stansberry > Labels: eap601candidate > Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 > > > For IBM JDK 6 and 7 parameter -server is not added for PC and HC, server-one and server-two processes contain -server parameter. > On OracleJDK and OpenJDK it's added by default for domain.sh, in standalone.sh for IBM JDK parameter -server is added. > Problem is in domain.sh script, part starting with line 76. > IBM JDK 6 version output: > java version "1.6.0" > Java(TM) SE Runtime Environment (build pxi3260sr10fp1-20120321_01(SR10 FP1)) > IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260sr10fp1-20120202_101568 (JIT enabled, AOT enabled) > J9VM - 20120202_101568 > JIT - r9_20111107_21307ifx1 > GC - 20120202_AA) > JCL - 20120320_01 > IBM JDK 7 version output: > java version "1.7.0" > Java(TM) SE Runtime Environment (build pxi3270-20110827_01) > IBM J9 VM (build 2.6, JRE 1.7.0 Linux x86-32 20110810_88604 (JIT enabled, AOT enabled) > J9VM - R26_Java726_GA_20110810_1208_B88592 > JIT - r11_20110810_20466 > GC - R26_Java726_GA_20110810_1208_B88592 > J9CL - 20110810_88604) > JCL - 20110809_01 based on Oracle 7b147 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5026) EL invocation creates high contention when running with multiple threads

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-5026: ----------------------------------- Summary: EL invocation creates high contention when running with multiple threads Key: AS7-5026 URL: https://issues.jboss.org/browse/AS7-5026 Project: Application Server 7 Issue Type: Bug Reporter: Stuart Douglas As the ExpressionFactory is looked up from a service loader each time we get a lot of contention on ZipEntry.getEntry() -- 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, 9 months

1
4
0 / 0

[JBoss JIRA] (AS7-5266) Allow execution of scripts from CLI GUI

by Stan Silvert (JIRA)

Stan Silvert created AS7-5266: --------------------------------- Summary: Allow execution of scripts from CLI GUI Key: AS7-5266 URL: https://issues.jboss.org/browse/AS7-5266 Project: Application Server 7 Issue Type: Feature Request Components: CLI Reporter: Stan Silvert Assignee: Stan Silvert >From CLI GUI, allow the user to browse the file system for a CLI script and run it. Also, present a list of previously-run scripts. The list should be persisted so that it survives a restart of CLI GUI. -- 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, 9 months

1
4
0 / 0

← Newer
1
...
125
126
127
128
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2012