August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3325) Remove old code

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3325?page=all ] Dimitris Andreadis updated JBAS-3325: ------------------------------------- Fix Version/s: JBossAS-4.0.5.GA (was: JBossAS-4.0.5.CR1) > Remove old code > --------------- > > Key: JBAS-3325 > URL: http://jira.jboss.com/jira/browse/JBAS-3325 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Other > Affects Versions: JBossAS-4.0.4.GA > Environment: JBoss 4.0.3.SP1 > $ java -version > java version "1.4.2_12" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03) > Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode) > $ java -version > java version "1.5.0_07" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03) > Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing) > Reporter: Robert Schroeder > Assigned To: Dimitris Andreadis > Fix For: JBossAS-4.0.5.GA > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingJBossBehindAFirewall mentions the parameter "java.rmi.server.hostname" to set if the external host name differs from the local host (e.g. server machine is behind a firewall) > But org.jboss.web.WebService doesn'r recognize this parameter: > String hostname = server.getBindAddress(); // this always returns something, at least "0.0.0.0"! > // If not user specified hostname given, then try to determine what it should be > if (hostname == null) //this branch is never executed! > { > // First look for the rmi server name > try > { > hostname = System.getProperty("java.rmi.server.hostname"); // this parameter is not recognized as this branch is never executed > } > catch (SecurityException e) > { > // ignore, but don't be silent > ThrowableHandler.addWarning(e); > } > // else use the localhost name > if (hostname == null) > { > try > { > hostname = InetAddress.getLocalHost().getHostName(); > } > catch (IOException e) > { > log.error("Failed to get localhost name; ignoring", e); > } > } > if (hostname != null) > { > setHost(hostname); > } > } > // Host must be set to continue (either by user or detection) > String address = getHost(); > if (address == null) > throw new MissingAttributeException("Host"); > // Set the rmi codebase if it is not already set > String codebase = System.getProperty("java.rmi.server.codebase"); > if (codebase == null) > { > address = ServerConfigUtil.fixRemoteAddress(address); > codebase = "http://" + address + ":" + getPort() + "/"; > System.setProperty("java.rmi.server.codebase", codebase); > } > log.info("Using RMI server codebase: " + codebase); > So the resulting problem is that codebase contains an address which is not reachable from the other side of firewall because "java.rmi.server.hostname" is not recognized (same for "-Djava.rmi.server.useLocalHostname=false" ) > Example: > JBoss started with parameter set "-Djava.rmi.server.hostname=as2.subdomain1.subdomain2.test.com" > but (thanks to rmi logging) the proxy objects on client side have codebase set to "http://as2:<port>" and not to "http://as2.subdomain1.subdomain2.test.com:<port>" as expected. > JBoss 4 runs on a linux machine > hostname --> "as2" > hostname -f --> "as2.subdomain1.subdomain2.test.com" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-108) Remove zap classes before we release

by Mark Little (JIRA)

Remove zap classes before we release ------------------------------------ Key: JBESB-108 URL: http://jira.jboss.com/jira/browse/JBESB-108 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Tom Fennelly Priority: Minor Fix For: 4.0 Beta 1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3465) updating entity bean not updates field in database

by Yura Kravchuk (JIRA)

updating entity bean not updates field in database -------------------------------------------------- Key: JBAS-3465 URL: http://jira.jboss.com/jira/browse/JBAS-3465 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: CMP service, EJB2 Affects Versions: JBossAS-4.0.4.GA, JBossAS-4.0.3 SP1 Environment: Windows XP service pack 2 OEM Reporter: Yura Kravchuk Assigned To: Alexey Loubyansky The entity bean doesn't update field in database. I have two entity beans OrgPersonnel and QualificationName. OrgPersonnel has field qualificationNameId (N:1 relation). For these entity beans in jboss.xml file specified different container configurations. The OrgPersonnel bean's configuration is 'Instance Per Transaction CMP 2.x EntityBean'. The QualificationName bean's configuration is 'Standard CMP 2.x EntityBean with cache invalidation' but with commit-option 'D'. When I am changing OrgPersonnel entity bean then changes affects all fields for corresponding record in database except qualificationNameId field, but it was changed. I examined the query that Jboss produced and found that field qualificationNameId missed in update. 2006-08-04 11:35:34,851 DEBUG [org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreEntityCommand.OrgPersonnelEJB] Executing SQL: UPDATE org_personnels SET family_name=?, family_name_prefix=? WHERE org_personnel_id=? I tried update other entities with similar configurations but all works properly. If I use default configuration 'Standard CMP 2.x EntityBean' for OrgPersonnel entity bean then qualificationNameId field appears in update query and changes in database. ejb-jar.xml <entity> <ejb-name>OrgPersonnelEJB</ejb-name> <local-home>com.usl.smash.data.orgPersonnel.LocalOrgPersonnelHome</local-home> <local>com.usl.smash.data.orgPersonnel.LocalOrgPersonnel</local> <ejb-class>com.usl.smash.data.orgPersonnel.OrgPersonnelBean</ejb-class> <persistence-type>Container</persistence-type> <prim-key-class>java.lang.Integer</prim-key-class> <reentrant>False</reentrant> <cmp-version>2.x</cmp-version> <abstract-schema-name>org_personnels</abstract-schema-name> <cmp-field> <field-name>orgPersonnelId</field-name> </cmp-field> <cmp-field> <field-name>number</field-name> </cmp-field> <cmp-field> <field-name>qualificationNameId</field-name> </cmp-field> <cmp-field> <field-name>organizationId</field-name> </cmp-field> <cmp-field> <field-name>familyName</field-name> </cmp-field> <cmp-field> <field-name>familyNamePrefix</field-name> </cmp-field> <primkey-field>orgPersonnelId</primkey-field> <query> <query-method> <method-name>ejbSelectGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <ejb-ql/> </query> <query> <query-method> <method-name>ejbSelectCountGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <ejb-ql/> </query> </entity> <entity> <ejb-name>QualificationNameEJB</ejb-name> <local-home>com.usl.smash.data.qualificationName.LocalQualificationNameHome</local-home> <local>com.usl.smash.data.qualificationName.LocalQualificationName</local> <ejb-class>com.usl.smash.data.qualificationName.QualificationNameBean</ejb-class> <persistence-type>Container</persistence-type> <prim-key-class>java.lang.Integer</prim-key-class> <reentrant>False</reentrant> <cmp-version>2.x</cmp-version> <abstract-schema-name>qualification_names</abstract-schema-name> <cmp-field> <field-name>qualificationNameId</field-name> </cmp-field> <cmp-field> <field-name>name</field-name> </cmp-field> <cmp-field> <field-name>standard</field-name> </cmp-field> <primkey-field>qualificationNameId</primkey-field> <query> <query-method> <method-name>ejbSelectGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <ejb-ql/> </query> <query> <query-method> <method-name>ejbSelectCountGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <ejb-ql/> </query> </entity> <ejb-relationship-role> <ejb-relationship-role-name>QualificationName-has-OrgPersonnels</ejb-relationship-role-name> <multiplicity>One</multiplicity> <relationship-role-source> <ejb-name>QualificationNameEJB</ejb-name> </relationship-role-source> <cmr-field> <cmr-field-name>orgPersonnels</cmr-field-name> <cmr-field-type>java.util.Collection</cmr-field-type> </cmr-field> </ejb-relationship-role> <ejb-relationship-role> <ejb-relationship-role-name>OrgPersonnel-is-QualificationName</ejb-relationship-role-name> <multiplicity>Many</multiplicity> <cascade-delete/> <relationship-role-source> <ejb-name>OrgPersonnelEJB</ejb-name> </relationship-role-source> <cmr-field> <cmr-field-name>qualificationName</cmr-field-name> </cmr-field> </ejb-relationship-role> </ejb-relation> jbosscmp-jdbc.xml <entity> <ejb-name>OrgPersonnelEJB</ejb-name> <table-name>org_personnels</table-name> <cmp-field> <field-name>orgPersonnelId</field-name> <column-name>org_personnel_id</column-name> </cmp-field> <cmp-field> <field-name>qualificationNameId</field-name> <column-name>qualification_name_id</column-name> </cmp-field> <cmp-field> <field-name>familyNamePrefix</field-name> <column-name>family_name_prefix</column-name> </cmp-field> <cmp-field> <field-name>familyName</field-name> <column-name>family_name</column-name> </cmp-field> <cmp-field> <field-name>organizationId</field-name> <column-name>organization_id</column-name> </cmp-field> <query> <query-method> <method-name>ejbSelectGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <dynamic-ql/> </query> <query> <query-method> <method-name>ejbSelectCountGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <dynamic-ql/> </query> </entity> <entity> <ejb-name>QualificationNameEJB</ejb-name> <table-name>qualification_names</table-name> <cmp-field> <field-name>qualificationNameId</field-name> <column-name>qualification_name_id</column-name> </cmp-field> <query> <query-method> <method-name>ejbSelectGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <dynamic-ql/> </query> <query> <query-method> <method-name>ejbSelectCountGeneric</method-name> <method-params> <method-param>java.lang.String</method-param> <method-param>java.lang.Object[]</method-param> </method-params> </query-method> <dynamic-ql/> </query> </entity> <ejb-relation> <ejb-relation-name>QualificationName - OrgPersonnel</ejb-relation-name> <ejb-relationship-role> <ejb-relationship-role-name>QualificationName-has-OrgPersonnels</ejb-relationship-role-name> <key-fields> <key-field> <field-name>qualificationNameId</field-name> <column-name>qualification_name_id</column-name> </key-field> </key-fields> </ejb-relationship-role> <ejb-relationship-role> <ejb-relationship-role-name>OrgPersonnel-is-QualificationName</ejb-relationship-role-name> <key-fields/> </ejb-relationship-role> </ejb-relation> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
1
0 / 0

[JBoss JIRA] Resolved: (JBAS-3371) Replace Sun activation.jar with a source-code friendly licensed implementation

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3371?page=all ] Dimitris Andreadis resolved JBAS-3371. -------------------------------------- Resolution: Done Mark as resolved until we find some problem with it. > Replace Sun activation.jar with a source-code friendly licensed implementation > ------------------------------------------------------------------------------ > > Key: JBAS-3371 > URL: http://jira.jboss.com/jira/browse/JBAS-3371 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > GNU JAF: JavaBeans? Activation Framework, is a drop-in replacement for sun's implementation found in activation.jar > The sources can be downloaded from here: > http://www.gnu.org/software/classpathx/jaf/jaf.html > We need to test to see if there are any issues with replacing this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAS-3372) Replace Sun javamail (mail.jar) with a source-code friendly licensed implementation

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3372?page=all ] Dimitris Andreadis resolved JBAS-3372. -------------------------------------- Resolution: Done Mark as resolved until we find some problem with it. > Replace Sun javamail (mail.jar) with a source-code friendly licensed implementation > ----------------------------------------------------------------------------------- > > Key: JBAS-3372 > URL: http://jira.jboss.com/jira/browse/JBAS-3372 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Other > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > GNU JavaMail is a free implementation of the JavaMail API specification, version 1.3. > We want to use it as a replacement for Sun's mail.jar > The sources can be downloaded from here: > http://www.gnu.org/software/classpathx/javamail/javamail.html > Issues with replacement by classpathx-mail: > jbossws must be patched to use gnu-handlers instead of sun-handlers > +//import com.sun.mail.handlers.multipart_mixed; > +import gnu.mail.handler.MultipartMixed; > +//import com.sun.mail.handlers.text_html; > +import gnu.mail.handler.TextHtml; > +//import com.sun.mail.handlers.text_plain; > +import gnu.mail.handler.TextPlain; > testsuite/src/main/org/jboss/test/classloader/resource/ResourceTest.java > must be patched, because it refers to javamail.default.address.map and javamail.default.providers while in classpathx-mail these are named javamail.address.map and javamail.providers in classpathx-mail This change isn't essential to javamail; those files (+javamail.jar) were chosen because they were supposed to be always there. The real purpose of ResouceTest.java is to check access to resouces, so any adequate resources could be the test objects. But the resource test is executed very often and in different contexts. Therefore the adjustment is important for testsuite. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2904) Allow for ear modules to be deployed in the order that they are declared in application.xml

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2904?page=comments#action_12340607 ] Dimitris Andreadis commented on JBAS-2904: ------------------------------------------ Can you port this to Branch_4_0 (again in SVN)? Then I'll have a look on the test undeployment issue > Allow for ear modules to be deployed in the order that they are declared in application.xml > ------------------------------------------------------------------------------------------- > > Key: JBAS-2904 > URL: http://jira.jboss.com/jira/browse/JBAS-2904 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP1 > Reporter: Jim Moran > Assigned To: Vicky Kak > Fix For: JBossAS-3.2.8.SP2, JBossAS-4.0.5.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-266) Faliure of clustering with TCP

by Manoranjan Sahu (JIRA)

Faliure of clustering with TCP --------------------------------- Key: JGRP-266 URL: http://jira.jboss.com/jira/browse/JGRP-266 Project: JGroups Issue Type: Bug Affects Versions: 2.2.9 SP3 (2.2.9.3) Reporter: Manoranjan Sahu Assigned To: Bela Ban I am using jgroups 2.2.9 SP3 for my cluster consisting of 4 servers (alps,karsha,ladakh,pumori) Here is the setting in alps (initial_hosts being set to the other 3 servers) TCP(start_port=7880;loopback=false;send_buf_size=100000;recv_buf_size=200000):TCPPING(timeout=3000;initial_hosts=karsha[7880],ladakh[7880],pumori[7880];port_range=3;num_initial_members=3):FD(timeout=2000;max_tries=4):VERIFY_SUSPECT(timeout=1500;down_thread=false;up_thread=false):pbcast.NAKACK(gc_lag=100;retransmit_timeout=600,1200,2400,4800):pbcast.STABLE(stability_delay=1000;desired_avg_gossip=20000;down_thread=false;max_bytes=0;up_thread=false):VIEW_SYNC(avg_send_interval=60000;down_thread=false;up_thread=false;):pbcast.GMS(print_local_addr=true;join_timeout=5000;join_retry_timeout=2000;shun=true):pbcast.STATE_TRANSFER(up_thread=true;down_thread=true) I started the servers one by one . However they don't cluster . one server sends heart bit message(are you alive message) to the other and dont get the response . hence got [NotificationBus] [ERROR] exception is ChannelClosedException ... however sometimes it is able to cluster. it works fine with protocol stack using UDP. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Commented: (JBAS-2904) Allow for ear modules to be deployed in the order that they are declared in application.xml

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2904?page=comments#action_12340604 ] Vicky Kak commented on JBAS-2904: --------------------------------- Dimitris , the changes are put in the head at here https://svn.jboss.org/repos/jbossas/trunk/ The build works fine after the changes but the test fails when invoked second time . This is true with the other test cases which I have tried I have tested this : C:\JBOSS-SVN\jbosshead\testsuite>build -Dtest=org.jboss.test.deployers.ear.test. EARDeploymentUnitTestCase one-test It seems that the undeployment does not occur .properly. > Allow for ear modules to be deployed in the order that they are declared in application.xml > ------------------------------------------------------------------------------------------- > > Key: JBAS-2904 > URL: http://jira.jboss.com/jira/browse/JBAS-2904 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Deployment services > Affects Versions: JBossAS-4.0.3 SP1, JBossAS-3.2.8.SP1 > Reporter: Jim Moran > Assigned To: Vicky Kak > Fix For: JBossAS-3.2.8.SP2, JBossAS-4.0.5.CR1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-1475) Provide optimized JGroups config for Clustering as default

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1475?page=all ] Bela Ban reassigned JBAS-1475: ------------------------------ Assignee: Brian Stansberry > Provide optimized JGroups config for Clustering as default > ---------------------------------------------------------- > > Key: JBAS-1475 > URL: http://jira.jboss.com/jira/browse/JBAS-1475 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Bela Ban > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.Beta > > Original Estimate: 2 days > Remaining Estimate: 2 days > > - Use fc-fast-minimalthreads.xml as default properties for JBoss Clustering. > - Provide a commented tcp-based configuration, with TCP:PING (mcast discovery) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-322) DateWrapper is not registered for remoting. Javascript-Java conversion of date types fails.

by Jens (JIRA)

DateWrapper is not registered for remoting. Javascript-Java conversion of date types fails. ------------------------------------------------------------------------------------------- Key: JBSEAM-322 URL: http://jira.jboss.com/jira/browse/JBSEAM-322 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 1.0.1 Environment: All Reporter: Jens in WrapperFactory.java the DateWrapper wrapper class is not registered. Javascript remote calls cannot be converted to Java Date type. This line needs to be added: registerWrapper("date", DateWrapper.class); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006