[JBoss JIRA] (JBASM-41) JBoss Crashes when i change port number from 8080 to 12001
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/JBASM-41?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on JBASM-41:
-------------------------------------
If this is still an issue for you, I suggest to move your discussion to the JBoss AS forums. This does not look like a problem with the Server Manager.
> JBoss Crashes when i change port number from 8080 to 12001
> ----------------------------------------------------------
>
> Key: JBASM-41
> URL: https://issues.jboss.org/browse/JBASM-41
> Project: JBoss AS Server Manager
> Issue Type: Feature Request
> Environment: Windows 2008 32 bit server
> Reporter: Manjunath Mudigonda
> Assignee: Shelly McGowan
> Labels: 5.0.1, AS, JBoss, change, port
> Original Estimate: 1 week
> Remaining Estimate: 1 week
>
> am having 2 instances of JBoss running for different Applications.
> the first application was installed on port 8080 and for the second instance i configured the server.xml to change the port to 12001 and started the JBoss AS in default mode which was crashed saying that port 8080 is already in use then i manually ran the following command to force the JBoss to run on the specific port still results the same
> c:\JBoss501\JBoss-AS\bin> run.bat -Djboss.service.binding.set=12001
> find the log content here
>
>
>
>
> Calling C:\idm\jbossas501\jboss-as\bin\run.conf.bat
> ===============================================================================
> JBoss Bootstrap Environment
> JBOSS_HOME: C:\jboss501\jboss-as
> JAVA: C:\Java\jdk1.6.0_25\bin\java
> JAVA_OPTS: -Dprogram.name=run.bat -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -server
> CLASSPATH: C:\Java\jdk1.6.0_25\lib\tools.jar;C:\jboss501\jboss-as\bin\run.jar
> ===============================================================================
> 23:00:39,545 INFO [ServerImpl] Starting JBoss (Microcontainer)...
> 23:00:39,546 INFO [ServerImpl] Release ID: JBoss [EAP] 5.0.1 (build: SVNTag=JBPAPP_5_0_1 date=201003301050)
> 23:00:39,546 INFO [ServerImpl] Bootstrap URL: null
> 23:00:39,546 INFO [ServerImpl] Home Dir: C:\jboss501\jboss-as
> 23:00:39,546 INFO [ServerImpl] Home URL: file:/C:/jboss501/jboss-as/
> 23:00:39,546 INFO [ServerImpl] Library URL: file:/C:/jboss501/jboss-as/lib/
> 23:00:39,548 INFO [ServerImpl] Patch URL: null
> 23:00:39,548 INFO [ServerImpl] Common Base URL: file:/C:/jboss501/jboss-as/common/
> 23:00:39,548 INFO [ServerImpl] Common Library URL: file:/C:/jboss501/jboss-as/common/lib/
> 23:00:39,548 INFO [ServerImpl] Server Name: default
> 23:00:39,548 INFO [ServerImpl] Server Base Dir: C:\jboss501\jboss-as\server
> 23:00:39,548 INFO [ServerImpl] Server Base URL: file:/C:/jboss501/jboss-as/server/
> 23:00:39,548 INFO [ServerImpl] Server Config URL: file:/C:/jboss501/jboss-as/server/default/conf/
> 23:00:39,548 INFO [ServerImpl] Server Home Dir: C:\jboss501\jboss-as\server\default
> 23:00:39,548 INFO [ServerImpl] Server Home URL: file:/C:/jboss501/jboss-as/server/default/
> 23:00:39,548 INFO [ServerImpl] Server Data Dir: C:\jboss501\jboss-as\server\default\data
> 23:00:39,548 INFO [ServerImpl] Server Library URL: file:/C:/jboss501/jboss-as/server/default/lib/
> 23:00:39,548 INFO [ServerImpl] Server Log Dir: C:\jboss501\jboss-as\server\default\log
> 23:00:39,548 INFO [ServerImpl] Server Native Dir: C:\jboss501\jboss-as\server\default\tmp\native
> 23:00:39,548 INFO [ServerImpl] Server Temp Dir: C:\jboss501\jboss-as\server\default\tmp
> 23:00:39,549 INFO [ServerImpl] Server Temp Deploy Dir: C:\jboss501\jboss-as\server\default\tmp\deploy
> 23:00:40,383 INFO [ServerImpl] Starting Microcontainer, bootstrapURL=file:/C:/jboss501/jboss-as/server/default/conf/bootstrap.xml
> 23:00:41,007 INFO [VFSCacheFactory] Initializing VFSCache [org.jboss.virtual.plugins.cache.CombinedVFSCache]
> 23:00:41,009 INFO [VFSCacheFactory] Using VFSCache [CombinedVFSCache[real-cache: null]]
> 23:00:41,317 INFO [CopyMechanism] VFS temp dir: C:\jboss501\jboss-as\server\default\tmp
> 23:00:41,317 INFO [ZipEntryContext] VFS force nested jars copy-mode is enabled.
> 23:00:42,711 INFO [ServerInfo] Java version: 1.6.0_25,Sun Microsystems Inc.
> 23:00:42,711 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> 23:00:42,711 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 20.0-b11,Sun Microsystems Inc.
> 23:00:42,711 INFO [ServerInfo] OS-System: Windows Server 2008 R2 6.1,x86
> 23:00:42,712 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.security.policy=.\workpoint_client.policy -Xms256m -Xmx1024m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m -Djava.endorsed.dirs=C:\jboss501\jboss-as\lib\endorsed
> 23:00:42,743 INFO [JMXKernel] Legacy JMX core initialized
> 23:00:47,321 INFO [WebService] Using RMI server codebase: http://casiteminder:8083/
> 23:00:53,922 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
> 23:00:53,922 INFO [NativeServerConfig] 3.1.2.SP3_CP01
> 23:00:55,315 INFO [LogNotificationListener] Adding notification listener for logging mbean "jboss.system:service=Logging,type=Log4jService" to server org.jboss.mx.server.MBeanServerImpl@7ab40c[ defaultDomain='jboss' ]
> 23:01:03,520 INFO [MailService] Mail Service bound to java:/Mail
> 23:01:05,726 WARN [JBossASSecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this.
> 23:01:06,634 INFO [TransactionManagerService] JBossTS Transaction Service (JTA version - tag:JBOSSTS_4_6_1_GA_CP04) - JBoss Inc.
> 23:01:06,634 INFO [TransactionManagerService] Setting up property manager MBean and JMX layer
> 23:01:06,828 INFO [TransactionManagerService] Initializing recovery manager
> 23:01:06,938 INFO [TransactionManagerService] Recovery manager configured
> 23:01:06,938 INFO [TransactionManagerService] Binding TransactionManager JNDI Reference
> 23:01:07,019 INFO [TransactionManagerService] Starting transaction recovery manager
> 23:01:07,548 INFO [AprLifecycleListener] The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Java\jdk1.6.0_25\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\SYSTEM32;C:\Windows;C:\Windows\SYSTEM32\WBEM
> 23:01:07,676 ERROR [Http11Protocol] Error initializing endpoint
> java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:8080
> at org.apache.tomcat.util.net.JIoEndpoint.init(JIoEndpoint.java:504)
> at org.apache.coyote.http11.Http11Protocol.init(Http11Protocol.java:175)
> at org.apache.catalina.connector.Connector.initialize(Connector.java:1029)
> at org.apache.catalina.core.StandardService.initialize(StandardService.java:683)
> at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:821)
> at org.jboss.web.tomcat.service.deployers.TomcatService.startService(TomcatService.java:313)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
> at org.jboss.system.ServiceMBeanSupport.pojoStart(ServiceMBeanSupport.java:216)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at org.jboss.system.ServiceController.start(ServiceController.java:460)
> at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:291)
> at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1570)
> at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1535)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:944)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at org.jboss.system.ServiceController.start(ServiceController.java:460)
> at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:291)
> at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1570)
> at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1535)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:944)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
> at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
> at org.jboss.Main.boot(Main.java:221)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:662)
> 23:01:07,679 ERROR [AbstractKernelController] Error installing to Start: name=WebServer state=Create
> LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:8080
> at org.apache.catalina.connector.Connector.initialize(Connector.java:1031)
> at org.apache.catalina.core.StandardService.initialize(StandardService.java:683)
> at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:821)
> at org.jboss.web.tomcat.service.deployers.TomcatService.startService(TomcatService.java:313)
> at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:376)
> at org.jboss.system.ServiceMBeanSupport.pojoStart(ServiceMBeanSupport.java:216)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:243)
> at org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:111)
> at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:72)
> at org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
> at org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
> at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
> at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
> at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at org.jboss.system.ServiceController.start(ServiceController.java:460)
> at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:291)
> at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1570)
> at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1535)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:944)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at org.jboss.system.ServiceController.start(ServiceController.java:460)
> at org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:291)
> at org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1570)
> at org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1535)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:944)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
> at org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
> at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
> at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1440)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1158)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1099)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:823)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:782)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.repository.ProfileDeployAction.install(ProfileDeployAction.java:70)
> at org.jboss.system.server.profileservice.repository.AbstractProfileAction.install(AbstractProfileAction.java:53)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.install(AbstractProfileService.java:403)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1633)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:935)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1083)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:985)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:775)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
> at org.jboss.system.server.profileservice.repository.AbstractProfileService.registerProfile(AbstractProfileService.java:308)
> at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:256)
> at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:461)
> at org.jboss.Main.boot(Main.java:221)
> at org.jboss.Main$1.run(Main.java:556)
> at java.lang.Thread.run(Thread.java:662)
> 23:01:07,738 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss501/jboss-as/server/default/deploy/jboss-local-jdbc.rar/META-INF/ra.xml
> 23:01:07,759 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss501/jboss-as/server/default/deploy/jboss-xa-jdbc.rar/META-INF/ra.xml
> 23:01:07,766 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss501/jboss-as/server/default/deploy/jms-ra.rar/META-INF/ra.xml
> 23:01:07,774 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss501/jboss-as/server/default/deploy/mail-ra.rar/META-INF/ra.xml
> 23:01:07,787 INFO [RARDeployment] Required license terms exist, view vfszip:/C:/jboss501/jboss-as/server/default/deploy/quartz-ra.rar/META-INF/ra.xml
> 23:01:07,858 INFO [SimpleThreadPool] Job execution threads will use class loader of thread: main
> 23:01:07,878 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
> 23:01:07,881 INFO [RAMJobStore] RAMJobStore initialized.
> 23:01:07,881 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzScheduler' initialized from default resource file in Quartz package: 'quartz.properties'
> 23:01:07,882 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
> 23:01:07,884 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED started.
> 23:01:08,757 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
> 23:01:09,117 INFO [ServerPeer] JBoss Messaging 1.4.6.GA server [0] started
> 23:01:09,222 INFO [QueueService] Queue[/queue/ExpiryQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 23:01:09,286 INFO [ConnectionFactory] Connector bisocket://casiteminder:4457 has leasing enabled, lease period 10000 milliseconds
> 23:01:09,286 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@11948f9 started
> 23:01:09,286 INFO [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover
> 23:01:09,286 INFO [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing
> 23:01:09,287 INFO [ConnectionFactory] Connector bisocket://casiteminder:4457 has leasing enabled, lease period 10000 milliseconds
> 23:01:09,287 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@1c20d4 started
> 23:01:09,289 INFO [QueueService] Queue[/queue/DLQ] started, fullSize=200000, pageSize=2000, downCacheSize=2000
> 23:01:09,289 INFO [ConnectionFactory] Connector bisocket://casiteminder:4457 has leasing enabled, lease period 10000 milliseconds
> 23:01:09,289 INFO [ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@17dde5 started
> 23:01:09,504 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
> 23:01:10,214 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@60f77e[domain=default, server=default, name=default]
> 23:01:10,216 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> DEPLOYMENTS MISSING DEPENDENCIES:
> Deployment "jboss.web.deployment:war=/ROOT" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> Deployment "jboss.web.deployment:war=/admin-console" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> Deployment "jboss.web.deployment:war=/invoker" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> Deployment "jboss.web.deployment:war=/jbossws" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> Deployment "jboss.web.deployment:war=/jmx-console" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> Deployment "jboss.web.deployment:war=/web-console" is missing the following dependencies:
> Dependency "jboss.web:service=WebServer" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.web:service=WebServer' **")
> DEPLOYMENTS IN ERROR:
> Deployment "WebServer" is in error due to the following reason(s): LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use: JVM_Bind /0.0.0.0:8080
> Deployment "jboss.web:service=WebServer" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.web:service=WebServer' **
> 23:01:10,217 INFO [ServerImpl] JBoss (Microcontainer) [5.0.1 (build: SVNTag=JBPAPP_5_0_1 date=201003301050)] Started in 30s:665ms
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2680) java:comp/DefaultDataSource doesn't work in persistence.xml
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-2680?page=com.atlassian.jira.plugin.... ]
Stuart Douglas commented on WFLY-2680:
--------------------------------------
The reason why this does not work is because java:comp is scoped to a component, and when dealing with persistence.xml there is no component.
We can probably just hack something in to make this work though, as it would be more user friendly.
> java:comp/DefaultDataSource doesn't work in persistence.xml
> -----------------------------------------------------------
>
> Key: WFLY-2680
> URL: https://issues.jboss.org/browse/WFLY-2680
> Project: WildFly
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: EE, JPA / Hibernate
> Affects Versions: 8.0.0.CR1
> Reporter: arjan tijms
> Assignee: David Lloyd
> Labels: javaee7, jdbc
>
> Having a persistence.xml with the following content fails the deployment on WildFly 8 CR1:
> {code:xml}
> <?xml version="1.0" encoding="UTF-8"?>
> <persistence version="2.1" xmlns="http://xmlns.jcp.org/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/persistence http://xmlns.jcp.org/xml/ns/persistence/persistence_2_1.xsd">
>
> <persistence-unit name="testPU">
> <jta-data-source>java:comp/DefaultDataSource</jta-data-source>
> </persistence-unit>
> </persistence>
> {code}
> It results in the following error:
> {noformat}
> 13:51:40,367 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014613: Operation ("deploy") failed - address: ([("deployment" => "dynamic-named-query.war")]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"dynamic-named-query.war#testPU\".__FIRST_PHASE__ is missing [jboss.naming.context.java.module.dynamic-named-query.dynamic-named-query.DefaultDataSource]"]}
> {noformat}
> When I proposed the feature for the default data source over at the Java EE JIRA (https://java.net/jira/browse/JAVAEE_SPEC-4) I intended this to work. In the description I hinted that the standard JNDI name would be the standard alternative for {{java:jboss/datasources/ExampleDS}} on JBoss. The latter indeed does work in {{persistence.xml}} using WildFly 8 CR1.
> Omitting the {{jta-data-source}} element altogether *does* work, which is great. However, I foresee a lot of users tripping over this in the future and just giving up the idea of using a default data source, especially since the error message is very cryptic for new developers.
> In GlassFish 4 using {{java:comp/DefaultDataSource}} in {{persistence.xml}} does work.
> See also WFLY-2027 and WFLY-2158
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2683) Problem with security subsystem model descriptions
by Stuart Douglas (JIRA)
Stuart Douglas created WFLY-2683:
------------------------------------
Summary: Problem with security subsystem model descriptions
Key: WFLY-2683
URL: https://issues.jboss.org/browse/WFLY-2683
Project: WildFly
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Security
Affects Versions: 8.0.0.CR1
Reporter: Stuart Douglas
Assignee: Darran Lofthouse
/subsystem=security/security-domain=*/acl=*:read-resource-description
results in:
"children" => {
"acl-module" => {
"description" => "ACL module",
"model-description" => undefined
},
"login-module" => {
"description" => "Login module",
"model-description" => undefined
}
}
These model descriptions should not be undefined.
--
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
10 years, 6 months
[JBoss JIRA] (JGRP-1759) BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/JGRP-1759?page=com.atlassian.jira.plugin.... ]
Richard Achmatowicz commented on JGRP-1759:
-------------------------------------------
The debugging output above clearly shows the correct rule being loaded, processed and called.
I can't say for sure where/why the program is being deadlocked; I guess the next step is to run it locally on that machine (the tests are run via Jenkins) and create a thread dump. But, as you know, whenever you use a rendezvous with no timeout, the possibility for deadlock is there.
I was going to suggest to Andrew to create a version of rendezvous which if all threads do not arrive after a specified timeout, performs the thread dump itself as well as listing the threads which did/did not make it to the rendezvous point. That information would have been helpful here.
> BecomeServerTest.testSendingOfMsgsOnUnconnectedChannel deadlocks
> ----------------------------------------------------------------
>
> Key: JGRP-1759
> URL: https://issues.jboss.org/browse/JGRP-1759
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.5
> Environment: Windows 2008, x86_64
> Reporter: Richard Achmatowicz
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.5
>
>
> Running the Byteman tests in the QA lab, this test deadlocks in a repeatable fashion and causes the testsuite to hang.
> The test makes use of the Byteman rendezvous built-in function to suspend (and reorder) thread execution. It appears that with threads re-ordered, certain parts of JGroups block in such a way that no progress is made and the test deadlocks.
> .
--
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
10 years, 6 months
[JBoss JIRA] (JGRP-1749) Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1749?page=com.atlassian.jira.plugin.... ]
Bela Ban resolved JGRP-1749.
----------------------------
Resolution: Done
> Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port
> -------------------------------------------------------------------------------------
>
> Key: JGRP-1749
> URL: https://issues.jboss.org/browse/JGRP-1749
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.2, 3.5
>
>
> If we have
> {code:xml}
> <UDP mcast_addr="${myapp.mcast_addr:235.5.5.5}".../>
> {code}
> , then the default mcast_addr is {{235.5.5.5}}.
> If we set {{-Dmyapp.mcast_addr=238.5.5.5}} but also set {{-Djgroups.udp.mcast_addr=239.5.5.5}}, then *the latter system property always overrides the former*, so we'll use {{239.5.5.5}} as mcast_addr.
> This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.mcast_addr}} and the other {{myapp2.mcast_addr}}. If {{-Djgroups.udp.mcast_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different mcast addresses !
> This means that - if we use the same {{mcast_port}} value - the 2 clusters will see each other's traffic as they use the same {{mcast_addr}}.
> Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this.
> SOLUTION:
> * If a property is set in the XML, either directly or via property substitution (e.g. {{myapp.mcast_addr}}, then use that value
> * If the value is not set and a system property (e.g. {{jgroups.udp.mcast_addr}}) has been set, set the value from that system property
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2682) Conversation identifier does not get incremented
by Adriano Scheffer (JIRA)
[ https://issues.jboss.org/browse/WFLY-2682?page=com.atlassian.jira.plugin.... ]
Adriano Scheffer updated WFLY-2682:
-----------------------------------
Description: The conversation id is not getting incremented when I open another browser tab. Conversely, this problems was not happening in Beta1. (was: The conversation id is not getting incremented when I open another browser tab. Conversally, this problems was not happening in Beta1.)
> Conversation identifier does not get incremented
> ------------------------------------------------
>
> Key: WFLY-2682
> URL: https://issues.jboss.org/browse/WFLY-2682
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: CDI / Weld, JSF
> Affects Versions: 8.0.0.CR1
> Environment: Windows 7
> Reporter: Adriano Scheffer
> Assignee: Stuart Douglas
>
> The conversation id is not getting incremented when I open another browser tab. Conversely, this problems was not happening in Beta1.
--
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
10 years, 6 months
[JBoss JIRA] (JGRP-1749) Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1749?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-1749:
---------------------------
Description:
If we have
{code:xml}
<UDP mcast_addr="${myapp.mcast_addr:235.5.5.5}".../>
{code}
, then the default mcast_addr is {{235.5.5.5}}.
If we set {{-Dmyapp.mcast_addr=238.5.5.5}} but also set {{-Djgroups.udp.mcast_addr=239.5.5.5}}, then *the latter system property always overrides the former*, so we'll use {{239.5.5.5}} as mcast_addr.
This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.mcast_addr}} and the other {{myapp2.mcast_addr}}. If {{-Djgroups.udp.mcast_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different mcast addresses !
This means that - if we use the same {{mcast_port}} value - the 2 clusters will see each other's traffic as they use the same {{mcast_addr}}.
Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this.
SOLUTION:
* If a property is set in the XML, either directly or via property substitution (e.g. {{myapp.mcast_addr}}, then use that value
* If the value is not set and a system property (e.g. {{jgroups.udp.mcast_addr}}) has been set, set the value from that system property
was:
If we have
{code:xml}
<UDP bind_addr="${myapp.bind_addr:127.0.0.1}".../>
{code}
, then the default bind_addr is {{127.0.0.1}}.
If we set {{-Dmyapp.bind_addr=1.2.3.4}} but also set {{-Djgroups.bind_addr=5.6.7.8}}, then *the latter system property always overrides the former*.
This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.bind_addr}} and the other {{myapp2.bind_addr}}. If {{-Djgroups.bind_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different bind addresses !
Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this.
SOLUTION:
* If a property is set in the XML, either directly or via property substitution (e.g. {{myapp.bind_addr}}, then use that value
* If the value is not set and a system property (e.g. {{jgroups.bind_addr}}) has been set, set the value from that system property
> Remove override for jgroups.bind_addr, jgroups.udp.mcast_addr, jgroups.udp.mcast_port
> -------------------------------------------------------------------------------------
>
> Key: JGRP-1749
> URL: https://issues.jboss.org/browse/JGRP-1749
> Project: JGroups
> Issue Type: Task
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 3.4.2, 3.5
>
>
> If we have
> {code:xml}
> <UDP mcast_addr="${myapp.mcast_addr:235.5.5.5}".../>
> {code}
> , then the default mcast_addr is {{235.5.5.5}}.
> If we set {{-Dmyapp.mcast_addr=238.5.5.5}} but also set {{-Djgroups.udp.mcast_addr=239.5.5.5}}, then *the latter system property always overrides the former*, so we'll use {{239.5.5.5}} as mcast_addr.
> This is bad, e.g. when we have multiple channels in the same JVM, where one channel uses {{myapp1.mcast_addr}} and the other {{myapp2.mcast_addr}}. If {{-Djgroups.udp.mcast_addr}} is set (e.g. by JBoss EAP), then we'll always use it rather than the different mcast addresses !
> This means that - if we use the same {{mcast_port}} value - the 2 clusters will see each other's traffic as they use the same {{mcast_addr}}.
> Investigate whether we still need to use those overrides. Contact Brian Stansberry, IIRC he's the one who suggested this.
> SOLUTION:
> * If a property is set in the XML, either directly or via property substitution (e.g. {{myapp.mcast_addr}}, then use that value
> * If the value is not set and a system property (e.g. {{jgroups.udp.mcast_addr}}) has been set, set the value from that system property
--
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
10 years, 6 months
[JBoss JIRA] (WFLY-2107) JASPI custom provider fails with no explicit error message
by Stefan Guilhen (JIRA)
[ https://issues.jboss.org/browse/WFLY-2107?page=com.atlassian.jira.plugin.... ]
Stefan Guilhen resolved WFLY-2107.
----------------------------------
Fix Version/s: 8.0.0.CR1
Resolution: Done
This has been fixed a while ago in PicketBox as part of SECURITY-759
> JASPI custom provider fails with no explicit error message
> ----------------------------------------------------------
>
> Key: WFLY-2107
> URL: https://issues.jboss.org/browse/WFLY-2107
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Security
> Reporter: Derek Horton
> Assignee: Darran Lofthouse
> Fix For: 8.0.0.CR1
>
>
> The JASPI module loading code does not provide a useful error message. The error appears to be generated in org.jboss.security.auth.message.config.JBossServerAuthConfig, but its lost before it makes it into the log file.
> A user can run into this issue when the auth-module class name (the 'code' attribute) is wrong or when a custom auth-module is used and the class loading dependencies are not setup correctly.
> Steps to Reproduce:
> 1. Misspell the auth-module class name
--
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
10 years, 6 months