May 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-9341) Datasource attribute "enabled" not writable

by Heiko Braun (JIRA)

Datasource attribute "enabled" not writable ------------------------------------------- Key: JBAS-9341 URL: https://issues.jboss.org/browse/JBAS-9341 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.0.0.Beta4 [localhost:9999 /] /profile=default/subsystem=datasources/data-source=myDS:write-attribute(name=enabled, value=false) { "outcome" => "failed", "result" => {"domain-failure-description" => "Attribute enabled is not writeable"} } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

3
8
0 / 0

[JBoss JIRA] Created: (AS7-709) update commands creating JMS resources to work in domain

by Alexey Loubyansky (JIRA)

update commands creating JMS resources to work in domain -------------------------------------------------------- Key: AS7-709 URL: https://issues.jboss.org/browse/AS7-709 Project: Application Server 7 Issue Type: Task Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 7.0.0.CR1 create-jms-cf, create-jms-topic, create-jms-queue currently work only for standalone. In the domain mode they are missing the profile argument. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Deleted: (AS7-717) support of @DataSourceDefinition

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/AS7-717?page=com.atlassian.jira.plugin.sy... ] Stefano Maestri deleted AS7-717: -------------------------------- > support of @DataSourceDefinition > -------------------------------- > > Key: AS7-717 > URL: https://issues.jboss.org/browse/AS7-717 > Project: Application Server 7 > Issue Type: Task > Reporter: Stefano Maestri > Assignee: Stefano Maestri > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1847) JBoss shutdown hangs to be caused by deadlock between "JBoss Shutdown Hook" and "WorkerThread"

by Masafumi Miura (JIRA)

JBoss shutdown hangs to be caused by deadlock between "JBoss Shutdown Hook" and "WorkerThread" ---------------------------------------------------------------------------------------------- Key: JBMESSAGING-1847 URL: https://issues.jboss.org/browse/JBMESSAGING-1847 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3_CP03 Reporter: Masafumi Miura Fix For: 1.4.0.SP3.CP12 JBoss shutdown hangs to be caused by deadlock between "JBoss Shutdown Hook" and JBoss Messaging "WorkerThread" "JBoss Shutdown Hook" daemon prio=1 tid=0x0a023258 nid=0x2a38 in Object.wait() [0x826f8000..0x826fa130] at java.lang.Object.wait(Native Method) - waiting on <0x91593088> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock) at java.lang.Object.wait(Object.java:474) at EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock.acquire(WriterPreferenceReadWriteLock.java:240) - locked <0x91593088> (a EDU.oswego.cs.dl.util.concurrent.WriterPreferenceReadWriteLock$WriterLock) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.setClosed(JMSServerInvocationHandler.java:68) at org.jboss.jms.server.ServerPeer.stopService(ServerPeer.java:349) - locked <0x914cd0a0> (a org.jboss.jms.server.ServerPeer) at org.jboss.system.ServiceMBeanSupport.jbossInternalStop(ServiceMBeanSupport.java:315) at org.jboss.system.ServiceMBeanSupport.stop(ServiceMBeanSupport.java:206) at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:995) at $Proxy0.stop(Unknown Source) at org.jboss.system.ServiceController.stop(ServiceController.java:508) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at org.jboss.system.ServiceController.stop(ServiceController.java:499) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.stop(Unknown Source) at org.jboss.deployment.SARDeployer.stop(SARDeployer.java:336) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy42.stop(Unknown Source) at org.jboss.deployment.XSLSubDeployer.stop(XSLSubDeployer.java:202) at org.jboss.deployment.MainDeployer.stop(MainDeployer.java:667) at org.jboss.deployment.MainDeployer.undeploy(MainDeployer.java:638) at org.jboss.deployment.MainDeployer.shutdown(MainDeployer.java:516) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdownDeployments(ServerImpl.java:1058) at org.jboss.system.server.ServerImpl$ShutdownHook.shutdown(ServerImpl.java:1033) at org.jboss.system.server.ServerImpl$ShutdownHook.run(ServerImpl.java:996) "WorkerThread#12[10.133.46.128:50365]" prio=1 tid=0x0badb610 nid=0x1077 waiting for monitor entry [0x85657000..0x85657eb0] at org.jboss.jms.server.ServerPeer.getDefaultDLQInstance(ServerPeer.java:1187) - waiting to lock <0x914cd0a0> (a org.jboss.jms.server.ServerPeer) at org.jboss.jms.server.endpoint.ServerSessionEndpoint.<init>(ServerSessionEndpoint.java:220) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.createSessionDelegate(ServerConnectionEndpoint.java:249) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$createSessionDelegate$aop(ConnectionAdvised.java:75) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$createSessionDelegate_6052335267724906805.invokeNext(ConnectionAdvised$createSessionDelegate_6052335267724906805.java) at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$createSessionDelegate_6052335267724906805.invokeNext(ConnectionAdvised$createSessionDelegate_6052335267724906805.java) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.createSessionDelegate(ConnectionAdvised.java) at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:87) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (AS7-717) support of @DataSourceDefinition

by Stefano Maestri (JIRA)

support of @DataSourceDefinition -------------------------------- Key: AS7-717 URL: https://issues.jboss.org/browse/AS7-717 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Stefano Maestri Assignee: Stefano Maestri Fix For: 7.0.0.CR1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (AS7-677) CCM configuration

by Jesper Pedersen (JIRA)

CCM configuration ----------------- Key: AS7-677 URL: https://issues.jboss.org/browse/AS7-677 Project: Application Server 7 Issue Type: Task Components: JCA Reporter: Jesper Pedersen Assignee: Stefano Maestri Fix For: 7.0.0.CR1 Add a <cached-connection-manager debug="false" error="false"/> configuration element to the <connector> subsystem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-1290) Assure version compatibility with earlier versions of Remoting

by Ron Sigal (JIRA)

Assure version compatibility with earlier versions of Remoting -------------------------------------------------------------- Key: JBREM-1290 URL: https://issues.jboss.org/browse/JBREM-1290 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1289) CLONE [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker

by Ron Sigal (JIRA)

CLONE [JBREM-1288] - StreamServer for in-jvm connection should create a LocalServerInvoker ------------------------------------------------------------------------------------------ Key: JBREM-1289 URL: https://issues.jboss.org/browse/JBREM-1289 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.4.SP1, 2.2.4 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP2, 2.2.4.SP1 When the org.jboss.remoting.Client method public Object invoke(InputStream inputStream, Object param) throws Throwable; or one of its variants is called, it calls new StreamServer(inputStream), which creates an org.jboss.remoting.transport.Connector to serve the contents of the InputStream. To determine the transport to be used, StreamServer looks for a system property "remoting.stream.transport", and, if it doesn't exist, it uses "socket" by default. However, if the InputStream is being sent to a server in the same JVM, the "local" transport should be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1288) StreamServer for in-jvm connection should create a LocalServerInvoker

by Ron Sigal (JIRA)

StreamServer for in-jvm connection should create a LocalServerInvoker --------------------------------------------------------------------- Key: JBREM-1288 URL: https://issues.jboss.org/browse/JBREM-1288 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.4.SP1, 2.2.4 Reporter: Ron Sigal Fix For: 2.2.4.SP1 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
5
0 / 0

[JBoss JIRA] Created: (JBREM-1285) Callback Connector for in-jvm connection should create a LocalServerInvoker

by Ron Sigal (JIRA)

Callback Connector for in-jvm connection should create a LocalServerInvoker --------------------------------------------------------------------------- Key: JBREM-1285 URL: https://issues.jboss.org/browse/JBREM-1285 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.5.4.SP1, 2.2.4 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.5.4.SP2, 2.2.4.SP1 When the org.jboss.remoting.Client method public void addListener(InvokerCallbackHandler callbackhandler, Map metadata) throws Throwable; or one of its variants is called, it checks if the ClientInvoker is an instance of BidirectionalClientInvoker as part of its determination of whether to set up push or pull callbacks. If the server is in the same jvm, and the parameter "force_remote" is not set to true, then the ClientInvoker will be an instance of LocalClientInvoker, which implements BidirectionalClientInvoker, so that push callbacks will be configured. That means that a callback Connector will be created, whose transport, if not configured in the metadata map, will be derived from the server's InvokerLocator. If, for instance, the transport in the InvokerLocator is "http", the callback Connector will create an instance of CoyoteInvoker. But CoyoteInvoker will create a ServerSocket, which is completely useless since callback invocations will be made by reference. Client.addListener() should check that its ClientInvoker is a LocalClientInvoker, in which case it should use the "local" transport, before deriving the transport from the servers InvokerLocator. Shout out to Justin Bertram for tracking down this problem. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

1
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 2011