July 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1212) :read-operation-description(name=add) shows pool-name as optional, but deploy without pool-name fail

by Heiko Rupp (JIRA)

:read-operation-description(name=add) shows pool-name as optional, but deploy without pool-name fail ---------------------------------------------------------------------------------------------------- Key: AS7-1212 URL: https://issues.jboss.org/browse/AS7-1212 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.CR1 Reporter: Heiko Rupp Assignee: Brian Stansberry [domain@localhost:9999 subsystem=datasources] ./data-source=java\:jboss\/datasources\/ExampleDS:read-operation-description(name=add) { "outcome" => "success", "result" => { "operation-name" => "add", "description" => "Adds a new data-source", "request-properties" => { .... "pool-name" => { "description" => "Specifies the pool name for the datasource used for management", "type" => STRING, "required" => false }, So the pool-name is optional, but when I deploy a data source without pool name, deployment fails: [Server:server-one] 17:26:49,124 ERROR [stderr] (pool-1-thread-42) org.jboss.jca.common.api.validator.ValidateException: IJ010068: Missing required attribute pool-name in org.jboss.jca.common.metadata.ds.DataSourceImpl -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
3
0 / 0

[JBoss JIRA] Created: (AS7-1339) Expose RA config properties in DMR

by Heiko Braun (JIRA)

Expose RA config properties in DMR ---------------------------------- Key: AS7-1339 URL: https://issues.jboss.org/browse/AS7-1339 Project: Application Server 7 Issue Type: Feature Request Components: JCA Reporter: Heiko Braun Assignee: Jesper Pedersen Fix For: 7.1.0.Beta1 The config attributes are not exposed: <subsystem xmlns="urn:jboss:domain:resource-adapters:1.0"> [...] <config-property name="host">talk.google.com</config-property> <config-property name="port">5222</config-property> [...] </resource-adapters> [standalone@localhost:9999 /] /subsystem=resource-adapters/resource-adapter=xmpp-ra.rar:read-resource { "outcome" => "success", "result" => { "archive" => "xmpp-ra.rar", "background-validation" => undefined, "background-validation-minutes" => undefined, "blocking-timeout-wait-millis" => undefined, "connection-definitions" => [{ "class-name" => "com/ramphastos/xmpp/jca/XmppManagedConnectionFactory", "jndi-name" => "java:/eis/ra-xmpp", "pool-name" => "XmppFactoryPool", "enabled" => true, "use-java-context" => true, "use-ccm" => true, "max-pool-size" => 100, "min-pool-size" => 10, "pool-prefill" => false, "pool-use-strict-min" => false, "flush-strategy" => "FAILING_CONNECTION_ONLY", "security-application" => true }], "idle-timeout-minutes" => undefined, "max-pool-size" => undefined, "min-pool-size" => undefined, "pool-prefill" => undefined, "pool-use-strict-min" => undefined, "transaction-support" => "NoTransaction", "use-fast-fail" => undefined } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1363) JGroups subsystem add operation executed using "ha" profile of default domain.xml

by Paul Ferraro (JIRA)

JGroups subsystem add operation executed using "ha" profile of default domain.xml --------------------------------------------------------------------------------- Key: AS7-1363 URL: https://issues.jboss.org/browse/AS7-1363 Project: Application Server 7 Issue Type: Bug Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro For whatever reason, in domain mode, the JGroupsSubsystemAdd operation is not being run. Consequently, clustered infinispan caches will not start due to a missing dependency. Strangely enough, standalone mode works fine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-9242) Ports in use message better

by Jim Tyrrell (JIRA)

Ports in use message better --------------------------- Key: JBAS-9242 URL: https://issues.jboss.org/browse/JBAS-9242 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 7.0.0.Beta2 Reporter: Jim Tyrrell When starting up two instances of JBoss AS 7 beta 2, I get the following error message that is not descriptive enough. This error should output the IP address and the port number that was not available. [Host Controller] 16:13:50,135 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.host.controller.management.communication: org.jboss.msc.service.StartException in service jboss.host.controller.management.communication: Failed to start server socket [Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:94) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] [Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] [Host Controller] Caused by: java.net.BindException: Address already in use [Host Controller] at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24] [Host Controller] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24] [Host Controller] at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24] [Host Controller] at org.jboss.as.protocol.ProtocolServer.start(ProtocolServer.java:118) [Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:92) [Host Controller] ... 4 more [Host Controller] [Host Controller] 16:13:50,138 ERROR [org.jboss.as.host.controller] (MSC service thread 1-3) Service [service jboss.host.controller.management.communication] failed.: org.jboss.msc.service.StartException in service jboss.host.controller.management.communication: Failed to start server socket [Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:94) [Host Controller] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1344) [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24] [Host Controller] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24] [Host Controller] at java.lang.Thread.run(Thread.java:680) [:1.6.0_24] [Host Controller] Caused by: java.net.BindException: Address already in use [Host Controller] at java.net.PlainSocketImpl.socketBind(Native Method) [:1.6.0_24] [Host Controller] at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [:1.6.0_24] [Host Controller] at java.net.ServerSocket.bind(ServerSocket.java:328) [:1.6.0_24] [Host Controller] at org.jboss.as.protocol.ProtocolServer.start(ProtocolServer.java:118) [Host Controller] at org.jboss.as.host.controller.mgmt.ManagementCommunicationService.start(ManagementCommunicationService.java:92) [Host Controller] ... 4 more [Host Controller] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-826) Fix or remove @Ignore in RespawnTestCase

by Thomas Diesler (JIRA)

Fix or remove @Ignore in RespawnTestCase ---------------------------------------- Key: AS7-826 URL: https://issues.jboss.org/browse/AS7-826 Project: Application Server 7 Issue Type: Sub-task Reporter: Thomas Diesler Assignee: Kabir Khan -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-9260) Test server respawn logic

by Kabir Khan (JIRA)

Test server respawn logic ------------------------- Key: JBAS-9260 URL: https://issues.jboss.org/browse/JBAS-9260 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Kabir Khan Assignee: Kabir Khan Fix For: 7.0.0.Beta4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
4
0 / 0

[JBoss JIRA] Assigned: (AS7-1344) JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-1344?page=com.atlassian.jira.plugin.s... ] Paul Ferraro reassigned AS7-1344: --------------------------------- Assignee: Paul Ferraro (was: Trustin Lee) > JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor > ---------------------------------------------------------------------------- > > Key: AS7-1344 > URL: https://issues.jboss.org/browse/AS7-1344 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.0.0.Final > Reporter: Michal Linhard > Assignee: Paul Ferraro > Fix For: 7.0.1.Final, 7.1.0.Alpha1 > > > 07:42:39,535 WARNING [org.jgroups.protocols.UDP] (DiagnosticsHandler,default,perf17-37478) Could not retrieve value of attribute (method) getNumTimerTasks: java.lang.reflect.InvocationTargetException > [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] > [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] > [JBoss] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] > [JBoss] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] > [JBoss] at org.jgroups.stack.Protocol.dumpStats(Protocol.java:272) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.stack.ProtocolStack.dumpStats(ProtocolStack.java:310) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.JChannel.dumpStats(JChannel.java:687) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.JChannel$MyProbeHandler.handleProbe(JChannel.java:2099) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2165) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2137) [jgroups-2.12.1.Final.jar:] > [JBoss] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] > [JBoss] Caused by: java.lang.UnsupportedOperationException > [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.getExecutor(TimerSchedulerAdapter.java:168) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.size(TimerSchedulerAdapter.java:153) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > [JBoss] at org.jgroups.protocols.TP.getNumTimerTasks(TP.java:714) [jgroups-2.12.1.Final.jar:] > [JBoss] ... 11 more > {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Resolved: (AS7-1344) JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/AS7-1344?page=com.atlassian.jira.plugin.s... ] Paul Ferraro resolved AS7-1344. ------------------------------- Fix Version/s: 7.0.1.Final 7.1.0.Alpha1 Resolution: Done > JGroups subsystem TimerSchedulerAdapter throws UOE when using timer-executor > ---------------------------------------------------------------------------- > > Key: AS7-1344 > URL: https://issues.jboss.org/browse/AS7-1344 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.0.0.Final > Reporter: Michal Linhard > Assignee: Paul Ferraro > Fix For: 7.0.1.Final, 7.1.0.Alpha1 > > > 07:42:39,535 WARNING [org.jgroups.protocols.UDP] (DiagnosticsHandler,default,perf17-37478) Could not retrieve value of attribute (method) getNumTimerTasks: java.lang.reflect.InvocationTargetException > [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_24] > [JBoss] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [:1.6.0_24] > [JBoss] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [:1.6.0_24] > [JBoss] at java.lang.reflect.Method.invoke(Method.java:597) [:1.6.0_24] > [JBoss] at org.jgroups.stack.Protocol.dumpStats(Protocol.java:272) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.stack.ProtocolStack.dumpStats(ProtocolStack.java:310) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.JChannel.dumpStats(JChannel.java:687) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.JChannel$MyProbeHandler.handleProbe(JChannel.java:2099) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2165) [jgroups-2.12.1.Final.jar:] > [JBoss] at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2137) [jgroups-2.12.1.Final.jar:] > [JBoss] at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] > [JBoss] Caused by: java.lang.UnsupportedOperationException > [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.getExecutor(TimerSchedulerAdapter.java:168) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > [JBoss] at org.jboss.as.clustering.jgroups.TimerSchedulerAdapter.size(TimerSchedulerAdapter.java:153) [jboss-as-clustering-jgroups-7.1.0.Alpha1-SNAPSHOT.jar:7.1.0.Alpha1-SNAPSHOT] > [JBoss] at org.jgroups.protocols.TP.getNumTimerTasks(TP.java:714) [jgroups-2.12.1.Final.jar:] > [JBoss] ... 11 more > {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBJCA-634) Support query timeout for check-valid-connection-sql

by Takayoshi Kimura (JIRA)

Support query timeout for check-valid-connection-sql ---------------------------------------------------- Key: JBJCA-634 URL: https://issues.jboss.org/browse/JBJCA-634 Project: IronJacamar Issue Type: Feature Request Components: JDBC Affects Versions: 1.0.0.Final Reporter: Takayoshi Kimura Assignee: Jesper Pedersen When network hangs and check-valid-connection-sql is executed, it hangs until socket timeout which is normally 5min or more longer. We can avoid this long timeout if we have ability to set query timeout for check-valid-connection-sql and the underlying JDBC driver supports query timeout. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (AS7-1283) Cookie-Based Sessions Broken

by Benjamin Browning (JIRA)

Cookie-Based Sessions Broken ---------------------------- Key: AS7-1283 URL: https://issues.jboss.org/browse/AS7-1283 Project: Application Server 7 Issue Type: Bug Affects Versions: 7.0.0.Final Reporter: Benjamin Browning Priority: Blocker See http://community.jboss.org/message/612763 and http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003120.html. Essentially cookie-based sessions are broken in major browsers and curl unless -Dorg.apache.tomcat.util.http.ServerCookie.FWD_SLASH_IS_SEPARATOR=false is passed on boot. It's likely a large percentage of the people that try AS7 Final will run into this issue and have to spend time trying to figure out why sessions aren't working. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 5 months

4
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011