September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBVFS-197) VFSUtils#getVirtualURL requires permissions

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/JBVFS-197?page=com.atlassian.jira.plugin.... ] Tomaz Cerar resolved JBVFS-197. ------------------------------- Fix Version/s: 3.5.0.Alpha1 Resolution: Done > VFSUtils#getVirtualURL requires permissions > ------------------------------------------- > > Key: JBVFS-197 > URL: https://issues.jboss.org/browse/JBVFS-197 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.6.Final > Reporter: David Lloyd > Assignee: Tomaz Cerar > Fix For: 3.2.7.Final, 3.5.0.Alpha1 > > > The {{org.jboss.vfs.VFSUtils#getVirtualURL(VirtualFile)}} method requires the permission {{java.net.NetPermission" specifyStreamHandler"}}. Therefore the URL construction should be in a privileged block. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-86) RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-86?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-86: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1113242|https://bugzilla.redhat.com/show_bug.cgi?id=1113242] from MODIFIED to ON_QA > RemotingConnector & VersionedConectionFactory need configurable connection, channel & versioned connection timeouts > -------------------------------------------------------------------------------------------------------------------- > > Key: REMJMX-86 > URL: https://issues.jboss.org/browse/REMJMX-86 > Project: Remoting JMX > Issue Type: Bug > Components: Connection > Affects Versions: 2.0.0.Final > Reporter: Mustafa Musaji > Assignee: Brad Maxwell > Fix For: 1.1.3.Final, 2.0.1.CR1 > > > In [1] we have the following snippet of code which has a hardcoded value of 5 seconds. > {code:title=RemotingConnector.java} > // Now open the channel > final IoFuture<Channel> futureChannel = connection.openChannel(serviceName, OptionMap.EMPTY); > IoFuture.Status result = futureChannel.await(5, TimeUnit.SECONDS); > if (result == IoFuture.Status.DONE) { > channel = futureChannel.get(); > } else if (result == IoFuture.Status.FAILED) { > throw new IOException(futureChannel.getException()); > } else { > throw new RuntimeException("Operation failed with status " + result); > } > {code} > This should be a system property or the default value should be raised. > [1] https://github.com/jbossas/remoting-jmx/blob/master/src/main/java/org/jbo... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (REMJMX-88) Release Remoting JMX 1.1.3.Final

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/REMJMX-88?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on REMJMX-88: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1113249|https://bugzilla.redhat.com/show_bug.cgi?id=1113249] from MODIFIED to ON_QA > Release Remoting JMX 1.1.3.Final > -------------------------------- > > Key: REMJMX-88 > URL: https://issues.jboss.org/browse/REMJMX-88 > Project: Remoting JMX > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.3.Final > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3888) Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3888?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3888: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1145896|https://bugzilla.redhat.com/show_bug.cgi?id=1145896] from MODIFIED to ON_QA > Show more informations of a timer in ERROR/WARN messages to identify the failed timer exactly > --------------------------------------------------------------------------------------------- > > Key: WFLY-3888 > URL: https://issues.jboss.org/browse/WFLY-3888 > Project: WildFly > Issue Type: Enhancement > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > > All ERROR and WARN messages should show the full timer information, specially the customer timer-information. > This will make it more easy to identify the exact timer in case of an EJB object has multiple timer instances active. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-46) Fix intermittent failures in DeploymentOverlayCLITestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-46?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFCORE-46: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1144222|https://bugzilla.redhat.com/show_bug.cgi?id=1144222] from MODIFIED to ON_QA > Fix intermittent failures in DeploymentOverlayCLITestCase > --------------------------------------------------------- > > Key: WFCORE-46 > URL: https://issues.jboss.org/browse/WFCORE-46 > Project: WildFly Core > Issue Type: Bug > Components: Server > Affects Versions: 1.0.0.Alpha4 > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 1.0.0.Alpha9 > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-125) Security realm cache definitions not possible for LDAP prinicipal to group group loading.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-125?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-125: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1146117|https://bugzilla.redhat.com/show_bug.cgi?id=1146117] from MODIFIED to ON_QA > Security realm cache definitions not possible for LDAP prinicipal to group group loading. > ----------------------------------------------------------------------------------------- > > Key: WFCORE-125 > URL: https://issues.jboss.org/browse/WFCORE-125 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management, Security > Affects Versions: 1.0.0.Alpha8 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > > It's not possible to configure LDAP cache in security realms under "authorization=ldap/group-search=principal-to-group" > Possible reason: > The LdapCacheResourceDefinition is not registered under the org.jboss.as.domain.management.security.PrincipalToGroupResourceDefinition > When I try to add the cache configuration manually to standalone.xml, server doesn't start and reports: > 15:23:44,619 ERROR [org.jboss.as.controller] (Controller Boot Thread) JBAS014629: No resource definition is registered for address [ > ("core-service" => "management"), > ("security-realm" => "JBossTest"), > ("authorization" => "ldap"), > ("group-search" => "principal-to-group"), > ("cache" => "by-search-time") > ] > 15:23:44,621 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (AS7-6245) ClassNotFoundException if CMP2 entity-command is used

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/AS7-6245?page=com.atlassian.jira.plugin.s... ] RH Bugzilla Integration commented on AS7-6245: ---------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 901279|https://bugzilla.redhat.com/show_bug.cgi?id=901279] from MODIFIED to ON_QA > ClassNotFoundException if CMP2 entity-command is used > ----------------------------------------------------- > > Key: AS7-6245 > URL: https://issues.jboss.org/browse/AS7-6245 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: Wolf-Dieter Fink > Labels: cmp, ejb2 > Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP) > > > If a EJB2 - CMP2 EntityBean uses an entity-command 'mysql-get-generated-keys' to generate the primary key, the server deploy with an error message: > Caused by: java.lang.RuntimeException: JBAS018572: Could not load driver class: com.mysql.jdbc.PreparedStatement > This may happen for different entity-commands if other databases are used! > If the datasource module is added to the org/jboss/as/cmp modules dependencies, the startup shows: > MSC000001: Failed to start service ... : JBAS010785: Failed start store manager > Caused by: java.lang.RuntimeException: JBAS010732: Couldn't create entity command > Caused by: java.lang.RuntimeException: JBAS018574: Could not load org.jboss.resource.adapter.jdbc.StatementAccess -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3600) TransactionRolledbackException doesn't reference the originating runtime-exception

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3600?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3600: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1109153|https://bugzilla.redhat.com/show_bug.cgi?id=1109153] from MODIFIED to ON_QA > TransactionRolledbackException doesn't reference the originating runtime-exception > ---------------------------------------------------------------------------------- > > Key: WFLY-3600 > URL: https://issues.jboss.org/browse/WFLY-3600 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If a RuntimeException is thrown by a business method this gets lost during propagation to the client. > The client is not able in this case to react appropriate to the cause. > Similar issue was fixed for the Local invocation, see AS7-5432 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-124) The yes/no checking in add-user converts the users input to lower case but not the translated values.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-124?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-124: ------------------------------------------------ Paul Gier <pgier(a)redhat.com> changed the Status of [bug 901193|https://bugzilla.redhat.com/show_bug.cgi?id=901193] from MODIFIED to ON_QA > The yes/no checking in add-user converts the users input to lower case but not the translated values. > ----------------------------------------------------------------------------------------------------- > > Key: WFCORE-124 > URL: https://issues.jboss.org/browse/WFCORE-124 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha9 > > > The end result is if the translated value contains upper case characters the users input will not match, as an example for German ja and Ja - whatever the user inputs it will be converted to 'ja' but is always compared to 'Ja'. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2515) JBAS014249 if a fire and forget asynchronous ejb call is made

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2515?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2515: ----------------------------------------------- Paul Gier <pgier(a)redhat.com> changed the Status of [bug 1030936|https://bugzilla.redhat.com/show_bug.cgi?id=1030936] from MODIFIED to ON_QA > JBAS014249 if a fire and forget asynchronous ejb call is made > ------------------------------------------------------------- > > Key: WFLY-2515 > URL: https://issues.jboss.org/browse/WFLY-2515 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Beta1, 8.0.0.CR1 > Environment: Beta2 SNAPSHOT > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > > If an ejb method > @Asynchronous void fireAndForget(...) > is called remote and the client disconnect an Exception JBAS014249 will be thrown if the async method return. > {noformat} > ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014249: Error invoking method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname : java.lang.NullPointerException > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.invokeMethod(MethodInvocationMessageHandler.java:322) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$100(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:203) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > 11:30:20,242 ERROR [org.jboss.as.ejb3] (EJB default - 1) JBAS014250: Could not write method invocation failure for method public abstract void org.jboss.as.quickstarts.ejb.asynchronous.AsynchronousAccess.fireAndForget(long) on bean named AsynchronousAccessBean for appname modulename jboss-as-ejb-asynchronous-ejb distinctname due to: java.io.IOException: JBAS014560: Could not open message outputstream for writing to Channel > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:102) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler.access$400(MethodInvocationMessageHandler.java:70) > at org.jboss.as.ejb3.remote.protocol.versionone.MethodInvocationMessageHandler$1.run(MethodInvocationMessageHandler.java:213) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_25] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_25] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_25] > at java.lang.Thread.run(Thread.java:724) [rt.jar:1.7.0_25] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: org.jboss.remoting3.NotOpenException: Writes closed > at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:112) > at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:301) > at org.jboss.as.ejb3.remote.protocol.versionone.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:68) > at org.jboss.as.ejb3.remote.protocol.AbstractMessageHandler.writeException(AbstractMessageHandler.java:100) > ... 9 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
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 September 2014