[JBoss JIRA] (AS7-3890) Unable to pass smoke tests part of testsuite when specify -Dnode0=<something>
by Pavel Janousek (JIRA)
Pavel Janousek created AS7-3890:
-----------------------------------
Summary: Unable to pass smoke tests part of testsuite when specify -Dnode0=<something>
Key: AS7-3890
URL: https://issues.jboss.org/browse/AS7-3890
Project: Application Server 7
Issue Type: Bug
Components: Test Suite
Affects Versions: 7.1.1.Final
Reporter: Pavel Janousek
Assignee: Andrew Rubinger
I'm unable to pass smoke tests part of testsuite.
I hope you get the same result when try:
{code}
./build.sh clean install [pass]
ifconfig lo:1 127.0.0.2 [pass]
./integration-tests.sh install -Dnode0=127.0.0.2
{code}
I got:
{code}
Tests in error:
testMessagingClient(org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase): java.net.ConnectException: JBAS012144: Could not connect to remote://pjanouse.brq.redhat.com:9999. The connection timed out
testMessagingClient(org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase): Cannot connect to server(s). Tried with all available servers.
{code}
Also in IPv6 mode like:
{code}
./integration-tests.sh install -Dnode0=::1 -Dipv6
{code}
I got error, but it differs from above:
{code}
Tests in error:
org.jboss.as.test.smoke.embedded.demos.jms.JmsTestCase: destination address may not be null
org.jboss.as.test.smoke.embedded.demos.client.jms.JmsClientTestCase: destination address may not be null
org.jboss.as.test.smoke.embedded.demos.client.messaging.MessagingClientTestCase: destination address may not be null
org.jboss.as.test.smoke.embedded.demos.messaging.MessagingTestCase: destination address may not be null
{code}
When I specify -Dnode0=127.0.0.1 as binding address, everything works fine...
PS: This state is *after* merging O. Zizka's TS-refactor branch (commit d0f1f3cef0ed90d4b655e5aec15be7b00a373f5c).
--
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] (JBASMP-22) deploy goal failing on 7.1 final
by shay Matasaro (JIRA)
shay Matasaro created JBASMP-22:
-----------------------------------
Summary: deploy goal failing on 7.1 final
Key: JBASMP-22
URL: https://issues.jboss.org/browse/JBASMP-22
Project: JBoss AS Maven Plugins
Issue Type: Bug
Components: deploy
Environment: ubuntu 11.10 , maven 303 ,AS 7.1 Final
Reporter: shay Matasaro
Assignee: Andrew Rubinger
Priority: Blocker
when running deploy goal using hello world sample app to AS 7.1 final , operation fails with the following error:
[INFO] Executing goal deploy for /home/shay/workspace/helloworld/jboss-as-helloworld/target/jboss-as-helloworld.war on server localhost (127.0.0.1) port 9999.
22-Feb-2012 5:05:44 PM org.jboss.remoting3.EndpointImpl <clinit>
INFO: JBoss Remoting version 3.2.0.Beta2
22-Feb-2012 5:05:44 PM org.xnio.Xnio <clinit>
INFO: XNIO Version 3.0.0.Beta2
22-Feb-2012 5:05:44 PM org.xnio.nio.NioXnio <clinit>
INFO: XNIO NIO Implementation Version 3.0.0.Beta2
22-Feb-2012 5:05:45 PM org.xnio.ChannelListeners invokeChannelListener
ERROR: A channel event listener threw an exception
java.lang.NullPointerException
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:291)
at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:182)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71)
at org.xnio.channels.TranslatingSuspendableChannel.handleReadable(TranslatingSuspendableChannel.java:173)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:94)
at org.xnio.channels.TranslatingSuspendableChannel$2.handleEvent(TranslatingSuspendableChannel.java:92)
at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:71)
at org.xnio.nio.NioHandle.invoke(NioHandle.java:77)
at org.xnio.nio.AbstractNioChannelThread$1.run(AbstractNioChannelThread.java:142)
at java.lang.Thread.run(Thread.java:662)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
--
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-3183) Admin console: validation of IP address when defining a network interface
by Jan Martiska (Created) (JIRA)
Admin console: validation of IP address when defining a network interface
-------------------------------------------------------------------------
Key: AS7-3183
URL: https://issues.jboss.org/browse/AS7-3183
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Dustin Kut Moy Cheung
In standalone mode, navigate to Profile/General Configuration/Interfaces. There are several issues concerning definition of a new network interface.
1) it seems impossible to create an interface with conditional IP address, such as ${jboss.bind.address.management:127.0.0.1}, this operation fails on server with description: JBAS014692: Invalid address ${jboss.bind.address.management:127.0.0.1} (${jboss.bind.address.management:127.0.0.1})"
2) the form for putting in an IP address should do some sort of validation. It should pass only when a valid IPv4 or IPv6 address is put in, and of course in case with conditional assignment as in 1).
3) when you pick either "Any IPv4 Address" or "Any IPv6 Address" in the form for creation of a new interface, the operation will fail on server with message:
"JBAS014763: any-address is required", I assume that this is because the console sends a parameter "any-ip4-address=true" to the server, which is wrong, the correct spelling of this parameter is any-ipv4-address. Analogically for ipv6.
--
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-3549) Make default-cache attribute of cache-container configurable
by Jan Martiska (JIRA)
Jan Martiska created AS7-3549:
---------------------------------
Summary: Make default-cache attribute of cache-container configurable
Key: AS7-3549
URL: https://issues.jboss.org/browse/AS7-3549
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.0.CR1b
Reporter: Jan Martiska
Assignee: Heiko Braun
Fix For: 7.1.1.Final
Currently, it is not possible to add a Cache Container using the admin console, cause the form is missing a required attribute 'cache-container':
JBAS014612: Operation ("add") failed - address: ([
("subsystem" => "infinispan"),
("cache-container" => "fff")
]): java.util.NoSuchElementException: No child 'default-cache' exists
according to AS7-3488 : it seems that default-cache attribute will no longer be required, so this will most likely work again in the future.
However, still there should be a form element to input a value for this attribute, it seems like it is not configurable at all (using the console) for the time being.
--
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-3865) CLI: data-source, jms-queue, jms-topic commands do not support --headers argument
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3865:
-------------------------------------
Summary: CLI: data-source, jms-queue, jms-topic commands do not support --headers argument
Key: AS7-3865
URL: https://issues.jboss.org/browse/AS7-3865
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.1.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
CLI: data-source, jms-queue, jms-topic commands do not support --headers argument.
Steps to reproduce:
[standalone@localhost:9999 /] data-source add --name=TestDS --jndi-name=java:jboss/datasources/TestDS --driver-name=h2 --connection-url=jdbc:h2:mem:test;DB_CLOSE_DELAY=-1
[standalone@localhost:9999 /] data-source enable --name=TestDS
[standalone@localhost:9999 /] data-source disable --name=TestDS --headers={"allow-resource-service-restart"}
Unrecognized argument --headers for command 'disable'.
--
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