[JBoss JIRA] (JBLOGGING-80) Avoid SimpleDataFormat
by Clebert Suconic (JIRA)
Clebert Suconic created JBLOGGING-80:
----------------------------------------
Summary: Avoid SimpleDataFormat
Key: JBLOGGING-80
URL: https://issues.jboss.org/browse/JBLOGGING-80
Project: JBoss Logging
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Clebert Suconic
Assignee: David Lloyd
SimpleDateFormat is a really dumb thing... it creates a synchronization point as it contains state on the class. (Can you believe that).
We have been bitten by SDF in the past as it "fixed" our bugs whenever you had races and had enabled trace logging. We could then get better tracing again after removing SDF.
And that's a bad thing for us on a messaging system with lots of multi-thread behind the scenes (with the types of issues we have to debug).
So, in order for us to move to jboss-logging (or whatever is underneath or around it), we can't have SDF being synchornized on every log being written.. that's just prohibitive for us.
For that reason we need SDF out of logging.
--
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, 1 month
[JBoss JIRA] (AS7-1338) Remote JNDI support for AS7
by Himanshu Gupta (JIRA)
[ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.s... ]
Himanshu Gupta commented on AS7-1338:
-------------------------------------
Hi,
Can someone please summarize what is the final resolution for this bug?
As I understand from the bug, "JBAS011806: Channel end notification received, closing channel Channel ID 72d0f3d7 (inbound) of Remoting connection 67ffa9c7 to null" - this message in logs is fine and will come on Windows and currently no way to suppress it for this OS.
We are testing with JBoss 7.1.1.Final and see this message at INFO level in JBoss console. Also it seems that this statememnt is logged via System.err.println also from code.
We just need to know what is the final stance on this one.
Thanks,
Himanshu
> Remote JNDI support for AS7
> ---------------------------
>
> Key: AS7-1338
> URL: https://issues.jboss.org/browse/AS7-1338
> Project: Application Server 7
> Issue Type: Task
> Components: Naming
> Reporter: Richard Opalka
> Assignee: John Bailey
> Priority: Critical
> Labels: eap6_prd_req
> Fix For: 7.1.0.Final
>
>
> Add support for remote JNDI after all. It was agreed that:
> * Remote JNDI would run over Remoting
> * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
> * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
> * Server-side services would opt-in to Remote JNDI; initially we'd only support:
> ** Remote EJB interfaces
> ** HornetQ connection factories
> * In the future we may support:
> ** User bindings, so long as they're serializable
> * In the future we will never support:
> ** Proxied DataSources
> ** Proxied JMS invocations
> Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.
--
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, 1 month
[JBoss JIRA] (AS7-3764) Intermittent AbstractModelControllerClient Channel closed exception after :reload operation in the domain
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3764:
-------------------------------------
Summary: Intermittent AbstractModelControllerClient Channel closed exception after :reload operation in the domain
Key: AS7-3764
URL: https://issues.jboss.org/browse/AS7-3764
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
I am getting intermittent channel closed exception after reload operation executed on HC in the domain.
Exception:
testAdminOnlyMode(org.jboss.as.test.integration.domain.suites.ServerManagementTestCase) Time elapsed: 0.57 sec <<< ERROR!
java.io.IOException: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:139)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:81)
at org.jboss.as.controller.client.helpers.domain.impl.DomainClientImpl.execute(DomainClientImpl.java:70)
at org.jboss.as.test.integration.domain.suites.ServerManagementTestCase.checkState(ServerManagementTestCase.java:390)
at org.jboss.as.test.integration.domain.suites.ServerManagementTestCase.waitUntilState(ServerManagementTestCase.java:371)
at org.jboss.as.test.integration.domain.suites.ServerManagementTestCase.waitUntilState(ServerManagementTestCase.java:366)
at org.jboss.as.test.integration.domain.suites.ServerManagementTestCase.testAdminOnlyMode(ServerManagementTestCase.java:291)
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:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:263)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:68)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:47)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:231)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:60)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:229)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:50)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:222)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:30)
at org.junit.runners.ParentRunner.run(ParentRunner.java:300)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
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:597)
at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcessWhenForked(SurefireStarter.java:107)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:68)
Caused by: java.util.concurrent.ExecutionException: Operation failed
at org.jboss.threads.AsyncFutureTask.operationFailed(AsyncFutureTask.java:74)
at org.jboss.threads.AsyncFutureTask.get(AsyncFutureTask.java:268)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:363)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient$DelegatingCancellableAsyncFuture.get(AbstractModelControllerClient.java:317)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:137)
... 37 more
Caused by: java.io.IOException: Channel closed
at org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleChannelClosed(AbstractMessageHandler.java:351)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$2.handleClose(RemotingModelControllerClient.java:127)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$2.handleClose(RemotingModelControllerClient.java:124)
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing$3.handleClose(ManagementClientChannelStrategy.java:189)
at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing$3.handleClose(ManagementClientChannelStrategy.java:180)
at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:54)
at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:501)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:406)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:277)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:489)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:153)
at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:118)
at org.jboss.remoting3.remote.RemoteConnectionChannel$2.run(RemoteConnectionChannel.java:273)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
--
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, 1 month
[JBoss JIRA] (AS7-4116) removal of unrequested json snippet '"server-groups" => undefined' postpended to operation responses via cli
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-4116?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber resolved AS7-4116.
--------------------------------------
Resolution: Done
> removal of unrequested json snippet '"server-groups" => undefined' postpended to operation responses via cli
> ------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4116
> URL: https://issues.jboss.org/browse/AS7-4116
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Domain Management
> Reporter: Simeon Pinder
> Assignee: Emanuel Muckenhuber
> Priority: Minor
> Labels: rhq
> Fix For: 7.1.2.Final
>
>
> When submitting operations to as7 via CLI sometimes and extra ["server-groups" => undefined] string is post-pended to the response. The result is still valid JSON it appears, but the results are potentially confusing to external json integrators.
> To reproduce:
> - run AS7 via domain.sh to run HostController.
> - login
> - submit the following operation:
> /host=master/core-service=platform-mbean/type=threading/:read-resource(recursive=true,proxies=false,include-runtime=true,include-defaults=true)
> - Look at the result returned:
> {
> "outcome" => "success",
> "result" => {
> "all-thread-ids" => [
> 2173L,
> 2172L,
> 2171L,
> 51L,
> 50L,
> 49L,
> 48L,
> 45L,
> 44L,
> 43L,
> 42L,
> 41L,
> 40L,
> 39L,
> 38L,
> 37L,
> 36L,
> 35L,
> 34L,
> 33L,
> 32L,
> 31L,
> 30L,
> 29L,
> 28L,
> 27L,
> 26L,
> 25L,
> 24L,
> 23L,
> 22L,
> 21L,
> 19L,
> 18L,
> 17L,
> 16L,
> 15L,
> 14L,
> 13L,
> 12L,
> 11L,
> 8L,
> 4L,
> 3L,
> 2L,
> 1L
> ],
> "thread-contention-monitoring-supported" => true,
> "thread-cpu-time-supported" => true,
> "current-thread-cpu-time-supported" => true,
> "object-monitor-usage-supported" => true,
> "synchronizer-usage-supported" => true,
> "thread-contention-monitoring-enabled" => false,
> "thread-cpu-time-enabled" => true,
> "thread-count" => 46,
> "peak-thread-count" => 49,
> "total-started-thread-count" => 2168L,
> "daemon-thread-count" => 6,
> "current-thread-cpu-time" => 0L,
> "current-thread-user-time" => 0L
> },
> "server-groups" => undefined
> }
--
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, 1 month