[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-3847:
----------------------------------
Priority: Major (was: Critical)
The issue here is java.net.Inet6Address.getHostAddress() does not follow the RFC 5952 standard; specifically http://tools.ietf.org/html/rfc5952#section-4.2.
A separate JBWEB JIRA needs to be filed for org.apache.coyote.http11.Http11Protocol as that code is not part of the AS7 code base.
> Non-standard format of IPv6 address(-es) in LOG files
> -----------------------------------------------------
>
> Key: AS7-3847
> URL: https://issues.jboss.org/browse/AS7-3847
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
>
> There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default).
> I think in enterprise product we should not violate this RFC.
> I'm mentioning about LOG messages like:
> {code}
> 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999
>
> 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447
> {code}
> In both lines IPv6 address should be stretched to "::1" string.
> More "funny" and obfuscated version of the same LOG content is LOG line like this:
> {code}
> 15:14:14,363 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A1%251-8080
> {code}
> But both version of the issue is almost unreadable by human.
--
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, 4 months
[JBoss JIRA] (AS7-3845) generateStandaloneJdrReport test case fails on Windows
by Shelly McGowan (JIRA)
Shelly McGowan created AS7-3845:
-----------------------------------
Summary: generateStandaloneJdrReport test case fails on Windows
Key: AS7-3845
URL: https://issues.jboss.org/browse/AS7-3845
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Reporter: Shelly McGowan
Assignee: Mike Clark
Fix For: 7.1.1.Final
org.jboss.as.test.integration.jdr.mgmt.JdrReportManagmentTestCase.generateStandaloneJdrReport
java.lang.AssertionError: JDR report missing, not located at
{code}
07:26:52,175 INFO [org.jboss.as.jdr] (management-handler-threads - 15) JBAS013300: Starting creation of a JBoss Diagnostic Report (JDR).
07:27:00,718 WARN [org.jboss.as.jdr] (MainThread) JBAS013303: JDR python interpreter encountered an exception.: Traceback (most recent call last):
File "<string>", line 1, in <module>
File "W:\workspace\JBoss-AS-7.1.x-testSuite-windows\testsuite\integration\basic\..\..\..\build\target\jboss-as-7.1.1.Final-SNAPSHOT\modules\org\jboss\as\jdr\main\jboss-as-sos-7.1.1.Final-SNAPSHOT.jar\sos\sosreport.py", line 220, in __init__
File "W:\workspace\JBoss-AS-7.1.x-testSuite-windows\testsuite\integration\basic\..\..\..\build\target\jboss-as-7.1.1.Final-SNAPSHOT\modules\org\jboss\as\jdr\main\jboss-as-sos-7.1.1.Final-SNAPSHOT.jar\sos\policies\__init__.py", line 148, in is_root
AttributeError: 'module' object has no attribute 'getuid'
at org.python.core.PyException.fillInStackTrace(PyException.java:70) [jython-standalone-2.5.2.jar:]
{code}
See:
http://hudson.jboss.org/hudson/view/All/job/JBoss-AS-7.1.x-testSuite-wind...
--
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, 4 months
[JBoss JIRA] (AS7-2785) Do not call @PostConstruct multiple times on @Startup @Singleton bean.
by Dan Spasojevic (Created) (JIRA)
Do not call @PostConstruct multiple times on @Startup @Singleton bean.
----------------------------------------------------------------------
Key: AS7-2785
URL: https://issues.jboss.org/browse/AS7-2785
Project: Application Server 7
Issue Type: Feature Request
Components: EJB
Affects Versions: 7.1.0.Beta1, 7.0.2.Final
Reporter: Dan Spasojevic
Assignee: Carlo de Wolf
Attachments: test.zip
Given an @Startup @Singleton bean with a @PostConstruct method called Controller; when the Controller's dependencies are satisfied then its @PostConstruct method is called.
Given another @Startup @Singleton bean with a @PostConstruct method called Client that has an @EJB injection of the Controller; when the Client's dependencies are satisfied then the @PostConstruct method of both the Controller and Client are called.
This is true for each Client instance. So if there are N Client instances, there will be N+1 invocations of Controller's @PostConstruct.
--
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, 4 months
[JBoss JIRA] (AS7-2272) run.sh and run.bat for compatibility
by Rich Sharples (Created) (JIRA)
run.sh and run.bat for compatibility
------------------------------------
Key: AS7-2272
URL: https://issues.jboss.org/browse/AS7-2272
Project: Application Server 7
Issue Type: Feature Request
Components: Scripts
Affects Versions: 7.1.0.Alpha1
Environment: all
Reporter: Rich Sharples
Assignee: Brian Stansberry
Fix For: 7.1.0.Beta1
Many seasoned JBoss users expect to be able to run bin/run.sh (bin\run.bat). Now deprecated these scripts inform the user what to use instead : eg.
run.sh is no longer supported. The scripts standalone.sh (standalone.bat on Windows) should be used to start a single instance. and domain.sh (domain.bat on Windows) should be used to start in domain mode. See the documentation for further information.
--
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, 4 months