[JBoss JIRA] Created: (JBJCA-484) make *.sh execute permission on in release package
by Jeff Zhang (JIRA)
make *.sh execute permission on in release package
--------------------------------------------------
Key: JBJCA-484
URL: https://issues.jboss.org/browse/JBJCA-484
Project: IronJacamar
Issue Type: Task
Components: Build
Affects Versions: 1.0.0.Beta3
Reporter: Jeff Zhang
Assignee: Jeff Zhang
svn/jbossas/projects/jboss-jca/trunk/build/ironjacamar-1.0.0.Beta4$ find . -name *sh | xargs ls -l
-rw-r--r-- 1 jizhang jizhang 1562 2010-12-29 11:23 ./bin/run.sh
-rw-r--r-- 1 jizhang jizhang 52 2010-12-29 11:23 ./doc/codegenerator/codegenerator.sh
-rw-r--r-- 1 jizhang jizhang 462 2010-12-29 11:23 ./doc/validator/validator.sh
go to
-rwxr-xr-x
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JGRP-1252) TCP Gossip Discovery Issue
by Grahame Rogers (JIRA)
TCP Gossip Discovery Issue
--------------------------
Key: JGRP-1252
URL: https://jira.jboss.org/browse/JGRP-1252
Project: JGroups
Issue Type: Bug
Affects Versions: 2.11
Environment: Windows XP and Solaris 5.10
Reporter: Grahame Rogers
Assignee: Bela Ban
Fix For: 2.11.1
I run the chat demo app that was shipped with an older version of Jgroups. Using tcp transport, with tcpgossip for discovery I start up 2 instances of the chat application. I then restart the gossip server and also another instance of the chat application. The 3rd instance of the chat application receives a view update (membershipListener.viewAccepted) only the logical name of one of the 2 previous instances of the chat client is incorrect. I have detailed the results in: http://old.nabble.com/TCPGossip-Discovery-Issue-td30227966.html
I will attach the test client to this bug report.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months
[JBoss JIRA] Created: (JBMDR-74) scanning-deployers-jboss-beans.xml should ignore MalformedParameterizedTypeException
by Richard Kennard (JIRA)
scanning-deployers-jboss-beans.xml should ignore MalformedParameterizedTypeException
------------------------------------------------------------------------------------
Key: JBMDR-74
URL: https://issues.jboss.org/browse/JBMDR-74
Project: JBoss MetaData Repository
Issue Type: Bug
Components: MetaData
Environment: JBoss AS 6 Final
Reporter: Richard Kennard
Priority: Minor
When deploying my app (which works on JBoss 5.1.0.GA) under JBoss 6 AS Final, the deployment fails citing:
Caused by: java.lang.reflect.MalformedParameterizedTypeException
...non JBoss methods...
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$2.run(IntrospectionTypeInfoFactoryImpl.java:230) [jboss-reflect.jar:2.2.0.GA]
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl$2.run(IntrospectionTypeInfoFactoryImpl.java:218) [jboss-reflect.jar:2.2.0.GA]
at java.security.AccessController.doPrivileged(Native Method) [:1.6.0_23]
at org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactoryImpl.getMethods(IntrospectionTypeInfoFactoryImpl.java:217) [jboss-reflect.jar:2.2.0.GA]
It appears this code is already configured (in scanning-deployers-jboss-beans.xml) to ignore a number of such Exceptions, but not MalformedParameterizedTypeException. So I believe this one needs to be added:
<install method="addIgnored">
<parameter>java.lang.reflect.MalformedParameterizedTypeException</parameter>
</install>
Regards,
Richard.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 2 months