[JBoss JIRA] (AS7-4473) Appclient: "JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete" in console
by Wolfgang Knauf (JIRA)
Wolfgang Knauf created AS7-4473:
-----------------------------------
Summary: Appclient: "JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete" in console
Key: AS7-4473
URL: https://issues.jboss.org/browse/AS7-4473
Project: Application Server 7
Issue Type: Bug
Components: Application Client
Affects Versions: 7.1.1.Final
Environment: JBoss 7.1.2 snapshot of 2012-04-10, Windows XP64, Sun Java 1.6.0_31
Reporter: Wolfgang Knauf
Assignee: Stuart Douglas
Priority: Minor
I tried to run the sample attached to the 7th reply in the linked forum thread, using "appclient.bat" (which was made functionable in snapshot of 2012-04-10).
Everything works fine, but in the console output, I see this exception:
20:52:17,156 ERROR [org.jboss.as.appclient.logging] JBAS013202: Error closing connection: java.io.InterruptedIOException: Interrupted while waiting for close to complete
at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:180) [jboss-remoting-3.2.4.GA.jar:3.2.4.GA]
at org.jboss.as.appclient.service.LazyConnectionContextSelector.close(LazyConnectionContextSelector.java:88) [jboss-as-appclient-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at org.jboss.as.appclient.service.ApplicationClientStartService$1.run(ApplicationClientStartService.java:148) [jboss-as-appclient-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
at java.lang.Thread.run(Unknown Source) [rt.jar:1.6.0_31]
Attached is the full console output of the appclient run.
--
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, 2 months
[JBoss JIRA] (AS7-4434) CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4434?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-4434:
---------------------------------------
Stefano, can you make this one a priority?
> CLONE - It's impossible to add more than 1 custom workmanager to JCA subsystem
> ------------------------------------------------------------------------------
>
> Key: AS7-4434
> URL: https://issues.jboss.org/browse/AS7-4434
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JCA
> Affects Versions: 7.1.1.Final
> Reporter: Vladimir Rastseluev
> Assignee: Stefano Maestri
> Fix For: 7.1.2.Final-redhat1
>
>
> 09:45:35,526 ERROR [org.jboss.as.server] JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.server.ServerService.boot(ServerService.java:266) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:155) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_23]
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[200,13]
> Message: JBAS014789: Unexpected element '{urn:jboss:domain:jca:1.1}workmanager' encountered
> at org.jboss.as.controller.parsing.ParseUtils.unexpectedElement(ParseUtils.java:85) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:311)
> at org.jboss.as.connector.subsystems.jca.JcaExtension$ConnectorSubsystemParser.readElement(JcaExtension.java:176)
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:897) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_1(StandaloneXml.java:332) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:128) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:100) [jboss-as-server-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
> at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.1.2.Final-SNAPSHOT.jar:7.1.2.Final-SNAPSHOT]
> ... 3 more
--
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, 2 months
[JBoss JIRA] (AS7-4475) Fix error handling in the helloworld-jms quickstart
by Farah Juma (JIRA)
Farah Juma created AS7-4475:
-------------------------------
Summary: Fix error handling in the helloworld-jms quickstart
Key: AS7-4475
URL: https://issues.jboss.org/browse/AS7-4475
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final
Reporter: Farah Juma
When building the helloworld-jms quickstart without having created an application user, the call to
connection = connectionFactory.createConnection();
fails with the error:
{code}
Apr 11, 2012 9:25:15 AM org.jboss.as.quickstarts.jms.HelloWorldJMSClient
main
SEVERE: Unable to validate user: null
{code}
The server log shows:
{code}
09:25:15,186 ERROR
[org.hornetq.core.protocol.core.impl.HornetQPacketHandler] (Old I/O
server worker (parentId: 213209572, [id: 0x0cb551e4, /127.0.0.1:5445]))
Failed to create session : HornetQException[errorCode=105 message=Unable
to validate user: null]
at
org.hornetq.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:147)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.server.impl.HornetQServerImpl.createSession(HornetQServerImpl.java:807)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handleCreateSession(HornetQPacketHandler.java:187)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.protocol.core.impl.HornetQPacketHandler.handlePacket(HornetQPacketHandler.java:85)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:508)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:556)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:517)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:533)
[hornetq-core-2.2.13.Final.jar:]
at
org.hornetq.core.remoting.impl.netty.HornetQChannelHandler.messageReceived(HornetQChannelHandler.java:73)
[hornetq-core-2.2.13.Final.jar:]
...
{code}
To run this quickstart, an application user needs to be created first. However, when a user hasn't been created, the quickstart still displays a BUILD SUCCESS even though that's not true. The exception is caught and the SEVERE message is logged but the messages were never sent nor received. The quickstart should be rewritten so that it succeeds only if the messages that were sent are effectively received.
--
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, 2 months