December 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-3343) JCA 1.5 Resource Adapter Config Properties cannot be specified

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3343?page=all ] Dimitris Andreadis updated JBAS-3343: ------------------------------------- Fix Version/s: JBossAS-5.0.0.CR1 > JCA 1.5 Resource Adapter Config Properties cannot be specified > -------------------------------------------------------------- > > Key: JBAS-3343 > URL: http://jira.jboss.com/jira/browse/JBAS-3343 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Affects Versions: JBossAS-4.0.4.GA > Environment: All. > Reporter: Andreas Mueller > Assigned To: Vicky Kak > Fix For: JBossAS-5.0.0.CR1 > > Attachments: ra.xml > > > A JCA 1.5 resource adapter might contain config properties in ra.xml. It is not possible in JBoss to override them with -ds.xml file. > For example, here is an excert of SwiftMQ's intraVM ra.xml: > <resourceadapter> > <resourceadapter-class> > com.swiftmq.connector.v15.ResourceAdapterImpl > </resourceadapter-class> > <config-property> > <config-property-name>ProviderURL</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>smqp://intravm/timeout=10000</config-property-value> > </config-property> > <config-property> > <config-property-name>IntraVM</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>true</config-property-value> > </config-property> > <config-property> > <config-property-name>DebugMode</config-property-name> > <config-property-type>java.lang.Boolean</config-property-type> > <config-property-value>false</config-property-value> > </config-property> > <config-property> > <config-property-name>RouterWorkingDirectory</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value><swiftmq_dir>/scripts/unix</config-property-value> > </config-property> > <config-property> > <config-property-name>ConfigurationFilename</config-property-name> > <config-property-type>java.lang.String</config-property-type> > <config-property-value>../../config/router1/routerconfig.xml</config-property-value> > </config-property> > It is not possible to overwrite them during deployment. It is only possible to specify the config properties of the ManagedConnectionFactory in -ds.xml. -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5013) TomcatInjectionContainer: Handle message-destination-ref

by Anil Saldhana (JIRA)

TomcatInjectionContainer: Handle message-destination-ref -------------------------------------------------------- Key: JBAS-5013 URL: http://jira.jboss.com/jira/browse/JBAS-5013 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Affects Versions: JBossAS-5.0.0.Beta2 Environment: asaldhana~/jboss-5.0/jboss-head/testsuite>ant -Dtest=org.jboss.test.jacc.test.WebIntegrationUnitTestCase one-test You can run this test against the JBoss default configuration to reproduce the error. Reporter: Anil Saldhana Assigned To: Remy Maucherat Fix For: JBossAS-5.0.0.Beta3 <web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> ...... <message-destination-ref> <description>consumes using a link</description> <message-destination-ref-name>mdr/ConsumesLink</message-destination-ref-na me> <message-destination-type>javax.jms.Queue</message-destination-type> <message-destination-usage>Consumes</message-destination-usage> <message-destination-link>TestQueue</message-destination-link> </message-destination-ref> <message-destination-ref> <description>produces using a link</description> <message-destination-ref-name>mdr/ProducesLink</message-destination-ref-na me> <message-destination-type>javax.jms.Topic</message-destination-type> <message-destination-usage>Produces</message-destination-usage> <message-destination-link>TestTopic</message-destination-link> </message-destination-ref> </web-app> ====================================== org.jboss.web.tomcat.service.TomcatInjectionContainer public String resolveMessageDestination(String link) { throw new NotImplementedException(); } -- 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

17 years, 10 months

2
2
0 / 0

[JBoss JIRA] Closed: (JBREM-166) JMXConnectorServer will not start if using rmi invoker elsewhere

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-166?page=all ] Ron Sigal closed JBREM-166. --------------------------- Resolution: Out of Date > JMXConnectorServer will not start if using rmi invoker elsewhere > ---------------------------------------------------------------- > > Key: JBREM-166 > URL: http://jira.jboss.com/jira/browse/JBREM-166 > Project: JBoss Remoting > Issue Type: Bug > Components: jmx remoting > Affects Versions: JMX Remoting 1.0.1 > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: 2.4.0.Beta1 (Pinto), JMX Remoting 1.0.2 > > > If have a remoting invoker using rmi transport, it will create a rmi registry. Then when the JMXConnectorServer starts, it will also try to create one. Even though is on a different port, will get the following exception: > java.rmi.server.ExportException: internal error: ObjID already in use > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168) > at sun.rmi.transport.Transport.exportObject(Transport.java:69) > at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190) > at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382) > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116) > at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145) > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) > at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78) > at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164) > at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBREM-166) JMXConnectorServer will not start if using rmi invoker elsewhere

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-166?page=comments#action_12390625 ] Ron Sigal commented on JBREM-166: --------------------------------- Actually, it's not related to "JBAS-3885: JMXConnectorServer not respecting the -b value". Instead, it is due to a problem with older version of the Sun jdk: bug ID 4267864: "Can't run create multiple registries in same vm." See http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4267864. The problem was that every java.rmi.registry.Registry was identifed by a single ObjID, independent of the port to which the Registry was bound. So that the following code would fail: createRegistry(portNumber); createRegistry(portNumber + 1); Apparently, that problem is fixed in jdk 1.5 and later versions of jdk 1.4. It was tested in two ways. 1. The two lines given above run successfully in jdk 1.4.2_13 and jdk 1.5.0_06 in Windows and jdk 1.5.0_10 in linux. 2. JBossAS 5.0.0 successfully starts with (a) a Remoting Connector using the rmi transport (b) the "jboss.remoting:service=JMXConnectorServer,protocol=rmi" org.jboss.mx.remoting.service.JMXConnectorServerService MBean. > JMXConnectorServer will not start if using rmi invoker elsewhere > ---------------------------------------------------------------- > > Key: JBREM-166 > URL: http://jira.jboss.com/jira/browse/JBREM-166 > Project: JBoss Remoting > Issue Type: Bug > Components: jmx remoting > Affects Versions: JMX Remoting 1.0.1 > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto) > > > If have a remoting invoker using rmi transport, it will create a rmi registry. Then when the JMXConnectorServer starts, it will also try to create one. Even though is on a different port, will get the following exception: > java.rmi.server.ExportException: internal error: ObjID already in use > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168) > at sun.rmi.transport.Transport.exportObject(Transport.java:69) > at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190) > at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382) > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116) > at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145) > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) > at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78) > at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164) > at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBREM-166) JMXConnectorServer will not start if using rmi invoker elsewhere

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-166?page=all ] Ron Sigal reassigned JBREM-166: ------------------------------- Assignee: Ron Sigal > JMXConnectorServer will not start if using rmi invoker elsewhere > ---------------------------------------------------------------- > > Key: JBREM-166 > URL: http://jira.jboss.com/jira/browse/JBREM-166 > Project: JBoss Remoting > Issue Type: Bug > Components: jmx remoting > Affects Versions: JMX Remoting 1.0.1 > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: JMX Remoting 1.0.2, 2.4.0.Beta1 (Pinto) > > > If have a remoting invoker using rmi transport, it will create a rmi registry. Then when the JMXConnectorServer starts, it will also try to create one. Even though is on a different port, will get the following exception: > java.rmi.server.ExportException: internal error: ObjID already in use > at sun.rmi.transport.ObjectTable.putTarget(ObjectTable.java:168) > at sun.rmi.transport.Transport.exportObject(Transport.java:69) > at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:190) > at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382) > at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116) > at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145) > at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92) > at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78) > at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164) > at org.jboss.mx.remoting.service.JMXConnectorServerService.start(JMXConnectorServerService.java:91) -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4882) TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services

by samson kittoli (JIRA)

TECH REVIEW: Server Configuration Guide - Chapter9 - Web Services ----------------------------------------------------------------- Key: JBAS-4882 URL: http://jira.jboss.com/jira/browse/JBAS-4882 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Server Configuration Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Attachments: JBAS-422-Server_Configuration_Guide-Chapter9-Web_Services.odt Attached is an Open Office 2.0 Document containing a chapter of the Server Configuration Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Server_Configuration_Guide/beta422/html/ -- 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

17 years, 10 months

3
7
0 / 0

[JBoss JIRA] Commented: (EJBTHREE-266) ejb3.deployer port needs to be added to Binding Manager supporet

by skud xavier (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-266?page=comments#action_12390583 ] skud xavier commented on EJBTHREE-266: -------------------------------------- I voted for it. Our unix admins seem to like it & I think it is inititutive too. > ejb3.deployer port needs to be added to Binding Manager supporet > ---------------------------------------------------------------- > > Key: EJBTHREE-266 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-266 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC1 > Environment: Windows XP Professional, JBossAS 4.0.3rc2 > Reporter: dknox > > The sample-bindings.xml doesn't include support for the ejb.deployer service. I thought that it could be added easily, but it appears that the format specifying the port in the ejb3.deployer jboss-services.xml is complex. Probably an xslt transform is required. I was going to try to write the transform but the port number is declared in two places. Additionally, the transform will need to leave most of the attribute value as is and only tranform the port number. > <mbean code="org.jboss.remoting.transport.Connector" > xmbean-dd="org/jboss/remoting/transport/Connector.xml" > name="jboss.remoting:type=Connector,transport=socket3874,handler=ejb3"> > <depends>jboss.aop:service=AspectDeployer</depends> > <attribute name="InvokerLocator">socket://0.0.0.0:3874</attribute> > Writing the transform for the element InvokerLocator is simple but the name attribute will require a bit more (if it is significant). -- 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

17 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4817) PreFillPoolingUnitTestCase isssues

by Weston Price (JIRA)

PreFillPoolingUnitTestCase isssues ---------------------------------- Key: JBAS-4817 URL: http://jira.jboss.com/jira/browse/JBAS-4817 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.Beta2, JBossAS-5.0.0.Beta1 Reporter: Weston Price Assigned To: Weston Price Fix For: JBossAS-5.0.0.Beta3 There are two types of failures in the PreFillPoolingUnitTestCase. The first has to do with the new JAXB based deployment in AS5. JAXB appears to have an issue with the following type of XML booleans <prefill>True</prefill> JAXB incorrectly marshalls this to false while values such as <prefill>tRue</prefill> work. The other issue appears to be in timing and relation to the PoolFiller thread. -- 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

17 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3595) Tomcat allows http access with transport guarantie CONFIDENTIAL

by Thomas Diesler (JIRA)

Tomcat allows http access with transport guarantie CONFIDENTIAL --------------------------------------------------------------- Key: JBAS-3595 URL: http://jira.jboss.com/jira/browse/JBAS-3595 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossAS-5.0.0.Beta The generated web.xml contains CONFIDENTIAL. Access via http:// should be denied. This woks in Branch_4_0 /home/tdiesler/svn/jbossws/trunk/src/test [tdiesler@tdvaio test]$ ant -Dtest=org.jboss.test.ws.samples.secureejb.SecureEJBTestCase one-test one-test: [junit] Running org.jboss.test.ws.samples.secureejb.SecureEJBTestCase [junit] Tests run: 5, Failures: 1, Errors: 0, Time elapsed: 5.452 sec [junit] Test org.jboss.test.ws.samples.secureejb.SecureEJBTestCase FAILED -- 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

17 years, 10 months

5
7
0 / 0

[JBoss JIRA] Created: (JBAS-5035) MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver hard coded

by Luc Boudreau (JIRA)

MySQLValidConnectionChecker has driver name com.mysql.jdbc.Driver hard coded ---------------------------------------------------------------------------- Key: JBAS-5035 URL: http://jira.jboss.com/jira/browse/JBAS-5035 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JCA service Affects Versions: JBossAS-5.0.0.GA, JBossAS-4.2.3.GA, JBossAS-5.1.0.CR1, JBossAS-4.0.5.SP1 Environment: Any Reporter: Luc Boudreau Assigned To: Weston Price Priority: Blocker The JCA MySQLValidConnectionChecker class has the driver name com.mysql.jdbc.Driver hard coded which prevents it from using any other driver class provided by the standard MySQL library. A good example of this is the replicated driver, which uses class com.mysql.jdbc.ReplicationDriver. -- 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

17 years, 10 months

3
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007