[JBoss JIRA] (AS7-4171) mod_cluster registers ROOT context
by Michal Babacek (JIRA)
Michal Babacek created AS7-4171:
-----------------------------------
Summary: mod_cluster registers ROOT context
Key: AS7-4171
URL: https://issues.jboss.org/browse/AS7-4171
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.0.0.Final, 7.1.0.Final
Reporter: Michal Babacek
Assignee: Jean-Frederic Clere
Priority: Critical
Fix For: 7.1.1.Final
mod_cluster registers ROOT context even though its specified in excluded-list
default profile
[rhusar@rhusar jboss-as-7.1.0.Final-SNAPSHOT]$ ./bin/standalone.sh -c standalone-ha.xml
http://localhost:6666/mod_cluster_manager
mod_cluster/1.1.x
Auto Refresh show DUMP output show INFO output
Node 498bb1f0-00d9-3436-a341-7f012bc2e7ec (http://localhost.localdomain:8080):
Enable Contexts Disable Contexts
Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: OK,Elected: 5,Read: 81387,Transferred: 2531,Connected: 0,Load: 1
Virtual Host 1:
Contexts:
/, Status: ENABLED Request: 0 Disable
Aliases:
default-host
localhost
example.com
--
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, 1 month
[JBoss JIRA] (AS7-4169) CLI: ls fails on <ear>/<war>/subsystem=web
by Ondrej Zizka (JIRA)
Ondrej Zizka created AS7-4169:
---------------------------------
Summary: CLI: ls fails on <ear>/<war>/subsystem=web
Key: AS7-4169
URL: https://issues.jboss.org/browse/AS7-4169
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.1.Final
Reporter: Ondrej Zizka
Assignee: Dominik Pospisil
STR:
1) Deploy the attached EAR (quickstart in development, not necessarily correct).
2) in CLI: $ cd /deployment=javaee-inject-example-ear-1.5.4.ear/subdeployment=javaee-inject-example-war/subsystem=web
(pwd should verify that path)
3) $ ls fails with:
{code}
JBAS014807: Management resource '[
(\"deployment\" => \"javaee-inject-example-ear-1.5.4.ear\"),
(\"subdeployment\" => \"javaee-inject-example-war\"),
(\"subsystem\" => \"web\")
]' not found
{code}
Full log attached.
--
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, 1 month
[JBoss JIRA] (JBNAME-58) JBoss ignoring SECURITY_PRINCIPALand SECURITY_CREDENTIALS when using org.jboss.naming.HttpNamingContextFactory. Its lead to "Server redirect too many times(20).
by Sasi Levi (JIRA)
Sasi Levi created JBNAME-58:
-------------------------------
Summary: JBoss ignoring SECURITY_PRINCIPALand SECURITY_CREDENTIALS when using org.jboss.naming.HttpNamingContextFactory. Its lead to "Server redirect too many times(20).
Key: JBNAME-58
URL: https://issues.jboss.org/browse/JBNAME-58
Project: JBoss Naming
Issue Type: Bug
Components: jnp-client, jnpserver, naming
Environment: JBoss 4.2.3GA linux
Reporter: Sasi Levi
I tried to use the following configuration.
hm.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.HttpNamingContextFactory");
hm.put(Context.PROVIDER_URL, "https://<host>:443/invoker/JNDIFactory");
hm.put(Context.SECURITY_PRINCIPAL, "<user>");
hm.put(Context.SECURITY_CREDENTIALS, "<password>");
InitialContext ic = new InitialContext(hm);
I'm getting in the client side:
TRACE] Retrieving content from : https://<host_name>:443/invoker/JNDIFactory
[DEBUG] Using ThreadLocal: false
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] getPrincipal, principal=null
[TRACE] ContentLength: 948
ContentType: text/html;charset=utf-8
Exception in thread "main" javax.naming.NamingException: Failed to retrieve Naming interface for provider https://<host_name>:443/invoker/JNDIFactory [Root exception is java.net.ProtocolException: Server redirected too many times (20)]
at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:84)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at client.TestJndiWithHttpsWithLoginModule.main(TestJndiWithHttpsWithLoginModule.java:45)
Caused by: java.net.ProtocolException: Server redirected too many times (20)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at sun.net.www.protocol.http.HttpURLConnection$6.run(HttpURLConnection.java:1368)
at java.security.AccessController.doPrivileged(Native Method)
at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1362)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1016)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:133)
at org.jboss.naming.HttpNamingContextFactory.getInitialContext(HttpNamingContextFactory.java:80)
... 5 more
Caused by: java.net.ProtocolException: Server redirected too many times (20)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1323)
at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(HttpURLConnection.java:2173)
at java.net.URLConnection.getHeaderFieldInt(URLConnection.java:579)
at java.net.URLConnection.getContentLength(URLConnection.java:474)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getContentLength(HttpsURLConnectionImpl.java:378)
at org.jboss.naming.HttpNamingContextFactory.getNamingServer(HttpNamingContextFactory.java:128)
... 6 more
I used only custom LoginModule and I saw NULL/NULL as username password.
I don't want to use the LoginJndi...
--
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, 1 month
[JBoss JIRA] (AS7-4165) NullPointerException with SSL and modcluster
by Michal Babacek (JIRA)
Michal Babacek created AS7-4165:
-----------------------------------
Summary: NullPointerException with SSL and modcluster
Key: AS7-4165
URL: https://issues.jboss.org/browse/AS7-4165
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.0.Final
Reporter: Michal Babacek
Assignee: Paul Ferraro
Priority: Critical
Fix For: 7.1.1.Final
If I try to use SSL with mod_cluster I get a NullPointerException at JBoss startup and modcluster subsystem doesn't start. Configuration:
{code:xml}
<subsystem xmlns="urn:jboss:domain:modcluster:1.0">
<mod-cluster-config advertise="false" proxy-list="sd06009.uyellow.yellowcorp.test:6199" balancer="test">
<ssl password="123456" certificate-key-file="configuration/keys/jspStore.jks" ca-certificate-file="configuration/keys/yellowJspDynWesTrust.jks"/>
</mod-cluster-config>
</subsystem>
{code}
Log:
{noformat}
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /app/jboss/current
JAVA: java
JAVA_OPTS: -server -Xms64m -Xmx1512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=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
=========================================================================
WARNING: -logmodule is deprecated. Please use the system property 'java.util.logging.manager' or the 'java.util.logging.LogManager' service loader.
14:20:23,022 INFO [org.jboss.modules] JBoss Modules version 1.1.1.GA
14:20:23,440 INFO [org.jboss.msc] JBoss MSC version 1.0.2.GA
14:20:23,531 INFO [org.jboss.as] JBAS015899: JBoss AS 7.1.0.Final "Thunder" starting
14:20:25,113 INFO [org.xnio] XNIO Version 3.0.3.GA
14:20:25,117 INFO [org.jboss.as.server] JBAS015889: Creating http management service using secure-socket-binding (management-http)
14:20:25,129 INFO [org.xnio.nio] XNIO NIO Implementation Version 3.0.3.GA
14:20:25,146 INFO [org.jboss.remoting] JBoss Remoting version 3.2.2.GA
14:20:25,172 INFO [org.jboss.as.logging] JBAS011502: Removing bootstrap log handlers
14:20:25,312 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 24) JBAS010280: Activating Infinispan subsystem.
14:20:25,312 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) JBAS010403: Deploying JDBC-compliant driver class com.ibm.db2.jcc.DB2Driver (version 4.13)
14:20:25,393 INFO [org.jboss.as.connector] (MSC service thread 1-1) JBAS010408: Starting JCA Subsystem (JBoss IronJacamar 1.0.7.Final)
14:20:25,405 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 38) JBAS015537: Activating WebServices Extension
14:20:25,436 INFO [org.jboss.as.security] (ServerService Thread Pool -- 34) JBAS013101: Activating Security Subsystem
14:20:25,440 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 30) JBAS011800: Activating Naming Subsystem
14:20:25,485 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
14:20:25,491 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default]
14:20:25,680 INFO [org.apache.coyote.ajp.AjpProtocol] (MSC service thread 1-3) Starting Coyote AJP/1.3 on ajp--0.0.0.0-8009
14:20:25,697 INFO [org.jboss.as.modcluster] (MSC service thread 1-4) JBAS011704: Mod_cluster uses default load balancer provider
14:20:25,761 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0.0.0.0-8080
14:20:25,792 INFO [org.jboss.ws.common.management.AbstractServerConfig] (MSC service thread 1-3) JBoss Web Services - Stack CXF Server 4.0.1.GA
14:20:25,810 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013100: Current PicketBox version=4.0.6.final
14:20:25,939 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 21) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
14:20:26,042 INFO [org.jboss.modcluster.ModClusterService] (MSC service thread 1-4) Initializing mod_cluster 1.2.0.Final
14:20:26,251 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.mod-cluster: org.jboss.msc.service.StartException in service jboss.mod-cluster: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_02]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_02]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_02]
Caused by: java.lang.NullPointerException
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.getKeyManagers(JSSESocketFactory.java:284)
at org.jboss.modcluster.mcmp.impl.JSSESocketFactory.<init>(JSSESocketFactory.java:98)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler$Proxy.<init>(DefaultMCMPHandler.java:747)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.add(DefaultMCMPHandler.java:183)
at org.jboss.modcluster.mcmp.impl.DefaultMCMPHandler.init(DefaultMCMPHandler.java:139)
at org.jboss.modcluster.ModClusterService.init(ModClusterService.java:146)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.init(CatalinaEventHandlerAdapter.java:258)
at org.jboss.modcluster.container.catalina.CatalinaEventHandlerAdapter.start(CatalinaEventHandlerAdapter.java:99)
at org.jboss.as.modcluster.ModClusterService.start(ModClusterService.java:229)
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]
... 3 more
14:20:27,282 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) Starting Coyote HTTP/1.1 on http--0.0.0.0-8443
14:20:28,126 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/jdbc/app_name/DataSourceDB2]
14:20:28,128 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/PrestOracleDS]
14:20:28,183 INFO [org.jboss.as.remoting] (MSC service thread 1-1) JBAS017100: Listening on /0.0.0.0:4447
14:20:28,190 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on /0.0.0.0:9999
14:20:28,251 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.mod-cluster: org.jboss.msc.service.StartException in service jboss.mod-cluster: Failed to start service
14:20:28,260 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.1.0.Final "Thunder" started (with errors) in 5892ms - Started 148 of 202 services (1 services failed or missing dependencies, 43 services are passive or on-demand)
{noformat}
The paths and names of the certificates are correct.
--
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, 1 month