You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by "Zakharov, Vasily M" <va...@intel.com> on 2007/11/14 04:50:11 UTC
RE: Deployer needs internet access?
David,
As far as I can see, it's fixed in OpenEJB 3.0 beta 2,
so the fix should make it to Geronimo 2.1, am I right?
Vasily
-----Original Message-----
From: David Blevins [mailto:david.blevins@visi.com]
Sent: Wednesday, October 03, 2007 3:15 AM
To: user@geronimo.apache.org
Subject: Re: Deployer needs internet access?
This looks like a bug. Filed a jira here: https://issues.apache.org/
jira/browse/OPENEJB-700
-David
On Sep 24, 2007, at 9:37 AM, Zakharov, Vasily M wrote:
> org.apache.openejb.OpenEJBException: Cannot unmarshall the
> ejb-jar.xml file:
> jar:file:/C:/VMZ/Temp/geronimo-deploymentUtil50850.jar!/META-INF/
> ejb-jar
> .xml: null
> at
> org.apache.openejb.config.ReadDescriptors.readEjbJar
> (ReadDescriptors.jav
> a:260)
> at
> org.apache.openejb.config.ReadDescriptors.deploy
> (ReadDescriptors.java:52
> )
> at
> org.apache.geronimo.openejb.deployment.EjbModuleBuilder.createModule
> (Ejb
> ModuleBuilder.java:237)
> ... 59 more
> Caused by: javax.xml.bind.UnmarshalException
> - with linked exception:
> [java.net.ConnectException: Connection timed out: connect]
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0
> (Unm
> arshallerImpl.java:196)
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal
> (Unma
> rshallerImpl.java:167)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal
> (AbstractUnmars
> hallerImpl.java:120)
> at
> javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal
> (AbstractUnmars
> hallerImpl.java:103)
> at
> org.apache.openejb.jee.JaxbJavaee.unmarshal(JaxbJavaee.java:103)
> at
> org.apache.openejb.config.ReadDescriptors.readEjbJar
> (ReadDescriptors.jav
> a:255)
> ... 61 more
> Caused by: java.net.ConnectException: Connection timed out: 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.Socket.connect(Socket.java:519)
> at java.net.Socket.connect(Socket.java:469)
> at sun.net.NetworkClient.doConnect(NetworkClient.java:157)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:382)
> at sun.net.www.http.HttpClient.openServer(HttpClient.java:509)
> at sun.net.www.http.HttpClient.<init>(HttpClient.java:231)
> at sun.net.www.http.HttpClient.New(HttpClient.java:304)
> at sun.net.www.http.HttpClient.New(HttpClient.java:316)
> at
> sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient
> (HttpURLConn
> ection.java:817)
> at
> sun.net.www.protocol.http.HttpURLConnection.plainConnect
> (HttpURLConnecti
> on.java:769)
> at
> sun.net.www.protocol.http.HttpURLConnection.connect
> (HttpURLConnection.ja
> va:694)
> at
> sun.net.www.protocol.http.HttpURLConnection.getInputStream
> (HttpURLConnec
> tion.java:938)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentE
> nt
> ity(XMLEntityManager.java:973)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity
> (XML
> EntityManager.java:905)
> at
> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntit
> y(
> XMLEntityManager.java:872)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSour
> ce
> (XMLDTDScannerImpl.java:282)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl
> $DTDDispat
> cher.dispatch(XMLDocumentScannerImpl.java:1021)
> at
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl
> .s
> canDocument(XMLDocumentFragmentScannerImpl.java:368)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML1
> 1Configuration.java:834)
> at
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse
> (XML1
> 1Configuration.java:764)
> at
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse
> (XMLParser.jav
> a:148)
> at
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse
> (Abstr
> actSAXParser.java:1242)
> at
> org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:333)
> at
> com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0
> (Unm
> arshallerImpl.java:194)
> ... 66 more
--------------------------------------------------------------------
Closed Joint Stock Company Intel A/O
Registered legal address: 125252, Moscow, Russian Federation,
Chapayevsky Per, 14.
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
Re: Deployer needs internet access?
Posted by Kevan Miller <ke...@gmail.com>.
On Nov 17, 2007, at 3:28 PM, Jacek Laskowski wrote:
> On Nov 17, 2007 8:29 PM, Kevan Miller <ke...@gmail.com> wrote:
>
>> Right. Just need to get OpenEJB to actually release beta-2.
>
> Unless the jars are not published, they should be already included in
> the latest builds of Geronimo, shouldn't it? That doesn't preclude
> openejb3 beta2 from being released though.
Right. We're currently picking up 3.0.0-SNAPSHOT. Vasily was asking
about a 2.1 "release". We'll need an OpenEJB release prior to a
Geronimo 2.1 release.
--kevan
Re: Deployer needs internet access?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Nov 17, 2007 8:29 PM, Kevan Miller <ke...@gmail.com> wrote:
> Right. Just need to get OpenEJB to actually release beta-2.
Unless the jars are not published, they should be already included in
the latest builds of Geronimo, shouldn't it? That doesn't preclude
openejb3 beta2 from being released though.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Deployer needs internet access?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On Nov 23, 2007 12:01 PM, Akram Ben Aissi <ak...@gmail.com> wrote:
> Otherwise, is there a workaround to deploy successfully event when offline
> (or behind a proxy) ?
> This is very very annoying :( .
> Any workaround would be greatly appreciated.
I'm not sure if it works or not, but I'd upgrade all the libs in
geronimo\repository\org\apache\openejb to the latest snapshot version
(published tomorrow evening CET). Do it for 2.0.2 where
openejb-3.0-beta-1 is used and for 2.1-SNAPSHOT with
openejb-3.0-snapshot. Very annoying, but worth to give it a try before
openejb-3.0-beta-2's on the shelves.
Jacek
--
Jacek Laskowski
http://www.JacekLaskowski.pl
Re: Deployer needs internet access?
Posted by Akram Ben Aissi <ak...@gmail.com>.
Kevan Miller wrote:
>
> Right. Just need to get OpenEJB to actually release beta-2.
> --kevan
>
Hello all,
Otherwise, is there a workaround to deploy successfully event when offline
(or behind a proxy) ?
This is very very annoying :( .
Any workaround would be greatly appreciated.
Akram
--
View this message in context: http://www.nabble.com/Deployer-needs-internet-access--tf4510229s134.html#a13910298
Sent from the Apache Geronimo - Users mailing list archive at Nabble.com.
Re: Deployer needs internet access?
Posted by Kevan Miller <ke...@gmail.com>.
On Nov 13, 2007, at 10:50 PM, Zakharov, Vasily M wrote:
> David,
>
> As far as I can see, it's fixed in OpenEJB 3.0 beta 2,
> so the fix should make it to Geronimo 2.1, am I right?
Right. Just need to get OpenEJB to actually release beta-2.
--kevan