[JBoss JIRA] (AS7-3995) make add-users.sh/bat script have domain directory location a parameter
by Nicholas DiPiazza (JIRA)
Nicholas DiPiazza created AS7-3995:
--------------------------------------
Summary: make add-users.sh/bat script have domain directory location a parameter
Key: AS7-3995
URL: https://issues.jboss.org/browse/AS7-3995
Project: Application Server 7
Issue Type: Feature Request
Components: ConfigAdmin
Affects Versions: 7.1.0.Final
Environment: all
Reporter: Nicholas DiPiazza
Assignee: Thomas Diesler
Priority: Minor
add-users.sh / add-users.bat hard codes the location of the domains directory.
Would be very useful for some deployments if this were optional so that the domain could be in a different directory.
So...
org.jboss.as.domain.management.security.AddPropertiesUser
private boolean findFiles(final String jbossHome, final List<File> foundFiles, final String fileName) {
File standaloneProps = new File(jbossHome + "/standalone/configuration/" + fileName);
if (standaloneProps.exists()) {
foundFiles.add(standaloneProps);
}
File domainProps = new File(jbossHome + "/domain/configuration/" + fileName);
if (domainProps.exists()) {
foundFiles.add(domainProps);
}
Could become:
private boolean findFiles(final String jbossHome, final List<File> foundFiles, final String fileName) {
File standaloneProps = new File(jbossHome + "/standalone/configuration/" + fileName);
if (standaloneProps.exists()) {
foundFiles.add(standaloneProps);
}
File domainProps = new File((DOMAIN_ROOT_DIRECTORY == NULL ? jbossHome : DOMAIN_ROOT_DIRECTORY)+ "/domain/configuration/" + fileName);
if (domainProps.exists()) {
foundFiles.add(domainProps);
}
--
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, 12 months
[JBoss JIRA] (AS7-4442) Errors in AS7-Infinispan during failover test
by rang s (JIRA)
rang s created AS7-4442:
---------------------------
Summary: Errors in AS7-Infinispan during failover test
Key: AS7-4442
URL: https://issues.jboss.org/browse/AS7-4442
Project: Application Server 7
Issue Type: Bug
Components: Clustering
Affects Versions: 7.1.1.Final
Environment: Windows7
Reporter: rang s
Assignee: Paul Ferraro
I am using a local cache and a remote store. Have deployed a distributable web app. I get the following errors on each of the server instance console during a failover
[Server:server-one] 17:23:14,015 ERROR [org.apache.catalina.core.ContainerBase] (MSC service thread 1-6) ContainerBase.setManager: start: : LifecycleException: JBAS018
072: Unable to start manager: java.lang.ClassCastException: org.infinispan.remoting.transport.jgroups.JGroupsAddress cannot be cast to java.lang.String
[Server:server-one] at org.jboss.as.web.session.DistributableSessionManager.start(DistributableSessionManager.java:205) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:459) [jbossweb-7.0.13.Final.jar:]
[Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:250) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:169) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:417) [jbossweb-7.0.13.Final.jar:]
[Server:server-one] at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:182) [jbossweb-7.0.13.Final.jar:]
[Server:server-one] at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:162) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.0.13.Final.jar:]
[Server:server-one] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3790) [jbossweb-7.0.13.Final.jar:]
[Server:server-one] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:90) [jboss-as-web-7.1.1.Final.jar:7.1.1.Final]
[Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
[Server:server-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]
[Server:server-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]
[Server:server-one] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
[Server:server-one]
--
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
[JBoss JIRA] Created: (AS7-1375) UnsupportedDataTypeException sending email
by Tomáš Remeš (JIRA)
UnsupportedDataTypeException sending email
-------------------------------------------
Key: AS7-1375
URL: https://issues.jboss.org/browse/AS7-1375
Project: Application Server 7
Issue Type: Bug
Environment: jdk-u26, jboss-as-7.1.0.Alpha1-SNAPSHOT(07/22/2011)
Reporter: Tomáš Remeš
Seam 3 send mail example fails on:
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
boundary="----=_Part_1_340486764.1311336438303"
at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:905) [activation-1.1.1.jar:1.1.1]
at javax.activation.DataHandler.writeTo(DataHandler.java:330) [activation-1.1.1.jar:1.1.1]
at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) [mail-1.4.4.jar:1.4.4]
at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) [mail-1.4.4.jar:1.4.4]
at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099) [mail-1.4.4.jar:1.4.4]
... 42 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] (AS7-3281) Add a "force" attribute to CLI add operations to allow existing resources to be transparently recreated
by Robert Reimann (JIRA)
Robert Reimann created AS7-3281:
-----------------------------------
Summary: Add a "force" attribute to CLI add operations to allow existing resources to be transparently recreated
Key: AS7-3281
URL: https://issues.jboss.org/browse/AS7-3281
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.0.CR1b
Reporter: Robert Reimann
Assignee: Alexey Loubyansky
To allow for repeatable CLI script executions (e.g. in case of a missconfiguration like wrong IP or DB-Password provided) conditional logic is required to prevent "Duplicate resource" failures. These logic is typically contained in a wrapper script (shell script or another scripting language).
Pseudocode:
{code}
exists = test if the resource to be (re-)added already exists
if (exists) remove resource
add resource
{code}
Adding a "force" or "override" attribute to the add operation (which recreates the resources transparently if necessary) would remove the need for conditional logic and additional wrapper scripts.
A simple example, assuming that the logger to be added already exists:
{code}
/subsystem=logging/logger=com.arjuna:add(level=TRACE, force=true)
{code}
In such a case the existing logger should be removed and recreated with the new properties provided.
--
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
[JBoss JIRA] (AS7-2656) Unable to deploy jsf2.0 application in as7.1.0 alpha2
by Juergen Hoffmann (Created) (JIRA)
Unable to deploy jsf2.0 application in as7.1.0 alpha2
-----------------------------------------------------
Key: AS7-2656
URL: https://issues.jboss.org/browse/AS7-2656
Project: Application Server 7
Issue Type: Bug
Components: JSF
Affects Versions: 7.1.0.Alpha1
Environment: EAP6 Alpha2
Reporter: Juergen Hoffmann
Assignee: Stan Silvert
When deploying an Applicatin that brings its own JSF Implementation, JBoss reads the correct jars after providing jboss-deployment-structure.xml but the AnnotationProvider fails to initialize with a NoSuchMethodException. I believe that it is related to this post: http://community.jboss.org/message/621225
09:52:20,870 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Mojarra 2.0.3 (FCS b03) für Kontext '/frameevolution-admin' wird initialisiert.
09:52:22,495 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/jsf-impl-2.0.3-FCS.jar/com/sun/faces/jsf-ri-runtime.xml
09:52:22,495 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/frame-ui-web-layout-9.0.0-20111109.013036-36.jar/META-INF/faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [31ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/jsf-facelets-1.1.15.jar/META-INF/faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/richfaces-impl-jsf2-3.3.3.Final.jar/META-INF/faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/richfaces-impl-jsf2-3.3.3.Final.jar/META-INF/ajax-context.faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/richfaces-ui-3.3.3.Final.jar/META-INF/faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse vfs:/D:/apps/jboss-eap-6.0/standalone/deployments/frameevolution-sf-ear.ear/frameevolution-sf-admin-web.war/WEB-INF/lib/spring-faces-2.1.1.RELEASE.jar/META-INF/faces-config.xml
09:52:22,526 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : Parse jndi:/default-host/frameevolution-admin/WEB-INF/faces-config.xml
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Starting sort pass number 1...
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Comparing ,
09:52:22,542 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [0ms] : "faces-config" document sorting complete in 1.
09:52:22,557 FEIN [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-4) java.lang.NoSuchMethodException: org.jboss.as.web.deployment.jsf.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider): java.lang.NoSuchMethodException: org.jboss.as.web.deployment.jsf.JandexAnnotationProvider.<init>(javax.servlet.ServletContext, com.sun.faces.spi.AnnotationProvider)
at java.lang.Class.getConstructor0(Class.java:2706) [:1.6.0_24]
at java.lang.Class.getDeclaredConstructor(Class.java:1985) [:1.6.0_24]
at com.sun.faces.spi.ServiceFactoryUtils.getProviderFromEntry(ServiceFactory.java:79) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:66) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:746) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:324) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) [jsf-impl-2.0.3-FCS.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
09:52:22,557 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Unsanitized stacktrace from failed start...: javax.faces.FacesException: Class org.jboss.as.web.deployment.jsf.JandexAnnotationProvider is not an instance of com.sun.faces.spi.AnnotationProvider
at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:74) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:746) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:324) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) [jsf-impl-2.0.3-FCS.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
09:52:22,557 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Mojarra (2.0.3 (FCS b03)) für Kontext ''{0}'' wurde initialisiert.
09:52:22,557 FEIN [javax.enterprise.resource.webcontainer.jsf.timing] (MSC service thread 1-4) [TIMING] - [1734ms] : Initialization of context /frameevolution-admin
09:52:22,557 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/frameevolution-admin]] (MSC service thread 1-4) Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener: com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Class org.jboss.as.web.deployment.jsf.JandexAnnotationProvider is not an instance of com.sun.faces.spi.AnnotationProvider
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) [jsf-impl-2.0.3-FCS.jar:]
at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
Caused by: javax.faces.FacesException: Class org.jboss.as.web.deployment.jsf.JandexAnnotationProvider is not an instance of com.sun.faces.spi.AnnotationProvider
at com.sun.faces.spi.AnnotationProviderFactory.createAnnotationProvider(AnnotationProviderFactory.java:74) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager$AnnotationScanTask.<init>(ConfigManager.java:746) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:324) [jsf-impl-2.0.3-FCS.jar:]
... 9 more
09:52:22,557 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart
09:52:22,557 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/frameevolution-admin] startup failed due to previous errors
09:52:22,557 DEBUG [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/frameevolution-admin]] (MSC service thread 1-4) Stopping filters
09:52:22,557 DEBUG [org.apache.catalina.session.ManagerBase] (MSC service thread 1-4) Unloading persisted sessions
09:52:22,557 DEBUG [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Sending application stop events
09:52:22,557 FEIN [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) ConfigureListener.contextDestroyed(frameevolution-sf-admin-web)
09:52:22,557 SCHWERWIEGEND [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Unexpected exception when attempting to tear down the Mojarra runtime: java.lang.IllegalStateException: Die Anwendung wurde bei Systemstart nicht einwandfrei initialisiert, Factory konnte nicht gefunden werden: javax.faces.application.ApplicationFactory
at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:800) [jsf-api-2.0.3-FCS.jar:]
at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:302) [jsf-api-2.0.3-FCS.jar:]
at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:104) [jsf-impl-2.0.3-FCS.jar:]
at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:312) [jsf-impl-2.0.3-FCS.jar:]
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3489) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3999) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.apache.catalina.core.StandardContext.start(StandardContext.java:3917) [jbossweb-7.0.3.Final-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.Alpha1-redhat-1.jar:7.1.0.Alpha1-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
09:52:22,557 INFO [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/frameevolution-admin]] (MSC service thread 1-4) Closing Spring root WebApplicationContext
--
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
[JBoss JIRA] (JBREM-1302) Can't invoke remote object if server bind address is 0.0.0.0
by Sergey Chernov (Created) (JIRA)
Can't invoke remote object if server bind address is 0.0.0.0
------------------------------------------------------------
Key: JBREM-1302
URL: https://issues.jboss.org/browse/JBREM-1302
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: transport
Affects Versions: 2.5.4.SP2
Environment: Jboss 5.1.0 jdk 1.6 jboss remoting 2.5.4.SP2
Reporter: Sergey Chernov
When jboss bind address is set to `0.0.0.0` remote client gets exception while trying to invoke remote object's method:
java.rmi.ConnectException: Connection refused to host: lx4-schernov.nn.five9.com; nested exception is:
java.net.ConnectException: Connection refused: connect
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
at org.jboss.remoting.transport.rmi.RMIServerInvoker_Stub.transport(Unknown Source)
at org.jboss.remoting.transport.rmi.RMIClientInvoker.callTransport(RMIClientInvoker.java:648)
at org.jboss.remoting.transport.rmi.RMIClientInvoker.access$100(RMIClientInvoker.java:78)
at org.jboss.remoting.transport.rmi.RMIClientInvoker$1.run(RMIClientInvoker.java:402)
at org.jboss.util.threadpool.RunnableTaskWrapper.run(RunnableTaskWrapper.java:147)
at org.jboss.util.threadpool.BasicThreadPool.executeOnThread(BasicThreadPool.java:473)
at org.jboss.util.threadpool.BasicThreadPool.runTaskWrapper(BasicThreadPool.java:201)
at org.jboss.remoting.transport.rmi.RMIClientInvoker.transport(RMIClientInvoker.java:420)
at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:169)
at org.jboss.remoting.Client.invoke(Client.java:2070)
at org.jboss.remoting.Client.invoke(Client.java:879)
at org.jboss.remoting.Client.invoke(Client.java:867)
at org.jboss.remoting.transporter.TransporterClient.invoke(TransporterClient.java:479)
at $Proxy0.getMySumHost(Unknown Source)
at test.Main.main(Main.java:45)
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:193)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at java.net.Socket.connect(Socket.java:475)
at java.net.Socket.<init>(Socket.java:372)
at java.net.Socket.<init>(Socket.java:186)
at javax.net.DefaultSocketFactory.createSocket(SocketFactory.java:206)
at org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory.createSocketPrivate(RemotingRMIClientSocketFactory.java:333)
at org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory.createSocket(RemotingRMIClientSocketFactory.java:210)
at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
... 18 more
It happens because RemotingRMIClientSocketFactory had been created with wrong ('0.0.0.0') host name which becomes effective host while creating socket:
log:
328 [main] TRACE org.jboss.remoting.transport.rmi.RemotingRMIClientSocketFactory - host: lx4-schernov.nn.five9.com, effective host: 0.0.0.0, port: 47952
source:
public Socket createSocket(String host, final int port) throws IOException
176 {
...
181 final String effectiveHost = hostName != null ? hostName : host;
While creating factory it should be checked, that host name is not broadcast or localhost address, to make client's locatorUri mandatory for such cases.
Client source code:
String address = "remote.host.com";
Properties props = new Properties();
props.put(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
props.put(InitialContext.PROVIDER_URL, "jnp://" + address + ":1099");
props.put(InitialContext.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");
InitialContext context = new InitialContext(props);
Object tmp = context.lookup("remote/subsystem/Object");
ObjectInf object = (ObjectInf) tmp;
object.doJob(); // here exception it thrown
--
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