[JBoss JIRA] (AS7-4703) CLONE - Create subsystem for JMS bridge
by Miroslav Novak (JIRA)
Miroslav Novak created AS7-4703:
-----------------------------------
Summary: CLONE - Create subsystem for JMS bridge
Key: AS7-4703
URL: https://issues.jboss.org/browse/AS7-4703
Project: Application Server 7
Issue Type: Task
Components: JMS
Affects Versions: 7.1.1.Final
Reporter: Miroslav Novak
Assignee: Jeff Mesnil
Currently there is no pre-defined way to deploy a JMS bridge (i.e. org.hornetq.jms.bridge.impl.JMSBridgeImpl) in AS7. In JBoss AS 6 and earlier you could deploy the bridge as an MBean or JBoss MC bean, but the current configuration schema in AS7 simply doesn't support it. The bridge is a nice feature so we need a way to deploy it.
It doesn't make sense to add the JMS bridge to a <hornetq-server> because the bridge can operate independently of a local HornetQ server. It really needs its own subsystem.
--
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, 8 months
[JBoss JIRA] (AS7-3752) Socket bind for Http11Apr fails on startup when using link-local IPv6 address
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-3752:
----------------------------------------
Summary: Socket bind for Http11Apr fails on startup when using link-local IPv6 address
Key: AS7-3752
URL: https://issues.jboss.org/browse/AS7-3752
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.1.0.Final
Reporter: Richard Achmatowicz
Assignee: Remy Maucherat
Start AS 7.1.0.Final with a link local IPv6 address:
{noformat}
[nrla@lenovo ~]$ /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr F0:DE:F1:40:75:B8
inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f2de:f1ff:fe40:75b8/64 Scope:Link
inet6 addr: 3ffe:ffff:100:f101::1/64 Scope:Global
[nrla@lenovo ~]$ ./standalone.sh -Djboss.bind.address=fe80::f2de:f1ff:fe40:75b8 -Djboss.bind.address.management=fe80::f2de:f1ff:fe40:75b8
{noformat}
and the following exception occurs:
{noformat}
11:01:28,909 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:4447
11:01:29,013 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-1) JBoss Web Services - Stack CXF Server 4.0.1.GA
11:01:29,185 ERROR [org.apache.coyote.http11.Http11AprProtocol] (MSC service thread 1-6) Error initializing endpoint: java.lang.Exception: Socket bind failed: [22] Invalid argument
at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:578) [jbossweb-7.0.10.Final.jar:]
at org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) [jbossweb-7.0.10.Final.jar:]
at org.apache.catalina.connector.Connector.init(Connector.java:983) [jbossweb-7.0.10.Final.jar:]
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267) [jboss-as-web-7.1.0.Final-SNAPSHOT.jar:7.1.0.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
11:01:29,254 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC00001: Failed to start service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:271)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: LifecycleException: Protocol handler initialization failed: java.lang.Exception: Socket bind failed: [22] Invalid argument
at org.apache.catalina.connector.Connector.init(Connector.java:985)
at org.jboss.as.web.WebConnectorService.start(WebConnectorService.java:267)
... 5 more
11:01:29,442 INFO [org.jboss.as.remoting] (MSC service thread 1-7) JBAS017100: Listening on /fe80:0:0:0:f2de:f1ff:fe40:75b8:9999
11:01:29,462 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/nrla/projects/jboss-as/build/target/jboss-as-7.1.0.Final-SNAPSHOT/standalone/deployments
11:01:29,615 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
11:01:29,626 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.web.connector.http: org.jboss.msc.service.StartException in service jboss.web.connector.http: JBAS018007: Error starting web connector
11:01:29,649 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final-SNAPSHOT "Flux Capacitor" started (with errors) in 2317ms - Started 133 of 203 services (1 services failed or missing dependencies, 68 services are passive or on-demand)
{noformat}
I had a look around and found this related (in fact the same) bug report:
https://issues.apache.org/bugzilla/show_bug.cgi?id=43327
Looks like it may have been fixed for IPv6 addresses other than link-local.
Link-local addresses are used often for running on a local network segment.
--
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, 8 months
[JBoss JIRA] (AS7-4194) Allow for pluggable user stores within realms
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-4194:
-------------------------------------
Summary: Allow for pluggable user stores within realms
Key: AS7-4194
URL: https://issues.jboss.org/browse/AS7-4194
Project: Application Server 7
Issue Type: Task
Components: Domain Management, Security
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.1.2.Final
We need to add the ability to plug in custom user store implementations - this will mean that should users and their passwords and roles be stored somewhere that we do not currently integrate with a custom store can be implemented to provide the bridge for username / password authentication.
This should be provided in the form of a SPI as we will need clearly identify what these user stores can access and provide interfaces they can implement while being sure of backwards compatibility.
This task will need to take into account both the loading of passwords based on usernames and realms and separately the loading of the roles. Implementations are free to manage their own connections but this should also contain support for using outbound connections defined in the domain model. The authentication process and role loading process occurs as two steps so this connection management should allow a connection to be shared by both steps.
As a two step process this should also cope with state potentially being passed from step 1 to step 2 - i.e. an implementation may choose to load everything it knows about a user in step 1 and just return it in step 2.
If a pluggable step is used in either step it should still be possible to use an AS provided mech for the other step.
--
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, 8 months
[JBoss JIRA] (AS7-4418) Atrribute <factory-type> is not parsed correctly in configuration of connection-factory
by Miroslav Novak (JIRA)
[ https://issues.jboss.org/browse/AS7-4418?page=com.atlassian.jira.plugin.s... ]
Miroslav Novak closed AS7-4418.
-------------------------------
Issue is fixed. Closing jira.
> Atrribute <factory-type> is not parsed correctly in configuration of connection-factory
> ---------------------------------------------------------------------------------------
>
> Key: AS7-4418
> URL: https://issues.jboss.org/browse/AS7-4418
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 7.1.2.Final-redhat1
>
>
> Attribute factory-type in configuration connection factory is not parsed correctly and default "CF" type is always used.
> Following configuration should register XAConnectionFactory but attribute factory-type is ignored:
> {code}
> <connection-factory name="RemoteConnectionFactory">
>
> <jms-connection-factories>
> ...
> <connection-factory name="RemoteConnectionFactory">
> <factory-type>XA_GENERIC</factory-type>
> <connectors>
> <connector-ref connector-name="netty"/>
> </connectors>
> <entries>
> <entry name="RemoteConnectionFactory"/>
> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
> </entries>
> <ha>true</ha>
> </connection-factory>
> ...
> </jms-connection-factories>
> {code}
--
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, 8 months
[JBoss JIRA] (AS7-4539) Can't access management interface when binding to IPv6 addresses
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-4539:
----------------------------------------
Summary: Can't access management interface when binding to IPv6 addresses
Key: AS7-4539
URL: https://issues.jboss.org/browse/AS7-4539
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Environment: Fedora 16, x86_64
[nrla@lenovo bin]$ java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Richard Achmatowicz
Assignee: Heiko Braun
Fix For: 7.1.2.Final-redhat1
Can't connect to the management console when I bind the server to an IPv6 address:
{noformat}
[nrla@lenovo bin]$ ./standalone.sh --server-config standalone-ha.xml -Djboss.bind.address=3ffe:ffff:100:f101::2 -Djboss.bind.address.management=3ffe:ffff:100:f101::2 -Djboss.bind.address.unsecure=3ffe:ffff:100:f101::2
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /tmp/serverB
JAVA: /opt/jdk-1.6.0_26/bin/java
JAVA_OPTS: -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Addresses=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml
=========================================================================
10:51:11,675 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
10:51:11,822 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
10:51:11,861 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" starting
10:51:12,797 INFO [org.xnio] XNIO Version 3.0.3.GA
10:51:12,803 INFO [org.jboss.as.server] JBAS015888: Creating http management service using socket-binding (management-http)
10:51:12,809 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
10:51:12,823 INFO [org.jboss.remoting] JBoss Remoting version 3.2.4.GA
10:51:12,847 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
10:51:12,852 INFO [org.jboss.as.configadmin] (ServerService Thread Pool -- 28) JBAS016200: Activating ConfigAdmin Subsystem
10:51:12,864 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 33) JBAS010280: Activating Infinispan subsystem.
10:51:12,888 INFO [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 37) JBAS010260: Activating JGroups subsystem.
10:51:12,906 INFO [org.jboss.as.security] (ServerService Thread Pool -- 48) JBAS013101: Activating Security Subsystem
10:51:12,932 INFO [org.jboss.as.osgi] (ServerService Thread Pool -- 43) JBAS011940: Activating OSGi Subsystem
10:51:12,938 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 42) JBAS011800: Activating Naming Subsystem
10:51:12,958 INFO [org.jboss.as.connector] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.9.Final)
10:51:12,965 INFO [org.jboss.as.security] (MSC service thread 1-2) JBAS013100: Current PicketBox version=4.0.7.Final
10:51:12,990 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 52) JBAS015537: Activating WebServices Extension
10:51:13,003 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 29) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
10:51:13,025 INFO [org.jboss.as.naming] (MSC service thread 1-7) JBAS011802: Starting Naming Service
10:51:13,051 INFO [org.jboss.as.mail.extension] (MSC service thread 1-6) JBAS015400: Bound mail session [java:jboss/mail/Default]
10:51:13,191 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-7) JBoss Web Services - Stack CXF Server 4.0.2.GA
10:51:13,261 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp--3ffe_ffff_100_f101_0_0_0_2-2-8009
10:51:13,262 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--3ffe_ffff_100_f101_0_0_0_2-2-8080
10:51:13,330 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-5) Initializing mod_cluster 1.2.1.Beta2
10:51:13,364 INFO [org.jboss.modcluster.advertise.impl.AdvertiseListenerImpl] (MSC service thread 1-5) Listening to proxy advertisements on ff0e:0:0:0:0:0:0:1:23,364
10:51:13,430 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
10:51:13,448 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (ServerService Thread Pool -- 33) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
10:51:13,563 INFO [org.jboss.as.remoting] (MSC service thread 1-6) JBAS017100: Listening on /3ffe:ffff:100:f101:0:0:0:2%2:4447
10:51:13,563 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /3ffe:ffff:100:f101:0:0:0:2%2:9999
10:51:13,585 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-8) JBAS015012: Started FileSystemDeploymentService for directory /tmp/serverB/standalone/deployments
10:51:13,607 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-7) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
10:51:13,761 WARNING [org.jgroups.protocols.UDP] (pool-14-thread-1) send buffer of socket java.net.DatagramSocket@39126d91 was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
10:51:13,762 WARNING [org.jgroups.protocols.UDP] (pool-14-thread-1) receive buffer of socket java.net.DatagramSocket@39126d91 was set to 20MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
10:51:13,763 WARNING [org.jgroups.protocols.UDP] (pool-14-thread-1) send buffer of socket java.net.MulticastSocket@15e3d24a was set to 640KB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max send buffer in the OS correctly (e.g. net.core.wmem_max on Linux)
10:51:13,763 WARNING [org.jgroups.protocols.UDP] (pool-14-thread-1) receive buffer of socket java.net.MulticastSocket@15e3d24a was set to 25MB, but the OS only allocated 131.07KB. This might lead to performance problems. Please set your max receive buffer in the OS correctly (e.g. net.core.rmem_max on Linux)
10:51:13,768 INFO [stdout] (pool-14-thread-1)
10:51:13,768 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
10:51:13,769 INFO [stdout] (pool-14-thread-1) GMS: address=lenovo/web, cluster=web, physical address=3ffe:ffff:100:f101:0:0:0:2:55200
10:51:13,770 INFO [stdout] (pool-14-thread-1) -------------------------------------------------------------------
10:51:15,992 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-2) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
10:51:15,997 INFO [org.infinispan.configuration.cache.EvictionConfigurationBuilder] (MSC service thread 1-7) ISPN000152: Passivation configured without an eviction policy being selected. Only manually evicted entities will be pasivated.
10:51:16,170 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://[3ffe:ffff:100:f101:0:0:0:2%2]:9990
10:51:16,171 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss AS 7.1.2.Final-SNAPSHOT "Brontes" started in 4674ms - Started 134 of 268 services (133 services are passive or on-demand)
{noformat}
Trying to access the console:
{noformat}
[nrla@lenovo bin]$ ./jboss-cli.sh
You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
[disconnected /] connect controller=3ffe:ffff:100:f101:0:0:0:2
The controller is not available at controller=3ffe:ffff:100:f101:0:0:0:2
[disconnected /] connect controller=3ffe:ffff:100:f101:0:0:0:2%2
The port must be a valid non-negative integer: '[controller=3ffe:ffff:100:f101:0:0:0:2%2]'
[disconnected /] connect controller=[3ffe:ffff:100:f101:0:0:0:2%2]
The controller is not available at controller=[3ffe:ffff:100:f101:0:0:0:2%2]:9999
[disconnected /] connect controller=[3ffe:ffff:100:f101:0:0:0:2%2]:9990
The controller is not available at controller=[3ffe:ffff:100:f101:0:0:0:2%2]:9990
[disconnected /]
{noformat}
--
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, 8 months