[jira] Assigned: (AMQCPP-35) Stomp content-length header not being set on BytesMessage
[ https://issues.apache.org/activemq/browse/AMQCPP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish reassigned AMQCPP-35: -- Assignee: Timothy Bish (was: Nathan Mittler) Stomp content-length header not being set on BytesMessage - Key: AMQCPP-35 URL: https://issues.apache.org/activemq/browse/AMQCPP-35 Project: ActiveMQ C++ Client Issue Type: Bug Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Timothy Bish Fix For: 1.1 Not sure if this is a bug or if I'm just doing something wrong, but here goes. On a cms::Session I'm calling createBytesMessage and getting back a cms::BytesMessage which is an activemq::connector::stomp::commands::BytesMessageCommand underneath. On this message I set an int property and write a string using writeString. Then I send the message to my producer. At no point does it seem as if the content-length header is set in this case. I verified by checking the properties written out for this message in StompCommandWriter::writeCommand. Due to the absence of this header, when AMQCPP receives this message, it assumes it is a TextMessageCommand instead of a BytesMessageCommand. The only way the header can get set is by something calling setBytes on the BytesMessageCommand which calls through to setBytes of AbstractCommand which sets the header. I don't think this happens when one only does a writeString. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (AMQCPP-35) Stomp content-length header not being set on BytesMessage
[ https://issues.apache.org/activemq/browse/AMQCPP-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish updated AMQCPP-35: --- Fix Version/s: 1.1 Stomp content-length header not being set on BytesMessage - Key: AMQCPP-35 URL: https://issues.apache.org/activemq/browse/AMQCPP-35 Project: ActiveMQ C++ Client Issue Type: Bug Components: Stomp Affects Versions: 1.1 Reporter: Albert Strasheim Assigned To: Timothy Bish Fix For: 1.1 Not sure if this is a bug or if I'm just doing something wrong, but here goes. On a cms::Session I'm calling createBytesMessage and getting back a cms::BytesMessage which is an activemq::connector::stomp::commands::BytesMessageCommand underneath. On this message I set an int property and write a string using writeString. Then I send the message to my producer. At no point does it seem as if the content-length header is set in this case. I verified by checking the properties written out for this message in StompCommandWriter::writeCommand. Due to the absence of this header, when AMQCPP receives this message, it assumes it is a TextMessageCommand instead of a BytesMessageCommand. The only way the header can get set is by something calling setBytes on the BytesMessageCommand which calls through to setBytes of AbstractCommand which sets the header. I don't think this happens when one only does a writeString. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: UDP transport over satellite
could you provide some more information about what config etc you used for ActiveMQ and UDP please? cheers, Rob On 28 Dec 2006, at 18:34, toolpusher2006 wrote: Hello, We are trying to move packets over a satellite connection. The broker is on the inside. The producer is on the outside connected via satellite. A simple client that talks using a DatagramSocket with a server works fine. I cannot, however, use the out-of-the-box sample from ActiveMQ to connect over UDP though. The same out-of-the-box sample from ActiveMQ works well over TCP. Any ideas or suggestions please. Thanks. -Hari -- View this message in context: http://www.nabble.com/UDP-transport- over-satellite-tf2891588.html#a8078348 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
[jira] Assigned: (AMQ-1110) JMS to JMS Bridge fails with Number format exception on physical name
[
https://issues.apache.org/activemq/browse/AMQ-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies reassigned AMQ-1110:
---
Assignee: Rob Davies
JMS to JMS Bridge fails with Number format exception on physical name
-
Key: AMQ-1110
URL: https://issues.apache.org/activemq/browse/AMQ-1110
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6
Reporter: Kay Stanke
Assigned To: Rob Davies
Attachments: activemq.xml
Maybe this is just some missconfiguration from my site but ...
I'm trying to use activemq to integrate some c++ code with the j2ee world. My
task is to forward messages generated on the c++ side to the JMS of Bea
Weblogic 8.1. ActiveMQ is running outside the WLS in a separate process. The
startup looks fine as the wls context can be used to get references to the
ConnectionFactory and the configured test destination WLSTestQ. On sending a
message to the local queue of the bridge i get the following stacktrace:
java.lang.NumberFormatException: For input string: WLSTESTQ
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at
org.apache.activemq.command.ActiveMQTempDestination.setPhysicalName(ActiveMQTempDestination.java:66)
at
org.apache.activemq.command.ActiveMQDestination.init(ActiveMQDestination.java:142)
at
org.apache.activemq.command.ActiveMQTempDestination.init(ActiveMQTempDestination.java:38)
at
org.apache.activemq.command.ActiveMQTempQueue.init(ActiveMQTempQueue.java:36)
at
org.apache.activemq.command.ActiveMQDestination.transform(ActiveMQDestination.java:107)
at
org.apache.activemq.command.ActiveMQMessage.setJMSDestination(ActiveMQMessage.java:219)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:428)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:152)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:215)
at
org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:87)
at
org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:134)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:840)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:96)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:165)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
ERROR DestinationBridge - failed to forward message on attempt: 1
reason: java.lang.NumberFormatException:
For input string: WLSTESTQ message:
ActiveMQTextMessage {
commandId = 14,
responseRequired = false,
messageId = ID:KStanke-1523-1167310376227-0:0:1:1:10,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-1523-1167310376227-0:0:1:1,
destination = queue://TEST.FOO,
transactionId = null,
expiration = 0,
timestamp = 1167310385795,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0,
targetConsumerId = null,
compressed = false,
userID = null,
content = null,
marshalledProperties = null,
dataStructure = null,
redeliveryCounter = 0,
size = 0,
properties = null,
readOnlyProperties = true,
readOnlyBody = true,
droppable = false,
text = Message: 9 sent at: Thu Dec 28 13:53:05 CET 2006
[Skipped some blank lines]
}
I'm using the message producer from the example to test the routing to wls
JMS. I also attached my activemq.xml configuration for you reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1110) JMS to JMS Bridge fails with Number format exception on physical name
[
https://issues.apache.org/activemq/browse/AMQ-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-1110.
-
Resolution: Fixed
Fix Version/s: 4.2.0
Fixed by the latest SVN revision 491753
JMS to JMS Bridge fails with Number format exception on physical name
-
Key: AMQ-1110
URL: https://issues.apache.org/activemq/browse/AMQ-1110
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0
Environment: Using Windows XP SP2, JDK 1.6.0, Bea Weblogic Server 8.1
SP6
Reporter: Kay Stanke
Assigned To: Rob Davies
Fix For: 4.2.0
Attachments: activemq.xml
Maybe this is just some missconfiguration from my site but ...
I'm trying to use activemq to integrate some c++ code with the j2ee world. My
task is to forward messages generated on the c++ side to the JMS of Bea
Weblogic 8.1. ActiveMQ is running outside the WLS in a separate process. The
startup looks fine as the wls context can be used to get references to the
ConnectionFactory and the configured test destination WLSTestQ. On sending a
message to the local queue of the bridge i get the following stacktrace:
java.lang.NumberFormatException: For input string: WLSTESTQ
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:447)
at java.lang.Integer.parseInt(Integer.java:497)
at
org.apache.activemq.command.ActiveMQTempDestination.setPhysicalName(ActiveMQTempDestination.java:66)
at
org.apache.activemq.command.ActiveMQDestination.init(ActiveMQDestination.java:142)
at
org.apache.activemq.command.ActiveMQTempDestination.init(ActiveMQTempDestination.java:38)
at
org.apache.activemq.command.ActiveMQTempQueue.init(ActiveMQTempQueue.java:36)
at
org.apache.activemq.command.ActiveMQDestination.transform(ActiveMQDestination.java:107)
at
org.apache.activemq.command.ActiveMQMessage.setJMSDestination(ActiveMQMessage.java:219)
at weblogic.jms.client.JMSProducer.sendInternal(JMSProducer.java:428)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:152)
at weblogic.jms.client.JMSProducer.send(JMSProducer.java:215)
at
org.apache.activemq.network.jms.QueueBridge.sendMessage(QueueBridge.java:87)
at
org.apache.activemq.network.jms.DestinationBridge.onMessage(DestinationBridge.java:134)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:840)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:96)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:165)
at
org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:88)
at
org.apache.activemq.thread.DedicatedTaskRunner.access$000(DedicatedTaskRunner.java:25)
at
org.apache.activemq.thread.DedicatedTaskRunner$1.run(DedicatedTaskRunner.java:39)
ERROR DestinationBridge - failed to forward message on attempt: 1
reason: java.lang.NumberFormatException:
For input string: WLSTESTQ message:
ActiveMQTextMessage {
commandId = 14,
responseRequired = false,
messageId = ID:KStanke-1523-1167310376227-0:0:1:1:10,
originalDestination = null,
originalTransactionId = null,
producerId = ID:KStanke-1523-1167310376227-0:0:1:1,
destination = queue://TEST.FOO,
transactionId = null,
expiration = 0,
timestamp = 1167310385795,
arrival = 0,
correlationId = null,
replyTo = null,
persistent = false,
type = null,
priority = 4,
groupID = null,
groupSequence = 0,
targetConsumerId = null,
compressed = false,
userID = null,
content = null,
marshalledProperties = null,
dataStructure = null,
redeliveryCounter = 0,
size = 0,
properties = null,
readOnlyProperties = true,
readOnlyBody = true,
droppable = false,
text = Message: 9 sent at: Thu Dec 28 13:53:05 CET 2006
[Skipped some blank lines]
}
I'm using the message producer from the example to test the routing to wls
JMS. I also attached my activemq.xml configuration for you reference.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (SM-798) Cannot start Bridge-SA in Geronimo 1.1 + Servicemix 3.0.1 plugin
[ https://issues.apache.org/activemq/browse/SM-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37810 ] xiaoxiong duan commented on SM-798: --- I found the same problem in geronimo plugin for Servicemix 3.1 Cannot start Bridge-SA in Geronimo 1.1 + Servicemix 3.0.1 plugin Key: SM-798 URL: https://issues.apache.org/activemq/browse/SM-798 Project: ServiceMix Issue Type: Bug Components: geronimo Affects Versions: 3.0.1 Environment: Windows XP, JDK 1.5_10, Geronimo 1.1, Servicemix 3.0.1 Reporter: xiaoxiong duan Fix For: 3.1 Attachments: geronimo-service.xml Installed deployer-3.0.1-incubating.car servicemix-3.0.1-incubating.car plugin in Geronimo 1.1, and deploy all Servicemix 3.0.1 components in Geronimo 1.1, . servicemix-bpe-3.0.1-incubating-installer.zip . servicemix-eip-3.0.1-incubating-installer.zip . servicemix-http-3.0.1-incubating-installer.zip . servicemix-jms-3.0.1-incubating-installer.zip . servicemix-jsr181-3.0.1-incubating-installer.zip . servicemix-lwcontainer-3.0.1-incubating-installer.zip . servicemix-sca-3.0.1-incubating-installer.zip . servicemix-shared-3.0.1-incubating-installer.zip . servicemix-wsn2005-3.0.1-incubating-installer.zip then deploy bridge-sa-3.0.1-incubating.zip and get the following error 17:33:56,166 INFO [BrokerService] ActiveMQ 4.0.2 JMS Message Broker (localhost) is starting 17:33:56,166 INFO [BrokerService] For help or more information please see: http://incubator.apache.org/activemq/ 17:33:56,506 INFO [ServiceAssembly] doFail called for JBI service assembly: bridge-sa 17:33:56,506 ERROR [GBeanInstanceState] Error while starting; GBean is now in the FAILED state: abstractName=servicemix-assemblies/bridge-sa/0.0/car?jbiType=JBIServiceAssembly,name=bridge-sa java.lang.NoClassDefFoundError: org/apache/derby/jdbc/EmbeddedDataSource at org.apache.activemq.store.DefaultPersistenceAdapterFactory.createDataSource(DefaultPersistenceAdapterFactory.java:187) at org.apache.activemq.store.DefaultPersistenceAdapterFactory.getDataSource(DefaultPersistenceAdapterFactory.java:96) at org.apache.activemq.store.DefaultPersistenceAdapterFactory.createPersistenceAdapter(DefaultPersistenceAdapterFactory.java:54) at org.apache.activemq.broker.BrokerService.createPersistenceAdapter(BrokerService.java:968) at org.apache.activemq.broker.BrokerService.getPersistenceAdapter(BrokerService.java:559) at org.apache.activemq.broker.BrokerService.createRegionBroker(BrokerService.java:929) at org.apache.activemq.broker.BrokerService.createBroker(BrokerService.java:888) at org.apache.activemq.broker.BrokerService.getBroker(BrokerService.java:458) at org.apache.activemq.broker.BrokerService.start(BrokerService.java:361) at org.apache.activemq.transport.vm.VMTransportFactory.doCompositeConnect(VMTransportFactory.java:102) at org.apache.activemq.transport.vm.VMTransportFactory.doConnect(VMTransportFactory.java:48) at org.apache.activemq.transport.TransportFactory.doConnect(TransportFactory.java:42) at org.apache.activemq.transport.TransportFactory.connect(TransportFactory.java:76) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:223) at org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(ActiveMQConnectionFactory.java:211) at org.apache.activemq.ActiveMQConnectionFactory.createConnection(ActiveMQConnectionFactory.java:158) at org.apache.servicemix.jms.AbstractJmsProcessor.start(AbstractJmsProcessor.java:74) at org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:351) at org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:50) at org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:149) at org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103) at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:130) at org.apache.servicemix.jbi.framework.ServiceAssemblyLifeCycle.start(ServiceAssemblyLifeCycle.java:105) at org.apache.servicemix.geronimo.ServiceMixGBean.register(ServiceMixGBean.java:216) at org.apache.servicemix.geronimo.ServiceMixGBean$$FastClassByCGLIB$$fcdcf76b.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) at
[jira] Created: (GERONIMO-2677) HttpSession Relocation - Sticky load-balancing via HTTP Cookie
HttpSession Relocation - Sticky load-balancing via HTTP Cookie -- Key: GERONIMO-2677 URL: http://issues.apache.org/jira/browse/GERONIMO-2677 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: Clustering Reporter: Gianny Damour Assigned To: Gianny Damour When an HttpSession is migrated from one node to another: * its id must be updated (the worker name suffix is to be set to the name of the node owning the HttpSession); and * the session cookie must be updated accordingly. The worker name suffix, which can be retrieved from the session cookie, can be leverage to configure sticky load-balancing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-2677) HttpSession Relocation - Sticky load-balancing via HTTP Cookie
[ http://issues.apache.org/jira/browse/GERONIMO-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gianny Damour updated GERONIMO-2677: Attachment: GERONIMO-2677.patch JETTY-2677.patch HttpSession Relocation - Sticky load-balancing via HTTP Cookie -- Key: GERONIMO-2677 URL: http://issues.apache.org/jira/browse/GERONIMO-2677 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Reporter: Gianny Damour Assigned To: Gianny Damour Attachments: GERONIMO-2677.patch, JETTY-2677.patch When an HttpSession is migrated from one node to another: * its id must be updated (the worker name suffix is to be set to the name of the node owning the HttpSession); and * the session cookie must be updated accordingly. The worker name suffix, which can be retrieved from the session cookie, can be leverage to configure sticky load-balancing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2677) HttpSession Relocation - Sticky load-balancing via HTTP Cookie
[ http://issues.apache.org/jira/browse/GERONIMO-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461613 ] Gianny Damour commented on GERONIMO-2677: - I attach two patches: * JETTY-2677.patch: Jetty6 patch in order to simplify the integration code. ** AbstractSessionManager.Session is updated such that its two constructors share the same logic with respect to the definition of the _id field. Also, the method initValues is added such that sub-classes can explicitly control the initialization of the _values field. ** SessionHandler.handle is refactored: the method setRequestedId has been extracted such that sub-classes can also share this behavior; and ** Request.getSession(boolean) is improved such that a session cookie is set against a session whose id has changed (following a migration). * GERONIMO-2677.patch: Geronimo patch to leverage the Jetty6 code base after having applied the Jetty6 patch. HttpSession Relocation - Sticky load-balancing via HTTP Cookie -- Key: GERONIMO-2677 URL: http://issues.apache.org/jira/browse/GERONIMO-2677 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Clustering Reporter: Gianny Damour Assigned To: Gianny Damour Attachments: GERONIMO-2677.patch, JETTY-2677.patch When an HttpSession is migrated from one node to another: * its id must be updated (the worker name suffix is to be set to the name of the node owning the HttpSession); and * the session cookie must be updated accordingly. The worker name suffix, which can be retrieved from the session cookie, can be leverage to configure sticky load-balancing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2678) Exception parsing a XML with Digester
Exception parsing a XML with Digester - Key: GERONIMO-2678 URL: http://issues.apache.org/jira/browse/GERONIMO-2678 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 1.1.1 Environment: Windows XP SP2, Geronimo 1.1.1 with Tomcat Reporter: Sergio Montesa My web application, deploy in geronimo, parse with Digester the following XML: ?xml version=1.0 encoding=iso-8859-1? data-sources !-- JDBC -- data-source name=ing__yy schema=ingres connection-driver=ca.edbc.jdbc.EdbcDriver url=jdbc:edbc://host:1919/bdd;CURSOR=READONLY username=user password=passwd jndi= / /data-sources and generate this exception: java.lang.ClassNotFoundException: com.unizar.sql.DataSource in classloader geronimo/tomcat/1.1.1/car org.apache.commons.digester.Digester.createSAXException(Digester.java:2792) org.apache.commons.digester.Digester.createSAXException(Digester.java:2818) org.apache.commons.digester.Digester.startElement(Digester.java:1289) org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XMLParser.parse(Unknown Source) org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) org.apache.commons.digester.Digester.parse(Digester.java:1591) com.unizar.sql.DataSourceCollection.parse(Unknown Source) com.unizar.sql.DataSourceCollection.parse(Unknown Source) org.apache.jsp.benchXml_jsp._jspService(org.apache.jsp.benchXml_jsp:136) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2679) ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar
ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar --- Key: GERONIMO-2679 URL: http://issues.apache.org/jira/browse/GERONIMO-2679 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: mail Affects Versions: 2.0-M2 Reporter: Geist Alexander There are 2 messages in the pop3-account. Using the following code Store store = session.getStore(pop3); store.connect(popServer, 110, popUser, popKey); Folder folder = store.getFolder(INBOX); folder.open(Folder.READ_WRITE); Message message[] = folder.getMessages(); runs in this exception java.lang.ArrayIndexOutOfBoundsException: 2 = 2 at java.util.Vector.setElementAt(Vector.java:483) at org.apache.geronimo.javamail.store.pop3.POP3Folder.getMessage(POP3Folder.java:257) at javax.mail.Folder.getMessages(Folder.java:468) at javax.mail.Folder.getMessages(Folder.java:495) at keygen.main.MailReceiver.receive(MailReceiver.java:42) at keygen.main.MailReceiver.main(MailReceiver.java:171) Sample code works with Suns mail.jar. Tested this code with a web application and a standalone client application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Board Report Due for January - Input Requested
Hi all, We are scheduled to provide a board report by the 17th. Please be thinking about the items that will can report on. I'll send out another note later this week. Oh, and Happy New Year :) Matt Hogstrom [EMAIL PROTECTED]
[jira] Assigned: (GERONIMO-2679) ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar
[ http://issues.apache.org/jira/browse/GERONIMO-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire reassigned GERONIMO-2679: -- Assignee: Rick McGuire ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar --- Key: GERONIMO-2679 URL: http://issues.apache.org/jira/browse/GERONIMO-2679 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Affects Versions: 2.0-M2 Reporter: Geist Alexander Assigned To: Rick McGuire There are 2 messages in the pop3-account. Using the following code Store store = session.getStore(pop3); store.connect(popServer, 110, popUser, popKey); Folder folder = store.getFolder(INBOX); folder.open(Folder.READ_WRITE); Message message[] = folder.getMessages(); runs in this exception java.lang.ArrayIndexOutOfBoundsException: 2 = 2 at java.util.Vector.setElementAt(Vector.java:483) at org.apache.geronimo.javamail.store.pop3.POP3Folder.getMessage(POP3Folder.java:257) at javax.mail.Folder.getMessages(Folder.java:468) at javax.mail.Folder.getMessages(Folder.java:495) at keygen.main.MailReceiver.receive(MailReceiver.java:42) at keygen.main.MailReceiver.main(MailReceiver.java:171) Sample code works with Suns mail.jar. Tested this code with a web application and a standalone client application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (GERONIMO-2679) ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar
[ http://issues.apache.org/jira/browse/GERONIMO-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rick McGuire resolved GERONIMO-2679. Resolution: Fixed Fix Version/s: 2.0-M2 Committed revision 491576. ArrayIndexOutOfBoundsException when getting Mails from Pop3-Account with geronimo-javamail_1.4_mail-1.0.jar --- Key: GERONIMO-2679 URL: http://issues.apache.org/jira/browse/GERONIMO-2679 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: mail Affects Versions: 2.0-M2 Reporter: Geist Alexander Assigned To: Rick McGuire Fix For: 2.0-M2 There are 2 messages in the pop3-account. Using the following code Store store = session.getStore(pop3); store.connect(popServer, 110, popUser, popKey); Folder folder = store.getFolder(INBOX); folder.open(Folder.READ_WRITE); Message message[] = folder.getMessages(); runs in this exception java.lang.ArrayIndexOutOfBoundsException: 2 = 2 at java.util.Vector.setElementAt(Vector.java:483) at org.apache.geronimo.javamail.store.pop3.POP3Folder.getMessage(POP3Folder.java:257) at javax.mail.Folder.getMessages(Folder.java:468) at javax.mail.Folder.getMessages(Folder.java:495) at keygen.main.MailReceiver.receive(MailReceiver.java:42) at keygen.main.MailReceiver.main(MailReceiver.java:171) Sample code works with Suns mail.jar. Tested this code with a web application and a standalone client application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (GERONIMO-2678) Exception parsing a XML with Digester
[ http://issues.apache.org/jira/browse/GERONIMO-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461621 ] David Jencks commented on GERONIMO-2678: It looks like Digester can't find the right classes. I think all that Geronimo can do is assure that the thread context classloader is correctly set to include all the classes in your web app together with the dependencies you declare in your geronimo plan. Can you: 1. find out what the TCCL is in your jsp page, either by debugging (perhaps in com.unizar.sql.DataSourceCollection) or by logging it. It should have a name that is recognizably associated with your web app. If this is not the classloader you find something may be wrong in geronimo. 2. Check that the TCCL can in fact load com.unizar.sql.DataSource. If it can't there is probably something wrong in how you assembled your web app. 3. Find out what classloader Digester is using to try to load com.unizar.sql.DataSource. If it's not the TCCL and there is no way to supply the correct classloader in code this might be considered a problem with Digester. I think you might have trimmed off some of the stack trace. If these suggestions don't help resolve the issue quickly please supply a more complete stack trace and the version of Digester you are using. In particular the trace from the underlying exception that the SaxException wraps would be very useful. Exception parsing a XML with Digester - Key: GERONIMO-2678 URL: http://issues.apache.org/jira/browse/GERONIMO-2678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.1.1 Environment: Windows XP SP2, Geronimo 1.1.1 with Tomcat Reporter: Sergio Montesa My web application, deploy in geronimo, parse with Digester the following XML: ?xml version=1.0 encoding=iso-8859-1? data-sources !-- JDBC -- data-source name=ing__yy schema=ingres connection-driver=ca.edbc.jdbc.EdbcDriver url=jdbc:edbc://host:1919/bdd;CURSOR=READONLY username=user password=passwd jndi= / /data-sources and generate this exception: java.lang.ClassNotFoundException: com.unizar.sql.DataSource in classloader geronimo/tomcat/1.1.1/car org.apache.commons.digester.Digester.createSAXException(Digester.java:2792) org.apache.commons.digester.Digester.createSAXException(Digester.java:2818) org.apache.commons.digester.Digester.startElement(Digester.java:1289) org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XMLParser.parse(Unknown Source) org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) org.apache.commons.digester.Digester.parse(Digester.java:1591) com.unizar.sql.DataSourceCollection.parse(Unknown Source) com.unizar.sql.DataSourceCollection.parse(Unknown Source) org.apache.jsp.benchXml_jsp._jspService(org.apache.jsp.benchXml_jsp:136) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Patches in RTC (Geronimo - 2007-01-01)
Geronimo - Monday, January 1, 2007 5 Patches in RTC [GERONIMO-2638] Improve ModuleBuilder and ConfigurationBuilder interfaces to replace use of JarFile - Assignee: Sachin Patel - Reporter: Sachin Patel - Created: Thu Dec 07 23:41:31 GMT 2006 - Updated: Mon Dec 11 16:21:45 GMT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMO-2638 [GERONIMO-2485] PersistenceUnitGBean needs a NamespaceDrivenDeployer - Assignee: David Jencks - Reporter: David Jencks - Created: Wed Oct 11 21:23:29 GMT 2006 - Updated: Thu Dec 07 20:28:27 GMT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMO-2485 [GERONIMO-1277] Change group-id to org.apache.geronimo - Assignee: Jason Dillon - Reporter: Dain Sundstrom - Created: Sat Dec 03 10:55:12 GMT 2005 - Updated: Tue Nov 07 23:57:44 GMT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMO-1277 [GERONIMO-2015] Let's replace JKS to PKCS12 key store type - Assignee: Unassigned - Reporter: Nikolay Chugunov - Created: Fri May 12 21:54:17 GMT 2006 - Updated: Wed Dec 06 06:57:11 GMT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMO-2015 [GERONIMODEVTOOLS-112] Loading deployment plan editor on empty file should auto-create plan - Assignee: Sachin Patel - Reporter: Sachin Patel - Created: Wed Oct 11 21:45:57 GMT 2006 - Updated: Wed Dec 06 14:11:15 GMT 2006 - Votes: 0 - http://issues.apache.org/jira/browse/GERONIMODEVTOOLS-112 NOTE: This email is generated and does not constitute and offical vote or vote result. All official voting is done on the dev list. If you do not see your issue here, click the Begin RTC Review link under the Available Workflow Actions of the JIRA page. If you do not see your vote here, click the Vote link under the Operations section of the JIRA page. *** ALL COMMUNITY MEMBERS ARE ENCOURAGED TO VOTE *** Template: http://svn.apache.org/repos/asf/geronimo/gbuild/jirareports/patchesInRtc.vm
[jira] Created: (GERONIMO-2680) mod_jk configfilegenerator produces unusable configentries
mod_jk configfilegenerator produces unusable configentries -- Key: GERONIMO-2680 URL: http://issues.apache.org/jira/browse/GERONIMO-2680 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Affects Versions: 2.0-M1 Environment: G 2.0 M1 Reporter: Tobias Strauß Priority: Trivial FIRST issue: instead of: JkMount /console-standard geronimo_ajp13 should be produced: JkMount /console-standard/* geronimo_ajp13 ... and so on. SECOND issue: instead of: worker.list=ajp13 worker.geronimo_ajp13.port=8009 worker.geronimo_ajp13.host=127.0.0.1 worker.geronimo_ajp13.type=ajp13 should be produced: worker.list=geronimo_ajp13 worker.geronimo_ajp13.port=8009 worker.geronimo_ajp13.host=127.0.0.1 worker.geronimo_ajp13.type=ajp13 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2681) IOException when reading content of a message
IOException when reading content of a message
-
Key: GERONIMO-2681
URL: http://issues.apache.org/jira/browse/GERONIMO-2681
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Affects Versions: 2.0-M1
Reporter: Geist Alexander
Reading a content from a simple text-message. Tests with another text-messege
returns an empty String.
Sample code:
Folder folder = store.getFolder(INBOX);
folder.open(Folder.READ_WRITE);
Message message[] = folder.getMessages();
for (int msgNum = 0; msgNum message.length; msgNum++) {
String text = (String)message[msgNum].getContent();
java.io.IOException: Underlying input stream returned zero bytes
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:268)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at sun.nio.cs.StreamDecoder.read0(StreamDecoder.java:107)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:93)
at java.io.InputStreamReader.read(InputStreamReader.java:151)
at
org.apache.geronimo.mail.handlers.TextHandler.getContent(TextHandler.java:107)
at
javax.activation.DataSourceDataContentHandler.getContent(DataHandler.java:774)
at javax.activation.DataHandler.getContent(DataHandler.java:521)
at javax.mail.internet.MimeMessage.getContent(MimeMessage.java:923)
at keygen.main.MailReceiver.receive(MailReceiver.java:49)
at keygen.main.MailReceiver.main(MailReceiver.java:173)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (GERONIMO-2682) Sending a message throws a SendFailedException
Sending a message throws a SendFailedException
--
Key: GERONIMO-2682
URL: http://issues.apache.org/jira/browse/GERONIMO-2682
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: mail
Affects Versions: 2.0-M1
Reporter: Geist Alexander
// Get system properties
Properties props = System.getProperties();
// Setup mail server
props.put(mail.smtp.host, Settings.smtpServer);
props.put(mail.imap.partialfetch, false);
props.put(mail.smtp.auth, true);
Authenticator auth = new Authenticator()
{
protected PasswordAuthentication getPasswordAuthentication()
{
return new PasswordAuthentication(Settings.user, Settings.key);
}
};
return Session.getDefaultInstance(props, auth);
The method was used to get the session. It works.
Next step is to build and to send the message.
// Define message
MimeMessage message = new MimeMessage(mailParam.getSession());
// Set the from address
message.setFrom(new InternetAddress(Settings.from));
// Empfänger
message.addRecipient(Message.RecipientType.TO, new
InternetAddress(mailParam.getMailAddress()));
// Set the subject
message.setSubject(Subject);
BodyPart messageBodyPart = new MimeBodyPart();
String text =
getEmailText(mailParam.getXmgKey(),mailParam.getXlgKey(), mailParam.getDate());
messageBodyPart.setContent(text, text/html);
Multipart multipart = new MimeMultipart();
multipart.addBodyPart(messageBodyPart);
// Put parts in message
message.setContent(multipart);
// Send message
Transport.send(message);
Transport.send(message) is throwing this Exception
javax.mail.SendFailedException: Send failure (javax.mail.MessagingException:
Connection error (java.net.ConnectException: Connection refused: connect))
at javax.mail.Transport.send(Transport.java:163)
at javax.mail.Transport.send(Transport.java:48)
at keygen.main.MailSender.sendMail(MailSender.java:44)
at keygen.main.MailSender.main(MailSender.java:112)
Caused by: javax.mail.MessagingException: Connection error
(java.net.ConnectException: Connection refused: connect)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:403)
at javax.mail.Service.connect(Service.java:254)
at javax.mail.Service.connect(Service.java:85)
at javax.mail.Service.connect(Service.java:70)
at javax.mail.Transport.send(Transport.java:94)
... 3 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.init(Socket.java:366)
at java.net.Socket.init(Socket.java:239)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.getConnectedSocket(SMTPTransport.java:1091)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.getConnection(SMTPTransport.java:851)
at
org.apache.geronimo.javamail.transport.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:380)
... 7 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [vote] Release geronimo-ejb_3.0_spec
On Dec 31, 2006, at 10:55 PM, Matt Hogstrom wrote: On Dec 31, 2006, at 10:54 AM, Kevan Miller wrote: On Dec 30, 2006, at 1:51 PM, Dain Sundstrom wrote: David is out of town but I think I can answer The previous release was only a milestone. These are final 1.0 jars that have been verified using the JEE 5 signature tests. If you want to know what has changed just run svn diff: Right, but I didn't ask a question. I stated that we ought to be identifying this information in the vote (or a previous discussion thread). All it takes is -- Testing of the EJB3 spec has identified signature problems in the existing 1.0-M1 release of the spec. I've fixed these problems and updated the version numbers of the specs that EJB3 is dependent on. I propose we release a final 1.0 version of EJB3. This way all voters (and non- voters) understand. I agree that the person proposing the vote should provide some information about what the changes are. It seems a little unreasonable to rely on an svn diff to document the changes. I don't think we ever done that before because because up til now everyone has just known what's changed. For this spec he did say Fixed, verified to be compliant and ready for release. which based on the diff sadly does describe what has changed for this release :) Anyway, if this is another requirement for a Geronimo release, I'm sure David will add it to the remaining specs he is releasing. BTW, David was out of town for the holiday weekend and I think he will be back tomorrow of the next day. Happy New Year, -dain
Re: [vote] Release geronimo-ejb_3.0_spec
I don't think we ever done that before because because up til now everyone has just known what's changed. For this spec he did say Fixed, verified to be compliant and ready for release. which based on the diff sadly does describe what has changed for this release :) Anyway, if this is another requirement for a Geronimo release, I'm sure David will add it to the remaining specs he is releasing. I agree that we don't want to get pedantic on the releases; that will just make life more difficult. I think there is a balance between Release this and I updated this that and the other thing and would like to get these out. We need to operate from a position of trust and respect. I think that we'll see both of these be executed with a short statement and an ok from the community. BTW, David was out of town for the holiday weekend and I think he will be back tomorrow of the next day. Happy New Year, And here we go... :) -dain Matt Hogstrom [EMAIL PROTECTED]
Re: Trunk build failure: NoClassDefFoundError: javax/xml/stream/XMLStreamException
Can we host a repo per release (1.2, 2.0, ...) on guild.org and only
check-in the repo contents in svn when a branch is created, so it gets
tagged with a release (milestone, beta, final, ...)? That would keep us
from bloating the storage space required in the repo due to binary diffs
of frequently changing artifacts.
Then, we could define m2 profiles to pull the artifacts from the gbuild
hosted repo or svn for released builds or from the public repos for
people working on new code before it is committed and the gbuild repo
updated.
-Donald
Jason Dillon wrote:
Thanks Kevan for looking into this.
This is one of the big issues I have with mvn and SNAPSHOT artifacts...
other peoples projects can break your projects build with out any
notice, no change log, and in many cases hours of someone debugging a
build to figure it out.
Perhaps we should simply not use *any* SNAPSHOT artifacts anymore? And
only use timestamp-build artifacts when non-released (snapshot deployed)
artifacts need to be consumed. The chances of those *just changing* and
breaking things are slimmer... though the chance of them disappearing
from a repo are much higher.
We could always fix that by finally setting up our own repo in svn,
maybe here for now:
https://svn.apache.org/repos/asf/geronimo/repository
Might hold anywhere from 50-100 megs of artifacts to support a Geronimo
Server build. And we could probably just start out with some of the
more risky artifacts, like this timestamp-build artifact (and move over
the local repos that are in the server/trunk build).
Though eventually it would be nice to simply be able to prime the local
repo and build offline:
svn co https://svn.apache.org/repos/asf/geronimo/repository
cp -r repository/* ~/.m2/repository
svn co https://svn.apache.org/repos/asf/geronimo/server/trunk server
cd server
mvn -o
Though I'm not sure if the current ASF httpd config for svn.apache.org
will handle this well. I know that its possible to setup httpd+svn to
behave optimally for this, just not sure that the ASF config asis will
or not.
--jason
On Dec 27, 2006, at 9:33 AM, Kevan Miller wrote:
On Dec 26, 2006, at 6:55 PM, Jason Dillon wrote:
I've run the server/trunk build twice on JDK 1.5 twice from a clean
repo, both times it fails here:
snip
[INFO]
[INFO] Building Geronimo :: Service :: Builder
[INFO]task-segment: [install]
[INFO]
[INFO] snapshot
org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for
updates from apache-snapshots
[INFO] snapshot
org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for
updates from codehaus-snapshots
[INFO] snapshot
org.codehaus.mojo:xmlbeans-maven-plugin:2.0.1-SNAPSHOT: checking for
updates from apache.snapshots
Downloading:
http://snapshots.repository.codehaus.org/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1-SNAPSHOT/xmlbeans-maven-plugin-2.0.1-20061223.141616-9.pom
5K downloaded
Downloading:
http://repository.codehaus.org/org/codehaus/mojo/mojo/11/mojo-11.pom
7K downloaded
Downloading:
http://snapshots.repository.codehaus.org/org/codehaus/mojo/xmlbeans-maven-plugin/2.0.1-SNAPSHOT/xmlbeans-maven-plugin-2.0.1-20061223.141616-9.jar
30K downloaded
[INFO] [tools:require-java-version {execution: validate-java-version}]
[INFO] [xmlbeans:xmlbeans {execution: default}]
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] javax/xml/stream/XMLStreamException
[INFO]
[INFO] Trace
java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2395)
at java.lang.Class.getMethod0(Class.java:2642)
at java.lang.Class.getMethod(Class.java:1579)
at org.apache.xmlbeans.XmlBeans.buildMethod(XmlBeans.java:174)
at org.apache.xmlbeans.XmlBeans.buildNodeMethod(XmlBeans.java:195)
at
org.apache.xmlbeans.XmlBeans.buildNodeToCursorMethod(XmlBeans.java:232)
at org.apache.xmlbeans.XmlBeans.(XmlBeans.java:131)
at
org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.(SchemaTypeLoaderBase.java:64)
at
org.apache.xmlbeans.impl.tool.SchemaCompiler.compile(SchemaCompiler.java:1063)
at
org.codehaus.mojo.xmlbeans.AbstractXmlBeansPlugin.execute(AbstractXmlBeansPlugin.java:270)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at
[jira] Commented: (GERONIMO-2678) Exception parsing a XML with Digester
[ http://issues.apache.org/jira/browse/GERONIMO-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461678 ] Sergio Montesa commented on GERONIMO-2678: -- But my web application is working -correctly- in Tomcat 5.5 and working in Geronimo 2.0M1 (not in Geronimo 1.2Beta). In addition, if I edit the Xml file : ?xml version=1.0 encoding=iso-8859-1? data-sources /data-sources then, the exception disappears. Exception parsing a XML with Digester - Key: GERONIMO-2678 URL: http://issues.apache.org/jira/browse/GERONIMO-2678 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Affects Versions: 1.1.1 Environment: Windows XP SP2, Geronimo 1.1.1 with Tomcat Reporter: Sergio Montesa My web application, deploy in geronimo, parse with Digester the following XML: ?xml version=1.0 encoding=iso-8859-1? data-sources !-- JDBC -- data-source name=ing__yy schema=ingres connection-driver=ca.edbc.jdbc.EdbcDriver url=jdbc:edbc://host:1919/bdd;CURSOR=READONLY username=user password=passwd jndi= / /data-sources and generate this exception: java.lang.ClassNotFoundException: com.unizar.sql.DataSource in classloader geronimo/tomcat/1.1.1/car org.apache.commons.digester.Digester.createSAXException(Digester.java:2792) org.apache.commons.digester.Digester.createSAXException(Digester.java:2818) org.apache.commons.digester.Digester.startElement(Digester.java:1289) org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) org.apache.xerces.parsers.XMLParser.parse(Unknown Source) org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) org.apache.commons.digester.Digester.parse(Digester.java:1591) com.unizar.sql.DataSourceCollection.parse(Unknown Source) com.unizar.sql.DataSourceCollection.parse(Unknown Source) org.apache.jsp.benchXml_jsp._jspService(org.apache.jsp.benchXml_jsp:136) org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264) javax.servlet.http.HttpServlet.service(HttpServlet.java:688) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
