[JBoss JIRA] (SECURITY-703) Picketbox logs an ERROR on each failed login
by Thomas Heute (JIRA)
Thomas Heute created SECURITY-703:
-------------------------------------
Summary: Picketbox logs an ERROR on each failed login
Key: SECURITY-703
URL: https://issues.jboss.org/browse/SECURITY-703
Project: PicketBox
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Thomas Heute
Assignee: Anil Saldhana
Priority: Critical
Picketbox logs an ERROR with a stacktrace on each failed login:
See:
catch (LoginException e)
{
// Don't log anonymous user failures unless trace level logging is on
if (principal != null && principal.getName() != null)
PicketBoxLogger.LOGGER.errorDuringLogin(e);
authException = e;
}
09:57:30,100 ERROR [org.jboss.security] (http-/127.0.0.1:8080-6) PBOX000206: Login failure: javax.security.auth.login.LoginException: Login failed for
at org.exoplatform.services.security.jaas.DefaultLoginModule.login(DefaultLoginModule.java:136) [exo.core.component.security.core-2.5.0-CR1.jar:2.5.0-CR1]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_25]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_25]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_25]
at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_25]
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) [rt.jar:1.6.0_25]
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) [rt.jar:1.6.0_25]
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) [rt.jar:1.6.0_25]
at java.security.AccessController.doPrivileged(Native Method) [rt.jar:1.6.0_25]
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) [rt.jar:1.6.0_25]
at javax.security.auth.login.LoginContext.login(LoginContext.java:579) [rt.jar:1.6.0_25]
at org.jboss.security.authentication.JBossCachedAuthenticationManager.defaultLogin(JBossCachedAuthenticationManager.java:408) [picketbox-infinispan-4.0.13.Final-redhat-1.jar:4.0.13.Final-redhat-1]
in http://anonsvn.jboss.org/repos/picketbox/tags/4.0.14.Final/picketbox-infi...
Failed login are expected from users and shouldn't be logged. This will seriously pollute EPP 6 logs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5773) JBoss 7 hangs after "Started FileSystemDeploymentService for directory ..." message
by gaurav singhal (JIRA)
gaurav singhal created AS7-5773:
-----------------------------------
Summary: JBoss 7 hangs after "Started FileSystemDeploymentService for directory ..." message
Key: AS7-5773
URL: https://issues.jboss.org/browse/AS7-5773
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.1.1.Final
Environment: Operating System z/OS
java version "1.7.0"
Java(TM) SE Runtime Environment (build pmz6470sr2-20120901_01(SR2))
IBM J9 VM (build 2.6, JRE 1.7.0 z/OS s390x-64 20120809_118929 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR2_20120809_0948_B118929
JIT - r11.b01_20120808_24925
GC - R26_Java726_SR2_20120809_0948_B118929
J9CL - 20120809_118929)
JCL - 20120831_02 based on Oracle 7u3-b05
Reporter: gaurav singhal
Assignee: Jason Greene
When we start jboss, it doesn't go past this log message:
20:46:24,504 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) JBAS015012: Started FileSystemDeploymentService for directory /u/users/castoadm/chorus/jboss/standalone/deployments
and we never see the Brontes started message. server and boot log as well as the thread dump from when it stays hung at that message is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5777) Form processing broken in GWT 2.5
by Heiko Braun (JIRA)
Heiko Braun created AS7-5777:
--------------------------------
Summary: Form processing broken in GWT 2.5
Key: AS7-5777
URL: https://issues.jboss.org/browse/AS7-5777
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
{noformat}
[ERROR] Caused by: java.lang.NullPointerException
[ERROR] at com.google.web.bindery.autobean.vm.impl.JsonSplittable.asBoolean(JsonSplittable.java:144)
[ERROR] at com.google.web.bindery.autobean.shared.ValueCodex$Type$3.decode(ValueCodex.java:68)
[ERROR] at com.google.web.bindery.autobean.shared.ValueCodex$Type$3.decode(ValueCodex.java:1)
[ERROR] at com.google.web.bindery.autobean.shared.ValueCodex.decode(ValueCodex.java:299)
[ERROR] at com.google.web.bindery.autobean.shared.impl.AutoBeanCodexImpl$ValueCoder.decode(AutoBeanCodexImpl.java:492)
[ERROR] at com.google.web.bindery.autobean.shared.impl.AbstractAutoBean.getOrReify(AbstractAutoBean.java:241)
[ERROR] at org.jboss.as.console.client.shared.subsys.tx.model.TransactionManagerAutoBean.access$5(TransactionManagerAutoBean.java:1)
[ERROR] at org.jboss.as.console.client.shared.subsys.tx.model.TransactionManagerAutoBean$2.isProcessIdUUID(TransactionManagerAutoBean.java:242)
[ERROR] at org.jboss.as.console.client.shared.subsys.tx.model.TransactionManagerAutoBean$1.isProcessIdUUID(TransactionManagerAutoBean.java:22)
[ERROR] at org.jboss.as.console.client.shared.subsys.tx.model.TransactionManagerAutoBean.traverseProperties(TransactionManagerAutoBean.java:435)
[ERROR] at com.google.web.bindery.autobean.shared.impl.AbstractAutoBean.traverse(AbstractAutoBean.java:166)
[ERROR] at com.google.web.bindery.autobean.shared.impl.AbstractAutoBean.accept(AbstractAutoBean.java:101)
[ERROR] at org.jboss.ballroom.client.util.AutoBeanHelper.getAllProperties(AutoBeanHelper.java:173)
[ERROR] at org.jboss.ballroom.client.util.AutoBeanHelper.diff(AutoBeanHelper.java:113)
[ERROR] at org.jboss.ballroom.client.widgets.forms.Form.getChangedValues(Form.java:325)
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-5686) Maven build fails when using JDK 7
by Harald Pehl (JIRA)
Harald Pehl created AS7-5686:
--------------------------------
Summary: Maven build fails when using JDK 7
Key: AS7-5686
URL: https://issues.jboss.org/browse/AS7-5686
Project: Application Server 7
Issue Type: Bug
Components: Console
Reporter: Harald Pehl
Assignee: Heiko Braun
Fix For: 7.2.0.CR1
When building the console the maven build fails in module "build/app" phase generate-sources. The reason seems to be a changed API of the apt processor. Using JDK 6 solves the problem.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JGRP-1527) Unable to start JGroups - missing locale
by Martin Gencur (JIRA)
Martin Gencur created JGRP-1527:
-----------------------------------
Summary: Unable to start JGroups - missing locale
Key: JGRP-1527
URL: https://issues.jboss.org/browse/JGRP-1527
Project: JGroups
Issue Type: Bug
Affects Versions: 3.2
Reporter: Martin Gencur
Assignee: Bela Ban
Affects 3.2.0.CR2 which is bundled in JDG 6.1.ER1
Error:
{code}
17:44:45,546 ERROR [org.jboss.as.controller] JBAS014601: Error booting the container: java.lang.ExceptionInInitializerError
at org.jgroups.protocols.TP.<clinit>(TP.java:67)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.6.0_30]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) [rt.jar:1.6.0_30]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) [rt.jar:1.6.0_30]
at java.lang.reflect.Constructor.newInstance(Constructor.java:513) [rt.jar:1.6.0_30]
at java.lang.Class.newInstance0(Class.java:355) [rt.jar:1.6.0_30]
at java.lang.Class.newInstance(Class.java:308) [rt.jar:1.6.0_30]
at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.parseTransport(JGroupsSubsystemXMLReader_1_1.java:176)
at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.parseStack(JGroupsSubsystemXMLReader_1_1.java:140)
at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.readElement(JGroupsSubsystemXMLReader_1_1.java:90)
at org.jboss.as.clustering.jgroups.subsystem.JGroupsSubsystemXMLReader_1_1.readElement(JGroupsSubsystemXMLReader_1_1.java:50)
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:905) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:331) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:127) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:99) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final-redhat-1.jar:1.1.0.Final-redhat-1]
at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.server.ServerService.boot(ServerService.java:270) [jboss-as-server-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:156) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
Caused by: java.util.MissingResourceException: Can't find bundle for base name jg-messages, locale cs_CZ
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1427) [rt.jar:1.6.0_30]
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1250) [rt.jar:1.6.0_30]
at java.util.ResourceBundle.getBundle(ResourceBundle.java:952) [rt.jar:1.6.0_30]
at org.jgroups.util.Util.<clinit>(Util.java:95)
... 23 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBJCA-904) Verify connection factory and connection definitions
by Vladimir Rastseluev (JIRA)
Vladimir Rastseluev created JBJCA-904:
-----------------------------------------
Summary: Verify connection factory and connection definitions
Key: JBJCA-904
URL: https://issues.jboss.org/browse/JBJCA-904
Project: IronJacamar
Issue Type: Task
Components: Deployer
Affects Versions: 1.1.0.Beta2, 1.0.12.Final
Reporter: Vladimir Rastseluev
Assignee: Jesper Pedersen
Fix For: 1.0.13.Final, 1.1.0.Beta3
Resource adapter should return Connection factory and connection implementations, due to deployment descriptor and throw an exception, if it's impossible.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months