[JBoss JIRA] (AS7-6664) Unable to turn on/off logging handlers using enable()/disable() in CLI
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/AS7-6664?page=com.atlassian.jira.plugin.s... ]
James Perkins commented on AS7-6664:
------------------------------------
Closed PR to incorporate into a better change set.
> Unable to turn on/off logging handlers using enable()/disable() in CLI
> ----------------------------------------------------------------------
>
> Key: AS7-6664
> URL: https://issues.jboss.org/browse/AS7-6664
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, Logging
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Brian Stansberry
> Assignee: James Perkins
> Fix For: 8.0.0.Alpha1
>
>
> Peter Kremens reports:
> I am unable to use enable/disable operation in logging handlers.
>
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Calling disable() won't affect enabled attribute
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:disable()
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => true,
> ...
> }
> }
> {code}
> Must use write-attribute instead
> {code}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE/:write-attribute(name=enabled, value=false)
> {"outcome" => "success"}
> [standalone@localhost:9999 /] /subsystem=logging/console-handler=CONSOLE:read-resource
> {
> "outcome" => "success",
> "result" => {
> "autoflush" => true,
> "enabled" => false,
> ...
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (DROOLS-75) Eclipse IDE Debugger doesn't work for java dialect and named consequences
by Mario Fusco (JIRA)
Mario Fusco created DROOLS-75:
---------------------------------
Summary: Eclipse IDE Debugger doesn't work for java dialect and named consequences
Key: DROOLS-75
URL: https://issues.jboss.org/browse/DROOLS-75
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 5.5
Reporter: Mario Fusco
Assignee: Mario Fusco
Eclipse IDE Debugger works only in mvel dialect.
For what regards Java dialect the problem is caused by the random name of Java classes implementing consequences (see DialectUtil.getUniqueLegalName).
Also the named consequences are still not supported.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6216) Some javax.* bundles show version 0.0.0 in AS7
by Shelly McGowan (JIRA)
[ https://issues.jboss.org/browse/AS7-6216?page=com.atlassian.jira.plugin.s... ]
Shelly McGowan commented on AS7-6216:
-------------------------------------
The recent updates for JAX-RS 2.0 API (JBEE-131) includes OSGi metadata:
https://github.com/jboss/jboss-jaxrs-api_spec/blob/master/pom.xml
> Some javax.* bundles show version 0.0.0 in AS7
> ----------------------------------------------
>
> Key: AS7-6216
> URL: https://issues.jboss.org/browse/AS7-6216
> Project: Application Server 7
> Issue Type: Bug
> Components: OSGi
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Reporter: Thomas Diesler
> Assignee: Cheng Fang
> Fix For: 8.0.0.Alpha1
>
>
> Some javax bundles that we configure by default do not show valid bundle version info
> javax.jws.api:0.0.0
> javax.ws.rs.api:0.0.0
> The javax.persistence.api has its metadata defined in jbosgi-xservice.properties like this
> {code}
> Bundle-SymbolicName: hibernate-jpa-2.0-api
> Bundle-Version: 1.0.1.Final
> Export-Package: javax.persistence.spi;version="2.0.0",javax.persistence.criteria;version="2.0.0",javax.persistence;version="2.0.0",javax.persistence.metamodel;version="2.0.0"
> {code}
> This should be replaced by metadata coming from the artefacts manifest.
> Generally, all javax api artefacts should have valid OSGi metadata
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
by Alexey S. (JIRA)
[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ]
Alexey S. commented on AS7-6624:
--------------------------------
:) great. What is a connection between subscription and the bug in community version? Listen you can say: if you don't have a subscription do not open the bugs. That's an acceptable point of view (but very strange). But this is NOT what you said. You said "prove it". We proved. Why you reject the bug?
I dont think such policy is contributing much to the companies and individuals which wants to use JBoss, and I am very glad everybody reads our discussion
> Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
> ---------------------------------------------------------------------
>
> Key: AS7-6624
> URL: https://issues.jboss.org/browse/AS7-6624
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Alexey S.
> Assignee: Stefano Maestri
>
> I am using JPA Hibernate in Timer EJB.
> After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
> my datasource is
> <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
> <xa-datasource-property name="ServerName">
> localhost
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> db
> </xa-datasource-property>
> <xa-datasource-property name="User">
> root
> </xa-datasource-property>
> <xa-datasource-property name="Password">
> xxxxx
> </xa-datasource-property>
> <xa-datasource-property name="AutoReconnectForPools">
> true
> </xa-datasource-property>
> <xa-datasource-property name="FailOverReadOnly">
> false
> </xa-datasource-property>
> <xa-datasource-property name="MaxReconnects">
> 100
> </xa-datasource-property>
> <xa-datasource-property name="ReconnectAtTxEnd">
> true
> </xa-datasource-property>
> <driver>com.mysql</driver>
> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
> </validation>
> </xa-datasource>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
by Jesper Pedersen (JIRA)
[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ]
Jesper Pedersen closed AS7-6624.
--------------------------------
Resolution: Rejected
Buy a subscription
> Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
> ---------------------------------------------------------------------
>
> Key: AS7-6624
> URL: https://issues.jboss.org/browse/AS7-6624
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Alexey S.
> Assignee: Stefano Maestri
>
> I am using JPA Hibernate in Timer EJB.
> After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
> my datasource is
> <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
> <xa-datasource-property name="ServerName">
> localhost
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> db
> </xa-datasource-property>
> <xa-datasource-property name="User">
> root
> </xa-datasource-property>
> <xa-datasource-property name="Password">
> xxxxx
> </xa-datasource-property>
> <xa-datasource-property name="AutoReconnectForPools">
> true
> </xa-datasource-property>
> <xa-datasource-property name="FailOverReadOnly">
> false
> </xa-datasource-property>
> <xa-datasource-property name="MaxReconnects">
> 100
> </xa-datasource-property>
> <xa-datasource-property name="ReconnectAtTxEnd">
> true
> </xa-datasource-property>
> <driver>com.mysql</driver>
> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
> </validation>
> </xa-datasource>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
by Alexey S. (JIRA)
[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ]
Alexey S. commented on AS7-6624:
--------------------------------
Hello again.
We provided in https://community.jboss.org/message/801760 the detailed test case, including code, EAR archive, configuration etc.
During two week we didn't get any proof that the mess was in our side, misconfiguration etc.
Therefor we consider it as full evidence of the fact that this is a critical issue in Jboss 7.1.1.
We'll be glad to provide any other infos, codes, test cases etc, but we think that this bug should be reopened.
Best Regards,
Alexey
> Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
> ---------------------------------------------------------------------
>
> Key: AS7-6624
> URL: https://issues.jboss.org/browse/AS7-6624
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Alexey S.
> Assignee: Stefano Maestri
>
> I am using JPA Hibernate in Timer EJB.
> After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
> my datasource is
> <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
> <xa-datasource-property name="ServerName">
> localhost
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> db
> </xa-datasource-property>
> <xa-datasource-property name="User">
> root
> </xa-datasource-property>
> <xa-datasource-property name="Password">
> xxxxx
> </xa-datasource-property>
> <xa-datasource-property name="AutoReconnectForPools">
> true
> </xa-datasource-property>
> <xa-datasource-property name="FailOverReadOnly">
> false
> </xa-datasource-property>
> <xa-datasource-property name="MaxReconnects">
> 100
> </xa-datasource-property>
> <xa-datasource-property name="ReconnectAtTxEnd">
> true
> </xa-datasource-property>
> <driver>com.mysql</driver>
> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
> </validation>
> </xa-datasource>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6624) Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
by Alexey S. (JIRA)
[ https://issues.jboss.org/browse/AS7-6624?page=com.atlassian.jira.plugin.s... ]
Alexey S. reopened AS7-6624:
----------------------------
Hello again.
We provided in https://community.jboss.org/message/801760 the detailed test case, including code, EAR archive, configuration etc.
During two week we didn't get any proof that the mess was in our side, misconfiguration etc.
Therefor we consider it as full evidence of the fact that this is a critical issue in Jboss 7.1.1.
We'll be glad to provide any other infos, codes, test cases etc, but we think that this bug should be reopened.
Best Regards,
Alexey
> Jboss connection pool is not auto reconnects to mySQl (XA-datasource)
> ---------------------------------------------------------------------
>
> Key: AS7-6624
> URL: https://issues.jboss.org/browse/AS7-6624
> Project: Application Server 7
> Issue Type: Bug
> Components: JCA
> Affects Versions: 7.1.1.Final
> Reporter: Alexey S.
> Assignee: Stefano Maestri
>
> I am using JPA Hibernate in Timer EJB.
> After MySQL's restarted, JBOSS connection pool should be restarted also to renew the transaction, but it doesnt happened.
> my datasource is
> <xa-datasource jndi-name="java:jboss/datasources/db" pool-name="db" enabled="true" use-java-context="true">
> <xa-datasource-property name="ServerName">
> localhost
> </xa-datasource-property>
> <xa-datasource-property name="DatabaseName">
> db
> </xa-datasource-property>
> <xa-datasource-property name="User">
> root
> </xa-datasource-property>
> <xa-datasource-property name="Password">
> xxxxx
> </xa-datasource-property>
> <xa-datasource-property name="AutoReconnectForPools">
> true
> </xa-datasource-property>
> <xa-datasource-property name="FailOverReadOnly">
> false
> </xa-datasource-property>
> <xa-datasource-property name="MaxReconnects">
> 100
> </xa-datasource-property>
> <xa-datasource-property name="ReconnectAtTxEnd">
> true
> </xa-datasource-property>
> <driver>com.mysql</driver>
> <transaction-isolation>TRANSACTION_READ_COMMITTED</transaction-isolation>
> <validation>
> <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLValidConnectionChecker"/>
> <check-valid-connection-sql>select 1</check-valid-connection-sql>
> <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.mysql.MySQLExceptionSorter"/>
> </validation>
> </xa-datasource>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (DROOLS-25) Cannot unmarshall large session file: InvalidProtocolBufferException
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-25?page=com.atlassian.jira.plugin.... ]
Edson Tirelli resolved DROOLS-25.
---------------------------------
Assignee: Edson Tirelli (was: Mark Proctor)
Fix Version/s: 5.6
6.0.0.Alpha1
Resolution: Done
Thank you for reporting and providing the patch. We discussed the problem and decided it was not worth keeping it as an option, since for small sessions, the overhead of reading the stream into a byte[] is small anyway, and for large sessions it only works that way. We changed your patch to always preload the content into the byte[].
> Cannot unmarshall large session file: InvalidProtocolBufferException
> --------------------------------------------------------------------
>
> Key: DROOLS-25
> URL: https://issues.jboss.org/browse/DROOLS-25
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Environment: Jdk 7
> Reporter: Magnus Vojbacke
> Assignee: Edson Tirelli
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> When trying to unmarshall a large knowledge session from a file stream, an exception is thrown.
> It seems that there is a default message size limit in Protobuf (used by Drools marshalling). Apparently, what happens is that the marshalled "Header" message exceeds this size, which causes Protobuf to throw this exception.
> I suspect that the Header field "payload" is the culprit, since it seems to contain the rest of the knowledge base in byte array form.
> Here's the stack trace:
> {code:title=Stacktrace}
> com.google.protobuf.InvalidProtocolBufferException: Protocol message was too large. May be malicious. Use CodedInputStream.setSizeLimit() to increase the size limit.
> at com.google.protobuf.InvalidProtocolBufferException.sizeLimitExceeded:89
> at com.google.protobuf.CodedInputStream.refillBuffer:720
> at com.google.protobuf.CodedInputStream.isAtEnd:666
> at com.google.protobuf.CodedInputStream.readTag:99
> at org.drools.marshalling.impl.ProtobufMessages$Header$Builder.mergeFrom:967
> at org.drools.marshalling.impl.ProtobufMessages$Header$Builder.mergeFrom:773
> at com.google.protobuf.AbstractMessageLite$Builder.mergeFrom:212
> at com.google.protobuf.AbstractMessage$Builder.mergeFrom:746
> at org.drools.marshalling.impl.ProtobufMessages$Header.parseFrom:724
> at org.drools.marshalling.impl.PersisterHelper.readFromStreamWithHeader:234
> at org.drools.marshalling.impl.ProtobufInputMarshaller.loadAndParseSession:217
> at org.drools.marshalling.impl.ProtobufInputMarshaller.readSession:107
> at org.drools.marshalling.impl.ProtobufMarshaller.unmarshall:143
> {code}
> Suggested solutions:
> #1
> You can set the size limit of the Protobuf CodedInputStream, but there doesn't seem to be any way of providing this parameter to the Drools unmarshalling API.
> #2
> When you unmarshall from a byte array, Protobuf does not enforce any message size limit. I have successfully implemented a patch in drools-core that preloads the file into memory and unmarshalls from a byte array. Probably the least desirable fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (DROOLS-25) Cannot unmarshall large session file: InvalidProtocolBufferException
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-25?page=com.atlassian.jira.plugin.... ]
Edson Tirelli closed DROOLS-25.
-------------------------------
> Cannot unmarshall large session file: InvalidProtocolBufferException
> --------------------------------------------------------------------
>
> Key: DROOLS-25
> URL: https://issues.jboss.org/browse/DROOLS-25
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5
> Environment: Jdk 7
> Reporter: Magnus Vojbacke
> Assignee: Edson Tirelli
> Fix For: 5.6, 6.0.0.Alpha1
>
>
> When trying to unmarshall a large knowledge session from a file stream, an exception is thrown.
> It seems that there is a default message size limit in Protobuf (used by Drools marshalling). Apparently, what happens is that the marshalled "Header" message exceeds this size, which causes Protobuf to throw this exception.
> I suspect that the Header field "payload" is the culprit, since it seems to contain the rest of the knowledge base in byte array form.
> Here's the stack trace:
> {code:title=Stacktrace}
> com.google.protobuf.InvalidProtocolBufferException: Protocol message was too large. May be malicious. Use CodedInputStream.setSizeLimit() to increase the size limit.
> at com.google.protobuf.InvalidProtocolBufferException.sizeLimitExceeded:89
> at com.google.protobuf.CodedInputStream.refillBuffer:720
> at com.google.protobuf.CodedInputStream.isAtEnd:666
> at com.google.protobuf.CodedInputStream.readTag:99
> at org.drools.marshalling.impl.ProtobufMessages$Header$Builder.mergeFrom:967
> at org.drools.marshalling.impl.ProtobufMessages$Header$Builder.mergeFrom:773
> at com.google.protobuf.AbstractMessageLite$Builder.mergeFrom:212
> at com.google.protobuf.AbstractMessage$Builder.mergeFrom:746
> at org.drools.marshalling.impl.ProtobufMessages$Header.parseFrom:724
> at org.drools.marshalling.impl.PersisterHelper.readFromStreamWithHeader:234
> at org.drools.marshalling.impl.ProtobufInputMarshaller.loadAndParseSession:217
> at org.drools.marshalling.impl.ProtobufInputMarshaller.readSession:107
> at org.drools.marshalling.impl.ProtobufMarshaller.unmarshall:143
> {code}
> Suggested solutions:
> #1
> You can set the size limit of the Protobuf CodedInputStream, but there doesn't seem to be any way of providing this parameter to the Drools unmarshalling API.
> #2
> When you unmarshall from a byte array, Protobuf does not enforce any message size limit. I have successfully implemented a patch in drools-core that preloads the file into memory and unmarshalls from a byte array. Probably the least desirable fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months