December 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-494) Convert HA-JNDI stubs to Remoting

by David Lloyd (Resolved) (JIRA)

[ https://issues.jboss.org/browse/AS7-494?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved AS7-494. ----------------------------- Resolution: Out of Date This issue is now out of date. HA-JNDI is no longer the way we handle HA invocation. I will open more specific clustering tasks for the remainder of the AS 7.1 work. > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: AS7-494 > URL: https://issues.jboss.org/browse/AS7-494 > Project: Application Server 7 > Issue Type: Task > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assignee: David Lloyd > Priority: Blocker > Fix For: 7.1.0.CR1 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1957) Create subsystem for HA-JNDI

by Paul Ferraro (JIRA)

Create subsystem for HA-JNDI ---------------------------- Key: AS7-1957 URL: https://issues.jboss.org/browse/AS7-1957 Project: Application Server 7 Issue Type: Task Components: Clustering Affects Versions: 7.1.0.Alpha1 Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.1.0.CR1 Port code from AS6. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] (AS7-494) Convert HA-JNDI stubs to Remoting

by Jason Greene (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-494?page=com.atlassian.jira.plugin.sy... ] Jason Greene updated AS7-494: ----------------------------- Priority: Blocker (was: Major) > Convert HA-JNDI stubs to Remoting > --------------------------------- > > Key: AS7-494 > URL: https://issues.jboss.org/browse/AS7-494 > Project: Application Server 7 > Issue Type: Task > Components: Clustering, Naming, Remoting > Reporter: Brian Stansberry > Assignee: David Lloyd > Priority: Blocker > Fix For: 7.1.0.CR1 > > > The HA-JNDI naming service proxy is based on the old HARMIClient and HARMIServer code. We should convert this to use Remoting. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2820) JMX subsystem model doesn't match schema

by Heiko Braun (Created) (JIRA)

JMX subsystem model doesn't match schema ---------------------------------------- Key: AS7-2820 URL: https://issues.jboss.org/browse/AS7-2820 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JMX Reporter: Heiko Braun Assignee: Brian Stansberry Fix For: 7.1.0.CR1 The xsd contains a list of connectors, which is nor represented in the DMR model. -- 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, 7 months

6
5
0 / 0

[JBoss JIRA] (AS7-2882) CLONE - New Management Jars do not work on previous app-server versions

by Paul Gier (Created) (JIRA)

CLONE - New Management Jars do not work on previous app-server versions ----------------------------------------------------------------------- Key: AS7-2882 URL: https://issues.jboss.org/browse/AS7-2882 Project: Application Server 7 Issue Type: Bug Components: Remoting Affects Versions: 7.1.0.Beta1 Reporter: Paul Gier Assignee: Jason Greene Fix For: 7.1.0.Beta1 I'm not sure if this is in the correct component, however, using the new management jars in JBoss 7.1 beta1, and trying to access the management functions of as7.0.x, the result is not successful. These jars need to be tested for regressions with previous versions. My first test against what seems to be 7.0.0.final (built 5 days before the release, so I suspect it was a near-final build) involved the following error in the CLIENT: Caused by: javax.security.sasl.SaslException: No more authentication mechanisms to try at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:301) at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:200) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:179) at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:100) at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:98) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:72) at org.xnio.nio.NioHandle.run(NioHandle.java:90) at org.xnio.nio.WorkerThread.run(WorkerThread.java:184) at ...asynchronous invocation...(Unknown Source) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:263) at org.jboss.remoting3.EndpointImpl.doConnect(EndpointImpl.java:246) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:353) at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:337) at org.jboss.as.protocol.ProtocolChannelClient.connect(ProtocolChannelClient.java:133) ... 5 more A try against 7.0.2 has different results: when the server started up, the test client simply freezes, with the following stack trace: Object.wait(long) line: not available [native method] ManagementRequest$ManagementFuture<T>(Object).wait() line: 485 ManagementRequest$ManagementFuture<T>(AsyncFutureTask<T>).await() line: 192 ManagementRequest$ManagementFuture<T>(AsyncFutureTask<T>).get() line: 266 AbstractModelControllerClient$ExecuteRequest(ManagementRequest<T>).executeForResult(ExecutorService, ManagementClientChannelStrategy) line: 131 RemotingModelControllerClient(AbstractModelControllerClient).executeSynch(ModelNode, OperationAttachments, OperationMessageHandler) line: 128 RemotingModelControllerClient(AbstractModelControllerClient).execute(ModelNode, OperationMessageHandler) line: 93 RemotingModelControllerClient(AbstractModelControllerClient).execute(ModelNode) line: 83 TestClient.performOneCheck(ModelControllerClient) line: 201 No result is ever found. The exception on the server when performing this test client is as follows: 17:55:57,187 ERROR [org.xnio.listener] (XNIO NIO Read 1) A channel event listener threw an exception: java.lang.IllegalStateException: Unsupported Callback 'ANONYMOUSanonymous' at org.jboss.as.remoting.RealmAuthenticationProvider.getCallbackHandler(RealmAuthenticationProvider.java:132) at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:235) at org.jboss.remoting3.remote.ServerConnectionOpenListener$Initial.handleEvent(ServerConnectionOpenListener.java:107) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71) at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:173) at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:94) at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:92) at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71) at org.xnio.nio.NioHandle.invoke(NioHandle.java:77) at org.xnio.nio.AbstractNioChannelThread$1.run(AbstractNioChannelThread.java:142) at java.lang.Thread.run(Thread.java:662) [:1.6.0_24] The test client's logic will be attached momentarily -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-2683) Failed to remove interface in domain mode

by Heiko Braun (Created) (JIRA)

Failed to remove interface in domain mode ----------------------------------------- Key: AS7-2683 URL: https://issues.jboss.org/browse/AS7-2683 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Emanuel Muckenhuber Fix For: 7.1.0.CR1 First Step: {noformat} [INFO] { [INFO] "address" => [("interface" => "custom_interface")], [INFO] "operation" => "add", [INFO] "any-address" => true [INFO] } {noformat} Second Step: {noformat} [INFO] { [INFO] "address" => [("interface" => "custom_interface")], [INFO] "operation" => "remove" [INFO] } [ERROR] 2011-11-17 15:40:31,114 [ERROR] Message{conciseMessage='Error: Failed to remove interface custom_interface', detailedMessage='{"domain-failure-description" => "JBAS014749: Operation handler failed: JBAS014666: Duplicate resource [(\"interface\" => \"custom_interface\")]"}', fired=Thu Nov 17 15:40:31 CET 2011, severity=Error, options=[]} {noformat} -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2726) No-op handler in READ_RESOURCE_DESCRIPTION handler

by Brian Stansberry (Created) (JIRA)

No-op handler in READ_RESOURCE_DESCRIPTION handler -------------------------------------------------- Key: AS7-2726 URL: https://issues.jboss.org/browse/AS7-2726 Project: Application Server 7 Issue Type: Bug Components: Documentation Reporter: Brian Stansberry Assignee: Emanuel Muckenhuber Fix For: 7.1.0.CR1 This handler addition isn't doing anything: if (address.isMultiTarget()) { ..... // Add a handler at the end of the chain to aggregate the result context.addStep(new OperationStepHandler() { @Override public void execute(OperationContext context, ModelNode operation) throws OperationFailedException { context.completeStep(); } }, OperationContext.Stage.VERIFY); -- 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, 7 months

3
2
0 / 0

[JBoss JIRA] (AS7-2822) UX issue: AS7 should give info/warn if JAVA_OPTS set on environment will override one set by standalone.conf/domain.conf

by Michael Dobozy (Created) (JIRA)

UX issue: AS7 should give info/warn if JAVA_OPTS set on environment will override one set by standalone.conf/domain.conf ------------------------------------------------------------------------------------------------------------------------ Key: AS7-2822 URL: https://issues.jboss.org/browse/AS7-2822 Project: Application Server 7 Issue Type: Bug Reporter: Michael Dobozy Priority: Minor If the JAVA_OPTS environment variable is set prior to starting AS7 (either standalone or domain mode), standalone.conf will not its own JAVA_OPTS value (which include heap settings like -Xms and -Xmx). The two conf scripts provide no messaging indicating that the override has taken place, which can lead to user confusion. AS7 should provide a warning message that indicates that values from the environment are being applied instead of those from the standalone/domain conf scripts. -- 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, 7 months

4
4
0 / 0

[JBoss JIRA] Created: (AS7-1847) PreDestroy not called on pooled instances during undeploy

by Carlo de Wolf (JIRA)

PreDestroy not called on pooled instances during undeploy --------------------------------------------------------- Key: AS7-1847 URL: https://issues.jboss.org/browse/AS7-1847 Project: Application Server 7 Issue Type: Bug Components: EJB Reporter: Carlo de Wolf Pool is not started and stopped during component lifecycle operations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

6
5
0 / 0

[JBoss JIRA] (AS7-2875) Upgrade to Hibernate 4.0.0.CR7

by Scott Marlow (Created) (JIRA)

Upgrade to Hibernate 4.0.0.CR7 ------------------------------ Key: AS7-2875 URL: https://issues.jboss.org/browse/AS7-2875 Project: Application Server 7 Issue Type: Task Reporter: Scott Marlow -- 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, 7 months

3
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 December 2011