[JBoss JIRA] Created: (JBAS-3731) The default ServiceBindingManager's sample bindings file should override JBoss Messaging's Connector configuration
by Ovidiu Feodorov (JIRA)
The default ServiceBindingManager's sample bindings file should override JBoss Messaging's Connector configuration
------------------------------------------------------------------------------------------------------------------
Key: JBAS-3731
URL: http://jira.jboss.com/jira/browse/JBAS-3731
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.CR1, JBossAS-4.0.4.GA
Reporter: Ovidiu Feodorov
Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.Beta
The default ServiceBindingManager's sample bindings file (${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml) should contain <service-config> entries that would override JBoss Messaging's Connector configuration.
The <service-config> should be present in all <server> bindings ("ports-default", "ports-01", "ports-02", "ports-03").
Suggested <service-config> entries:
"ports-default":
<service-config name="jboss.messaging:service=Connector,transport=socket"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config>
<attribute name="InvokerLocator">socket://${jboss.bind.address}:4457/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
</delegate-config>
<binding port="4457"/>
</service-config></server>
"ports-01":
<service-config name="jboss.messaging:service=Connector,transport=socket"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config>
<attribute name="InvokerLocator">socket://${jboss.bind.address}:4557/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
</delegate-config>
<binding port="4557"/>
</service-config></server>
"ports-02":
<service-config name="jboss.messaging:service=Connector,transport=socket"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config>
<attribute name="InvokerLocator">socket://${jboss.bind.address}:4657/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
</delegate-config>
<binding port="4657"/>
</service-config></server>
"ports-03":
<service-config name="jboss.messaging:service=Connector,transport=socket"
delegateClass="org.jboss.services.binding.AttributeMappingDelegate">
<delegate-config>
<attribute name="InvokerLocator">socket://${jboss.bind.address}:4757/?dataType=jms&serializationtype=jms&timeout=0&leasePeriod=20000&socket.check_connection=false&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat</attribute>
</delegate-config>
<binding port="4757"/>
</service-config></server>
--
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
19 years, 7 months
[JBoss JIRA] Created: (JBAS-3727) NPE on context classloader changing in EJB container when caller doesn't have a context classloader
by Adrian Brock (JIRA)
NPE on context classloader changing in EJB container when caller doesn't have a context classloader
---------------------------------------------------------------------------------------------------
Key: JBAS-3727
URL: http://jira.jboss.com/jira/browse/JBAS-3727
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.0.5.CR1
Reporter: Adrian Brock
Assigned To: Scott M Stark
Fix For: JBossAS-4.0.5.GA, JBossAS-5.0.0.Beta
The following code in org.jboss.ejb.Container
doesn't work if the caller doesn't have a context classloader,
e.g. it is using the bootstrap classloader as its classloader on the Sun JDK
ClassLoader callerClassLoader = SecurityActions.getContextClassLoader();
long start = System.currentTimeMillis();
Method m = null;
boolean setCl = false;
Object type = null;
String contextID = getJaccContextID();
try
{
if (!callerClassLoader.equals(classLoader)) // !!! callerClassLoader is null !!!
{
setCl = true;
SecurityActions.setContextClassLoader(this.classLoader);
}
The classloaders should be reversed, since the ejb classloader can never be null.
Is there a reason for this optimization? I'd imagine the comparison of classloaders
is likely to be more expensive that just setting the TCL in some cases????
--
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
19 years, 7 months