[JBoss JIRA] (AS7-5555) NullPointerException at org.hibernate.hql.internal.ast.HqlSqlWalker.createFromJoinElement(HqlSqlWalker.java:393)
by Ondrej Zizka (JIRA)
Ondrej Zizka created AS7-5555:
---------------------------------
Summary: NullPointerException at org.hibernate.hql.internal.ast.HqlSqlWalker.createFromJoinElement(HqlSqlWalker.java:393)
Key: AS7-5555
URL: https://issues.jboss.org/browse/AS7-5555
Project: Application Server 7
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 7.1.2.Final (EAP)
Reporter: Ondrej Zizka
Assignee: Scott Marlow
A query
{code}
{code}
on a simple entity causes a NPEx:
{code}
Caused by: java.lang.NullPointerException
at org.hibernate.hql.internal.ast.HqlSqlWalker.createFromJoinElement(HqlSqlWalker.java:393) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.joinElement(HqlSqlBaseWalker.java:3516) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElement(HqlSqlBaseWalker.java:3302) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromElementList(HqlSqlBaseWalker.java:3180) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.fromClause(HqlSqlBaseWalker.java:706) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:562) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:299) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:247) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:248) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.hql.internal.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:105) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.engine.query.spi.HQLQueryPlan.<init>(HQLQueryPlan.java:80) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.engine.query.spi.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:168) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.internal.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:219) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.internal.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:197) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.internal.SessionImpl.createQuery(SessionImpl.java:1736) [hibernate-core-4.1.5.SP1.jar:4.1.5.SP1]
at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:291) [hibernate-entitymanager-4.1.5.SP1.jar:4.1.5.SP1]
at org.jboss.as.jpa.container.AbstractEntityManager.createQuery(AbstractEntityManager.java:425) [jboss-as-jpa-7.1.2.Final.jar:7.1.2.Final]
{code}
I'm filling this here since in Hibernate jira NPEx are ignored, whereas for AS 7 / EAP 6 we agreed that NPEx is not a good way to let user know that something's wrong.
--
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, 11 months
[JBoss JIRA] (AS7-5607) DataSourceEnable does not handle rollback
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5607:
-------------------------------------
Summary: DataSourceEnable does not handle rollback
Key: AS7-5607
URL: https://issues.jboss.org/browse/AS7-5607
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, JCA
Affects Versions: 7.1.3.Final (EAP)
Reporter: Brian Stansberry
Assignee: Stefano Maestri
The runtime execution handling does not revert the service changes it made in case of rollback:
public void execute(OperationContext context, ModelNode operation) throws OperationFailedException {
ServiceVerificationHandler verificationHandler = new ServiceVerificationHandler();
addServices(context, operation, verificationHandler, model, isXa());
context.addStep(verificationHandler, Stage.VERIFY);
context.completeStep();
--
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, 11 months
[JBoss JIRA] (AS7-5387) The CLI jconsole integration should be optional
by Darran Lofthouse (JIRA)
Darran Lofthouse created AS7-5387:
-------------------------------------
Summary: The CLI jconsole integration should be optional
Key: AS7-5387
URL: https://issues.jboss.org/browse/AS7-5387
Project: Application Server 7
Issue Type: Task
Components: CLI, JMX
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
When connecting jconsole to a remote JVM using Remoting the CLI integration should be optional and silently fail if not available.
At the moment killing a jconsole that does not have access to domain management the following stack is logged: -
Exception in thread "AWT-EventQueue-0" java.lang.RuntimeException: Error connecting to JBoss AS.
at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:79)
at sun.tools.jconsole.VMPanel.createPluginTabs(VMPanel.java:641)
at sun.tools.jconsole.VMPanel.propertyChange(VMPanel.java:315)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:339)
at javax.swing.event.SwingPropertyChangeSupport.firePropertyChange(SwingPropertyChangeSupport.java:75)
at javax.swing.event.SwingPropertyChangeSupport$1.run(SwingPropertyChangeSupport.java:80)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:646)
at java.awt.EventQueue.access$000(EventQueue.java:84)
at java.awt.EventQueue$1.run(EventQueue.java:607)
at java.awt.EventQueue$1.run(EventQueue.java:605)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:87)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:616)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
Caused by: java.util.concurrent.CancellationException: Operation was cancelled
at org.xnio.AbstractIoFuture.get(AbstractIoFuture.java:159)
at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectUsingRemoting(JConsoleCLIPlugin.java:118)
at org.jboss.as.cli.gui.JConsoleCLIPlugin.connectCommandContext(JConsoleCLIPlugin.java:98)
at org.jboss.as.cli.gui.JConsoleCLIPlugin.getTabs(JConsoleCLIPlugin.java:76)
... 19 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
13 years, 11 months
[JBoss JIRA] (SECURITY-698) command line utility to generate hashed passwords
by Tom Fonteyne (JIRA)
Tom Fonteyne created SECURITY-698:
-------------------------------------
Summary: command line utility to generate hashed passwords
Key: SECURITY-698
URL: https://issues.jboss.org/browse/SECURITY-698
Project: PicketBox
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: JBossSX
Affects Versions: JBossSecurity_2.0.4.SP8
Reporter: Tom Fonteyne
Assignee: Anil Saldhana
Priority: Trivial
org/ jboss/ security/ auth/ spi/ UsernamePasswordLoginModule.java supports "hashAlgorithm" setting to allow encrypted passwords to be used.
Current options to generate the passwords is with:
echo -n <password> | openssl dgst -md5 -binary | openssl base64
or with:
org.jboss.crypto.CryptoUtil:
String hashedPassword = CryptoUtil.createPasswordHash("MD5", CryptoUtil.BASE64_ENCODING, null, null, password);
It would be nice if we added a little class with a main method that taked the encoding + the password and generates the hashed password.
--
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, 11 months
[JBoss JIRA] (JBRULES-3517) Combining custom operators with OR results in compile error
by Stathis Rouvas (JIRA)
Stathis Rouvas created JBRULES-3517:
---------------------------------------
Summary: Combining custom operators with OR results in compile error
Key: JBRULES-3517
URL: https://issues.jboss.org/browse/JBRULES-3517
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler (expert)
Affects Versions: 5.4.0.Final
Environment: Drools.5.4.0
Java.1.6
Linux
Reporter: Stathis Rouvas
Assignee: Mark Proctor
I recently migrated from Drools.5.0.1 to Drools.5.4.0 and I am having issues when combining constraints with OR when custom operators are involved.
For example, the following rule:
rule "r548695.1"
no-loop true
dialect "mvel"
when
gnId : GN()
la : t547147( )
v1717 : Tra48( gnId.gNo==gNo , name F_str[startsWith] la.c547148 || postCode F_str[contains] la.c547149 )
then
System.out.println("Rule r548695.1 fired");
end
results in the following exception:
Unable to Analyse Expression gnId.gNo == gNo && ( F_str0.evaluate( name, la.c547148 ) || F_str1.evaluate( postCode, la.c547149 ) ):
[Error: unable to resolve method using strict-mode: my.package.rulez.Tra48.F_str0()]
[Near : {... gNo == gNo && ( F_str0.evaluate( name, la.c54 ....}]
^ : [Rule name='r548695.1']
Please note, that the same rule using AND (&&) between the custom operators compiles OK.
The above rule had not problem whatsoever in Drools.5.0.1.
--
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
13 years, 11 months
[JBoss JIRA] (AS7-5582) JDK ORB Subsystem
by Dimitris Andreadis (JIRA)
Dimitris Andreadis created AS7-5582:
---------------------------------------
Summary: JDK ORB Subsystem
Key: AS7-5582
URL: https://issues.jboss.org/browse/AS7-5582
Project: Application Server 7
Issue Type: Feature Request
Components: IIOP
Reporter: Dimitris Andreadis
Assignee: Stefan Guilhen
Implement a JDK ORB subsystem that can act as a replacement for the JacORB subsystem.
AFAIK, most/all JDK ORBs are based on the Sun ORB.
Ideally the 2 ORBs (JDK & JacORB) would be both supported in case we need to go through a transition period, or we need to support a particular interop scenario for which interop communication has issues.
--
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, 11 months
[JBoss JIRA] (JGRP-1516) JGroups not forming cluster between two linux machines
by Balamurali L (JIRA)
Balamurali L created JGRP-1516:
----------------------------------
Summary: JGroups not forming cluster between two linux machines
Key: JGRP-1516
URL: https://issues.jboss.org/browse/JGRP-1516
Project: JGroups
Issue Type: Bug
Affects Versions: 3.0.14
Environment: Node 1 : Fedora release 14 (Laughlin) (32 bit) + java version "1.6.0_33"
Node 2:- Red Hat Enterprise Linux Server release 6.0 (Santiago) (64 bit) + java version "1.6.0_33"
Reporter: Balamurali L
Assignee: Bela Ban
Priority: Minor
Between linux and windows the sample woks fine.
I used bind_addr for this also firwall disabled.
When new member join,viewAccepted() will be invoked.
In between two linux ,am also using this configuration ,but not forming cluster.(not invoking viewAccepted()).Here also firwall disabled.
McastReceiverTest and McastSenderTest works fine also i tried -Djgroups.bind_port=8801 -Djava.net.preferIPv4Stack=true.But not forming cluster.
I am running two jgroup channel as below in two linux machines.
Node 1 :-
java -Djgroups.bind_addr=192.168.1.119 -cp ./jgroups-3.0.14.Final.jar:./$JAVA_HOME: SimpleChat
public class SimpleChat extends ReceiverAdapter {
JChannel channel;
String user_name=System.getProperty("user.name", "n/a");
final List<String> state=new LinkedList<String>();
public void viewAccepted(View new_view) {
System.out.println("This is from @ADMIN@ ** view: " + new_view);
}
channel=new JChannel();
channel.setReceiver(this);
channel.connect("ChatCluster");
channel.getState(null, 10000);
Node 2 :
java -Djgroups.bind_addr=192.168.1.119 -cp ./jgroups-3.0.14.Final.jar:./$JAVA_HOME: SimpleChat1
channel=new JChannel();
channel.connect("ChatCluster");
in log :-
dmin-PC-38687: dropped message 6 from root-57050 (sender not in table [admin-PC-38687, localhost-53705]), view=[admin-PC-38687|1] [admin-PC-38687, localhost-53705]
--
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, 11 months