[jboss-jira] [JBoss JIRA] (WFLY-8247) Unable to send large message if JDBC-persistance-store is used

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil moved JBEAP-9145 to WFLY-8247:
------------------------------------------

              Project: WildFly  (was: JBoss Enterprise Application Platform)
                  Key: WFLY-8247  (was: JBEAP-9145)
             Workflow: GIT Pull Request workflow   (was: CDW with loose statuses v1)
          Component/s: JMS
                           (was: ActiveMQ)
                           (was: JMS)
    Affects Version/s:     (was: 7.1.0.DR8)
                           (was: 7.1.0.DR9)
                           (was: 7.1.0.DR10)
                           (was: 7.1.0.DR11)
                           (was: 7.1.0.DR12)
      Affects Testing:   (was: Blocks Testing)


> Unable to send large message if JDBC-persistance-store is used
> --------------------------------------------------------------
>
>                 Key: WFLY-8247
>                 URL: https://issues.jboss.org/browse/WFLY-8247
>             Project: WildFly
>          Issue Type: Bug
>          Components: JMS
>         Environment: The issue was hit with Oracle 12c database
>            Reporter: Jeff Mesnil
>            Assignee: Martyn Taylor
>            Priority: Blocker
>
> If producer sends large message to EAP with JDBC-persistance store, the following error arises on the server.
> {code}
> 11:49:34,248 ERROR [org.apache.activemq.artemis.core.server] (default I/O-9) AMQ224016: Caught exception: ActiveMQInternalErrorException[errorType=INTERNAL_ERROR message=Invalid conversion requested]
> 	at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.validateFile(LargeServerMessageImpl.java:376)
> 	at org.apache.activemq.artemis.core.persistence.impl.journal.JournalStorageManager.createLargeMessage(JournalStorageManager.java:458)
> 	at org.apache.activemq.artemis.core.server.impl.ServerSessionImpl.sendLarge(ServerSessionImpl.java:1189)
> 	at org.apache.activemq.artemis.core.protocol.core.ServerSessionPacketHandler.handlePacket(ServerSessionPacketHandler.java:436)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:624)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:373)
> 	at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:356)
> 	at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:621)
> 	at org.apache.activemq.artemis.core.remoting.impl.netty.ActiveMQChannelHandler.channelRead(ActiveMQChannelHandler.java:68)
> 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> 	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:277)
> 	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:264)
> 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:292)
> 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:278)
> 	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:962)
> 	at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:435)
> 	at org.xnio.netty.transport.AbstractXnioSocketChannel$ReadListener.handleEvent(AbstractXnioSocketChannel.java:371)
> 	at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> 	at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) [xnio-api-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> 	at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> 	at org.xnio.nio.WorkerThread.run(WorkerThread.java:567) [xnio-nio-3.4.1.Final-redhat-1.jar:3.4.1.Final-redhat-1]
> Caused by: java.sql.SQLException: Invalid conversion requested
> 	at oracle.jdbc.driver.T4CVarcharAccessor.StringToNUMBER(T4CVarcharAccessor.java:832)
> 	at oracle.jdbc.driver.T4CVarcharAccessor.getNUMBER(T4CVarcharAccessor.java:239)
> 	at oracle.jdbc.driver.T4CVarcharAccessor.getInt(T4CVarcharAccessor.java:527)
> 	at oracle.jdbc.driver.GeneratedStatement.getInt(GeneratedStatement.java:217)
> 	at oracle.jdbc.driver.GeneratedScrollableResultSet.getInt(GeneratedScrollableResultSet.java:573)
> 	at org.jboss.jca.adapters.jdbc.WrappedResultSet.getInt(WrappedResultSet.java:1490)
> 	at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFileFactoryDriver.createFile(JDBCSequentialFileFactoryDriver.java:165)
> 	at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFileFactoryDriver.openFile(JDBCSequentialFileFactoryDriver.java:102)
> 	at org.apache.activemq.artemis.jdbc.store.file.JDBCSequentialFile.open(JDBCSequentialFile.java:98)
> 	at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.openFile(LargeServerMessageImpl.java:391)
> 	at org.apache.activemq.artemis.core.persistence.impl.journal.LargeServerMessageImpl.validateFile(LargeServerMessageImpl.java:370)
> 	... 21 more
> Caused by: java.lang.NumberFormatException
> 	at java.math.BigDecimal.<init>(BigDecimal.java:494) [rt.jar:1.8.0_111]
> 	at java.math.BigDecimal.<init>(BigDecimal.java:383) [rt.jar:1.8.0_111]
> 	at java.math.BigDecimal.<init>(BigDecimal.java:806) [rt.jar:1.8.0_111]
> 	at oracle.jdbc.driver.T4CVarcharAccessor.StringToNUMBER(T4CVarcharAccessor.java:825)
> 	... 31 more
> {code}
> *Customer impact*: Clients are not able to send large messages. Sending/receiving large messages is common customer use case. This blocks RFE EAP7-591.
> There is no workaround. 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)