[JBoss JIRA] (AS7-4508) Auto reconnect for remote-naming
by Yves Peter (JIRA)
Yves Peter created AS7-4508:
-------------------------------
Summary: Auto reconnect for remote-naming
Key: AS7-4508
URL: https://issues.jboss.org/browse/AS7-4508
Project: Application Server 7
Issue Type: Feature Request
Components: Naming, Remoting
Affects Versions: 7.1.1.Final
Reporter: Yves Peter
Assignee: John Bailey
After restarting a JBoss 7 Server all remote jndi clients should automatically and transparently reconnect to the the server.
At the moment, trying to look something up after a restart throws this error:
Caused by: org.jboss.remoting3.NotOpenException: Writes closed
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:107)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.naming.remote.protocol.v1.WriteUtil.write(WriteUtil.java:59)
at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:76)
... 16 more
See forum threat for details.
--
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, 9 months
[JBoss JIRA] (AS7-2597) Cannot use same binding name in resource-ref
by Thomas Diesler (Created) (JIRA)
Cannot use same binding name in resource-ref
---------------------------------------------
Key: AS7-2597
URL: https://issues.jboss.org/browse/AS7-2597
Project: Application Server 7
Issue Type: Bug
Components: Naming
Reporter: Thomas Diesler
Assignee: John Bailey
Fix For: 7.1.0.CR1
Using this mapping (as the TCK does)
{code}
<jboss-web>
<resource-ref>
<res-ref-name>eis/JAXR</res-ref-name>
<jndi-name>eis/JAXR</jndi-name>
</resource-ref>
</jboss-web>
{code}
I get
{code}
17:56:29,921 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.deployment.unit."jaxr-connection-test.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxr-connection-test.war".INSTALL: Failed to process phase INSTALL of deployment "jaxr-connection-test.war"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
Caused by: org.jboss.msc.service.CircularDependencyException: Service jboss-as has a circular dependency
at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:617) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceContainerImpl.detectCircularity(ServiceContainerImpl.java:588) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:562) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:201) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2211) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:307) [jboss-msc-1.0.1.GA.jar:1.0.1.GA]
at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.addJndiBinding(ModuleJndiBindingProcessor.java:212)
at org.jboss.as.ee.component.deployers.ModuleJndiBindingProcessor.deploy(ModuleJndiBindingProcessor.java:103)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.1.0.Alpha2-SNAPSHOT.jar:7.1.0.Alpha2-SNAPSHOT]
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (AS7-3601) Component context not available on spawned threads
by Johannes Odland (JIRA)
Johannes Odland created AS7-3601:
------------------------------------
Summary: Component context not available on spawned threads
Key: AS7-3601
URL: https://issues.jboss.org/browse/AS7-3601
Project: Application Server 7
Issue Type: Bug
Components: Naming
Affects Versions: 7.1.0.CR1b
Reporter: Johannes Odland
Assignee: John Bailey
When a request is processed, the JavaNamespaceSetup pushes an InjectedEENamespaceContextSelector onto a ThreadLocalStack, making the app and component contexts available for lookups through InitialContext().lookup().
As a result, the application and component contexts are only available on the same thread as the request, and not on threads spawned by the application itself.
Many applications, such as Solr, spawns its own threads for doing asynchronous processing. These are not able to access the JNDI component context (java:comp/env/).
Perhaps one should use InheritableThreadLocal to store the selector instead?
--
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, 9 months
[JBoss JIRA] (AS7-4553) Error during VFS get virtual file
by Zhang Lan (JIRA)
Zhang Lan created AS7-4553:
------------------------------
Summary: Error during VFS get virtual file
Key: AS7-4553
URL: https://issues.jboss.org/browse/AS7-4553
Project: Application Server 7
Issue Type: Bug
Components: VFS
Affects Versions: 7.1.0.Final
Reporter: Zhang Lan
Assignee: John Bailey
I have a jar file ,in which have "seam.properties" to load the seam components in it.
I put the jar file as a module.
But I got the following error when I start jboss.
java.lang.IllegalArgumentException: Null path
at org.jboss.vfs.VFS.getChild(VFS.java:187) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFS.getChild(VFS.java:173) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.vfs.VFS.getChild(VFS.java:154) [jboss-vfs-3.1.0.Final.jar:3.1.0.Final]
at org.jboss.seam.integration.jbossas.vfs.VFSScanner.getRoot(VFSScanner.java:36) [jboss-seam-int.jar:6.0.0.GA]
VFS.java:187 is following source.
return getChild(uri.getPath());
But in my case ,the uri pattern is create by org.jboss.modules.JarFileResourceLoader#getJarURI use the following method.
return new URI("jar", b.toString(), null);
It is the [scheme:]scheme-specific-part[#fragment] pattern 's URI.it's path is null.
So when I change the VFS.java:187 to the following ,my problem is ok.IT's a bug?
public static VirtualFile getChild(URI uri) {
if(uri.getPath() != null){
return getChild(uri.getPath());
}else{
return getChild(uri.getSchemeSpecificPart());
}
}
--
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, 9 months
[JBoss JIRA] (AS7-2939) jar references in tmp/vfs consuming file handles
by Nicklas Karlsson (Created) (JIRA)
jar references in tmp/vfs consuming file handles
------------------------------------------------
Key: AS7-2939
URL: https://issues.jboss.org/browse/AS7-2939
Project: Application Server 7
Issue Type: Bug
Components: VFS
Affects Versions: 7.1.0.Beta1
Reporter: Nicklas Karlsson
Assignee: John Bailey
I see deployments in standalone/tmp/vfs/deployment1bdffd9028e55f79 that keep reference to multiple instances of the jars like
joda-time-1.6.2.jar-38f02aa25a811ed4
joda-time-1.6.2.jar-74d1519d59ff978d
joda-time-1.6.2.jar-b197315704b17d7
joda-time-1.6.2.jar-bc1bb40870af7097
3-4 of each jar and they all consume a file handle on OS level. Are they all needed?
all in all, the AS takes up around 1000 file handles on 4 deployed applications, causing out of file handles-errors if more applications are deployed without raising the limits.
--
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, 9 months