[JBoss JIRA] (GTNPORTAL-2960) Unable to determine Dialect to use [name=EnterpriseDB, majorVersion=9] - for PostgresPlus 9.2
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2960?page=com.atlassian.jira.pl... ]
RH Bugzilla Integration commented on GTNPORTAL-2960:
----------------------------------------------------
Boleslaw Dawidowicz <bdawidow(a)redhat.com> changed the Status of [bug 975374|https://bugzilla.redhat.com/show_bug.cgi?id=975374] from ASSIGNED to CLOSED
> Unable to determine Dialect to use [name=EnterpriseDB, majorVersion=9] - for PostgresPlus 9.2
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2960
> URL: https://issues.jboss.org/browse/GTNPORTAL-2960
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta02
> Environment: PostgresPlus 9.2 (EnterpriseDB)
> edb-jdbc14.jar
> Reporter: Tomas Kyjovsky
> Labels: JPP61-Test-dev
> Attachments: hibernate-exception.txt
>
>
> Hibernate DialectFactory cannot determine "hibernate.dialect" for PostgresPlus 9.2 (EnterpriseDB).
> ...
> org.hibernate.HibernateException: Unable to determine Dialect to use [name=EnterpriseDB, majorVersion=9]; user must register resolver or explicitly set 'hibernate.dialect'
> at org.hibernate.service.jdbc.dialect.internal.DialectFactoryImpl.determineDialect(DialectFactoryImpl.java:105) [hibernate-core-4.1.6.Final.jar:4.1.6.Final]
> at
> ...
--
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
12 years, 4 months
[JBoss JIRA] (GTNMGMT-59) CLI: Users from default portal container are able to log into other portal containers
by Nick Scavelli (JIRA)
[ https://issues.jboss.org/browse/GTNMGMT-59?page=com.atlassian.jira.plugin... ]
Nick Scavelli resolved GTNMGMT-59.
----------------------------------
Fix Version/s: 2.0.1.Final
Resolution: Done
Couple of changes to mgmt connect:
- mgmt connect command now accepts user and password as optional arguments.
- mgmt connect will now prompt for password if user or container options are specified and differ from previous/default values.
> CLI: Users from default portal container are able to log into other portal containers
> -------------------------------------------------------------------------------------
>
> Key: GTNMGMT-59
> URL: https://issues.jboss.org/browse/GTNMGMT-59
> Project: GateIn Management
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: cli
> Affects Versions: 2.0.0.CR01
> Environment: gatein-portal-quickstarst 3.6.0.Final-qs4-SNAPSHOT from 2013-06-27
> Reporter: Tomas Kyjovsky
> Assignee: Nick Scavelli
> Fix For: 2.0.1.Final
>
>
> In scenarios with multiple portal containers (e.g. with sample-portal deployed) users from the default /portal container are able to log into other containers.
--
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
12 years, 4 months
[JBoss JIRA] (GTNPORTAL-3160) JGroups warnings at startup of JPP 6.1 ER2
by Boleslaw Dawidowicz (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3160?page=com.atlassian.jira.pl... ]
Boleslaw Dawidowicz updated GTNPORTAL-3160:
-------------------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> JGroups warnings at startup of JPP 6.1 ER2
> ------------------------------------------
>
> Key: GTNPORTAL-3160
> URL: https://issues.jboss.org/browse/GTNPORTAL-3160
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Reporter: Marek Posolda
> Assignee: Marek Posolda
> Fix For: 3.7.0.Final
>
>
> There are some warnings at startup of "./standalone.xml -c standalone-ha.xml" like:
> 11:01:09,635 WARN [org.jgroups.stack.Configurator] (MSC service thread 1-3) [JGRP00013] TP.discard_incompatible_packets has been deprecated: incompatible packets are discarded anyway
> 11:01:09,647 WARN [org.jgroups.stack.Configurator] (MSC service thread 1-3) [JGRP00013] UNICAST2.setTimeout has been deprecated: not used anymore
> This is due to JGroups version upgrade in EAP 6.1. Configuration could be improved and synced with the defaults for EAP 6.1.
--
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
12 years, 4 months