Karaf shell still working after stopped geronimo server through GEP and error
happened when excute geronimo server related commands
---
Key:
[
https://issues.apache.org/jira/browse/GERONIMO-5674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Xiao updated GERONIMO-5674:
--
Attachment: dojo.7z
dojoOptmize.patch
1 The attach contains the readme file to
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacky Liu updated GERONIMODEVTOOLS-758:
---
Attachment: test-ejb2.jar
test-ejb.jar
Publishing one EJB
Publishing one EJB will cause another stopped EJB's starting
Key: GERONIMODEVTOOLS-758
URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-758
Project: Geronimo-Devtools
Hi Kevan,
Thanks for your response, you are right, the castor-1.0.5 is used by the
org\apache\geronimo\configs\webservices-common.
Can we overcome the jar issue by putting the castor-1.1 in the
repository.org.codehaus.castor/castor/1.1 and declare in the artifact alias
as
Geronimo Revision: 1130025 built with tests included
See the full build-0300.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-0300.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042059#comment-13042059
]
Yi Xiao commented on GERONIMODEVTOOLS-754:
--
I test under the same
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yi Xiao resolved GERONIMODEVTOOLS-754.
--
Resolution: Fixed
java.lang.NullPointerException: Could not publish to the
Hi Kevan,
With your suggestion to hide the castor, now it is working
dep:hidden-classes
dep:filterorg.exolab/dep:filter
dep:filterorg.castor/dep:filter
/dep:hidden-classes
/dep:environment
Instead of putting all the dependencies jar from the web-inf/lib to
repository folder
[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tina Li closed GERONIMODEVTOOLS-755.
Resolution: Cannot Reproduce
Fix Version/s: 3.0
Use the Gep version:Build
On May 31, 2011, at 1:44 AM, David Jencks wrote:
The new aries proxy code also seems to consume significantly more permgen
space. I didn't investigate in detail but a full server runs out of permgen
space around half way through starting with 128 MB permgen. My server
started OK with
The lock file in ActiveMQ is not referenced correctly
-
Key: GERONIMO-5987
URL: https://issues.apache.org/jira/browse/GERONIMO-5987
Project: Geronimo
Issue Type: Bug
Security Level:
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell E Glaue updated GERONIMO-5987:
--
Affects Version/s: 3.0-M2
3.0-M1
The lock file in ActiveMQ
Geronimo Revision: 1130142 built with tests included
See the full build-0900.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-0900.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test
According to my recent experience, permsize=256m is kind of small for 3.0,
though the server could start, but it will fail during application
deployment from admin console after.
Forrest
On Wed, Jun 1, 2011 at 9:05 PM, Kevan Miller kevan.mil...@gmail.com wrote:
On May 31, 2011, at 1:44 AM,
On Jun 1, 2011, at 12:10 PM, Forrest Xia wrote:
According to my recent experience, permsize=256m is kind of small for 3.0,
though the server could start, but it will fail during application deployment
from admin console after.
All depends on your application size, of course... I expect
[
https://issues.apache.org/jira/browse/GERONIMO-5987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Russell E Glaue updated GERONIMO-5987:
--
Description:
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
deploy:new-server-instance does not deploy a full new server instance
-
Key: GERONIMO-5988
URL: https://issues.apache.org/jira/browse/GERONIMO-5988
Project: Geronimo
Issue
This commit broke the build. See
http://ci.apache.org/builders/geronimo-server-trunk/builds/41
Can you fix the test errors?
--kevan
On May 30, 2011, at 9:50 AM, genspr...@apache.org wrote:
Author: genspring
Date: Mon May 30 13:50:57 2011
New Revision: 1129174
URL:
Geronimo Revision: 1130268 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-1500.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test
But first please explain why you think this change is correct. It looks wrong
to me, and I think the test was correct. Maybe i don't understand what the
test is doing, but I don't think libfolder/ is in the manifest classpath
being tested but it shows up in the results. Why should it?
CDI EAR deployment issue
Key: GERONIMO-5989
URL: https://issues.apache.org/jira/browse/GERONIMO-5989
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: deployment,
[
https://issues.apache.org/jira/browse/GERONIMO-5989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Blevins updated GERONIMO-5989:
Attachment: EnterpriseQualifierDefinitionTest.ear
As of OpenEJB/OpenWebBeans/XBean
Made great progress in CDI/EJB integration, but seems we have a general issue
with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
It looks like the deploy is successful but the EJB module doesn't start. No
errors in the log other than the webapp failing to start due to missing
Output a compound WSDL file for the queries from the clients
Key: GERONIMO-5990
URL: https://issues.apache.org/jira/browse/GERONIMO-5990
Project: Geronimo
Issue Type: New Feature
I'll take a look.
On Thu, Jun 2, 2011 at 8:27 AM, David Blevins david.blev...@gmail.comwrote:
Made great progress in CDI/EJB integration, but seems we have a general
issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
It looks like the deploy is successful but the EJB
Thanks, Shawn!
On Jun 1, 2011, at 7:02 PM, Shawn Jiang wrote:
I'll take a look.
On Thu, Jun 2, 2011 at 8:27 AM, David Blevins david.blev...@gmail.com wrote:
Made great progress in CDI/EJB integration, but seems we have a general issue
with deploying EARs the CDI TCK gives us so we aren't
On Wed, Jun 1, 2011 at 12:25 PM, David Jencks david_jen...@yahoo.comwrote:
On May 31, 2011, at 10:47 AM, Kevan Miller wrote:
On May 31, 2011, at 1:44 AM, David Jencks wrote:
Locally I now have a server that runs eba-with-isolation using aries
trunk and fixes a lot of the tck problems
Geronimo Revision: 1130367 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-2100.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test
It's quite tricky because the war and ejb module have the same name,
Hence, they have the same hashcode because we are returning
name.hashCode() in Module.hashCode().
r1130391 Change to moduleURI.hashCode() will fix this because the URI can
identify a module.It should be fixed, I will
Hi Forrest,
I've pushed today's source to people.apache.org. It compiles for me :-) I
just committed an update to OWB that makes it more compatible with aries
proxying/weaving so you may want to build owb also.
I'll probably be around on and off tonight so if you run into problems soon I
On Jun 1, 2011, at 11:14 PM, Shawn Jiang wrote:
It's quite tricky because the war and ejb module have the same name, Hence,
they have the same hashcode because we are returning name.hashCode() in
Module.hashCode().
r1130391 Change to moduleURI.hashCode() will fix this because the URI
The spec EE 8.3.1 does not specify if the classes in EJB module should be
visible for WAR. But the spec does say app should not depend on such EJB
and WEB module classloading relationship. I think the case is breaking the
rule.
Anyway, in geronimo impl, the content of ejb is visible to war
Geronimo Revision: 1130409 built with tests included
See the full build-0200.log file at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110602/build-0200.log
See the unit test reports at
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110602/unit-test-reports
On Jun 1, 2011, at 11:22 PM, David Jencks wrote:
Hi Forrest,
I've pushed today's source to people.apache.org. It compiles for me :-) I
just committed an update to OWB that makes it more compatible with aries
proxying/weaving so you may want to build owb also.
I'll probably be around
35 matches
Mail list logo