[JBoss JIRA] (JBCOMMON-133) 'https-remoting' not mentioned in 'connect --help' output
by Valery Sorokin (JIRA)
[ https://issues.jboss.org/browse/JBCOMMON-133?page=com.atlassian.jira.plug... ]
Valery Sorokin commented on JBCOMMON-133:
-----------------------------------------
s/above/bellow/
> 'https-remoting' not mentioned in 'connect --help' output
> ---------------------------------------------------------
>
> Key: JBCOMMON-133
> URL: https://issues.jboss.org/browse/JBCOMMON-133
> Project: JBoss Common
> Issue Type: Bug
> Environment: installed EAP7, domain/secured mode
> Reporter: Valery Sorokin
> Assignee: Dimitris Andreadis
> Priority: Minor
>
> in this help output not mentioned option 'https-remoting', which actually exists and works
> ----------------------------------------------------------------------------
> [disconnected /] connect --help
> SYNOPSIS
> connect [host][ort]
> DESCRIPTION
> Connects to the controller on the specified host and port using the specified
> protocol.
> The default values can be customized by specifying the desired defaults as
> command line arguments when launching the CLI. E.g.
> jboss-cli.sh controller=http-remoting://controller-host.net:1234
> Or
> jboss-cli.sh controller=controller-host.net
> In this case, the default port will be 9990 and the default protocol will be
> http.
> Note, specifying controller argument will only set the default host and port
> values for the connect command but will not automatically connect to the
> specified controller.
> To connect automatically after the launch, use '--connect' switch. E.g.
> jboss-cli.sh --connect
> jboss-cli.sh --connect controller=controller-host.net
> jboss-cli.sh --connect controller=controller-host.net:1234
> jboss-cli.sh --connect controller=remote://controller-host.net:1234
> jboss-cli.sh --connect controller=http-remoting://controller-host.net:1234
> The host may be any of these formats:
> - a host name, e.g. localhost
> - an IPv4 address, e.g. 127.0.0.1
> - an IPv6 address, e.g. [::1]
> ARGUMENTS
> protocol - optional, default value is http.
> host - optional, default value is localhost.
> port - optional, default value is 9990.
> ----------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBCOMMON-133) 'https-remoting' not mentioned in 'connect --help' output
by Valery Sorokin (JIRA)
Valery Sorokin created JBCOMMON-133:
---------------------------------------
Summary: 'https-remoting' not mentioned in 'connect --help' output
Key: JBCOMMON-133
URL: https://issues.jboss.org/browse/JBCOMMON-133
Project: JBoss Common
Issue Type: Bug
Environment: installed EAP7, domain/secured mode
Reporter: Valery Sorokin
Assignee: Dimitris Andreadis
Priority: Minor
in this help output not mentioned option 'https-remoting', which actually exists and works
----------------------------------------------------------------------------
[disconnected /] connect --help
SYNOPSIS
connect [host][ort]
DESCRIPTION
Connects to the controller on the specified host and port using the specified
protocol.
The default values can be customized by specifying the desired defaults as
command line arguments when launching the CLI. E.g.
jboss-cli.sh controller=http-remoting://controller-host.net:1234
Or
jboss-cli.sh controller=controller-host.net
In this case, the default port will be 9990 and the default protocol will be
http.
Note, specifying controller argument will only set the default host and port
values for the connect command but will not automatically connect to the
specified controller.
To connect automatically after the launch, use '--connect' switch. E.g.
jboss-cli.sh --connect
jboss-cli.sh --connect controller=controller-host.net
jboss-cli.sh --connect controller=controller-host.net:1234
jboss-cli.sh --connect controller=remote://controller-host.net:1234
jboss-cli.sh --connect controller=http-remoting://controller-host.net:1234
The host may be any of these formats:
- a host name, e.g. localhost
- an IPv4 address, e.g. 127.0.0.1
- an IPv6 address, e.g. [::1]
ARGUMENTS
protocol - optional, default value is http.
host - optional, default value is localhost.
port - optional, default value is 9990.
----------------------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2023) Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2023?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2023:
--------------------------------
I'm not an IPv6 expert but does this look normal?
{noformat}
[bela@dev87 classes]$ ip -6 route show
unreachable ::/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
2620:52:0:105f::/64 dev eth0 proto kernel metric 256 expires 2147089sec mtu 1500 advmss 1440 hoplimit 0
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 65536 advmss 65476 hoplimit 0
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 0
default via fe80::a0:98ff:fe05:fc dev eth0 proto kernel metric 1024 expires 1732sec mtu 1500 advmss 1440 hoplimit 64
default via fe80:52:0:105f::fd dev eth0 proto kernel metric 1024 expires 1732sec mtu 1500 advmss 1440 hoplimit 64
[bela@dev87 classes]$
{noformat}
> Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
> -----------------------------------------------------------------------------------------------
>
> Key: JGRP-2023
> URL: https://issues.jboss.org/browse/JGRP-2023
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: $ java -version
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Richard Janík
> Assignee: Bela Ban
>
> When setting {{-bind_addr}} to localhost (either 127.0.0.1 or ::1) without specifying {{-Djava.net.preferIPv4Stack=true}}, JGroups fail to connect. The following errors are logged:
> {code}
> -------------------------------------------------------------------
> GMS: address=rjanik-24069, cluster=draw, physical address=0:0:0:0:0:0:0:1:37921
> -------------------------------------------------------------------
> Mar 03, 2016 11:41:12 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (108 bytes): java.io.IOException: Network is unreachable, headers: PING: [type=GET_MBRS_REQ, cluster=draw], TP: [cluster_name=draw]
> ** View=[rjanik-24069|0] (1) [rjanik-24069]
> Mar 03, 2016 11:41:15 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (56 bytes): java.io.IOException: Network is unreachable, headers: NAKACK2: [MSG, seqno=1], TP: [cluster_name=draw]
> {code}
> I'm not sure if there's some other configuration option that I forgot to add, but the example (in Steps to Reproduce) works with previous versions (3.6.6 for example), so I assume not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2023) Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
by Richard Janík (JIRA)
[ https://issues.jboss.org/browse/JGRP-2023?page=com.atlassian.jira.plugin.... ]
Richard Janík commented on JGRP-2023:
-------------------------------------
It's a pure IPv6 machine, so make sure you're using {{ping6}} or {{ping -6}}, whichever is your case [1]. If all else fails, you can also try with dev87 [2], which has some IPv6 addresses and I hit it there too (it is RHEL 6).
[1]: {{ping6 gen-vm003.mw.lab.eng.bos.redhat.com}} works for me, even from localhost
[2]: {{dev87.mw.lab.eng.bos.redhat.com}}
> Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
> -----------------------------------------------------------------------------------------------
>
> Key: JGRP-2023
> URL: https://issues.jboss.org/browse/JGRP-2023
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: $ java -version
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Richard Janík
> Assignee: Bela Ban
>
> When setting {{-bind_addr}} to localhost (either 127.0.0.1 or ::1) without specifying {{-Djava.net.preferIPv4Stack=true}}, JGroups fail to connect. The following errors are logged:
> {code}
> -------------------------------------------------------------------
> GMS: address=rjanik-24069, cluster=draw, physical address=0:0:0:0:0:0:0:1:37921
> -------------------------------------------------------------------
> Mar 03, 2016 11:41:12 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (108 bytes): java.io.IOException: Network is unreachable, headers: PING: [type=GET_MBRS_REQ, cluster=draw], TP: [cluster_name=draw]
> ** View=[rjanik-24069|0] (1) [rjanik-24069]
> Mar 03, 2016 11:41:15 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (56 bytes): java.io.IOException: Network is unreachable, headers: NAKACK2: [MSG, seqno=1], TP: [cluster_name=draw]
> {code}
> I'm not sure if there's some other configuration option that I forgot to add, but the example (in Steps to Reproduce) works with previous versions (3.6.6 for example), so I assume not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JGRP-2023) Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2023?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-2023:
--------------------------------
I cannot find (ping) gen-vm003... Not even from within the lab.
> Network unreachable with localhost addresses if -Djava.net.preferIPv4Stack=true isn't specified
> -----------------------------------------------------------------------------------------------
>
> Key: JGRP-2023
> URL: https://issues.jboss.org/browse/JGRP-2023
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.6.7, 3.6.8
> Environment: $ java -version
> java version "1.8.0_45"
> Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
> Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
> Reporter: Richard Janík
> Assignee: Bela Ban
>
> When setting {{-bind_addr}} to localhost (either 127.0.0.1 or ::1) without specifying {{-Djava.net.preferIPv4Stack=true}}, JGroups fail to connect. The following errors are logged:
> {code}
> -------------------------------------------------------------------
> GMS: address=rjanik-24069, cluster=draw, physical address=0:0:0:0:0:0:0:1:37921
> -------------------------------------------------------------------
> Mar 03, 2016 11:41:12 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (108 bytes): java.io.IOException: Network is unreachable, headers: PING: [type=GET_MBRS_REQ, cluster=draw], TP: [cluster_name=draw]
> ** View=[rjanik-24069|0] (1) [rjanik-24069]
> Mar 03, 2016 11:41:15 AM org.jgroups.protocols.TP$BaseBundler sendSingleMessage
> SEVERE: JGRP000029: rjanik-24069: failed sending message to cluster (56 bytes): java.io.IOException: Network is unreachable, headers: NAKACK2: [MSG, seqno=1], TP: [cluster_name=draw]
> {code}
> I'm not sure if there's some other configuration option that I forgot to add, but the example (in Steps to Reproduce) works with previous versions (3.6.6 for example), so I assume not.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1314) Log datasource name in warn message when Network Adapter fails to establish connection with database.
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1314?page=com.atlassian.jira.plugin... ]
Jesper Pedersen updated JBJCA-1314:
-----------------------------------
Issue Type: Task (was: Feature Request)
Priority: Minor (was: Major)
Labels: (was: jboss l)
> Log datasource name in warn message when Network Adapter fails to establish connection with database.
> -----------------------------------------------------------------------------------------------------
>
> Key: JBJCA-1314
> URL: https://issues.jboss.org/browse/JBJCA-1314
> Project: IronJacamar
> Issue Type: Task
> Components: Core
> Environment: Red Hat JBoss Enterprise Application Platform
> Reporter: Lin Gao
> Assignee: Lin Gao
> Priority: Minor
> Fix For: WildFly/IronJacamar 1.3.3.Final, 1.2.7.Final
>
>
> When there's following log statement in "server.log":
> {code}
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: javax.resource.ResourceException: Could not create connection
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:331)
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:288)
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:834) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.fillToMin(SemaphoreArrayListManagedConnectionPool.java:775) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1]
> at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97) [ironjacamar-core-impl-1.0.28.Final-redhat-1.jar:1.0.28.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_80]
> Caused by: java.sql.SQLRecoverableException: I/O-Fehler: The Network Adapter could not establish the connection
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:517)
> at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:557)
> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:233)
> at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:29)
> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:556)
> at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:303)
> ... 5 more
> Caused by: oracle.net.ns.NetException: The Network Adapter could not establish the connection
> at oracle.net.nt.ConnStrategy.execute(ConnStrategy.java:389)
> at oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:431)
> at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:882)
> at oracle.net.ns.NSProtocol.connect(NSProtocol.java:267)
> at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1625)
> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:365)
> ... 10 more
> {code}
> With the above warn message how to figure which DB connection could not be established with out testing connection using CLI or management console.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month