[JBoss JIRA] Created: (JBAS-4735) Upon Shutdown connectors should be stopped before applications are undeployed
by Dominik Pospisil (JIRA)
Upon Shutdown connectors should be stopped before applications are undeployed
-----------------------------------------------------------------------------
Key: JBAS-4735
URL: http://jira.jboss.com/jira/browse/JBAS-4735
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-4.2.1.GA
Reporter: Dominik Pospisil
Assigned To: Brian Stansberry
In clustered environment the process of shutting down single AS instance should be transparent to clients. This is not the case since applications are udeployed at first while connectors are still servicing requests. This causes clients not to be redirected to another cluster nodes and to receive resource not avaiable exceptions.
>From the client perspective, shutdown process should should work like follows:
1) stop connectors so they refuse servicing new requests
2) complete running requests
3) undeploy applications
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBAS-5799) HAJNDI lookup clarification
by Galder Zamarreno (JIRA)
HAJNDI lookup clarification
---------------------------
Key: JBAS-5799
URL: https://jira.jboss.org/jira/browse/JBAS-5799
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR1
Reporter: Galder Zamarreno
Assignee: Samson Kittoli
In AS documentation, in the clustering section, it says:
"For clients running inside the application server.
If you want to access HA-JNDI from inside the application server, you must explicitly get an InitialContext
by passing in JNDI properties. The following code shows how to create a naming Context bound to HA-JNDI:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces");
p.put(Context.PROVIDER_URL, "localhost:1100"); // HA-JNDI port.
return new InitialContext(p); "
As explained in http://wiki.jboss.org/auth/wiki/JBossHAJNDIUseCluster I think this section below should
appended to the comment above.
"However, this does not work in all cases, especially when running a multi-homed cluster (several JBoss
instances on one machine bound to different IPs). A safer method is not to specify the Context.PROVIDER_URL
(which does not work in all scenarios) but the partition name property:
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
p.put(Context.URL_PKG_PREFIXES, "jboss.naming:org.jnp.interfaces");
p.put("jnp.partitionName", "DefaultPartition"); // partition name.
return new InitialContext(p); "
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBAS-5698) Add RmiBindAddress to HANamingServiceMBean documentation
by Paul Ferraro (JIRA)
Add RmiBindAddress to HANamingServiceMBean documentation
--------------------------------------------------------
Key: JBAS-5698
URL: http://jira.jboss.com/jira/browse/JBAS-5698
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: JBossAS-5.0.0.CR2
Reporter: Paul Ferraro
Assigned To: Samson Kittoli
Previously, HANamingServiceMBean.bindAddress served two functions:
>From trunk/cluster/src/etc/hajndi-service.xml:
<!-- Bind address of bootstrap and HA-JNDI RMI endpoints -->
<attribute name="BindAddress">${jboss.bind.address}</attribute>
The bootstrap and HA-JNDI RMI endpoints are now defined separately:
<!-- Bind address of bootstrap endpoint -->
<attribute name="BindAddress">${jboss.bind.address}</attribute>
<!-- Bind address of the HA-JNDI RMI endpoint -->
<attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
They each default to the same value.
Users may want to override the RMI bind address if deployed on a multi-homed machine, and want to use an specific network interface for HA-JNDI RMI calls.
This ability already exists in the standard NamingService.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBAS-6222) "javax.xml.bind.MarshalException: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR" error occurs when attempting to update a Topic or Queue via ManagementView.updateComponent()
by Ian Springer (JIRA)
"javax.xml.bind.MarshalException: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR" error occurs when attempting to update a Topic or Queue via ManagementView.updateComponent()
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBAS-6222
URL: https://jira.jboss.org/jira/browse/JBAS-6222
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: ProfileService
Reporter: Ian Springer
Assignee: Scott M Stark
Here's the full stack trace:
javax.xml.bind.MarshalException - with linked exception: [org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it.] at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:328) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:254) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:83) at org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer.saveAttachment(JAXBAttachmentSerializer.java:61) at org.jboss.system.server.profileservice.repository.AbstractFileAttachmentsSerializer.saveAttachment(AbstractFileAttachmentsSerializer.java:90) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.saveAttachmentMetaData(AbstractAttachmentStore.java:398) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.updateDeployment(AbstractAttachmentStore.java:316) at org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository.updateDeployment(SerializableDeploymentRepository.java:1068) at org.jboss.system.server.profile.repository.ProfileImpl.updateDeployment(ProfileImpl.java:152) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1019) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:623) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:67) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.JndiResourceComponent.updateResourceConfiguration(JndiResourceComponent.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:623) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:450) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:713) Caused by: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it. at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:242) at com.sun.xml.bind.v2.runtime.XMLSerializer.reportError(XMLSerializer.java:257) at com.sun.xml.bind.v2.runtime.reflect.AdaptedLister$ListIteratorImpl.next(AdaptedLister.java:111) at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:135) at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:152) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:322) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:589) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:312) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490) at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:254) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:83) at org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer.saveAttachment(JAXBAttachmentSerializer.java:61) at org.jboss.system.server.profileservice.repository.AbstractFileAttachmentsSerializer.saveAttachment(AbstractFileAttachmentsSerializer.java:90) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.saveAttachmentMetaData(AbstractAttachmentStore.java:398) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.updateDeployment(AbstractAttachmentStore.java:316) at org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository.updateDeployment(SerializableDeploymentRepository.java:1068) at org.jboss.system.server.profile.repository.ProfileImpl.updateDeployment(ProfileImpl.java:152) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1019) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:623) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:67) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.remoting.MergeMetaDataInterceptor.invoke(MergeMetaDataInterceptor.java:74) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) at AOPProxy$1.updateComponent(AOPProxy$1.java) at org.rhq.plugins.jbossas5.JndiResourceComponent.updateResourceConfiguration(JndiResourceComponent.java:138) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:623) at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:450) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:713) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) ... 17 more Caused by: org.w3c.dom.DOMException: WRONG_DOCUMENT_ERR: A node is used in a different document than the one that created it. at org.apache.xerces.dom.ParentNode.internalInsertBefore(Unknown Source) at org.apache.xerces.dom.ParentNode.insertBefore(Unknown Source) at org.apache.xerces.dom.NodeImpl.appendChild(Unknown Source) at org.jboss.system.metadata.ServiceMetaData2ElementConverter.addAttributes(ServiceMetaData2ElementConverter.java:277) at org.jboss.system.metadata.ServiceMetaData2ElementConverter.createServiceMetaDataElement(ServiceMetaData2ElementConverter.java:76) at org.jboss.system.metadata.ServiceMetaDataAdapter.marshal(ServiceMetaDataAdapter.java:60) at org.jboss.system.metadata.ServiceMetaDataAdapter.marshal(ServiceMetaDataAdapter.java:37) at com.sun.xml.bind.v2.runtime.reflect.AdaptedLister$ListIteratorImpl.next(AdaptedLister.java:109) at com.sun.xml.bind.v2.runtime.property.ArrayElementProperty.serializeListBody(ArrayElementProperty.java:135) at com.sun.xml.bind.v2.runtime.property.ArrayERProperty.serializeBody(ArrayERProperty.java:152) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeBody(ClassBeanInfoImpl.java:322) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsSoleContent(XMLSerializer.java:589) at com.sun.xml.bind.v2.runtime.ClassBeanInfoImpl.serializeRoot(ClassBeanInfoImpl.java:312) at com.sun.xml.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:490) at com.sun.xml.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:325) at com.sun.xml.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:254) at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:83) at org.jboss.system.server.profileservice.repository.JAXBAttachmentSerializer.saveAttachment(JAXBAttachmentSerializer.java:61) at org.jboss.system.server.profileservice.repository.AbstractFileAttachmentsSerializer.saveAttachment(AbstractFileAttachmentsSerializer.java:90) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.saveAttachmentMetaData(AbstractAttachmentStore.java:398) at org.jboss.system.server.profileservice.repository.AbstractAttachmentStore.updateDeployment(AbstractAttachmentStore.java:316) at org.jboss.system.server.profileservice.repository.SerializableDeploymentRepository.updateDeployment(SerializableDeploymentRepository.java:1068) at org.jboss.system.server.profile.repository.ProfileImpl.updateDeployment(ProfileImpl.java:152) at org.jboss.profileservice.management.ManagementViewImpl.updateComponent(ManagementViewImpl.java:1019) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:623) at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:121) at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) at org.jboss.profileservice.remoting.ProfileServiceInvocationHandler.invoke(ProfileServiceInvocationHandler.java:67) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908) at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:106) at org.jboss.remoting.Client.invoke(Client.java:1708) at org.jboss.remoting.Client.invoke(Client.java:612) at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) ... 17 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months