June 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1328) SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured

by Geoffrey De Smet (JIRA)

SelectorConfig, AccepterConfig en other Config's aren't Serializable if they have a direct Selector/Accepter instance configured -------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-1328 URL: http://jira.jboss.com/jira/browse/JBRULES-1328 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: Solver Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Priority: Optional Because AbstractAccepter references LocalSearchSolver references the drools RuleBase references stuff that isn't Serializable... -- 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, 8 months

1
4
0 / 0

[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, 8 months

1
1
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, 8 months

5
9
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, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBAS-9023) EJB Timers

by David Lloyd (JIRA)

EJB Timers ---------- Key: JBAS-9023 URL: https://issues.jboss.org/browse/JBAS-9023 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta3 Parent task for EJB Timer implementation items. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
8
0 / 0

[JBoss JIRA] (AS7-4999) Alllow non persistent configuration(runtime) changes for server groups and domain using CLI

by Shay Matasaro (JIRA)

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (JBJCA-820) Transaction isolation level attribute doesn't accept integer values

by Tyronne Wickramarathne (JIRA)

Tyronne Wickramarathne created JBJCA-820: -------------------------------------------- Summary: Transaction isolation level attribute doesn't accept integer values Key: JBJCA-820 URL: https://issues.jboss.org/browse/JBJCA-820 Project: IronJacamar Issue Type: Feature Request Components: Common Affects Versions: 1.0.11.Final Environment: IronJacamar 1.0.11 Reporter: Tyronne Wickramarathne Assignee: Jesper Pedersen Fix For: 1.0.12.Final It is not possible to specify an integer value for the Transaction Isolation Level attribute. -- 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

2
2
0 / 0

[JBoss JIRA] Created: (SECURITY-610) The continuation of SPNEGO requests causes a 'Login failure' error to be reported.

by Darran Lofthouse (JIRA)

The continuation of SPNEGO requests causes a 'Login failure' error to be reported. ---------------------------------------------------------------------------------- Key: SECURITY-610 URL: https://issues.jboss.org/browse/SECURITY-610 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.2.0 The continuation from the login module now causes the following error to be logged: - 12:46:42,245 ERROR [org.jboss.security.authentication.JBossCachedAuthenticationManager] (http--10.36.4.52-8080-1) Login failure: javax.security.auth.login.LoginException: Continuation Required. at org.jboss.security.negotiation.spnego.SPNEGOLoginModule.login(SPNEGOLoginModule.java:174) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) [:1.6.0_24] at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [:1.6.0_24] at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [:1.6.0_24] at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_24] at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [:1.6.0_24] at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [:1.6.0_24] at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:411) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.authenticate(JBossCachedAuthenticationManager.java:345) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.security.authentication.JBossCachedAuthenticationManager.isValid(JBossCachedAuthenticationManager.java:154) [picketbox-infinispan-4.0.1.jar:4.0.1] at org.jboss.as.web.security.JBossWebRealm.authenticate(JBossWebRealm.java:127) [jboss-as-web-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] at org.jboss.security.negotiation.NegotiationAuthenticator.authenticate(NegotiationAuthenticator.java:187) [jboss-negotiation-2.2.0.SNAPSHOT.jar:2.2.0.SNAPSHO Bringing Kerberos to the domain management security is going to require some of the same behaviour as we have in the SPNEGOLoginModule - it may make sense to pull this common behaviour out of the login module anyway for consistency - this would also remove the exception being logged here. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[JBoss JIRA] (JBADMCON-165) Admin console uses fixed width

by Rico Neubauer (JIRA)

Rico Neubauer created JBADMCON-165: -------------------------------------- Summary: Admin console uses fixed width Key: JBADMCON-165 URL: https://issues.jboss.org/browse/JBADMCON-165 Project: JBoss Admin Console Issue Type: Bug Components: General Console Affects Versions: 1.0 alpha Environment: Any web-browser Reporter: Rico Neubauer With long deployment names, the fixed width of 816 pixels is too narrow, please see attached screenshots. Fix is simple, just use prozentual widths. I will send a pull request. -- 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

2
21
0 / 0

[JBoss JIRA] (AS7-4853) Should the deployments list show where an application is loaded from

by Jim Tyrrell (JIRA)

Jim Tyrrell created AS7-4853: -------------------------------- Summary: Should the deployments list show where an application is loaded from Key: AS7-4853 URL: https://issues.jboss.org/browse/AS7-4853 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun See the attached screen shot, but we can via API load applications, should the console indicate this information? -- 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

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