[JBoss JIRA] (AS7-3790) TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
by Ondrej Zizka (JIRA)
[ https://issues.jboss.org/browse/AS7-3790?page=com.atlassian.jira.plugin.s... ]
Ondrej Zizka resolved AS7-3790.
-------------------------------
Resolution: Done
Pavel, I think this is solved, right? If not, please let me and Rado know.
> TS: Unable to pass tests in integration smoke test part of testsuite in IPv6 environment
> ----------------------------------------------------------------------------------------
>
> Key: AS7-3790
> URL: https://issues.jboss.org/browse/AS7-3790
> Project: Application Server 7
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
> Assignee: Shelly McGowan
>
> I've tried to build AS7 and run default part of testsuite (including integration smoke tests) in IPv6 environment like:{code}./build.sh clean install -Dnode0=::1 -Dipv6{code}
> My lookpack network interface was configured as:{code}[root@fedora15-vrt1 Documents]# ifconfig lo
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:60156 errors:0 dropped:0 overruns:0 frame:0
> TX packets:60156 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:37911245 (36.1 MiB) TX bytes:37911245 (36.1 MiB)
> [root@fedora15-vrt1 Documents]#
> {code}
> The result is failure because timeout:
> {code}
> <snip>
> main:
> build-smoke:
> [INFO] Executed tasks
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ jboss-as-ts-integ-smoke ---
> [INFO] Compiling 110 source files to /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/test-classes
> [WARNING] /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/src/test/java/org/jboss/as/test/smoke/surefire/servermodule/AbstractServerInModuleTestCase.java:[54,62] [deprecation] getModulesDir() in org.jboss.as.server.ServerEnvironment has been deprecated
> [INFO]
> [INFO] --- maven-surefire-plugin:2.10:test (smoke-full.surefire) @ jboss-as-ts-integ-smoke ---
> [INFO] Surefire report directory: /home/pjanouse/devel/tmp/ozizka/jboss-as/testsuite/integration/smoke/target/surefire-reports
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [1.952s]
> [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [1.435s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.276s]
> [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [1.525s]
> [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [11.337s]
> [INFO] JBoss Application Server: Controller Client ....... SUCCESS [5.599s]
> [INFO] JBoss Application Server: Controller Core ......... SUCCESS [21.175s]
> [INFO] JBoss Application Server: Domain Management ....... SUCCESS [3.940s]
> [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [2.620s]
> [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [2.615s]
> [INFO] JBoss Application Server: Embedded ................ SUCCESS [4.239s]
> [INFO] JBoss Application Server: Platform MBean integration SUCCESS [5.673s]
> [INFO] JBoss Application Server: Process Controller ...... SUCCESS [6.888s]
> [INFO] JBoss Application Server: Network ................. SUCCESS [3.532s]
> [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [8.944s]
> [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [4.899s]
> [INFO] JBoss Application Server: Server .................. SUCCESS [11.049s]
> [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [5.775s]
> [INFO] JBoss Application Server: JMX Subsystem ........... SUCCESS [9.914s]
> [INFO] JBoss Application Server: Naming Subsystem ........ SUCCESS [8.926s]
> [INFO] JBoss Application Server: EE ...................... SUCCESS [13.024s]
> [INFO] JBoss Application Server: Transaction Subsystem ... SUCCESS [7.015s]
> [INFO] JBoss Application Server: Clustering Subsystem .... SUCCESS [0.184s]
> [INFO] JBoss Application Server: Common code for clustering subsystems SUCCESS [5.332s]
> [INFO] JBoss Application Server: JGroups Subsystem ....... SUCCESS [8.036s]
> [INFO] JBoss Application Server: Infinispan Subsystem .... SUCCESS [23.168s]
> [INFO] JBoss Application Server: Security Subsystem ...... SUCCESS [11.052s]
> [INFO] JBoss Application Server: Connector Subsystem ..... SUCCESS [19.138s]
> [INFO] JBoss Application Server: Clustering Server API ... SUCCESS [13.274s]
> [INFO] JBoss Application Server: Clustered registry service SUCCESS [2.203s]
> [INFO] JBoss Application Server: JacORB Subsystem ........ SUCCESS [16.268s]
> [INFO] JBoss Application Server: EJB Subsystem ........... SUCCESS [35.557s]
> [INFO] JBoss Application Server: Distributed Web Session SPI SUCCESS [5.422s]
> [INFO] JBoss Application Server: Clustering Server API implementation SUCCESS [5.224s]
> [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SUCCESS [7.409s]
> [INFO] JBoss Application Server: Web Subsystem ........... SUCCESS [19.789s]
> [INFO] JBoss Application Server: Web Services Subsystem .. SUCCESS [0.183s]
> [INFO] JBoss Application Server: Web Services Server Integration Subsystem SUCCESS [9.624s]
> [INFO] JBoss Application Server: Application Client Bootstrap SUCCESS [7.014s]
> [INFO] JBoss Application Server: Command line interface .. SUCCESS [12.399s]
> [INFO] JBoss Application Server: EJB Client BOM .......... SUCCESS [0.226s]
> [INFO] JBoss Application Server: JMS Client BOM .......... SUCCESS [0.213s]
> [INFO] JBoss Application Server: EJB and JMS client combined jar SUCCESS [4.948s]
> [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SUCCESS [3.795s]
> [INFO] JBoss Application Server: Clustered service provider registry services SUCCESS [4.434s]
> [INFO] JBoss Application Server: Clustered singleton services SUCCESS [5.016s]
> [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SUCCESS [24.135s]
> [INFO] JBoss Application Server: Config Admin ............ SUCCESS [5.690s]
> [INFO] JBoss Application Server: Deployment Scanner ...... SUCCESS [7.514s]
> [INFO] JBoss Application Server: EE Deployment ........... SUCCESS [4.195s]
> [INFO] JBoss Application Server: JAXR Client ............. SUCCESS [4.562s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [0.231s]
> [INFO] JBoss Application Server: JPA SPI ................. SUCCESS [4.460s]
> [INFO] JBoss Application Server: JPA UTIL ................ SUCCESS [1.698s]
> [INFO] JBoss Application Server: JPA Subsystem ........... SUCCESS [7.273s]
> [INFO] JBoss Application Server: Weld Integration ........ SUCCESS [8.499s]
> [INFO] JBoss Application Server: JAX-RS Integration ...... SUCCESS [8.492s]
> [INFO] JBoss Application Server: JBoss Diagnostic Reporter SUCCESS [0.158s]
> [INFO] JBoss Application Server: JDR ..................... SUCCESS [6.291s]
> [INFO] JBoss Application Server: JSR-77 Subsystem ........ SUCCESS [5.485s]
> [INFO] JBoss Application Server: Management Client Content SUCCESS [3.706s]
> [INFO] JBoss Application Server: Host Controller ......... SUCCESS [18.260s]
> [INFO] JBoss Application Server: Logging Subsystem ....... SUCCESS [13.138s]
> [INFO] JBoss Application Server: Mail subsystem .......... SUCCESS [7.227s]
> [INFO] JBoss Application Server: Messaging Subsystem ..... SUCCESS [18.398s]
> [INFO] JBoss Application Server: ModCluster Subsystem .... SUCCESS [7.415s]
> [INFO] JBoss Application Server: OSGi .................... SUCCESS [0.148s]
> [INFO] JBoss Application Server: OSGi Subsystem .......... SUCCESS [9.388s]
> [INFO] JBoss Application Server: OSGi ConfigurationAdmin . SUCCESS [4.866s]
> [INFO] JBoss Application Server: POJO Subsystem .......... SUCCESS [7.217s]
> [INFO] JBoss Application Server: sosreport scripts ....... SUCCESS [2.259s]
> [INFO] JBoss Application Server: Service Archive Subsystem SUCCESS [6.041s]
> [INFO] JBoss Application Server: XTS Subsystem ........... SUCCESS [7.902s]
> [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SUCCESS [3.552s]
> [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SUCCESS [4.524s]
> [INFO] JBoss Application Server: Infinispan Hibernate 2nd level cache provider SUCCESS [1.783s]
> [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SUCCESS [3.333s]
> [INFO] JBoss Application Server: Build ................... SUCCESS [21.975s]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [0.190s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [1.574s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [3.888s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [2.520s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [18.181s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [3.492s]
> [INFO] JBoss Application Server: Exported Java EE Specification APIs SUCCESS [0.261s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration SUCCESS [15.898s]
> [INFO] JBoss Application Server: Demos: Aggregator ....... SUCCESS [2.748s]
> [INFO] JBoss Application Server: Demos: Spec ............. SUCCESS [4.056s]
> [INFO] JBoss Application Server: Demos: Legacy TO BE MOVED SUCCESS [10.657s]
> [INFO] JBoss Application Server: Distribution ............ SUCCESS [1.035s]
> [INFO] JBoss Application Server: Remoting Subsystem Test . SUCCESS [2.981s]
> [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SUCCESS [2.360s]
> [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SUCCESS [1.969s]
> [INFO] JBoss Application Server Test Suite: Shared ....... SUCCESS [7.605s]
> [INFO] JBoss Application Server Test Suite: Aggregator ... SUCCESS [6.152s]
> [INFO] JBoss Application Server Test Suite: Integration .. SUCCESS [2.203s]
> [INFO] JBoss Application Server Test Suite: Integration - Smoke FAILURE [15:07.181s]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 26:31.461s
> [INFO] Finished at: Thu Feb 16 11:51:51 CET 2012
> [INFO] Final Memory: 341M/494M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.10:test (smoke-full.surefire) on project jboss-as-ts-integ-smoke: Failure or timeout -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :jboss-as-ts-integ-smoke
> [pjanouse@fedora15-vrt1 jboss-as]$
> {code}
> Unfortunately org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase.txt and org.jboss.as.test.smoke.embedded.demo~essaging.MessagingTestCase-output.txt files in jboss-as/testsuite/integration/smoke/target/surefire-reports are created, but leaved empty only. Nor work-around mentioned in [ARQ-696|https://issues.jboss.org/browse/ARQ-696?focusedCommentId=12667010...] comment doesn't help.
> BTW I've checked standalone-full.xml and basic things are correctly assigned to ::1 (especially _management_ and _public_ interface)
--
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-5617) LdapExtLoginModule ALL_VALID_OPTIONS does not contain ROLE_ATTRIBUTE_IS_DN_OPT, though the code uses it
by Jess Sightler (JIRA)
Jess Sightler created AS7-5617:
----------------------------------
Summary: LdapExtLoginModule ALL_VALID_OPTIONS does not contain ROLE_ATTRIBUTE_IS_DN_OPT, though the code uses it
Key: AS7-5617
URL: https://issues.jboss.org/browse/AS7-5617
Project: Application Server 7
Issue Type: Bug
Components: Security
Affects Versions: 7.1.2.Final (EAP)
Reporter: Jess Sightler
Assignee: Anil Saldhana
ROLE_ATTRIBUTE_IS_DN_OPT is present and used by LdapExtLoginModule. However, if an AS7 configuration actually uses it, the following log is presented:
13:04:36,235 WARN [org.jboss.security.auth.spi.LdapExtLoginModule] (ip) Invalid or misspelled option: roleAttributeIsDN
It appears that it is not part of the ALL_VALID_OPTIONS array, and therefore is missed by the addValidOptions(ALL_VALID_OPTIONS); call in the initialize method.
--
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] (JBRULES-3506) KnowledgeAgent is not detecting changes of a function defined in a package
by Elisabeth Wirth (JIRA)
Elisabeth Wirth created JBRULES-3506:
----------------------------------------
Summary: KnowledgeAgent is not detecting changes of a function defined in a package
Key: JBRULES-3506
URL: https://issues.jboss.org/browse/JBRULES-3506
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-core
Affects Versions: 5.4.0.Final
Reporter: Elisabeth Wirth
Assignee: Mark Proctor
I have a pkg containing a function and I am checking, if there are any changes in my pkg by using the KnowledgeAgent.
Now I have the problem, that changes of the function are not recognized.
In the log I see the following entry:
KnowledgeAgent: impossible to add a map for a null resource! skiping.
I have analyzed the code of KnowledgeAgentImpl and found the reason for the problem:
in the method createPackageFromResource(Resource resource, KnowledgeBuilder kbuilder) in KnowledgeAgentImpl
the mapping for functions is missing.
I have added the following code and everything works as expected:
for( KnowledgePackage kpkg : kpkgs ) {
for ( Rule rule : ((KnowledgePackageImp)kpkg).pkg.getRules() ) {
rule.setResource( resource );
} ....
// added
for ( Function function : ((KnowledgePackageImp)kpkg).pkg.getFunctions().values() ) {
function.setResource( resource );
}
}
--
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
13 years, 9 months
[JBoss JIRA] (AS7-5632) add-user scripts to check password strength immediately after it's entered
by Cheng Fang (JIRA)
Cheng Fang created AS7-5632:
-------------------------------
Summary: add-user scripts to check password strength immediately after it's entered
Key: AS7-5632
URL: https://issues.jboss.org/browse/AS7-5632
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Affects Versions: 7.2.0.CR1
Reporter: Cheng Fang
Assignee: Brian Stansberry
Can we validate the password immediately after the password is entered, before asking the user to enter a potentially useless password a second time, and before asking the user to assign a role. Currently the validation kicks in after adding role:
Realm (ApplicationRealm) :
Username : user1
Password :
Re-enter Password :
What roles do you want this user to belong to? (Please enter a comma separated list, or leave blank for none)[ ]:
Error *
--
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-2756) Implement username / password strength checks
by Darran Lofthouse (Created) (JIRA)
Implement username / password strength checks
---------------------------------------------
Key: AS7-2756
URL: https://issues.jboss.org/browse/AS7-2756
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Darran Lofthouse
Assignee: Brian Stansberry
Fix For: Open To Community
The AS 7.1 distribution now contains a utility for adding new users to the property files, this utility contains some very basic checks of the username and password e.g. bad choices of username and disallowing passwords which match the username.
This Jira is to implement a more advanced check to enforce complexity.
I believe we should have something along the lines of a util that will take a username and password and will respond ACCEPT, REJECT, or WARN where WARN has a message to display to the user and the user an opportunity to ignore the warning or return to re-entry of the details.
At some point in the future this could become a management operations so the implementation shouldn't be too constrained to the current command line tool.
As a management op we may also want to take into account the user making the request, i.e. a user changing their own password has tighter restrictions than the overall administrator.
As the add user script is currently stand alone this may be a nice task for someone to undertake who would like to get more familiar with submitting an AS change without needing to get too involved with the internals of the application server at this stage.
--
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
13 years, 9 months
[JBoss JIRA] (AS7-5611) Domain mode does not work with Windows 2008R2 and multiple ip-addresses
by Peter Bijl (JIRA)
Peter Bijl created AS7-5611:
-------------------------------
Summary: Domain mode does not work with Windows 2008R2 and multiple ip-addresses
Key: AS7-5611
URL: https://issues.jboss.org/browse/AS7-5611
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Environment: Windows 2008R2 Service Pack 1, Oracle Java JRE 1.6.0_35-b10 64 bit, jboss-as-7.1.1.Final
Reporter: Peter Bijl
Domain mode does not work in Windows 2008 when I add additional ip-addresses to the network interface (with Advanced TCP/IP settings).
As Windows 2008 does not have such a thing as a primary ip-address anymore I have added the primary ip-address to the hosts-file.
When I do a ping -4 <hostname> the correct ip-address is being used. By default Windows 2008 will use the "lowest" ip-address of network interface instead of the primary ip-address.
For instance the primary ip-address of the win01 host is: 192.168.178.10 (also added to the Windows hosts-file)
Then I add a second ip-address to the network interface: 192.168.178.9
Then I configure the interfaces of host.xml using ip-address 192.168.178.10 instead of the loop back address.
Starting up domain.bat results in errors.
[Server:server-one] 20:38:11,752 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.host.controller.client: org.jboss.msc.service.StartException in service jboss.host.controller.client: java.net.ConnectException: JBAS012144: Could not connect to remote://win01:9999. The connection timed out
Looks like JBoss is mixing up the 192.168.178.10 and 192.168.178.9 although in the JBoss configuration the 192.168.178.9 address is never used and the 192.168.178.10 has been added to the Windows hosts file.
When I remove the additonal 192.168.178.9 ip-address everything works just fine.
--
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-5630) MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL
by Zachary Bedell (JIRA)
Zachary Bedell created AS7-5630:
-----------------------------------
Summary: MBean created via EAR/META-INF/jboss-service.xml from class defined in JBoss module gets wrong TCCL
Key: AS7-5630
URL: https://issues.jboss.org/browse/AS7-5630
Project: Application Server 7
Issue Type: Bug
Components: Class Loading, Server
Affects Versions: 7.1.1.Final
Environment: Java 6u31
Reporter: Zachary Bedell
Assignee: David Lloyd
When an MBean is loaded from jboss-service.xml within an EAR, the TCCL should point to the EAR deployment so that config files and other resources can be classloaded from the EAR. Under JBoss 7.1.1.Final, the TCCL in a module loaded MBean's start() method is the module's ClassLoader. No reference to the EAR deployment's classloader is available, thus EAR resources are not available within the MBean.
It appears that org.jboss.as.service.AbstractService::invokeLifecycleMethod() incorrectly sets the TCCL to the module's defining classloader rather than the EAR's:
{{{
protected void invokeLifecycleMethod(final Method method) throws InvocationTargetException, IllegalAccessException {
if (method != null) {
final ClassLoader old = SecurityActions.setThreadContextClassLoader(mBeanInstance.getClass().getClassLoader());
try {
method.invoke(mBeanInstance);
} finally {
SecurityActions.resetThreadContextClassLoader(old);
}
}
}
}}}
--
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