[JBoss JIRA] (AS7-4060) Remote Naming throws org.jboss.remoting3.NotOpenException: Writes closed
by Richard Opalka (JIRA)
Richard Opalka created AS7-4060:
-----------------------------------
Summary: Remote Naming throws org.jboss.remoting3.NotOpenException: Writes closed
Key: AS7-4060
URL: https://issues.jboss.org/browse/AS7-4060
Project: Application Server 7
Issue Type: Bug
Components: Naming
Reporter: Richard Opalka
Assignee: Stuart Douglas
Fix For: 7.1.1.Final
I'm getting the following exception with jboss-remote-naming master :(
( commit id https://github.com/jbossas/jboss-remote-naming/commit/57f0a3cdccd8f35e7db... )
{code}
java.rmi.RemoteException: Call invocation failed; nested exception is:
javax.xml.rpc.JAXRPCException: javax.naming.NamingException: Failed to lookup [Root exception is org.jboss.remoting3.NotOpenException: Writes closed]
at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:549)
at org.jboss.ws.core.jaxrpc.client.CallImpl.invoke(CallImpl.java:289)
at org.jboss.ws.core.jaxrpc.client.PortProxy.invoke(PortProxy.java:157)
at $Proxy3.helloEnvEntry(Unknown Source)
at org.jboss.test.ws.jaxrpc.enventry.EnvEntryEJBTestCase.testEndpoint(EnvEntryEJBTestCase.java:71)
Caused by: javax.xml.rpc.JAXRPCException: javax.naming.NamingException: Failed to lookup [Root exception is org.jboss.remoting3.NotOpenException: Writes closed]
at org.jboss.test.ws.jaxrpc.enventry.EnvEntryHandler.handleRequestAndResponse(EnvEntryHandler.java:99)
at org.jboss.test.ws.jaxrpc.enventry.EnvEntryHandler.handleResponse(EnvEntryHandler.java:61)
at org.jboss.ws.core.jaxrpc.handler.HandlerWrapper.handleResponse(HandlerWrapper.java:144)
at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleResponseInternal(HandlerChainBaseImpl.java:377)
at org.jboss.ws.core.jaxrpc.handler.HandlerChainBaseImpl.handleResponse(HandlerChainBaseImpl.java:343)
at org.jboss.ws.core.jaxrpc.client.CallImpl.callResponseHandlerChain(CallImpl.java:575)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:409)
at org.jboss.ws.core.jaxrpc.client.CallImpl.invokeInternal(CallImpl.java:530)
... 36 more
Caused by: javax.naming.NamingException: Failed to lookup [Root exception is org.jboss.remoting3.NotOpenException: Writes closed]
at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)
at org.jboss.naming.remote.protocol.v1.Protocol$1.execute(Protocol.java:101)
at org.jboss.naming.remote.protocol.v1.RemoteNamingStoreV1.lookup(RemoteNamingStoreV1.java:76)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:77)
at org.jboss.naming.remote.client.RemoteContext.lookup(RemoteContext.java:81)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at org.jboss.test.ws.jaxrpc.enventry.EnvEntryHandler.handleRequestAndResponse(EnvEntryHandler.java:82)
... 43 more
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:73)
... 48 more
{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
14 years, 1 month
[JBoss JIRA] (AS7-4086) domain.sh fails to start processes in cygwin
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created AS7-4086:
--------------------------------------
Summary: domain.sh fails to start processes in cygwin
Key: AS7-4086
URL: https://issues.jboss.org/browse/AS7-4086
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.0.Final
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 7.1.1.Final
The problem is file system paths. The boot java process is started correctly from the domain.sh using JAVA path.
The same JAVA path is passed as a command line argument (jvm and default-jvm) to start other java processes from the running JVM.
Those attempts will fail with an invalid path error.
So, in case of cygwin, the values for jvm and default-jvm have to translated into the absolute paths.
Note, this can't be done to the JAVA path that starts the original JVM, it'll fail to start.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-3871) $JBOSS_CONFIG_DIR not switched to Windows format when running standalone.sh on Cygwin
by Rune Flobakk (JIRA)
Rune Flobakk created AS7-3871:
---------------------------------
Summary: $JBOSS_CONFIG_DIR not switched to Windows format when running standalone.sh on Cygwin
Key: AS7-3871
URL: https://issues.jboss.org/browse/AS7-3871
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Environment: Windows 7, Cygwin
Reporter: Rune Flobakk
Assignee: Alexey Loubyansky
Paths which are fed to the JVM as parameters are switched to Windows format using cygpath, but $JAVA_CONFIG_DIR seems to have been forgotten. This results in an error during bootup:
{quote}
Unable to read the logging configuration from 'file:/cygdrive/c/apps/jboss-7.1.0.Final/standalone/configuration/logging.properties'
(java.io.FileNotFoundException: \cygdrive\c\apps\jboss-7.1.0.Final\standalone\configuration\logging.properties (The system cannot find the path specified))
{quote}
Fix:
This line needs to be inserted after line 157 in standalone.sh (inside the {{if $cygwin}} block)
{quote}
JBOSS_CONFIG_DIR=`cygpath --path --windows "$JBOSS_CONFIG_DIR"`
{quote}
The same bug seems to be the case for domain.sh.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (AS7-1561) <distributable> web applications fail to deploy with the DOMAIN HA configuration
by Riccardo Pasquini (JIRA)
<distributable> web applications fail to deploy with the DOMAIN HA configuration
--------------------------------------------------------------------------------
Key: AS7-1561
URL: https://issues.jboss.org/browse/AS7-1561
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.0.0.Final, 7.1.0.Alpha1
Environment: riccardo@7suse:~> uname -a
Linux 7suse.localhost 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
riccardo@7suse:~> java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02, mixed mode)
Reporter: Riccardo Pasquini
Assignee: Remy Maucherat
Using the console to deploy a web application packaged as WAR and described as <distributable /> fails on enabling in the server group with the following message:
Failed to disable Webapp-0.1-SNAPSHOT.war.
Unexpected HTTP response: 500
Request
{
"address" => [
("server-group" => "dragon-standalone"),
("deployment" => "Webapp-0.1-SNAPSHOT.war")
],
"operation" => "deploy"
}
Response
Internal Server Error
{
"outcome" => "failed",
"result" => {"server-groups" => [("dragon-standalone" => {"master" => {
"host" => "master",
"response" => {
"outcome" => "failed",
"failure-description" => "Operation handler failed to complete",
"rolled-back" => true
}
}})]},
"failure-description" => "Operation failed or was rolled back on all servers.",
"rolled-back" => true
}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month