[JBoss JIRA] Created: (JBESB-905) Increase Permgen: -XX:MaxPermSize=128m
by Burr Sutter (JIRA)
Increase Permgen: -XX:MaxPermSize=128m
--------------------------------------
Key: JBESB-905
URL: http://jira.jboss.com/jira/browse/JBESB-905
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Critical
Fix For: 4.2
On windows, modify the run.bat that is created for the ESB Server so that it has a larger than average MaxPermSize
set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m -XX:MaxPermSize=128m
Otherwise, you'll eventually run out of PermGen space while performing numerous hot deploys/undeploys. It is especially noticeable while working with the BPM capabilites which use a substantial amount of Hibernate which generates classes for data access (persistence of the in-flight process state).
--
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, 7 months
[JBoss JIRA] Created: (JBESB-820) Programmatic Routing Documentation/Examples
by Burr Sutter (JIRA)
Programmatic Routing Documentation/Examples
-------------------------------------------
Key: JBESB-820
URL: http://jira.jboss.com/jira/browse/JBESB-820
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Documentation
Affects Versions: 4.2 Milestone Release 3
Reporter: Burr Sutter
Assigned To: Mark Little
Priority: Minor
Fix For: 4.2.1
Update documentation (perhaps update one of the quickstart examples as well) to demonstrate the use of ServiceInvoker as a method to programmatically perform routing in a custom action class.
You would still want load-balancing/fail-over as well as the retry with auto-routing to the DLQ capabilities even when you are programmatically routing.
Using ServiceInvoker sounds like the best technique.
--
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, 7 months
[JBoss JIRA] Created: (JBESB-815) JAXB-Intros @XmlAttribute annotation handling issue
by Sylvia Isler (JIRA)
JAXB-Intros @XmlAttribute annotation handling issue
---------------------------------------------------
Key: JBESB-815
URL: http://jira.jboss.com/jira/browse/JBESB-815
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports, Web Services
Affects Versions: 4.2 Milestone Release 3
Environment: Windows XP v2002 sp2, JAVA 1.5_02
Reporter: Sylvia Isler
Assigned To: Mark Little
JAXB with JAXB-introductions fails to Marshall @XmlAttribute annotations in the following example:
The following class contains a simple double for an attribute:
public class UnitPrice {
public double value;
UnitPrice(double value){
this.value=value;
}
UnitPrice()
{
}
public double getValue()
{
return this.value;
}
}
The following JAXB-intros config file was used
<?xml version = "1.0" encoding = "UTF-8"?>
<jaxb-intros xmlns="http://www.jboss.org/xsd/jaxb/intros">
<Class name="junit.prices.UnitPrice">
<XmlType name = "UnitPrice"/>
<Field name="value">
<XmlAttribute name="value" required="true" />
</Field>
</Class>
</jaxb-intros>
along with the following schema file:
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
<xs:element name="UnitPrice">
<xs:complexType>
<xs:attribute name="value" type=xs:double use="required"/>
<xs:attribute name="currency" use="optional">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="USD"/>
<xs:enumeration value="Euro"/>
<xs:enumeration value="JPY"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:complexType>
</xs:element>
</xs:schema>
To unmarshall this XML file:
<?xml version="1.0" encoding="UTF-8"?>
<UnitPrice value="40.0" xsi:noNamespaceSchemaLocation="C:\UnitPrice.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
I then used the following code to test the unmarshalling of the above XML.
JaxbIntros config = IntroductionsConfigParser.parseConfig(getClass().getResourceAsStream("UnitConfig.xml"));
ClassIntroConfig classIntroConfig = config.getClazz().get(0);
assertEquals(UnitPrice.class.getName(), classIntroConfig.getName());
IntroductionsAnnotationReader reader = new IntroductionsAnnotationReader(config);
Map<String, Object> jaxbConfig= new HashMap<String, Object>();
jaxbConfig.put(JAXBRIContext.ANNOTATION_READER, reader);
JAXBContext jaxbContext = JAXBContext.newInstance(new Class[] {UnitPrice.class}, jaxbConfig);
Unmarshaller unmarshaller = jaxbContext.createUnmarshaller();
JAXBElement jbe = null;
UnitPrice order =null;
StreamSource ss = new StreamSource(getClass().getResourceAsStream("UsdUnitPrice1.xml"));
jbe = unmarshaller.unmarshal(ss, UnitPrice.class);
order =(UnitPrice)jbe.getValue();
try{
assertEquals("get double value error", 40.0, order.getValue());
} catch (Exception e) {
fail(e.getMessage());
}
a UnitPrice instance is instantiated. However, the above test code fails because the value attribute of the unmarshalled UnitPrice instance is 0.0 instead of 40.0..
After some discussion on the forums, I decided to try using <Method> tag instead of the <Field> in the config file above. When this yielded the same result,
--
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, 7 months